Definition of Done
The Definition of Done (DoD) is a formal description of the state of the Increment when it meets the quality measures required for the product, providing a shared understanding of what it means for work to be complete.
Explanation
The Definition of Done is a commitment for the Increment artifact. It creates transparency by providing a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or presented at the Sprint Review.
The DoD typically includes criteria such as code review completed, unit tests passing, integration tests passing, documentation updated, and acceptance criteria met. If the organization has a standard Definition of Done, all Scrum Teams must follow it as a minimum. Individual teams can add stricter criteria.
The Definition of Done helps the team understand how much work they can select during Sprint Planning and ensures that the Increment truly represents usable, high-quality output. Over time, teams often strengthen their DoD as they mature, adding more rigorous quality standards.
Key Points
- •Formal description of quality standards the Increment must meet
- •Creates transparency and shared understanding of completeness
- •Organization-level DoD applies as a minimum; teams can add stricter criteria
- •Items not meeting the DoD cannot be released or presented at Sprint Review
Exam Tip
The Definition of Done is not the same as acceptance criteria. DoD applies to every item uniformly, while acceptance criteria are unique to individual backlog items.
Frequently Asked Questions
Related Topics
Increment
An Increment is a concrete stepping stone toward the Product Goal, where each Increment is additive to all prior Increments and must meet the Definition of Done to be considered complete.
Definition of Ready
The Definition of Ready (DoR) is an informal checklist that a team uses to determine when a Product Backlog item is sufficiently refined and understood to be pulled into Sprint Planning.
Sprint Retrospective
The Sprint Retrospective is a Scrum event where the Scrum Team inspects how the last Sprint went with regard to people, relationships, processes, and tools, and creates a plan for improvements.
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.