Overview | |
---|---|
Definition (Hover Text) | gives a measure of efficiency of the development team in closing defects raised because of new functionalities within the iteration |
Source Tools | Jira, Azure Boards |
Graph type | Line |
Filters | - |
Hover Format on KPI | Sprint Name: <<Percentage Value>> Closed Defects: <<Value>> Total Defects : <<Value>> |
Fields on Overlay |
|
Business Logic | |
Calculation Formula | No. of defects in the iteration that are fixed/ Total no. of defects in a iteration |
Trend | Higher the percentage, better is the ‘Quality’ |
Maturity Levels | M1 <25% M2 >=25-50% , M3 - >=50-75% , M4 - >=75-90% , M5 - >=90% |
Instance level thresholds | |
Configurations | |
Processor Fields | NA |
Mandatory fields |
|
How to Validate KPI | |
Suggested ways of working | |
Sample JQLs | |
Benefits of KPI | |
How does the KPI help |
General
Content
Integrations