Agile Management or Agile Project Management is an iterative method of determining Requirements

for Software and for delivering projects in a highly flexible and interactive manner. It requires empowered
individuals from the relevant business, with supplier and customer input. There are also links to Lean
techniques and 6 Sigma. Agile techniques are best used in small-scale projects or on elements of a wider
programme of work.

Agile techniques may also be called Extreme Project Management. It is a variant of iterative life
cycle[1] where deliverables are submitted in stages. One difference between Agile and iterative
development is that the delivery time in Agile is in weeks rather than months. Since Agile Management
derives from Agile software development, it follows the same standards defined in the Agile
Manifesto when it comes to collaboration and documentation. Several software methods derive from
Agile, including Scrum and Extreme Programming.

The Agile Project Leadership Network[2] provides a community of practice for those using Agile methods,
with international conferences and online forums. Their Declaration of Interdependence[3] extends the
Agile Manifesto[4] further into the value stream and emphasises the collaborative, whole-business nature
of this work.

[edit]Comparison with Traditional or "Waterfall" Project Management

Waterfall, as a Project Management methodology, has been criticized for not being able to cope with
constant changes in software projects. The iterative nature of Agile makes it an excellent alternative when
it comes to managing software projects.

Agile, however, has its disadvantages. Many believe that it doesn't scale well, hence large software
projects are still being conducted in Waterfall. Additionally, since the strength and usefulness of Agile are
both exhibited in projects with frequent changes, it does not offer any advantage over Waterfall when it
comes to classical projects where requirements are nearly always constant and unknowns are rare, such
as construction projects.

To explore the differences between traditional PMI style project management and the Agile approach, the
book by Sliger and Broderick[5] is useful. It can also assist those in transition to translate traditional issues
and skillsets into this rather different paradigm of software development. (Note that the PMI's "Project
Management Body of Knowledge" or PMBOK now also includes agile methods).

Here is a summary and comparison of these and other styles of Project Management.