What does it truly mean for a product increment to be “done” in Scrum, and why does this matter for agile success?
Scrum teams often talk about โdone,โ but what does that really mean? In the world of agile, the difference between โdoneโ and โalmost doneโ can determine whether a sprint achieves its purpose โ and whether the team continues to improve. This lesson unpacks why only potentially releasable increments count as truly โdone.โ
Done Means Releasable
Ending sprints with nonreleasable product increments is an antipattern to becoming more agile. Done means potentially releasable. A sprint that ends without potentially releasable functionality is, by definition, not a sprint.
Developers get to done by swarming on user stories โ working together on one user story at a time until it is complete before starting the next. Developers hold each other accountable by ensuring that all rules for their definition of done, including test automation, are satisfied before starting a new user story. Product owners review completed work against the scrum teamโs definition of done (as well as the user storyโs acceptance criteria โ see the module on user stories) before approving and moving on to a new user story.
The term “antipattern” refers to a common practice that looks appealing but undermines agile principles. Ending sprints with nonreleasable increments is a classic antipattern in Scrum.
A shared agreement within the Scrum team that specifies the rules, quality criteria, and requirements a user story or increment must meet to be considered complete.
An increment that meets all requirements and quality standards so it can be released to users immediately, if the Product Owner chooses.
In a software company, teams often finish sprints with features that are “almost working.” These features may pass basic tests, but if they aren’t integrated, documented, and fully tested, they can’t be released. Only increments that are fully ready โ tested, documented, and integrated โ are considered “done” in Scrum.
Want to go deeper? The science behind “done” in agile teams
Research into high-performing agile teams shows that clear, enforceable definitions of โdoneโ reduce ambiguity and build trust. When teams know exactly what counts as โdone,โ they spend less time arguing, more time collaborating, and produce higher-quality, releasable code. Test automation and peer accountability are proven drivers for reaching this standard.
Work with your team (or imagine one) to create a definition of “done” for a single user story.
- List the criteria that must be met for the story to be considered complete (e.g., code reviewed, tests automated, documentation updated).
- Compare your list with your teammates. Are there any gaps or disagreements?
- Revise the definition together to ensure everyone agrees.
Ending sprints with nonreleasable product increments is an antipattern to becoming more agile.
Anything that passes basic tests or is “almost done” counts as a finished sprint increment.
Only increments that are potentially releasable โ meeting all criteria in the definition of done โ are truly “done” in Scrum.
How would your teamโs workflow change if you enforced a stricter definition of “done”?
What risks arise if a sprint delivers features that arenโt ready for release?
Think of a time when you or your team considered a task “done” but later found gaps or issues. What would have been different if you had used a strict, shared definition of done?
Experienced Scrum practitioners recommend swarming on user stories โ the team works together to finish one story before starting another. This approach ensures all aspects of the definition of done are met, and prevents unfinished work from piling up.
What is the “definition of done” in Scrum?
Tap to revealA shared agreement specifying the rules and quality standards required for work to be considered complete.
Why must a sprint increment be potentially releasable?
Tap to revealBecause only releasable increments fulfill the purpose of a sprint and support continuous delivery and improvement.
What is an antipattern in Scrum?
Tap to revealA common but harmful practice, such as ending sprints with nonreleasable increments.
In Scrum, what does “done” mean for a product increment?
- Learned the importance of a clear definition of done
- Understood why only potentially releasable increments count as done
How does swarming on user stories help teams achieve โdoneโ status?
In Scrum, “done” means potentially releasable โ only increments meeting all criteria can be considered complete and ready to deliver.
Swarming on user stories and holding each other accountable to the definition of done ensures quality, collaboration, and continuous improvement.
The Shift
- A sprint is only complete when the increment is potentially releasable.
- Clear definitions of done and team accountability prevent unfinished work from accumulating.
- Swarming on user stories drives collaboration and ensures every increment is truly โdone.โ