Agile Practices with the Highest Return on Investment
Return on Investment (ROI) is defined as the amount of money gained or lost on an investment relative to the amount of money invested. ROI expected is a very important deciding factor in adopting a particular technique of software development.
- Agile's potential to deliver superior Return on Investment (ROI)
- Agile's ability to drive down Total Cost of Ownership (TCO)
- The importance of trust in making the business case for Agile
According to Roger, focusing on superior ROI delivered by Agile gives an opportunity to take the decision making to the next level. Discussion can move from the subjective ("things are better with Agile") to the objective ("Agile increases ROI by x%").
Roger evaluated the ROI on the basis of two variables namely Cost and Return. The study evaluates the results of cost reduction and increase in returns with Agile projects versus plan-drive approaches. It provided the following results,
ROI variation 1: Cost reduction, constant return: For the same return and just focusing on reducing the cost, Agile boosts efficiency and has an advantage of 141% over plan driven approach.
ROI variation 2: Constant cost, increased return: With the same cost Agile provides higher returns with its customer focus. Agile has an advantage of 63% over plan driven approach.
ROI variation 3: Cost reduction, increased return: Taking the advantages of both the above variations. Lower costs and higher returns lead to forward leaning projects and here Agile has an advantage of 205% over traditional plan driven approaches.
Roger also studies the TCO and importance of trust with the findings favoring Agile over traditional approaches.
So given that Agile results in favorable ROI what are the most important Agile practices which would result in highest ROI?
In a post on Agile Advice, Mishkin Berteig, mentioned three practices which are a part of XP and Scrum, however, for following these practices a team does not need to be following XP or Scrum. Mishkin mentions them as inexpensive practices with a high ROI. The practices mentioned are
A proper team room
This is astonishing: you can expect a 60% boost in team productivity from this single practice! The cost of re-stacking your cubes or office spaces is trivial compared to the benefits. If you are going to do this, do it right!
Mishkin mentioned some tips on having a proper team room on Agile Advice.
Any software development projects use iterations that are two weeks long or even a month long. I strongly recommend iterations that are only one week long. Again, the benefits are incredible: your team will move through the stages of team development (forming, storming, norming and performing) much more quickly than with longer iterations or no iterations… thus leading to high productivity much sooner.
Mishkin acknowledged that short iterations lead to some kind of pressure but given that every iteration is leading to valuable, working software the pressure is not demoralizing but it in fact motivates.
Test Driven Development
Mishkin mentioned that the gains can be substantial when high speed of development is done with high quality development. TDD results in doing higher quality development. He added,
I have seen teams doing this that reduce defect rates to 5% (or less!) of what they once were prior to test driven development… while at the same time delivering projects faster than expected.
Mishkin suggested that a team who follows the above 3 practices can easily double their productivity if not more. According to him,
For a team of 5 people working on a 100 day project this amounts to shortening the project to 50 days (save $200,000) or get twice as much work done.
As suggested in the study, it is easy to see that Agile delivers a higher ROI as compared to traditional approaches. For getting the highest ROI a team might not need to follow XP and Scrum to the core, they could start with a select set of practices and see the benefits.
Show me the data
J. B. Rainsberger
Mishkin suggested that a team who follows the above 3 practices can easily double their productivity if not more.
I find it pretty irresponsible to make this claim without substantiating it at all. I happen to believe in the claim, but I wouldn't make the claim in public without something to point to. Mishkin? Show us the data.
Re: Show me the data
Delivering Performance Under Schedule and Resource Pressure: Lessons Learned at Google and Microsoft
Ivan Filho Mar 06, 2014
Andrew Stellman Mar 06, 2014