Definition of Done and acceptance criteria both live in the quality conversation, which is exactly why CSM candidates confuse them. The clean difference is scope. Acceptance criteria usually describe what must be true for a specific backlog item. The Definition of Done describes the quality standard that work must meet before it counts as part of a usable Increment. On the CSM exam, that distinction matters because it affects transparency, release confidence, and what “done” is allowed to mean.
The Scrum Guide explicitly connects the Definition of Done to the Increment. Scrum Alliance then tests candidates through a 16-hour CSM training path and a 50-question exam in 60 minutes with a 74% passing score. Questions around done quality are common because they reveal whether you prefer honest quality signals or optimistic labeling.
Direct answer: how are they different?
| Concept | Scope | Main question it answers |
|---|---|---|
| Acceptance criteria | A single Product Backlog item or feature slice | What must this item do to satisfy its intended behavior? |
| Definition of Done | The Increment as a whole | What shared quality standard must completed work meet to count as done? |
What acceptance criteria are for
Acceptance criteria reduce ambiguity around a specific backlog item. They might describe behavior, edge cases, or business rules. For a password reset feature, the criteria could include successful email delivery, token expiration handling, and clear error feedback when the token is invalid.
Those criteria help the team understand what “this item should do.” They are item-specific. A different backlog item will need different criteria.
What the Definition of Done is for
The Definition of Done is broader. It protects a shared understanding of what quality must be true before work is considered complete as part of the Increment. Depending on the product, that might include integration, testing, code review, documentation, security checks, or deployment readiness. The exact contents can vary. The function does not: it keeps “done” from becoming a political word.
This is why a feature can satisfy its acceptance criteria and still fail the Definition of Done. It might do what it is supposed to do functionally, but still lack testing, integration, or another team-wide quality requirement.
A worked example candidates actually remember
Imagine a backlog item: Allow customers to update their saved payment method.
Acceptance criteria might include:
- the customer can replace a stored card successfully
- expired cards trigger a clear validation message
- the updated card is used on the next renewal
Definition of Done requirements might include:
- automated tests pass
- the change is integrated into the shared branch
- security review checks are complete
- documentation is updated where required
If the feature behaves correctly but skips the required security review, it may satisfy acceptance criteria and still fail the Definition of Done. The work is not part of a done Increment yet.
Why this distinction shows up on the CSM exam
The exam likes this concept because it tests several Scrum ideas at once:
- whether quality is transparent
- whether the Increment is being represented honestly
- whether candidates can separate item-level clarity from team-level done standards
If a question asks whether work can be demonstrated, released, or counted as complete, always ask yourself which quality tool the scenario is really describing.
Common wrong-answer patterns
| Wrong assumption | Why it fails | Stronger Scrum interpretation |
|---|---|---|
| Acceptance criteria and Definition of Done are synonyms | They operate at different levels | One is item-specific; one is Increment-wide |
| If acceptance criteria are met, the work is automatically done | It may still miss the shared quality bar | Definition of Done still must be met |
| Definition of Done belongs to one backlog item | It defines done quality for the Increment | It should apply consistently across completed work |
How this affects Sprint Reviews and reporting
Teams get into trouble when they show work in a Sprint Review that functions on the surface but does not meet the Definition of Done. That creates false confidence for stakeholders. CSM answers usually reward transparency over optics. A smaller, genuinely done Increment is healthier than a larger pile of half-finished work labeled as complete.
This article also connects closely to artifacts and the Increment and Sprint Goal versus Sprint Backlog, because all three ideas help define what quality and progress mean in Scrum.
What this looks like in a bad real-world team
Teams that confuse these two ideas often start reporting feature work as done because the business behavior looks complete in a demo. Then production issues surface because shared technical or compliance standards were skipped. The CSM exam rewards the opposite instinct: tell the truth about quality even when that truth is less flattering in the moment.
That is also why Scrum treats transparency as a competitive advantage, not a bureaucratic burden. If the team cannot trust the word done, planning and forecasting both get weaker immediately.
How to study this topic for the exam
- Practice identifying whether a scenario is item-level or Increment-level.
- Write one example of acceptance criteria and one Definition of Done for the same feature.
- Review questions where work “looks finished” but still has quality gaps.
- Choose the answer that preserves honest transparency about done work.
This is much more effective than memorizing a one-line definition, because the exam usually wraps the distinction in a scenario.
FAQ
Who creates acceptance criteria?
They are usually shaped through collaboration around a backlog item, often with strong Product Owner involvement because they clarify intended value and behavior.
Can the Definition of Done change?
Yes, but it should change intentionally and transparently as the team improves its quality standard.
Which one matters more on the CSM exam?
Both matter, but candidates more often miss the Definition of Done because it exposes whether they are willing to call unfinished work unfinished.
Exam details verified against Scrum Alliance and the Scrum Guide on May 23, 2026. Test policy and support materials can change, so confirm current details before your exam.
If you want this topic condensed into a faster review format, the CSM PDF study guide includes a done-quality comparison sheet and scenario questions. If you want interactive practice, SimpuTech's CSM AI tutor can walk you through Definition of Done versus acceptance-criteria scenarios and explain the best answer.