How much does an agile project management software differ from a traditional project management software? On short: pretty much. But on the other side both types of products have many things in common.
Many say that agile is not a project management methodology but rather a product development methodology. But in many cases the companies prefer to treat the development as a project and hence the notion of agile project management. Now the agile and traditional approaches are totally different so the first thought would be that the software used to manage each type of projects to be different. The idea is that agile PM is not a method per se, but rather an umbrella term for different processes. In turn, agile processes are very different among them.
In Scrum there are small teams, usually collocated, no project manager, and very often there is no need for a software for the managing the project. The team is self organizing, team members are doing daily meetings, and the project is split in iterations that take maximum one month. At the end of each iteration it is decided the next one and so on… No one wants to loose time by updating a plan that keeps changing or to monitor the daily progress of the team with a project scheduling tool.
In other agile processes the iterations take longer but the main idea is that the project plan, the requirements and the product specifications are subject to change. So a traditional project management software does not solve these needs. Indeed it is necessary to have a monitoring process for the project and the team, a system for client communication etc. but due to the dynamic nature of the processes there is no needs to have fancy or complicated features. An agile product should be light in functionality, easy to use, easy to access and highly portable. (more…)