Definition of Ready (DoR)
Definition of Ready (DoR) is a set of criteria that a user story must meet before it can be taken into a sprint.
DoR answers: “Is this story ready to be worked on?”
1. Definition
Definition of Ready (DoR) is a set of criteria that a user story must meet before it can be taken into a sprint. It ensures that work is well-defined, understood, and testable before development and testing begin.
DoR answers: “Is this story ready to be worked on?”
2. Purpose of Definition of Ready
- Prevent poorly defined stories from entering sprints
- Reduce mid-sprint confusion and rework
- Improve sprint predictability
- Enable early and effective testing
3. Typical DoR Checklist (Manual Testing View)
A story is considered Ready when:
- Business value is clearly defined
- Acceptance criteria are written and testable
- Requirements are clear and unambiguous
- Dependencies are identified
- Test scenarios can be derived
- Test data requirements are known
- UI designs or references are available (if needed)
- Story size is small enough to complete in a sprint
4. Manual Tester’s Role in DoR
- Review stories during backlog refinement
- Identify missing acceptance criteria
- Check for testability and edge cases
- Raise data, environment, or dependency concerns
- Reject stories that are not test-ready
5. DoR vs Definition of Done (DoD)
| Aspect | Definition of Ready (DoR) | Definition of Done (DoD) |
|---|---|---|
| Purpose | Start work | Finish work |
| Timing | Before sprint | End of sprint |
| Focus | Readiness | Completion |
| Owner | Team | Team |
6. Real-Time Example
A story fails DoR if:
- Acceptance criteria are missing
- Business rules are unclear
- External API dependency is not ready
Such stories should not enter the sprint.
7. Benefits of Strong DoR
- Fewer blockers during sprint
- Better test planning
- Higher sprint success rate
- Reduced defect leakage
8. Common Mistakes
- Treating DoR as optional
- Making DoR too rigid or too vague
- Ignoring tester input during refinement
9. Interview-Ready Answers
Short answer:
Definition of Ready defines the criteria a user story must meet before it can be taken into a sprint.
Detailed answer:
DoR ensures that user stories are clear, testable, and fully understood so the team can work efficiently without mid-sprint blockers.
10. Key Takeaway
Definition of Ready ensures quality starts before development, not after.