Definition of Done vs Acceptance Criteria
People think acceptance criteria are a story's own Definition of Done. They are not. Acceptance criteria belong to one story and say what it must do. The Definition of Done is one list for all work, like tested and reviewed. A story is done only when it meets both.
Definition of Done
The checklist all work must pass to count as finished. The whole team uses the same one.
The Definition of Done is the shared list of checks that work must pass to count as finished. It might say the code is tested, reviewed and written up in the help pages. When work meets it, it becomes part of an increment. Work that does not meet it cannot be released or shown at the Sprint Review. It goes back to the Product Backlog instead.
Acceptance Criteria
The checks one user story must pass to be accepted. Each one can pass or fail.
Acceptance criteria are the checks one user story must pass to be accepted. They are written before the work starts, often by the Product Owner with the team. Each one is a plain check that can pass or fail. Many teams write them as Given, When, Then, a form from behaviour-driven development. Each story has its own list. The Definition of Done is one list for all work.
In one line
- Definition of Done
- The checklist all work must pass to count as finished. The whole team uses the same one.
- Acceptance Criteria
- The checks one user story must pass to be accepted. Each one can pass or fail.