Sprint rollover report

Key features of the Sprint rollover report

The Sprint rollover chart helps Agile teams and leaders visualize how much of the planned work is carried over into the next sprints. Whether you track a single team or multiple Scrum boards, this real-time chart surfaces recurring rollover trends to help improve planning and delivery flow.

Trend lines, averages, and ratios provide context for understanding whether rollover is improving or getting worse over time. This makes it easier to inspect and adapt team practices, improve estimation accuracy, and have evidence-based discussions during sprint reviews and retrospectives.

The Sprint rollover report is part of the Agile Velocity Chart Gadget app - a comprehensive toolkit for visualizing velocity trends, commitments, and delivery consistency across teams directly on Jira dashboards.

How do different roles use the Sprint rollover chart

✅ Delivery Leaders (Managers / RTEs): Inspect rolled-over work across multiple teams to evaluate planning reliability vs. actual outcomes. Use rollover trends to identify recurring risks early, adapt program-level commitments, and maintain stakeholder trust through evidence-based transparency.

✅ Scrum Masters: Analyze carried-over backlog items at the sprint level to inspect and adapt team practices. Highlight recurring unfinished work, refine estimation and capacity planning, and facilitate retrospectives to strengthen the Definition of Done and improve sprint reliability.

✅ Agile Coaches: Leverage rollover data to assess team flow efficiency and long-term sustainability. Coach teams on improving delivery consistency, encourage continuous improvement practices, and align scaling practices with organizational goals to enable healthier Agile delivery.

Bring clarity to your sprint outcomes and improve planning accuracy with the SPRINT ROLLOVER REPORT

TRY IT FREE SCHEDULE A DEMO

1. Key feature: Sprint rollover metric visualization across one or multiple Scrum teams

Get clarity on unfinished work by tracking the sprint rollover. It’s one of the 10 essential velocity metrics you can monitor across one or multiple Scrum teams and see how carried-over work evolves across sprints, and compare Scrum teams' performance on one Jira dashboard.

⚙️Default settings:

• Data source: Scrum boards
• Interval: last 6 sprints
• Grouping: Parallel
• Estimation unit: Story points

Analyze rollover trends across multiple Scrum teams in a combined view, or focus on a single team - all within one Jira dashboard.

✅ With these insights, you can:

• Reveal where delivery reliability breaks down by tracking how much work is carried over into the next sprints.
• Spot recurring rollover patterns and use them as input for sprint reviews and retrospectives.
• Track rollover for a single team or across multiple Scrum teams within the same dashboard to identify where planning adjustments are needed.
• Strengthen estimation and commitment practices with evidence rather than assumptions.
• Set more realistic expectations with stakeholders by showing transparent rollover ratios and trends.

2. Key feature: Sprint rollover data deep analysis

Apply filter by rollover metric (1️⃣) to better focus on unfinished work carried over into the next sprint.

Once the filter is applied, Breakdowns let you segment the data, while the Issue list shows which specific issues contribute to it.

🔎 Breakdowns

Segment sprint rollover metric by any Jira field (e.g., board, issue type, status) to see which categories contribute most to carried-over work. You can also switch views to analyze data by projects, releases, epics, and more:

📋 Issue list

Get deeper insights into spilled-over work items: by applying filters for rollover, board, and stories (1️⃣), you can identify exactly which work items were moved forward from previous sprints.

The Issue list splits items into Completed and Not Completed, so you can clearly see what was delivered and what is still pending. Each work item also includes a Sprint count, showing how many sprints it has already been part of - helping you spot long-running items that repeatedly roll over.

✅ With these insights, you can:

• Pinpoint which Scrum teams, work item types, or statuses contribute most to rollover.
• Detect recurring patterns of unfinished work that undermine delivery consistency.
• Compare rollover trends across projects, releases, epics, and more.
• Identify long-running work items with high sprint counts and repeated carry-overs.
• Separate completed vs. not completed work to support sprint reviews.
• Back up retrospectives with transparent issue-level data instead of assumptions.

3. Key feature: Sprint rollover relative values (%) view

Switch the chart to percentage mode to analyze rollover in relation to your team’s total commitment - not just in absolute story points.

This real-time perspective helps teams instantly see what portion of planned work was carried over into the next sprints, making delivery insights more actionable and comparable.

✅ With these insights, you can:

• Spot rollover ratios to instantly see what portion of planned work spilled over into the next sprints.
• Identify recurring rollover trends that reveal planning or estimation issues.
• Compare results across Scrum boards, projects, releases, and epics to detect where consistency drops.
• Highlight long-running items that repeatedly spill over or stay open for multiple sprints.
• Validate sprint outcomes by separating completed vs. carried-over work.

4. Key feature: Sprint spillover with moving average trend line

Add a moving average trend line to smooth out short-term sprint fluctuations and reveal how carryover behaves over time.

By configuring the average type (e.g., 2 or more sprints), you can monitor whether rollover is increasing, stabilizing, or decreasing - helping teams spot delivery shifts before they escalate.

⚙️ Custom settings:

• Average: Only for Rollover (or any selected metric)
• Average type: 2 sprints (or choose the number of sprints to calculate the trend line)

✅ With these insights, you can:

• Visualize long-term carryover dynamics instead of relying on single-sprint snapshots.
• Detect early warning trends when unfinished work starts to accumulate across sprints.
• Compare actual vs. expected improvement after process or estimation changes.
• Validate team stability over time using the averaged sprint carryover KPI instead of short-term sprint metrics.

5. Key feature: Sprint carryover KPI with target lines

Set custom targets for sprint spillover (1️⃣) to define acceptable thresholds and track how teams perform against them (3️⃣).

You can configure the target as an absolute value (e.g., 15 SPs) or a relative ratio - based on Initial or Final commitment (2️⃣) - to align measurement with your planning approach.

This feature transforms the rollover data into a measurable KPI, allowing Agile leaders to assess how consistently teams meet their delivery commitments and how much work spills over beyond the planned scope.

✅ With these insights, you can:

• Measure sprint rollover against clear thresholds to quantify delivery reliability.
• Identify when rollover exceeds healthy limits and proactively address planning gaps.
• Compare teams’ adherence to sprint goals using unified metrics across dashboards.
• Spot patterns of over-commitment that lead to recurring carry-overs and delivery strain.
• Support sprint reviews and retrospectives with transparent data on planning vs. outcome.

6. Key feature: Sprint rollover vs. Initial commitment

Compare how much work was rolled over versus initially committed in each sprint to spot planning gaps and improve future commitments.

This visualization helps teams assess whether sprint goals were realistic and how consistently they meet initial commitments over time.

⚙️ Custom settings

• Metrics: Rollover, Initial
• Average: Rollover, Initial

‍‍✅ With these insights, you can:

• Spot mismatches between planned and actually delivered work.
• Track rollover percentage to evaluate how commitments evolve sprint by sprint.
• Identify sprints where overcommitment or scope underestimation occurs.
• Refine planning accuracy based on data-backed insights instead of assumptions.
• Improve reliability of future commitments by analyzing historical rollover trends.

Additional features of the Sprint rollover report

1. Exclude from sprint rollover

Filter out specific statuses (e.g., To Do, In Progress, Released) from the rollover calculation to keep metrics focused only on relevant unfinished work.

✅ Helps ensure accurate rollover ratios and prevents inflated results caused by items that shouldn’t be counted.

2. Advanced issue filtering

Apply multi-level filters to refine your sprint rollover analysis - by issue type, epic, release, or custom JQL query.

✅ Helps isolate specific work segments and analyze rollover trends with higher precision.

What about the native Jira Sprint rollover chart

There isn’t a built-in “Sprint rollover” chart or dashboard gadget in native Jira. Jira offers a few adjacent views, but none calculate rollover across sprints or support targets/averages/breakdowns.

Limitations of native Jira reports:

❌ The Sprint Report only shows completed vs. incomplete issues for one sprint - no cumulative rollover view.

❌ The Velocity Chart compares committed vs. completed work, but doesn’t track carried-over issues between sprints.

❌ None of these options provides averages, target lines, or cross-board comparisons.

➡️ That’s why teams use the Sprint rollover report - to analyze rollover ratios, trends, and planning accuracy across multiple sprints in one real-time chart.

Advantages of using the Sprint rollover report

• Real-time chart gadget in Jira dashboard enables instant visibility into rollover trends without leaving Jira, supporting quick inspection and sprint review discussions.
• Comprehensive rollover tracking provides full visibility into how much work is carried over between sprints - helping teams measure planning accuracy and delivery focus.
• Multi-board visibility allows comparing sprint rollover metrics across multiple Scrum boards for program-level transparency.
• Breakdowns and issue lists reveal which specific work items were rolled over and how often, making retrospectives data-driven.
• Trend and KPI tracking with moving averages and target lines highlights recurring patterns and progress over time.
• Rollover vs. commitment comparison helps identify planning gaps and improve estimation accuracy.
• Flexible configuration supports relative (%) view, issue-type, and status filtering, JQL queries, and exclusion of irrelevant statuses to focus on meaningful data.

Explore the interactive chart, no setup, no risk

TRY THE CHART

Apps used in this Sprint rollover report example

Build your own Jira Dashboard use cases with our interactive examples.

Both Jira apps featured here come with a 30-day free trial and are free forever for teams of up to 10 users:

Agile Velocity Chart Gadget Agile Reports and Gadgets

The Agile Reports and Gadgets app includes Sprint rollover report capabilities along with a wide range of advanced Agile charts and reports.

Frequently Asked Questions

1. What is a sprint rollover in Scrum?

The sprint rollover metric in Scrum refers to the work items that are not completed within previous sprints and are carried over into the next sprint:

“Sprint rollover” metric is often described using various terms such as "carryover", "spillover", or "leftover", all of which indicate the same concept of unfinished work that needs to be addressed in subsequent sprints.

2. Why is the sprint rollover metric important?

Sprint rollover metric is such an important indicator of sprint health that, alongside with say-do ratio metric,  it is often used as a KPI for Scrum teams.

Here is why it is important to track and analyze sprint leftovers:

1. Performance Insight: It provides insights into the team's performance and capacity. A high rollover rate may indicate that the team is overcommitting or facing obstacles that prevent them from completing their planned work.
2. Improvement Opportunities: By analyzing the reasons behind the rollover, teams can identify areas for improvement in their processes, estimation techniques, or resource allocation.
3. Planning Accuracy: Understanding rollover trends helps teams make more accurate sprint planning decisions. If certain types of tasks consistently roll over, teams can adjust their future sprint commitments accordingly.
4. Stakeholder Communication: It serves as a communication tool with stakeholders, illustrating the challenges the team faces and the need for adjustments in expectations or support.
5. Focus on Value Delivery: Tracking this metric encourages teams to focus on delivering value within the sprint, as they become more aware of the implications of not completing work on time.

Overall, the sprint rollover metric is a valuable tool for Scrum teams to enhance their effectiveness, improve their processes, and ensure better alignment with project goals.

3. How does the Sprint rollover report compare teams using different estimation fields?

Yes. While teams may use different estimation fields (like Story Points or Issue Count), the relative (percentage) view in the Sprint rollover report converts all data into normalized values, enabling fair cross-team comparison.

4. How to save the Sprint rollover report in a Jira dashboard?

You can add the Agile Velocity Chart Gadget to your Jira dashboard, then configure it to display the Sprint rollover report. You can start from the app’s Getting started page using the default setup or a template, or add the gadget directly from the dashboard via the Add gadget button and select Agile Velocity Chart Gadget.