Definition of Done
You'll learn: How the Definition of Done creates a shared quality standard that ensures everyone agrees when work is truly complete.
What Is the Definition of Done?
The Definition of Done (DoD) is a checklist or set of criteria that every work item—whether a user story, task, or feature—must satisfy before it's considered complete. It's not just "the code runs"; it's a comprehensive agreement about quality standards that the entire team commits to upholding.
Think of it like a pilot's pre-flight checklist. Before takeoff, every item must be checked—fuel, instruments, control surfaces. Similarly, before marking work "done," every DoD criterion must be met—no exceptions, no shortcuts.
Why It Matters
Without a Definition of Done, "done" becomes subjective. One developer might think "done" means code committed; another might assume it includes tests, documentation, and deployment. This misalignment creates confusion, quality gaps, and surprises during Sprint Reviews.
The DoD eliminates ambiguity by establishing:
- Shared understanding across the team and stakeholders
- Quality gates that prevent technical debt from accumulating
- Transparency into the true state of work
- Consistency across all deliverables
Common DoD Criteria
A typical Definition of Done might include:
- Code written and peer-reviewed
- Unit tests written and passing
- Integration tests passing
- Documentation updated
- Code merged to main branch
- Acceptance criteria met and verified
- No critical bugs outstanding
- Deployed to staging environment
The DoD evolves with the team's maturity—starting simple, growing more rigorous over time.
Key Takeaway: The Definition of Done is your team's shared quality contract—meeting every criterion ensures work is truly shippable, not just "developer done."