Definition (Hover Text)

gives a measure of efficiency of the development team in closing defects raised because of new functionalities within the iteration

Source Tools

Jira, Azure Boards

Graph type

Line

Filters

-

Hover Format on KPI

Sprint Name: <<Percentage Value>>

Closed Defects: <<Value>>

Total Defects : <<Value>>

Fields on Overlay

• Sprint Name

• Defect ID

• Issue Description

• Defects Removed

Business Logic

Calculation Formula

No. of defects in the iteration that are fixed/ Total no. of defects in a iteration

Trend

Higher the percentage, better is the ‘Quality’

Maturity Levels

M1 <25% 

M2 >=25-50% , 

M3 - >=50-75% , 

M4 - >=75-90%  , 

M5 - >=90%  

Instance level thresholds

Configurations

Processor Fields

NA

Mandatory fields

• Resolution type to be included

• Status to identify Rejected defects

• Status to identify completed issues

How to Validate KPI

Suggested ways of working

Sample JQLs

JQL query to get the defects found and fixed during a sprint: project = "Your Project Name" AND issuetype = Bug AND Sprint in closedSprints() AND status in (Done, Closed)

JQL query to get the total defects found during and after a sprint: project = "Your Project Name" AND issuetype = Bug AND (Sprint in closedSprints() OR createdDate > endOfSprint)

Benefits of KPI

How does the KPI help

The Defect Removal Efficiency KPI measures the effectiveness of the testing process in identifying and removing defects before they reach production. It helps teams improve the quality of the product, reduce the cost of fixing defects, and increase customer satisfaction by identifying areas for improvement in the testing process and ensuring that defects are caught early in the development cycle.