Definition (Hover Text)

The Defect Removal Efficiency (DRE) KPI measures how effectively the development team is at fixing defects that arise from new functionalities within an iteration.

Source Tools

Jira, Azure Boards

Graph type

Line Chart

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

1. Numerator:

   • This is the number of defects that were identified and fixed within the iteration.

2. Denominator :

   • This is the total number of defects that were identified in the iteration, regardless of whether they were fixed or not.

   • Formula:

     Imagine your team identified 20 defects in an iteration and managed to fix 18 of them. The DRE would be:

     DRE=18 / 20 ​=0.9 or 90%

Trend

A higher DRE percentage indicates better quality, as it means more defects are being fixed within the same iteration they were found

Maturity Levels

DRE maturity is assessed by averaging data from the last 5 sprints. This helps in understanding the stability and improvement over time.

M1 <25% 

M2 >=25-50% , 

M3 - >=50-75% , 

M4 - >=75-90%  , 

M5 - >=90%  

Instance level thresholds

Target KPI Value denotes the bare minimum a project should maintain for a KPI.

Global Configurations- (Field Mapping)

Processor Fields

Whenever we update the defect mapping and issue type mapping, whether we add or remove any issue type, we must run the processor. This is necessary to show the changes in the KPI.

Defect Mapping :

Mandatory fields

Project Settings

1. Navigate to Project Settings: Start by going to the Project Settings in your application.

2. Access the Mapping Section: Within Project Settings, find and click on the Mapping option.

3. Mandatory Field: In the Mapping section, you’ll find the Mandatory Field. This is where you’ll configure the necessary global mapping fields.

4. Configure the Fields:

Defect Mapping :

• Issue Type to identify Defect - all the issue type that signify defect

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)

Best Practices

Automate Testing

Implement automated testing (unit, integration, and end-to-end tests) to catch defects early in the development process.

Pair Programming

Implement pair programming to increase code quality and reduce the likelihood of defects being introduced.

Adopt TDD/BDD

Use Test-Driven Development (TDD) or Behavior-Driven Development (BDD) methodologies to write tests before code, ensuring that functionality is well-defined and tested from the start.

Use Static Analysis Tools

Implement static code analysis tools to automatically check code for potential defects and enforce coding standards.

Benefits of KPI

Quality Measurement

It helps in measuring the quality of the code being produced and identifying areas where improvements are needed.

Predictability

Understanding the defect removal efficiency can help in forecasting the amount of rework required and in planning more accurately.

Cost Reduction

Reducing the defect removal efficiency can lead to lower costs associated with fixing bugs, especially those found later in the development cycle or after release.

Process Improvement

By tracking this metric, teams can identify stages in the development process where defects are commonly introduced and take steps to improve those stages.