Content Comparison

Applicability

Scrum-based projects

Definition

It gives intelligence to the team about Measures the number of issues work items that could potentially not get completed during the iteration. Issues which have a Predicted Completion date > Sprint end date are considered.

Calculation Logic

This widget shows number of issues likely to spill.

It is based on the logic of remaining estimate of an issue and comparing it with the remaining time in the sprint. 1 day considered as 8 hoursare 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 typeFilter by Priority

Hover Format on datapoints

1. Date

2. No. of unrefined items : <<Count/Size>>

3. Total items : <<Count/Size>>

Columns in Overlay ScreenExplore overlay

1. Issue ID

2. Issue Type

3. Issue Description

4. Issue Priority

5. Size (Story Point/Days)

6. Issue Status 

7. Original Estimate

8. Remaining Estimate

9. Due Date

10. Actual Start Date

11. Remaining Estimate Dev Completion Date

12. Actual Completion Date

13. Delay

14. Predicted Completion Date

15. Assignee
    and more…

Business Logic

Calculation Logic

1. Unrefined_CurrentSprint = (Unrefined items in current sprint / Total items in current sprint) * 100

2. Unrefined_NextSprint = (Unrefined items in next sprint / Total items in next sprint) * 100

Scope of detection

1. Current Sprint Work Items
   Assigned to the current active sprint but do not meet DoR (status, fields).

2. 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

NA

Mandatory fields

1. Refinement criteria

   1. Custom field to consider for a refined workitem
      Provide field name to identify a refined workitem, Example : customfield_13999

   2. Custom field value min length

   3. Keywords to match (case-insensitive, ALL match)

Mandatory fields

1. Issue types to consider

2. 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?

1. Detect bottlenecks in sprint execution early

2. Improve quality of sprint planning

3. Avoid last minute clarifications and context gaps