Sprint carryover can make each new sprint harder to plan. Stories waiting for review or testing move into the next sprint alongside new work. A sprint later, some of those same stories are still unfinished.
Your team is completing work, so why does this keep happening? Our Velocity vs Throughput article looked at measuring completed work. Tracking sprint carryover in Jira adds another perspective. A velocity or throughput chart can show how much the team delivers. To understand carryover, you also need to examine what enters each sprint from earlier ones, what remains unfinished, and how scope changes.
In this article, you’ll learn how to track sprint carryover in Jira, compare unfinished work across sprints, and investigate recurring patterns.
What is sprint carryover?
Sprint carryover is unfinished work brought into a sprint from an earlier sprint. Teams also use terms such as sprint rollover or sprint spillover.
Separate sprint carryover from unfinished work
For reporting, the useful distinction is between work left unfinished and work actually carried over (spilled over, rolled over).
Unfinished work is work still in the sprint’s scope that has not reached Done when the sprint closes. It may later enter another sprint, return to the backlog, or be reconsidered.
Carryover describes previously unfinished work included when another sprint starts. Keeping these views separate helps you understand both the work left behind and the work inherited by the next sprint.
For example, Sprint 10 might end with six unfinished issues. If four are selected for Sprint 11 and two stay in the backlog, Sprint 10 has six unfinished issues, while four issues have carried into Sprint 11. The two totals answer different questions.
Moving work forward should be a planning decision. The Scrum Guide says that items which do not meet the Definition of Done return to the Product Backlog for future consideration. Review their value, priority, and remaining work before selecting them again.
How Jira’s Native Reports Help You Investigate Carryover and Unfinished Work
Jira provides useful information for examining individual sprints and comparing planned work with completed work. They don’t directly report sprint carryover (also called spillover or rollover). The reports also don’t show what percentage of a sprint’s starting scope came from earlier sprints or which issues rolled over more than once.
The native reports below apply to Jira Cloud’s company-managed Scrum projects.
Sprint Report: Identify Unfinished Work
Open Reports → More Reports → Sprint Report and select a closed sprint. The Sprint Report shows which issues your team completed and which remained unfinished when the selected sprint closed.
Jira considers an issue complete for sprint closure when its status is mapped to the board’s rightmost column. Atlassian’s guide to completing a sprint explains the available destinations for unfinished work and completion rules.
Use it to identify the issues left unfinished and examine changes to the sprint’s work. From there, inspect individual issue histories to see what happened during the sprint and where the issues went afterward.
The Sprint Report shows which issues remained unfinished at the end of a sprint, but it doesn’t flag work the team carried over from earlier sprints.
Velocity Chart: Compare Planning and Completion
Open Reports → More Reports → Velocity Chart.The Velocity Chart compares the work recorded at sprint start, labelled Commitment, with the work completed by the end of the sprint. The completed total can include work added after the sprint began.
This helps you compare how much work your team planned at the start of each sprint with how much it completed by the end.
The Velocity Chart report, however, doesn’t help you identify individual unfinished issues or flag work carried over from earlier sprints.
What Teams Need From a Sprint Carryover Report
A useful report should help the team answer three questions: How much unfinished work enters each sprint? How much remains unfinished at the end? What happened to the items behind those totals?
Track initial scope, final scope, completed work, carried-over work, and unfinished work together.
Compare carried-over work with initial scope to see how much of the starting plan came from earlier sprints. At sprint close, look at completed work and unfinished work alongside final scope. Check what the team added and removed along the way. Even if the scope totals match, the work itself may have changed.
Both totals and percentages matter. Four carried-over issues represent a different share of a ten-issue plan than of a forty-issue plan. The count tells you how many items need attention; the percentage shows their share of the selected scope.
You also need access to the spilled-over issues themselves. If four issues carried over into this sprint, your team may want to know which four. A useful sprint carryover report should also let you inspect the issues behind the totals so you can investigate what kept them from reaching Done.
Alternative Approaches to Tracking Carryover
You can start with manual retrospective reviews. Compare a few Sprint Reports, inspect issue histories, and record why work remained unfinished. This can be enough for an occasional investigation, but repeating the process every sprint is time-consuming and adds to the team’s reporting workload.
For regular monitoring, a reporting app can make it easier to compare results across sprints. When choosing one, check how it reconstructs sprint history, defines carryover, calculates percentages, and lets you inspect the underlying issues.
Great Gadgets is one option. Its Team Velocity gadget lets you compare carryover and unfinished work alongside sprint scope and completion, directly on your Jira dashboard. You can review patterns across several sprints, then explore the contributing issues to understand what needs attention.
How to Track Sprint Carryover With Team Velocity Gadget in Great Gadgets
You can use the Team Velocity gadget to build three complementary views: work carried over, unfinished work at sprint end, and a combined view showing both alongside scope and completion.
Start by adding the Team Velocity gadget to your Jira dashboard. Select your Scrum board and the number of sprints to display. Use a consistent measurement unit, such as work item count, story points, time estimates, or any numerical custom field.
Tip: Use Work Item Count when you want to see how many issues keep returning. Use story points when you want to examine those items through the team’s estimates. Keep the unit consistent across the views you compare.
1. Configure the sprint carryover view
In the Series tab of the gadget, select Carried Over and % Carried Over.
This view shows how much work in each sprint’s initial scope came from a previously closed sprint.
The chart helps you identify carryover trends, spot potential over-commitment, and improve sprint planning and delivery predictability.
2. Configure the sprint unfinished work view
In the Series tab of the gadget, select Unfinished and % Unfinished to compare what remained incomplete at the end of each sprint.
This shows how much work remains unfinished at the end of each sprint. Comparing the results over time helps you assess sprint outcomes, spot recurring delivery challenges, and plan future sprints more realistically.
The distinction between the two percentages matters: % Carried Over uses Initial Scope, while % Unfinished uses Final Scope. They describe different stages of the sprint.
| Measure | What it shows | Percentage calculation |
|---|---|---|
| Carryover | Previously unfinished work included at sprint start | (Carried Over Work ÷ Initial Scope) × 100 |
| Unfinished work | Work left unfinished at sprint end | (Unfinished work ÷ Final Scope) × 100 |
4. Add scope and completion for context
For a broader view, display Initial Scope, Final Scope, Completed, Carried Over, % Carried Over, Unfinished and % Unfinished together.
Add Added, Removed, or Average Velocity when those series help answer a specific question. For example, additions and removals help explain why the final plan differs from the starting plan.
If the chart becomes crowded, use separate gadget instances for carryover and unfinished-work trends. Keep a combined view for investigating how those results relate to scope and completion.
5. Explore the data behind the chart to see which issues carried over and investigate why
The Team Velocity gadget lets you inspect each Jira issue behind a sprint’s carryover total. Enable Show data table in the More Settings tab to display the underlying information in a separate Data tab or directly below the chart.
Use it to identify the issues contributing to carryover and unfinished work. Then open the relevant issues to examine sprint changes, status transitions, comments, and dependencies.
Focus on what happened during the sprint being reviewed. An issue that is Done today may still have been unfinished when that sprint closed.
Final thoughts
Tracking sprint carryover in Jira helps you understand how unfinished work affects future plans. It becomes more informative when you compare it with final scope, completed work, and the issues left unfinished at sprint end.
Start with consistent definitions and a manageable set of closed sprints. Check what changed in each sprint, then inspect the issues behind a recurring pattern.
Use the evidence to choose a practical improvement. That might mean adjusting a forecast, splitting a story, changing how urgent requests are handled, or resolving a dependency before planning the work again.
The Team Velocity gadget from Great Gadgets brings these comparisons and issue details into a recurring dashboard review.
If you would like to build these views for your team, you can try Great Gadgets for Jira and configure the Team Velocity gadget using your Scrum board.
FAQs
Are sprint carryover, rollover, and spillover the same?
Yes. Teams often use these terms interchangeably. For clear reporting, distinguish work left unfinished at sprint end (unfinished work) from work actually brought forward into another sprint (carryover/spillover/rollover).
Is carryover always equal to the previous sprint’s unfinished work?
No. Some unfinished issues may remain in the backlog or enter a different sprint. A sprint can also receive unfinished work from several earlier sprints.
Should You Include Active Sprints in a Carryover Review?
Use closed sprints when comparing final unfinished-work results. Work still open in an active sprint has not yet reached its deadline, so it should not be assessed as if the sprint had already ended.
Leave a Reply