Page Comparison

Definition (Hover Text)

measures the effectiveness of testing team

Source Tools

Jira, Azure Boards

Graph type

Line

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

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’

Maturity Levels

M1 - >=75%  ,

M2 - >=50-75%  , 

M3 - >=30-50% , 

M4 >=10-30% , 

M5 <10% 

Instance level thresholds

Configurations

Processor Fields

NA

Mandayory fields

• Workflow Status Mapping

  • Resolution type to be included eg; Invalid , Duplicate

  • Status to identify Rejected defects  eg; Rejected

  • Status to identify completed issues

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

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 satisfaction.