Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Overview

Definition (Hover Text)

measures the percentage of defects leaked from the current testing stage to the subsequent stage

Source Tools

Jira, Azure Boards

Graph type

Line

Filters

-

Hover Format on KPI

Sprint Name: <<Percentage Value>>

Escaped Defects: <<Value>>

Total Defects : <<Value>>

Fields on Overlay

  • Sprint Name

  • Defect ID

  • Issue Description

  • Escaped Defect

Business Logic

Calculation Formula

No. of  valid defects reported at a stage (e.g. UAT)/ Total no. of defects reported in the current stage and previous stage (UAT & QA)

Trend

Lesser the percentage, better is the ‘Quality’

Maturity Levels

M1 - >=90% 

M2 - >=75-90%

M3 - >=50-75% , 

M4 >=25-50% , 

M5 <25%   

Instance level thresholds

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 :

image-20240704-094534.png

 

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

image-20240704-094534.png

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(407)") and label ="ClientDefect")

Benefits of KPI

How does the KPI help

The Defect Seepage Rate KPI helps teams proactively identify and address weaknesses in the quality assurance process, minimizing the number of defects that escape to production or later stages. This results in improved product quality, reduced customer-reported issues, and increased customer satisfaction by ensuring a higher level of reliability and stability.

C

  • No labels