Purpose
A Definition of Ready is the shared checklist for a story being ready to enter a sprint. Not met — not pulled in. Goal: don't start "raw" work (no clear value, no criteria, hidden dependencies). DoR is the sprint's entry filter (vs DoD, the exit). Agreed by the team, not imposed.
Template
# Definition of Ready — a story is ready if:
- [ ] Value ("why") and user role are clear.
- [ ] Acceptance criteria (Given/When/Then), observable.
- [ ] Key edges/errors covered.
- [ ] Dependencies known and NOT blocking.
- [ ] Fits a sprint (else split).
- [ ] Design/mockup present if needed.
- [ ] Technical questions resolved.
- [ ] Estimated (story points).
Example 1 — READY
# Story: Save a card to favorites — DoR check
- [x] Value: quick return to needed tools; role — base user.
- [x] Criteria: star click → in Favorites; survives reload.
- [x] Edges: re-click removes; works locally when logged out.
- [x] Deps: existing IndexedDB layer, nothing blocking.
- [x] Size: 3 SP. Design: star icon in mockup. Estimate agreed.
✅ READY — take into the sprint.
Example 2 — NOT ready
# Story: "Tool recommendations" — DoR check
- [ ] Value vague ("make it smarter"). ❌
- [ ] No acceptance criteria. ❌
- [ ] Needs a model/data that don't exist → blocked. ❌
- [ ] Size unknown. ❌
⛔ NOT READY. Action: clarify value with PO, write criteria, split out the dependency, re-estimate.
Quality checklist (of the DoR)
- Criteria observable & binary.
- Checks dependencies.
- Includes "fits a sprint".
- Agreed by the team.
- Realistic (too strict → paralysis).
Common mistakes
DoR as bureaucracy; ignoring dependencies; pulling raw work under pressure; confusing DoR with DoD; imposed not agreed.