Overview |
|---|
Applicability | Scrum-based projects |
Definition | Measures the number of work items that are not adequately refined in time for development planning. This includes: Work items in the current sprint that do not meet DoR (Definition of Ready). Work items tagged to the next sprint that lack sufficient refinement (e.g., missing description, acceptance criteria, etc).
Sprint Readiness metric flags backlog items that should be refined by now but aren't, either because they’re already in the current sprint and not meeting the Definition of Ready (DoR), or because they're slated for the next sprint but still lack necessary refinement details. |
Source Tools | Jira, Azure Board |
Graph type | Line chart for Current Sprint
Single stats for Next Sprint |
Filters | Filter by Issue type |
Hover Format on datapoints | Date No. of unrefined items : <<Count/Size>> Total items : <<Count/Size>>
|
Columns in Explore overlay | Issue ID Issue Type Issue Description Issue Priority Size (Story Point/Days) Issue Status Original Estimate Remaining Estimate Due Date Actual Start Date Dev Completion Date Actual Completion Date Delay Predicted Completion Date Assignee
and more…
|
Business Logic |
Calculation Logic | Unrefined_CurrentSprint = (Unrefined items in current sprint / Total items in current sprint) * 100
Unrefined_NextSprint = (Unrefined items in next sprint / Total items in next sprint) * 100
|
Scope of detection | Current Sprint Work Items
Assigned to the current active sprint but do not meet DoR (status, fields). Next Sprint Work Items
Tagged for the next sprint but lack key refinement attributes such as Description, Acceptance criteria,etc
|
| |
Configuration (Field Mapping) |
Processor Fields | Refinement criteria Custom field to consider for a refined workitem
Provide field name to identify a refined workitem, Example : customfield_13999 Custom field value min length Keywords to match (case-insensitive, ALL match)
|
Mandatory fields | Issue types to consider Status/es before DOR
|
Refinement Criteria | Work item is considered refined if it meets all of the following: Status is one of: Refined, Ready for Dev, or equivalent Has a non-empty description or, has specific keywords Includes clearly defined acceptance criteria
|
Benefits of KPI |
How does the KPI help? | Detect bottlenecks in sprint execution early Improve quality of sprint planning Avoid last minute clarifications and context gaps
|