Content Comparison

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, as per Definition of Ready (DoR) criteria. This includes:

• Work items in the current sprint that do not meet DoR.

• Work items tagged to the next sprint that lack sufficient refinement (e.g., missing description, acceptance criteria, etc).

Late Refinement 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.

Calculation Logic

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

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

Filters

Filter by Issue typeFilter by Priority

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. Dev Completion Date

12. Actual Completion Date

13. Remaining Estimate Delay

14. Predicted Completion Date

15. Assignee
    and more…

Configuration

Processor Fields

NARefinement criteria

Mandatory fieldsNA

1. Issue types to consider

2. Status/es before DOR