Defect Status by Severity [Build]

Software Testing 101

Defect Status by Severity [Build]

What is “Defect Status by Severity”?

The  “Defect Status by Severity” DevOps quality metric tracks how the number of reported defects fall into each severity category. Defect severity categories can be created and defined according to a team’s or organization’s custom scale. The severity indicates how much damage the defect is expected to cause.  

How “Defect Status by Severity” Ranks vs. Other DevOps Quality Metrics

In new Forrester research on DevOps quality metrics, DevOps leaders ranked “Defect Status by Severity” as the #8 most valued build quality metric. Of the 36% of DevOps leaders who measured this metric, 56% of them ranked it as one of their most valuable DevOps quality metrics. This metric was not found to be a “DevOps Differentiator” (DevOps experts/leaders measured it significantly more than DevOps laggards did).

Here‘s a quick look at how “Defect Status by Severity” is positioned vs. other Build Metrics—based on the raw data collected from DevOps experts. “DevOps Differentiators” are highlighted in green.

These findings are expanded upon in the new ebook: Forrester Research on DevOps Quality Metrics that Matter: 75 Common Metrics—Ranked by Industry Experts.