Definition (Hover Text)

measures ratio of the total number of defects (bugs) linked to closed stories and the size of a closed stories

Source Tools

Jira, Azure

Graph type

Line

Filters

<None>

Hover Format on KPI

Sprint Name: <<Percentage Value>>

Defects: <<Value>>

Total Size of Closed stories : <<Value>>

Fields on Overlay

1. Sprint Name

2. Story ID

3. Issue Description

4. Linked Defects to Story

5. Size(story point/hours)

Business Logic

Calculation Formula

No. of defects tagged to all stories closed in a sprint/ Total size of stories closed in the iteration

Trend

Positive trend indication - Decrease

Maturity Levels

M1: > 90%

M2: 60% -90%

M3: 25%-60%

M4: 10-25%

M5: <10%

Instance level thresholds

Configurations

Processor Fields

NA

KPI Specific fields

• Issue Type Mapping

  • Issue Type which will have Linked defects eg; Story Enabler Story, Tech Story

• WorkFlow Status Mapping

  • Status consider for Issue closure eg; Closed, Done, Ready for Delivery

How to Validate KPI

Suggested ways of working

Sample JQLs

project in ("XYZ") and component =ABC and type in (Defect) and issueFunction in linkedIssuesOf("type in (Story) AND sprint in(406)")

Benefits of KPI

How does the KPI help

The Defect Density KPI measures the number of defects per unit of code or product, helping teams improve product quality, reduce costs, and increase customer satisfaction by identifying areas for improvement and prioritizing testing efforts.