It’s All About Numbers – Business analysis value and the Price of BA Mistakes

Business analysis value and the price of mistakes

Business analysis value is demonstrated in the table below. It shows the relative expense of fixing defects depending on when they’re introduced and when they’re found (including Requirements stage).

Time detected

Time introduced

Requirements Architecture Construction Testing Post-Release
Requirements 1 3 5-10 10 10-100
Architecture 1 10 15 25-100
Construction 1 10 10-25

 

This table should be read the following way: a mistake introduced in Requirements costs to fix, for example, 1000$ during the Requirements stage; fixing the same mistake may result in 3000$ during Architecture stage; during Construction – from 5000$ to 10000$; and after the Release – from 10000$ up to 100000$!

To learn more about how poor requrements effect project costs/success please read the Part 2 of the article.

Note: the data is adapted by the author of the source material (see the References below) based on the following works: : “Design and Code Inspections to Reduce Errors in Program Development” (Fagan 1976), Software Defect Removal (Dunn 1984), “Software Process Improvement at Hughes Aircraft” (Humphrey, Snyder, and Willis 1991), “Calculating the Return on Investment from More Effective Requirements Management” (Leffingwell 1997), “Hughes Aircraft’s Widespread Deployment of a Continuously Improving Software Process” (Willis et al. 1998), “An Economic Release Decision Model: Insights into Software Project Management” (Grady 1999), “What We Have Learned About Fighting Defects” (Shull et al. 2002), and Balancing Agility and Discipline: A Guide for the Perplexed (Boehm and Turner 2004).

References: McConnell, Steve, 2012: Code Complete.

Author: Veronika Baeva, see original resource in Russian.

Leave a Reply

Your email address will not be published.