Rollover
Since sprints exist only in Scrum boards, charts based on other data sources don’t include sprint-related metrics. The only available metric for data sources other than Scrum is Completed work.
Definition
Planned issues carried over from a previous sprint, either incomplete or not yet started.
Category
Commitment.
How rollover is calculated
The chart counts as rollover the issues that move from one sprint to the next on the chart timeline, taking into account the applied sprint filters. It does not rely on the board configuration.
Example 1
The chart shows rollover for all sprints from the BETA & GAMMA board (1️⃣), with no filters applied (2️⃣). Rollover in Sprint 5 (Gamma) is 0 (3️⃣), meaning no issues were carried over directly from Sprint 5 (Beta) to Sprint 5 (Gamma).
Example 2
The chart shows rollover for Gamma sprints from the BETA & GAMMA board (1️⃣), filtered by sprint name (2️⃣). Rollover in Sprint 5 (Gamma) is 9 (3️⃣), meaning 9 issues were carried over from Sprint 4 (Gamma) to Sprint 5 (Gamma).
What you can analyze with this metric
This metric helps you analyze the following aspects:
How many story points were rolled over, affecting the team’s actual capacity for new work?
Open the Cross-team or Benchmarking velocity chart.
Click Metrics and select Rollover.
Set the view to absolute values.
How often did a particular issue roll over from one sprint to another?
Open the Cross-team velocity chart.
Click Metrics and select Rollover.
Click a period in the chart to open the issue list and check the Sprint count column. It shows how many sprints each issue has belonged to.
Hover to see sprint names.
What proportion of the Initial Commitment was taken up by Rollover issues across a series of sprints? Are we comfortable with this? What do we consider a healthy pattern?
Open the Cross-team velocity chart.
Set the view to percentages.
Click Metrics and set the ratio basis to Initial commitment.
Select Rollover and Initial commitment.
Were all incomplete issues transferred to the next sprint? Are we okay with that?
Open the Cross-team velocity chart.
Set the view to absolute values.
Select Rollover and Not completed work.
Exclude statuses from rollover
You can exclude from rollover issues in certain statuses at sprint start (for example, In Testing or Dev Done) if they don’t meaningfully affect the next sprint’s scope.