Agile management: Difference between revisions

Content deleted Content added

Inline

Revision as of 17:51, 10 January 2012

Agile management or agile project management is a whack, iterative method of determining requirements for engineering and information technology development projects in a highly flexible and interactive manner, for example agile software development. It requires empowered individuals from the relevant business, with supplier and customer input.^{[citation needed]} There are also links to lean techniques and Six Sigma.^{[citation needed]} Agile techniques are best used in small-scale projects or on elements of a wider programme of work, or on projects that are too complex for the customer to understand and specify before testing prototypes.^{[citation needed]}

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.

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, and with the inability of customers to specify adequate requirements before they have tried prototypes. Also, the huge overhead of specifying requirements before starting the actual development may cause long delays of a project. The iterative nature of agile makes it an excellent alternative when it comes to managing development projects, especially software projects.^{[citation needed]}

Agile, however, has its disadvantages. Many believe that it doesn't scale well, hence large software projects are still being conducted in Waterfall.^{[citation needed]} 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.^{[citation needed]}

References

^ ExecutiveBrief, Which Life Cycle Is Best For Your Project?, PM Hut. Accessed 23. Oct 2009.
^ Agile Project Leadership Network (APLN)
^ Agile Project Leadership Network}'s [http://pmdoi.org/ Declaration of Interdependence
^ Agile Manifesto

This software-engineering-related article is a stub. You can help Wikipedia by expanding it.

[1] ExecutiveBrief, Which Life Cycle Is Best For Your Project?, PM Hut. Accessed 23. Oct 2009.

[2] Agile Project Leadership Network (APLN)

[3] Agile Project Leadership Network}'s [http://pmdoi.org/ Declaration of Interdependence

[4] Agile Manifesto

[1]

[2]

[3]

[4]

@@ Line 1: / Line 1: @@
 {{Context|date=October 2009}}
-'''Agile management''' or '''agile project management''' is an iterative method of determining requirements for engineering and information technology development projects in a highly flexible and interactive manner, for example [[agile software development]]. It requires empowered individuals from the relevant business, with supplier and customer input.{{Citation needed|date=April 2011}} There are also links to [[lean project management|lean techniques]] and [[Six Sigma]].{{Citation needed|date=April 2011}} Agile techniques are best used in small-scale projects or on elements of a wider programme of work, or on projects that are too complex for the customer to understand and specify before testing prototypes.{{Citation needed|date=April 2011}}
+'''Agile management''' or '''agile project management''' is a whack, iterative method of determining requirements for engineering and information technology development projects in a highly flexible and interactive manner, for example [[agile software development]]. It requires empowered individuals from the relevant business, with supplier and customer input.{{Citation needed|date=April 2011}} There are also links to [[lean project management|lean techniques]] and [[Six Sigma]].{{Citation needed|date=April 2011}} Agile techniques are best used in small-scale projects or on elements of a wider programme of work, or on projects that are too complex for the customer to understand and specify before testing prototypes.{{Citation needed|date=April 2011}}
 Agile techniques may also be called [[extreme project management]]. It is a variant of [[iterative and incremental development|iterative life cycle]]<ref> ExecutiveBrief, [http://www.pmhut.com/which-life-cycle-is-best-for-your-project Which Life Cycle Is Best For Your Project?], PM Hut. Accessed 23. Oct 2009.</ref> 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 software development|agile manifesto]] when it comes to collaboration and documentation. Several software methods derive from agile, including [[Scrum (development)|scrum]] and [[extreme programming]].