Definition of Ready vs Definition of Done: What Each Is For and How to Write Them
Two phrases cause endless confusion among Scrum learners: Definition of Ready and Definition of Done. They sound like twins, yet one is part of the Scrum framework and the other is a popular but optional practice. Understanding the difference helps you avoid two opposite problems: delivering work of unclear quality, and building a bureaucratic gate that slows the team.
Definition of Done: A Scrum Commitment
The Definition of Done (DoD) is a formal description of the state of the Increment when it meets the quality measures required for the product. The 2020 Scrum Guide treats it as the commitment for the Increment. When a Product Backlog item meets the Definition of Done, an Increment is born. If an item does not meet it, it cannot be released or even presented at the Sprint Review; it returns to the Product Backlog.
If the organisation has a standard DoD, all Scrum Teams must follow it as a minimum. If there is none, the Scrum Team defines one appropriate for the product. The Developers are required to conform to it. For the underlying concept see Increment and Definition of Done Explained.
Example Definition of Done (software team)
- Code is peer reviewed (or paired) and merged to the main branch.
- Unit and integration tests are written and passing in the CI pipeline.
- No critical or high-severity defects are open for the item.
- Acceptance criteria are verified by the Product Owner or tester.
- Security and performance checks relevant to the change are completed.
- Documentation, such as the API reference or runbook, is updated where needed.
- The feature is deployed to a production-like environment and, where appropriate, behind a feature flag in production.
Definition of Ready: A Helpful Practice, Not a Framework Element
A Definition of Ready (DoR) is a checklist that a Product Backlog item must satisfy before the team accepts it into a Sprint. It does not appear in the Scrum Guide; some teams find it useful for preventing half-baked items from entering Sprint Planning, and others find it harmful when it turns into a rigid gate.
The Scrum Guide's own idea is that the Product Backlog items that can be Done by the Developers within one Sprint are deemed ready for selection in a Sprint Planning event. They usually acquire this degree of transparency after refining activities. In other words, readiness is a result of good refinement, not a form to sign. See Product Backlog Refinement Explained.
Example Definition of Ready
- The story has a clear title, value statement and acceptance criteria. See Acceptance Criteria in Scrum.
- The Developers understand it and have no blocking questions.
- It is small enough to complete within a Sprint (ideally a few days).
- Dependencies are identified and, where external, resolved or planned.
- The Product Owner has ordered it in the backlog.
- Any necessary designs, data or access are available.
Side-by-Side Comparison
| Aspect | Definition of Ready | Definition of Done |
|---|---|---|
| Status in Scrum | Optional practice | Part of the framework (commitment for the Increment) |
| Applies to | Items about to enter a Sprint | Items finishing the Sprint |
| Purpose | Reduce uncertainty at the start | Ensure consistent quality at the end |
| Who owns it | The Scrum Team, typically with the Product Owner | Developers conform; the Scrum Team or organisation defines |
| Risk if misused | Becomes a gate that blocks learning and creates handoffs | If weak, produces low-quality or unreleasable work |
| Failure sign | Items bounce back and forth for sign-off | "Done" stories later reopened with bugs |
Common Traps with the Definition of Ready
- The gate mentality. If the DoR becomes a contract between Product Owner and Developers ("you did not meet the DoR, so we won't pick this up"), it recreates the hand-offs Scrum tries to remove.
- Over-specifying. Demanding full designs and sign-offs before planning turns Agile into mini-waterfall.
- Treating it as unchangeable. Review it in Retrospectives and keep it short, five or six items.
- Using it to avoid hard work. Some uncertainty is part of complex work. Spikes can reduce it; see Technical Debt and Spikes in Scrum.
Common Traps with the Definition of Done
- Too weak. "Code written" is not Done. If testing, integration or deployment are not included, work remains hidden and accumulates at the end.
- Too aspirational. A DoD the team cannot meet today leads to constant exceptions. Start with what is achievable and expand as capability grows.
- Hidden "done-done" and "undone" work. Teams that declare stories done then have a "hardening Sprint" are carrying an unacknowledged gap between their DoD and a releasable product.
- Never revisiting it. As the team matures, the DoD should become stricter; use the Retrospective to improve it.
How to Create or Improve Your Definition of Done
- Ask: "What must be true for us to be willing to release this without worry?"
- Capture everything the team currently does before calling something finished, then list what is routinely skipped.
- Sort the list into done now and aspirational. Commit to the first group.
- Agree on one or two aspirational items to add over the next few Sprints.
- Make the DoD visible, for example on the team board.
- Check compliance at the end of each item and at the Sprint Review.
What About Acceptance Criteria?
Acceptance criteria are specific to one item ("a user can reset a password using an email link"). The Definition of Done is common to all items ("tested, reviewed, documented"). An item is done when it satisfies both. Mixing them up causes duplicate or missing checks.
Interview Tip
A classic question is, "Is Definition of Ready part of Scrum?" The accurate answer: no, it is not in the Scrum Guide; Definition of Done is. Add that readiness should emerge from refinement and that you would treat a DoR as a guideline rather than a gate. See Scrum Master Scenario Interview Questions.
- The Definition of Done is a Scrum commitment; the Definition of Ready is an optional practice.
- A strong DoD protects quality; a rigid DoR can recreate hand-offs.
- Keep both short, visible and regularly improved through Retrospectives.
- Acceptance criteria are per item; the DoD applies to every item.