Sprint completion
The Sprint completion report measures the percentage of total sprint work that was finished, including both planned and unplanned items. Use this metric to evaluate overall throughput and closure rate across your sprints.
When to use sprint completion
Sprint completion answers the question: How much of everything in the sprint did we finish?
This report helps teams:
- Measure overall throughput — Understand how much total work the team closed out during the sprint, regardless of when it was added.
- Track closure rate — Identify whether work is accumulating or being consistently completed.
- Account for scope changes — Get a realistic view of sprint execution that reflects mid-sprint adjustments.
How completion percentage is calculated
The completion percentage is calculated as:
Completed work÷ Total work
Where:
- Completed work is the story point/issue count for all issues marked complete during the sprint
- Total work is the story point/issue count for all issues in the sprint, whether planned or unplanned
This metric captures the full picture of sprint execution, including any work added after the sprint started. Sprint completion can be calculated based on either story points or issue counts.
Understanding planned vs. unplanned work
| Term | Definition |
|---|---|
| Planned points | Story points for issues that existed in the sprint at the sprint start time |
| Unplanned points | Story points for issues added after the sprint started |
| Completed points | Story points for all issues marked complete during the sprint, regardless of when they were added |
How sprint completion differs from sprint predictability
Unlike sprint predictability, sprint completion measures against the final scope, including work added mid-sprint.
For example, if you add 10 points mid-sprint but do not finish them:
- Your Completion score drops (because the total scope increased).
- Your Predictability score stays the same (because it ignores items added after the sprint started).
Use sprint completion to see if scope creep is preventing you from closing out sprints, and sprint predictability to see if you are delivering the volume you originally promised.