Overview | ||
---|---|---|
Definition (Hover Text) | measures Measures the rate at which a team can deliver every Sprint. Since a stable velocity helps in forecasting, the KPI also measures the last 5 sprints average velocity and plots it along with the sprint velocitycompletes work in each sprint. | |
Source Tools | Jira, Azure Board | |
Graph type |
| |
Filters | - | |
Hover Format on KPI |
| |
Fields on Overlay | Sprint Name Story ID Issue Description Size | |
Business Logic | ||
Calculation Formula |
| |
Trend | - | |
Maturity Levels | Compare Sprint Velocity with Average Velocity M1: Velocity is 0-40% or >160% M2: Velocity is 40-60% or 140-160% M3: Velocity is 60-75% or 125-140% M4: Velocity is 75-90% or 110-125% M5: Velocity is 90% -110% - M5Settings | Step 1: Custom Completion Status
*Please note:- Global mappings and default Jira statuses will apply if the KPI level settings are not used. |
Trend | - | |
Maturity Levels | NA | |
Instance level thresholds | Target KPI value denote denotes the bare minimum project should maintain for KPI | |
Configurations | ||
Processor Fields | NA | |
Mandatory fields | NA | |
How to Validate KPI | ||
Suggested ways of working |
| |
Sample JQLs | project = "XYZ" AND "SCRUM Team" = ABC AND issuetype = Story AND status in (Closed) AND sprint in(433) | |
Benefits of KPI | ||
How does the KPI help |
|
...