Agile Agenda Philosophy

Here at AgileAgenda, we hate most project scheduling solutions out there. They take too much of a managers time to create a schedule and keep it current. We believe scheduling software should make the computer do the hard work and let your schedule adapt to real world changes as you work on the project.

Target Audience

This product is for people who think of a project in terms of tasks, how long those tasks take, and what resources should perform those tasks. It can be used for any size project. We've successfully used this program internally and have found the "sweet spot" to be projects ranging from 3 months to 2 years with 2-10 resources.

Durations and Priorities, not Start and End

Figuring out the start and end dates of tasks is a time consuming process to go through. What's worse is that that slight changes in your schedule can cause every single task to move. To make that easy, Agile Agenda asks for durations and priorities, and then it'll figure out the start and end dates for you.

As you enter more detailed information (vacations, dependencies, etc.) those start and end dates become more accurate. The more accurate your facts, the more accurate the estimate will be. You only have to think about the project-specific pieces and not about the scheduling-specific pieces.

Schedules Constantly Change

Nobody has perfect knowledge of how long a project will take before it's completed. In many projects scope, resource availability, and task estimates all change frequently. Agile Agenda wants to make it as easy as possible to make those changes without going back and reworking unrelated things. For instance, if an employee decides to take a vacation, you should only have to enter in that vacation and not have to worry about how that affects other areas such as tasks, milestones, or the project completion date. The software should take as much information about a project as you can give and give a best guess as to when things will be completed.

"Today" is important

Today's date can tell us a lot about a project. If a task should have been done by "today" and it's not, that task is late. If a project shouldn't be done today and it is marked as such then that task is early. Agile Agenda understands both of those and will automatically mark tasks as early or late depending on their status. Late tasks will hold up other tasks and push completion dates further into the future. Early tasks won't block other tasks and will move completion dates closer to today.

Sharing data should be easy

Everyone on a project should have access to view the schedule. They shouldn't have to download special software to view it.

For the standard edition, the AgileAgenda.com website allows you to post a schedule for your entire team to view. In the Basecamp edition, the sharing is built-in with your Basecamp account. Both editions let you export PDF files that you can print or digitally share.

Not everyone works on a PC

Agile Agenda currently runs on Windows and OSX and Linux as well. Why should you have to keep a PC around just to maintain a schedule?

Who's using it?

We've sold copies to both domestic and international companies and a couple of government agencies. Since we're software developers, we tend to think in those terms, but Agile Agenda is general enough to be used in a wide variety of projects.