What is the Definition of Done
The Definition of Done is the team's shared standard for when a piece of work is complete. When a Product Backlog item meets the Definition of Done, it becomes part of the Increment.
If the item does not meet the Definition of Done, it returns to the Product Backlog.
Why It Matters
The Definition of Done is the line between "done" and "done-ish."
Without a strong Definition of Done, work piles up in a hidden inventory that looks finished. Problems surface late, usually right before release. With a strong Definition of Done, every Increment is genuinely shippable.
How It Works in Scrum
If the organization has a Definition of Done for the product, every Scrum Team must follow it as a minimum. If not, the team creates its own.
Multiple teams on the same product share a single Definition of Done. Without that, the integrated product has uneven quality.
A practical Definition of Done usually covers:
- Quality standards (peer review, code review, craft)
- Testing (functional, regression, security as relevant)
- Integration with the existing product
- Release readiness (deployable and demonstrable)
The Definition of Done is not static. As the team matures, it expands.
Common Mistakes
- No written Definition of Done. If it isn't written, it isn't shared.
- Done means "code complete." Code complete is not Done.
- Different Definitions of Done across teams on the same product. Quality becomes uneven.
- Lowering the bar under deadline pressure. This just hides unfinished work.
- Never expanding the Definition of Done. A static Definition of Done means the team has stopped raising its quality bar.
Key Takeaways
- The Definition of Done is the team's standard for what counts as complete.
- Work that does not meet it is not part of the Increment.
- A strong Definition of Done eliminates hidden inventory.
- The Definition of Done should grow as the team matures.