Definition of Ready

The checklist a backlog item must satisfy before the team will pull it into a sprint — usually scoped, sized, and clear.

What is the definition of ready?

The definition of ready (DoR) is the checklist a backlog item must satisfy before the team will pull it into a sprint. It's the gatekeeper between "an idea" and "work the team will commit to."

A typical definition of ready

  • User story written in standard format
  • Acceptance criteria documented
  • Dependencies (designs, specs, RFCs) linked and complete
  • Estimated in story points
  • Sized to fit inside one sprint (split if >13)
  • Understood by at least two team members
  • Has a clear "why" — connects to a roadmap item or business goal

DoR vs DoD

WhenWhat
Definition of ReadyBefore a ticket enters a sprint
Definition of DoneBefore a ticket leaves a sprint

Why DoR matters

Without a DoR, sprint planning turns into a mini-spec review for every ticket. The team commits, then discovers the ticket needs design or unblocking, and the sprint slips. DoR moves that discovery into refinement, where it belongs.

Common DoR mistakes

  • Too strict — a 12-item checklist makes nothing ready. Aim for 4-6 items.
  • Soft enforcement — if "not ready" tickets still get pulled in, the DoR is theatre.
  • Confusing with DoD — DoR gates entry, DoD gates exit.

Related

Run sprints without a glossary tab open

SprintFlint sets up a working sprint with sensible defaults in 30 seconds — velocity, burndown, retros, and capacity all built in. Free for the first 300 tickets.