Agile Agenda Philosophy
Agile Agenda is built upon a few ideas about what a scheduling package should try to accomplish. Some of those concepts are discussed below.
Durations & 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, AgileAgenda asks for durations & priorities, and then it'll figure out the start & end dates for you.
As you enter more detailed information (vacations, dependencies, etc.) those start & 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 fairly 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 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. The AgileAgenda.com website allows you to post a schedule for your entire team to view. The software also allows you to export PDF files that you can print or digitally share. While still in it's early stages there is also a "developer's client" which allows your resources to subscribe to your schedule and view their own individual tasks. We're also working on a full third party API to integrate other applications into the AgileAgenda.com web service.Not everyone works on a PC
AgileAgenda currently runs on Windows and OSX with plans for a Linux version as well. Why should you have to keep a PC around just to maintain a schedule?[Back To Help Contents]