Main Menu
Home / Project Management / Risk Management / Why “Cost Per Defect” is Harmful for Software Quality

Why “Cost Per Defect” is Harmful for Software Quality

From Namcook Analytics: 

The oldest metric for software quality economic study is that of “cost per defect.” While there may be earlier uses, the metric was certainly used within IBM by the late 1960′s for software; and probably as early as 1950′s for hardware.

For software the cost-per-defect-metric has developed into an urban legend, with hundreds of assertions in the literature that early defect detection and removal is cheaper than late defect detection and removal by more than 100 to 1. This is true mathematically, but there is an economic problem with the cost per defect calculations that will be discussed in the article.

As will be shown, cost per defect is always cheapest where the greatest volumes of defects are found. More importantly the cost-per-defect metric tends to ignore the major economic value of improved quality: shorter development schedules and reduced development costs outside of explicit defect repairs.

Read the full PDF here:

About Matthew Kabik

Matthew Kabik is the former Editor of Computer Aid's Accelerating IT Success. He worked at Computer Aid, Inc. from 2008 to 2014 in the Harrisburg offices, where he was a copywriter, swordsman, social media consultant, and trainer before moving into editorial.

Check Also

Conduct an Unshakeable SWOT Analysis in 2 Hours or Under

Where risk and opportunity are concerned, the SWOT framework is one of the most versatile …

Leave a Reply

Your email address will not be published. Required fields are marked *