Definition of Done Checklist
Build a practical Definition of Done for your Agile team. Check code quality, testing, acceptance, release readiness, and documentation before calling work complete.
Quality risk
0 of 16 checks complete
Code quality
Testing
Product acceptance
Release readiness
How to use this Definition of Done
Treat this as a team working agreement. If a story fails one of these checks, it is not done yet. Keep the checklist short enough to use every sprint, then adjust it after retrospectives.
Definition of Done vs acceptance criteria
The Definition of Done applies to every story. Acceptance criteria describe what must be true for one specific story. A story is complete only when both are satisfied.
Frequently Asked Questions
What is a Definition of Done?
A Definition of Done is a shared quality checklist that every story must satisfy before the team calls it complete. It applies across stories, unlike acceptance criteria, which are specific to one story.
Who creates the Definition of Done?
The whole Scrum team creates and maintains it. Engineering, QA, product, design, security, and operations concerns should all be reflected when relevant.
How often should we update the Definition of Done?
Review it after retrospectives, production incidents, recurring escaped defects, or major process changes. Keep it practical enough to use every sprint.
Is this checklist free?
Yes. The checklist is free, runs in your browser, and can be copied into Jira, Confluence, Notion, or team docs.