Overview | ||||
---|---|---|---|---|
Definition (Hover Text) | gives an idea about The Created vs Resolved KPI measures the speed at which the team closes the defects that are raised during a sprint. It provides insights into the team’s efficiency in handling and resolving defects. | |||
Source Tools | Jira, Azure Boards | |||
Graph type | Line + Column Chart | |||
Filters | Total Defects, Added defects | |||
Hover Format on KPI | Created Defects - <<Value>> Resolved Defects - <<Value>> Resolved Percentage - | |||
Fields on Overlay |
| |||
Business Logic | ||||
Calculation Formula |
| |||
Trend | Higher the Resolved trend, better is the qualityA higher trend in resolved defects indicates better quality and efficiency, as it shows the team is effectively closing the defects they raise. | |||
Maturity Levels | Compare Resolved defects with Created Defects M1: Velocity is 0-40% M2: Velocity is 40-60% M3: Velocity is 60-75% M4: Velocity is 75-90% M5: Velocity is >90% | |||
Instance level thresholds | -Target KPI Value denotes the bare minimum a project should maintain for a KPI. | |||
Configurations | ||||
Processor Fields |
| |||
Mandatory fields |
| |||
How to Validate KPI | ||||
Suggested ways of working | ||||
Sample JQLs | project = "Your Project Name" AND issuetype in standardIssueTypes() AND resolved >= startOfDay(-7) AND resolved <= endOfDay() | |||
Best Practice | ||||
Consistent Tracking |
| |||
Regular Reviews |
| Benefits of KPI | ||
How does the KPI helpEffective Communication |
| |||
Benefits of KPI | ||||
Efficiency Measurement |
| |||
Quality Assurance |
| |||
Customer Satisfaction |
|
Page Comparison
General
Content
Integrations