Definition of Ready
A team agreement that defines the minimum criteria a backlog item must meet before it can be pulled into a Sprint. The Definition of Ready prevents teams from starting work on stories that are too vague, too large, or missing critical information — the leading cause of mid-Sprint blockages.
How to run it
- 1
Gather the full Scrum team (Product Owner, developers, Scrum Master).
- 2
Brainstorm: 'What would need to be true about a story before we'd be comfortable starting it?' Capture everything on sticky notes.
- 3
Cluster and vote on the criteria that matter most. Common ones: clear acceptance criteria, estimated, no unresolved dependencies, small enough to complete in one Sprint, approved by Product Owner.
- 4
Agree on the final list — typically 5-8 criteria. Write it up visibly.
- 5
Test it immediately against 3-5 backlog items. Does it feel right? Adjust if needed.
- 6
Review the DoR quarterly — it should evolve as the team matures.
Tips
Keep the DoR short enough to be remembered — 5-8 criteria max.
The DoR is a team agreement, not a gatekeeping tool. Use it to help, not block.
Don't confuse DoR with Definition of Done — DoR is for entry, DoD is for exit.
If stories regularly fail the DoR, fix the refinement process, not the DoR.
Variations
Digital teams often embed the DoR as a checklist directly in their issue tracker (Jira, Linear, GitHub). Stories can't leave 'Backlog' status without all boxes checked.
Where it fits
Related methods
Plan your next workshop with AI
Workshop Weaver helps you combine methods like Definition of Ready into a complete, timed agenda in minutes.
Try it freeMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Workshop Weaver.