Skip to content
Resources > > How Agile should your Project be
How Agile should your Project be

How Agile should your Project be

How Agile should your Project be?
A Mathematician Derives the Answer


Advocates of agile development claim that agile software projects succeed more often than classic plan-driven projects. Unfortunately, attempts to validate this claim statistically are problematic, because “success” is not defined consistently across studies. This paper addresses the question through a mathematical analysis of these projects. We model agile and plan-driven software projects with identical requirements, and show how they are affected by the same set of unanticipated problems. We find that that the agile project provides clear benefits for return-on-investment and risk reduction, compared to the plan-driven project, when uncertainty is high. When uncertainty is low, plan-driven projects are more cost-effective. Finally, we provide criteria for choosing effective process types.


  1. Background
  2. Common Problems in Software Projects
  3. Statistics on Success Rates for Plan-Driven and Agile Projects
    1. Scott Ambler, 2007
    2. QSM Associates, 2008
    3. Conclusions from the Surveys
  4. Key Differences between Agile and Plan-Driven Strategies
  5. Gedanken Experiment
    1. Project Description
    2. Uncertainty
    3. The Plan-Driven Project
    4. The Agile Project
  6. Comparison
    1. Comparison of Planned Project Schedules
    2. Comparison of Actual Project Schedules
    3. Comparison of Project Results
  7. Lessons Learned from the Gedanken Experiment
    1. The Financial Impact of Uncertainty
    2. Risk
    3. Value Delivery and ROI versus Time
  8. Guidance for Selecting Processes
    1. Common Processes
    2. Selection Criteria
    3. Decision Matrix for Process Types
  9. Conclusion
  10. Appendix: Task Durations for the Plan-Driven and Agile Schedules


Download the White Paper

Some of the images used were designed by