In Agile, sprints are time-boxed periods where teams commit to completing a set of work. However, it’s not uncommon for some tasks to remain unfinished by the end of a sprint. This article explains what to do when that happens and how it impacts your Agile metrics.
What Is an Incomplete Sprint?
An incomplete sprint occurs when one or more tasks (user stories, bugs, etc.) are not finished by the sprint’s end date.
What To Do at the End of an Incomplete Sprint
-
Close the Sprint on Schedule
Always close the sprint at the planned time — even if not all tasks are done. Agile focuses on consistency and learning, not perfection.
-
Review Unfinished Work
During the sprint review or retrospective, identify:
-
Why the work wasn’t completed (e.g. blockers, unexpected changes)
-
Whether the task is still a priority
-
-
Move Incomplete Tasks
You have two options:
-
Move to the next sprint if it’s still a high priority
-
Return to the product backlog to be re-prioritized
-
-
Update Task Status
Make sure all task statuses are correct:
-
“Done” for completed work
-
“To Do” or “In Progress” for unfinished tasks
-
Impact on Agile Metrics
-
Velocity
Only completed work is counted toward sprint velocity. Unfinished tasks don’t contribute.
-
Burndown Chart
The chart will show remaining work at the end of the sprint. This helps identify scope issues or process bottlenecks.
Tips for the Future
-
Avoid overcommitting — plan based on past sprint velocity.
-
Break down tasks into smaller, manageable pieces.
-
Address blockers early during daily stand-ups.
-
Use retrospectives to improve future sprint planning.
Remember: Incomplete sprints are a learning opportunity, not a failure. The goal is to adapt, improve, and keep delivering value consistently
Want to learn more about Agile? Read this EBOOK, listen to this AUDIOBOOK or enroll in this COURSE