The term "agile project management" applies in projects where project management is very dynamic (responsive). In agile software projects it is typical, that there's only a high level specification of requirements at the beginning of a project; detailed requirements are only developed in the course of a project. The detailed specification is done in so-called iteration cycles, and the result of each iteration cycle is a product increment. This iterative approach allows for an ongoing integration of new / adapted requirements and the early consideration of user feedback for software products. In long-term development projects, this method allows technical innovations to be taken into account during the course of the project, and also enables fast product cycles.

There is, however, no uniform understanding / definition of "agile project management". Highly structured processes with daily monitoring are considered "agile project management" as well as largely unplanned work on a task. A popular variant of "agile project management" is SCRUM, another variant is DSDM (Dynamic Systems Development Method). It is often emphasized that agile projects are characterized by collaboration and by assigning special importance to the individual in the team, while processes and tools are of secondary importance. In this sense, all methods of agile project management can be traced back to some basic principles, which are formulated in the 2001 published Agile Manifesto: Individuals and interactions over processes and tools; Working software over comprehensive documentation; Customer collaboration over contract negotiation; Responding to change over following a plan.


The author is a manager in the software industry with international expertise: Authorized officer at one of the large consulting firms - Responsible for setting up an IT development center at the Bangalore offshore location - Director M&A at a software company in Berlin.