Two of the most misunderstood concepts in Scrum. Often confused, sometimes skipped, always important.
Here's what they are, how they differ, and why getting both right makes your team dramatically more effective.
📌 Definition of Done (DoD)
The Definition of Done is a formal description of the state a Product Backlog Item must reach to be considered complete. It creates transparency and shared understanding of what "done" actually means across the Scrum Team.
It's not a checklist of tasks. It's a quality commitment — a guarantee to stakeholders that every increment meeting the DoD is truly releasable.
Examples of DoD criteria
- Code written and peer-reviewed
- Unit and integration tests passing
- Accepted by the Product Owner
- Documentation updated
- No known critical bugs
- Deployed to staging environment
If it doesn't meet the DoD, it isn't done. It goes back — not into the next sprint as a new item, not "almost done". Back.
📌 Definition of Ready (DoR)
The Definition of Ready describes the conditions a Product Backlog Item must meet before the team can pull it into a Sprint. It's a shared agreement on what "ready to work on" looks like.
Think of it as the entry gate for sprint planning — ensuring items are well-understood, sized, and actionable before the team commits to them.
Examples of DoR criteria
- User story clearly written with acceptance criteria
- Dependencies identified and resolved
- Sized by the team
- Mockups or designs attached if needed
- Business value understood
If it isn't ready, it doesn't enter the sprint. Pulling in unclear work mid-sprint is one of the fastest ways to derail a team.
🔍 Side by Side
| Definition of Done | Definition of Ready | |
|---|---|---|
| Answers | "Is this complete?" | "Can we start this?" |
| Applied at | End of work | Before sprint planning |
| Owned by | Scrum Team | Scrum Team (with PO input) |
| Scrum Guide | Formally defined | Not formally defined |
| Failure to meet | Item not shippable | Item not sprintable |
| Purpose | Quality assurance | Flow and clarity |
⚠️ The Key Distinction
Both definitions serve the same master — transparency. But they operate at opposite ends of the delivery cycle.
- DoR is about inputs — setting your team up to start well
- DoD is about outputs — ensuring your team finishes properly
A team with a strong DoR and a weak DoD ships unclear work. A team with a strong DoD and a weak DoR starts unclear work. You need both.
💬 A Common Misconception
"The Definition of Ready isn't in the Scrum Guide, so it doesn't matter."
It's true — the Scrum Guide only formally defines the Definition of Done. The DoR is a practical tool teams adopt, not a Scrum requirement.
But here's the nuance: the absence of a DoR doesn't mean items can enter a sprint unprepared. The Scrum Guide is clear that Sprint Planning requires the team to understand why the sprint is valuable, what can be done, and how the work will be accomplished. A DoR simply makes that expectation explicit.
Used well, it's one of the most effective tools for reducing sprint churn and improving team flow.
✅ TL;DR
- Definition of Done — quality gate at the end of work. Formally required by Scrum. Ensures every increment is truly releasable.
- Definition of Ready — clarity gate at the start of work. Not formally required but widely adopted. Ensures every item is genuinely actionable before the team touches it.
- Both are owned by the Scrum Team, both serve transparency, and both make the difference between a team that delivers and one that just stays busy.
Does your team have both — or are you running on one? Share your experience below 👇