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 | |
Configurations | |
Processor Fields |
|
Mandatory fields |
|
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 |
General
Content
Integrations