2. Software Development Survey Data
o 31% of software development projects are cancelled
o 75% of software development projects considered fail by those
who initiated
o 66% of the projects do not meet the needs of users or have to
rewrite
3. Why Waterfall Not
o 82% of Projects practice waterfall practices as their primary
reason of failure
o In waterfall only 10% of the code developed was actually
utilized and rest all was the wasted effort
o One in every two projects exceeds its budget by (200%) 2
o Most projects face the “Deadline Rush” and “Features Cut”
4. Why Agile
o According to the Jan 2012 survey by PM Network Magazine,
90% of Software Project Managers that were interviewed said,
they were using some form of Agile. 90% (4000 out of 4700)
o Gartner: 80% of Software development projects would use
Agile by the end of 2012
o 74% of IT professionals surveyed had practices Agile in some
form or other
5. Why Agile
o Data from 15183 respondents worldwide suggests consensus
on Agile compared with Traditional (companies involved in this
survey are shine, Agile Journal, Microsoft, Amby Soft, IT Agile
and Version One)
o 67% more Productivity
o 65% more Quality
o 49% better on cost
o Use of Agile has been tripled from Dec 2008 to May 2011
6. Why Agile
o Waterfall vs. Agile
Waterfall
Failed 29%
Success 14%
Challenged 57%
Agile
Failed 9%
Success 42%
Challenged 49%
o In terms of success there is an improvement of 200% in case
of Agile practices, that’s why industry is tilting towards Agile
o In waterfall code is not shippable until the end but in Agile
code is always shippable
7. Why Agile
o Agile deliver value sooner, gives higher ROI, better application
& interfaces
o team is given freedom to make decisions and respond freely
to changes
o Lack of emphasis on designing and documentations as in Agile
projects documentation should be bare-sufficient
o Agile teams escalate fewer issues than waterfall team
o Requires senior developers who have skills to adapt
o Agile is creating Innovative Products
o Agile is a combination of “People Skills” and “Process Skills”