Definition of Done (Done Criteria)
The Definition of Done (DoD) is a shared, standardized set of completion and quality conditions that every user story or backlog item must meet before it can be accepted. These Done Criteria are all-or-nothing: an item is only considered complete when every condition is satisfied. The Scrum Team applies the DoD as a checklist to confirm work is truly finished and meets agreed standards. Having a clear DoD removes ambiguity and helps the team consistently adhere to required quality norms.
Key Points
- A common checklist of completion and quality rules that applies to every backlog item.
- All criteria must be met; partial completion does not qualify as Done.
- Used by the Scrum Team to verify work at the end of development and during review.
- Improves transparency, reduces ambiguity, and enforces consistent quality.
Example
A team building a new login feature marks it Done only after: code is implemented, peer review completed, unit and integration tests pass, security checks are clear, documentation and release notes are updated, and the change is integrated into the main branch with a successful build. Because all DoD items are satisfied, the Product Owner can accept the story.
PMP Example Question
During Sprint Review, a story passes user acceptance tests but lacks documentation required by the team's checklist. What should the team do?
- Accept the story because users approved it.
- Mark it Done if the Product Owner signs off.
- Keep the story incomplete and finish the documentation to meet the Definition of Done.
- Create a separate story for documentation and close the current one as Done.
Correct Answer: C — Keep the story incomplete and finish the documentation to meet the Definition of Done.
Explanation: All Done Criteria must be met for an item to be considered complete; missing documentation means it does not meet the DoD.
