Definition (Hover Text)

The Defect Rejection Rate KPI measures how effective the effectiveness of testing team is by tracking the percentage of defects that are rejected during an iteration.

Source Tools

Jira, Azure Boards

Graph type

Line Chart

Filters

-

Hover Format on KPI

Sprint Name: <<Percentage Value>>

Rejected Defects: <<Value>>

Total Defects : <<Value>>

Fields on Overlay

Sprint Name

Defect ID

Issue Description

Defects Rejected

Business Logic

Calculation Formula

Maturity Levels

No. of defects tagged to stories in the iteration that are rejected / Total no. of defects tagged to stories in a iteration

Trend

Lesser the percentage, better is the ‘Quality’

1. Numerator :

   • This is the number of defects that were tagged to stories in the iteration but were later rejected (i.e., deemed not valid defects).

2. Denominator :

   • This is the total number of defects that were tagged to stories in the same iteration.

Formula:

Imagine your team tagged 50 defects to stories in an iteration, but 10 of these defects were rejected. The Defect Rejection Rate would be:

Defect Rejection Rate =10 / 50 ​= 0.2 or 20%
This means 20% of the reported defects were rejected, indicating areas where the testing process can be improved.

Trend

A lower Defect Rejection Rate indicates better quality, as it means fewer defects are being incorrectly reported and then rejected.

Maturity Levels

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

M1 - >=75%  ,

M2 - >=50-75%  , 

M3 - >=30-50% , 

M4 >=10-30% , 

M5 <10% 

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 created during a sprint: project = "Your Project Name" AND issuetype = Bug AND Sprint in openSprints()

JQL query to get the defects rejected during a sprint: project = "Your Project Name" AND issuetype = Bug AND Sprint in openSprints() AND status changed to Rejected

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

How does the KPI help

The Defect Rejection Rate KPI measures the effectiveness of the testing process in identifying and reporting defects, with a high rate indicating a robust testing process that leads to improved product quality, reduced costs, and increased customer satisfactionQuality Measurement

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

Predictability

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

Cost Reduction

Reducing the defect injection rate 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.