Overview | |
---|---|
Definition (Hover Text) | measures the total number of defects (bugs) linked to closed stories which are part of a Iteration. |
Source Tools | Jira, Azure Boards |
Graph type | Line |
Filters | <None> |
Hover Format on KPI | Sprint Name: <<Percentage Value>> Defects: <<Value>> Closed Stories: <<Value>> |
Fields on Overlay |
|
Business Logic | |
Calculation Formula | No. of defects tagged to all stories closed in an iteration/ Total no. of stories closed in the iteration. |
Trend | Positive trend indication - Decrease |
Maturity Levels | M1: > 175% M2: 175% -125% M3: 125%-75% M4: 75-25% 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(406)") |
Benefits of KPI | |
How does the KPI help | The Defect Injection Rate KPI helps in identifying the number of defects introduced during the development process, which can help in improving the quality of the product and reducing the cost of fixing defects in later stages. It also helps in tracking the effectiveness of the testing process and identifying areas for improvement. |
Page Comparison
General
Content
Integrations