Defect Status By Priority [Build]

Software testing 101

Defect Status By Priority [Build]

What is “Defect Status By Priority”?

The  “Defect Status By Priority” DevOps quality metric tracks the status (open, closed, etc.,) of the defects in each defect priority category. A defect’s priority indicates how urgently it should be fixed. It is commonly used in concert with severity (e.g., a high-severity defect would likely be assigned a high priority). 

How “Defect Status By Priority” Ranks vs. Other Quality Metrics

In new Forrester research on DevOps quality metrics, DevOps leaders ranked “Defect Status By Priority” as the #14 most valued build quality metric. Of the 23% of DevOps leaders who measured this metric, 49% 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 Priority” 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.