Overview | |||
---|---|---|---|
Definition (Hover Text) | measures the percentage work completed at the end of a sprint in comparison to the total work in the sprint | ||
Source Tools | Jira, Azure | ||
Graph type | Line | ||
Filters | Commitment type/Scope, Issue Type | ||
Hover Format on KPI | Sprint Name: <<Percentage Value>> Delivered: <<Count/Size>> Committed: <<Count/Size>> | ||
Fields on Overlay |
| ||
Business Logic | |||
Calculation Formula | It is calculated No. of issues or Size of issues completed/No. of issues or Size of issues committed | ||
Trend | Higher the percentage during a sprint, better forecasting can be done for future sprints | ||
Maturity Levels | M1 - <40% M2 - 40-60% M3 - 60-75% M4 - 75% - 90% , M5 - > 90% | ||
Instance level thresholds | - | ||
ConfigurationsGlobal Configuration (Field Mapping) | |||
Processor Fields | NA | ||
Mandatory Fields | KPI Specific fields | Project Settings
| |
How to Validate KPI | |||
Suggested ways of working |
| ||
Sample JQLs | JQL Query to get the issues committed at the start of a sprint: project = "Your Project Name" AND Sprint in openSprints() AND issueFunction in addedDuringSprint("Your Board Name", "Your Sprint Name") | ||
Benefits of KPI | |||
How does the KPI help |
|
Page Comparison
General
Content
Integrations