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 |
|
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 |
Escaped defects identification
Mandatory fields
Issue Type Mapping
Issue types which will have linked defects eg; Story, Tech StoryWhenever 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
Defect Mapping :
|
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. |