If you need to decide how to proceed in a project, the book “Going Agile – Project Management Practices” starts with a guidance on if and how to move over to an agile methodology. The first two chapters explain what it means what changes for which projects agile practices are applicable. Even more, the benefits or failures are plausibly illustrated through many survey results and business cases. The book explains in detail how to lead over to agile project practices. Furthermore, there are choices between, agile versus – traditional methodologies, making traditional projects agile, de-risking agile projects, or selecting the right agile methodology.
Agile Traditional
|
|
What does it mean? With Agile methodologies there is a continuous cycle of inspecting the process for correct output and operations adapting the process as needed. There are more than 12 agile methodologies. How?
|
What does it mean? According to Lindvall et al. (2002), plan-driven methods are those in which work begins with the elicitation and documentation of a complete set of requirements, followed by architectural and high-level design development and inspection. Waterfall and spiral methodologies are plan-driven methods (or traditional methodologies) |
For which projects is it applicable?
|
|
Agile… if
|
Traditional …. if
|
Benefits Failures
|
|
What are the benefits of going agile? Survey results illustrate benefits of agile
|
|
Agile processes are recommended within the top ten success factors for projects (Chaos Report of The Standish Group 2012) through the following improvements:
Agile projects benefit directly performance, output and outcome, indirectly organizational impacts:
The result is higher ROI and stakeholder value. (survey and study examples of PMI 2012, Scott Ambler 2011, the Cutter Consortium 2008, VersionOne 2012, Microsoft 2006, Salesforce 2007, Dr. David F. Rico 2008) |
In general a project never delivering a solution fails. Agile projects do not fail more than others. Reasons for agile project failures:
|