In 30 seconds
- A team agreement on when an item is clear enough to start.
- Not part of the official Scrum Guide.
- Useful as a guide; harmful if used as a strict gate.
An example checklist
- Written as a user story with a clear user and value
- Acceptance criteria agreed
- Small enough to finish in a sprint
- Estimated by the team
- Known dependencies identified
Ready vs Done
| Definition of Ready | Definition of Done | |
|---|---|---|
| Checked | Before work starts | When work finishes |
| Official in Scrum | No | Yes |
| Purpose | Avoid starting unclear work | Guarantee quality |
See Definition of Done.
When it hurts
If the checklist becomes a gate that blocks anything imperfect, teams drift back toward big up-front specifications. Use it as a conversation guide during refinement, not a contract.
Myth vs reality
Myth · Scrum requires a Definition of Ready.
Reality · It's a popular practice, not part of the Scrum Guide.
Myth · Items must be 100% specified.
Reality · Ready means clear enough to start and learn the rest.
Myth · The Product Owner alone decides readiness.
Reality · The team agrees together.
FAQ
Who creates the Definition of Ready?
The Scrum team, during a retrospective or refinement.
How strict should it be?
Light enough that most refined items pass without paperwork.
Do Kanban teams use it?
Often as an explicit policy for the Ready column.