Done should mean more than coded
A Definition of Done (DoD) is a shared standard describing what must be true before work is considered complete.
“Development complete” is not the same as “done.”
Quality-focused DoD criteria
- Acceptance criteria satisfied
- Code reviewed
- Unit/component tests pass
- Required QA validation complete
- Critical defects resolved
- Regression impact addressed
- Automation updated
- Evidence retained
- Monitoring considered
- Documentation updated
Story Done vs Release Ready
DoD usually applies to an increment or story. Release readiness may require additional cross-story and operational controls.
| Story Done | Release Ready |
|---|---|
| AC met | Integrated regression complete |
| Story tests pass | Open defects assessed |
| Code merged | Deployment/rollback ready |
| Automation updated | Monitoring/support ready |
Keep DoD enforceable
If the team routinely ignores parts of the DoD, either the standard is unrealistic or accountability is weak. Review and improve it rather than allowing silent exceptions.
Use DoD as a quality contract
A good DoD removes ambiguity. Everyone should understand what quality work is required before an item leaves the team’s active delivery flow.