What Is Definition of Ready for User Stories?
Definition of Ready (DoR) is a shared checklist a team agrees a user story must satisfy before it's considered ready to be pulled into a sprint — clear enough, small enough, and understood well enough that the team can commit to it confidently, without major open questions surfacing mid-sprint.
Quick facts
- Definition of Ready is applied during backlog refinement, before a story enters sprint planning.
- A common DoR includes clear acceptance criteria, an agreed size estimate, and no major open questions or blocking dependencies.
- See related: What Is Definition of Done in Agile, the equivalent standard applied after work is completed.
Definition of Ready vs Definition of Done
| Definition of Ready | Definition of Done | |
|---|---|---|
| Applies before | A story enters a sprint | A story is considered complete |
| Purpose | Ensures the team can commit to a story confidently | Ensures consistent quality standards on finished work |
| Example criteria | Clear acceptance criteria, estimated size, no blocking dependencies | Code reviewed, tests passing, deployed to staging |
| Owned primarily by | Product Owner, with team input during refinement | The development team collectively |
A typical Definition of Ready checklist
- The story has clear, specific acceptance criteria.
- The story is small enough to be completed within a single sprint (see INVEST criteria).
- The team has enough information to provide a reasonable size estimate.
- Any blocking dependencies (on another team, a decision, or external factor) are identified and resolved or clearly tracked.
- The story's value or reasoning is understood, not just its literal requirements.
The specific items vary by team, but the underlying purpose — confirming a story is genuinely ready for confident commitment — stays consistent.
Why Definition of Ready matters
Without a shared standard, stories sometimes enter a sprint still carrying significant ambiguity — unclear acceptance criteria, an unrealistic size, or an unresolved dependency. This ambiguity often surfaces mid-sprint, disrupting the team's flow and sometimes forcing a story to be abandoned partway through. A clear Definition of Ready pushes this clarification work earlier, into backlog refinement, where it's cheaper and less disruptive to resolve than mid-sprint.
How Definition of Ready connects to backlog refinement
Definition of Ready gives backlog refinement sessions (see Backlog Grooming/Refinement Best Practices) a concrete goal: get upcoming stories to meet this checklist before they're proposed for the next sprint. Without this explicit standard, refinement sessions can feel unfocused, without a clear signal for when a story has actually been sufficiently prepared.
A worked example
A team's Definition of Ready requires clear acceptance criteria, an agreed story point estimate, and no unresolved dependencies. During refinement, a story about "adding two-factor authentication" is flagged as not ready — it lacks specific acceptance criteria around which authentication methods to support, and depends on a security team decision that hasn't been made yet. The team defers this story from the upcoming sprint planning, working instead with the Product Owner to resolve the missing details, rather than pulling in a story likely to stall mid-sprint.
Common mistakes with Definition of Ready
- Never establishing an explicit DoR, leaving story readiness as an inconsistent, informal judgment call.
- Applying DoR too rigidly to every backlog item, including ones far from being worked on, adding unnecessary upfront effort.
- Pulling stories into sprint planning that don't actually meet the team's own DoR, undermining the standard's purpose.
- Confusing Definition of Ready with Definition of Done, applying the wrong checklist at the wrong point in a story's lifecycle.
FAQ
Who decides a team's Definition of Ready? Typically the team collaboratively, often with strong input from the Product Owner, since it needs to reflect what the team genuinely needs to feel confident committing to a story.
Does every backlog item need to meet Definition of Ready? Only items being considered for an upcoming sprint — items further down the backlog can remain less detailed until they're closer to being prioritized.
What happens if a story doesn't meet Definition of Ready but is urgent? Ideally the team resolves the missing readiness criteria quickly rather than skipping the standard — pulling in a genuinely unready story, even an urgent one, often causes more disruption than the delay to properly prepare it.
Can Definition of Ready change over time? Yes — like Definition of Done, many teams revisit and adjust their DoR as they learn what level of preparation genuinely prevents mid-sprint surprises for their specific context.