Sprint closeout & rollover
When a sprint reaches its end date, Helpin marks it done and gives you a closeout view of what was completed and what remains. Use the closeout to review the outcome, then roll the right work into the next sprint.
Review the closeout
Go to Sprints and open the completed sprint.
Review its closeout summary.
The summary breaks the sprint's work down into categories such as the following, with item counts and story points where estimates are available:
Category | What it shows |
|---|---|
Committed | The tasks that were assigned to the sprint |
Completed | The tasks that reached a completed workflow state |
Unfinished | The tasks that did not reach a completed workflow state |
Rolled over | The tasks you moved into another sprint |
A task is unfinished because it has not reached a completed workflow state — it is not automatically work that should carry into the next sprint. Decide item by item.
Decide what to roll over
For each unfinished task, decide whether it is still the next best work:
If the task is still the right next work, roll it over into the next sprint.
If it needs more discovery, clarification, or reprioritization, leave it in the backlog instead of rolling it over.
Rollover moves an unfinished task into the selected next sprint. The receiving sprint shows an inbound rollover summary, so you can see which work arrived from a previous sprint.
Prepare the next sprint
Before moving tasks, make sure the next sprint exists and has the correct dates and team. Then use the sprint planning workspace to balance the incoming work with new commitments.
Tip: Avoid carrying every unfinished item forward by default. Review its priority, estimate, dependencies, and team capacity first. This keeps the next sprint's commitment meaningful.
Learn from the result
The closeout keeps completed, unfinished, and rolled-over work separate, so you can discuss delivery without losing history. Over several sprints, completed points help you compare planned load with actual throughput.
Use this as a planning input for the next sprint. If carryover is common, consider committing to fewer tasks, breaking large tasks down, or resolving blockers earlier.
Related
Was this article helpful?