Definition of done vs acceptance criteria (with a DoD template)
Definition of done vs acceptance criteria: one applies to every item, the other to one story. Examples, a copyable DoD template, and definition of ready.
A story passes all five of its acceptance criteria and gets demoed on Friday. On Monday, someone notices it has no tests, broke the API docs, and was never deployed past staging. Was it done? The story said yes. The team's standard said no, if the team had written one down.
That's the difference between acceptance criteria and a definition of done. This guide compares them using the Scrum Guide, checked on 16 November 2026, with a template you can copy.
The short answer
| Definition of done | Acceptance criteria | |
|---|---|---|
| Applies to | Every backlog item | One story |
| Covers | Quality and completeness | What this feature must do |
| Owned by | The Scrum team or the organization | Product owner, refined with the team |
| Changes | Rarely; as the team's standards rise | For every story |
| Example | "Tests pass in CI" | "The export includes role and last active date" |
An item is done only when it meets both.
Definition of done, per the Scrum Guide
The Scrum Guide calls the definition of done a formal description of the state of the Increment when it meets the quality measures required for the product. The moment an item meets it, an Increment exists. Key points:
- An item that doesn't meet it can't be released or even presented at the sprint review. It goes back to the product backlog.
- If the organization has a definition of done, every Scrum team follows it as a minimum. Otherwise the team creates one for the product.
- Developers are required to conform to it. Several teams on one product share one definition of done.
It creates transparency: everyone means the same thing by "done."
Acceptance criteria
Acceptance criteria are specific to a story: the conditions that show this particular feature works as intended. They're often written as Given/When/Then scenarios or a checklist of rules. See acceptance criteria examples.
The Scrum Guide doesn't define acceptance criteria, but they sit naturally inside the product backlog item.
Definition of done template
Adapt to your stack:
# Definition of done
A backlog item is done when:
## Code
- [ ] Meets the story's acceptance criteria
- [ ] Reviewed and approved by at least one other developer
- [ ] No new linter or type errors
- [ ] No new dependencies without team approval
## Tests
- [ ] Unit tests for new logic
- [ ] Integration or end-to-end test for the main path
- [ ] All tests pass in CI
## Quality
- [ ] Accessible: keyboard and screen reader checked for UI changes
- [ ] Performance within agreed limits
- [ ] Security review for auth, payments, or personal data changes
## Release
- [ ] Deployed to staging and verified
- [ ] Behind a feature flag or safe to release
- [ ] Monitoring and alerts in place for new services
## Docs
- [ ] User-facing docs and API reference updated
- [ ] Decision recorded if the work changed or set a team decision
Start small. A short definition the team meets every time is worth more than a long one it skips.
Definition of ready
Some teams add a definition of ready: the checklist for when an item can enter a sprint. It isn't part of the Scrum Guide, so keep it light enough that it doesn't become a gate:
- The story has acceptance criteria.
- It's small enough to finish in a sprint.
- Dependencies are known.
- Open questions have owners.
Think of it as the entry check, with the definition of done as the exit check.
Common mistakes
- Putting story-specific items in the DoD. "Export includes roles" belongs in the story.
- Putting quality items in every story. "Has tests" belongs in the DoD, once.
- A DoD nobody meets. Then it isn't the definition of done; it's a wish list.
- Never updating it. Raise the bar as the team matures.
When agents write the code
The definition of done applies to work, not to who wrote it. If AI coding agents produce some of the code, add the checks that keep agent output to the same bar: a person reviews agent-written changes, no new dependencies without approval, and the change is consistent with recorded team decisions. See technical debt from AI coding.
Where Lockstep fits
"Consistent with recorded team decisions" is hard to check by hand. Lockstep captures decisions from PRDs, Slack, and pull requests, routes each to its owner for approval, and briefs Claude Code sessions on the ones that apply before code is written. Its checks are advisory: they flag likely conflicts for a person to review.
See how it works.
Sources checked 16 November 2026
Related reading
For writing stories, see acceptance criteria examples. For planning sprints with AI, see sprint planning with AI. For writing the stories themselves, see the user story template. For revisiting the definition of done, see the retrospective template. For what reviewers check, see the code review checklist.
Frequently asked questions
- What is the difference between the definition of done and acceptance criteria?
- The definition of done applies to every backlog item and covers quality: code reviewed, tests passing, documentation updated. Acceptance criteria apply to one story and cover its specific behavior. A story is done when it meets its own acceptance criteria and the team's definition of done.
- What is the definition of done in Scrum?
- The Scrum Guide calls it a formal description of the state of the Increment when it meets the quality measures required for the product. An item that doesn't meet it can't be released or presented at the sprint review, and returns to the product backlog.
- Who creates the definition of done?
- If the organization has one as a standard, every Scrum team follows it as a minimum. Otherwise, the Scrum team creates one suitable for the product. Multiple teams working on the same product must share one.
- What is the definition of ready?
- A checklist some teams use for when a backlog item is ready to be pulled into a sprint, such as having acceptance criteria and being small enough. It isn't part of the Scrum Guide. The definition of done is the exit check; the definition of ready is the entry check.
- Should the definition of done include AI coding agent rules?
- If agents write code, yes. Add items like 'agent-written code reviewed by a person' and 'no new dependencies without approval'. The definition of done applies to the work regardless of who or what wrote it.
Keep reading