artifactDelivery & agility

Definition of Ready

A team-defined set of conditions indicating that a work item is sufficiently understood to be considered for selection.

Download Markdown (.md)

01What it means

A Definition of Ready is an optional working agreement describing the minimum clarity and conditions a Product Backlog Item should have before a team considers it for a Sprint or workflow stage. It is a complementary practice, not an official Scrum artifact or commitment, and it differs from the Definition of Done, which describes completed quality.[1][2]

A local selection aid, not a universal commitment gate A candidate is ready enough when purpose, risk, dependencies, and next conversation are visible
Purpose
Why the item matters and which outcome it supports
Shared understanding
Team can discuss the need and important behavior
Dependencies
Known coordination and enabling conditions are visible
Risk
Uncertainty is acceptable or has a learning plan
Size
Small enough for the intended selection horizon
Evidence boundary
Acceptance examples or questions guide the next step

A Definition of Ready must not become a rigid handoff contract or demand certainty that discovery and delivery can only create later.

02Why it matters

A lightweight readiness agreement can reveal missing context, unresolved dependencies, or oversized work before planning. It helps teams discuss uncertainty consistently while keeping refinement focused on what is likely to be selected soon.

03When to use it

Use it when recurring readiness problems disrupt planning or flow. Keep it flexible for different work types; avoid it when teams use it as a gate that blocks discovery, collaboration, urgent work, or responsible learning during delivery.

04How it works

  1. Review recent planning failures and identify the few conditions that would have prevented them.
  2. Agree on observable readiness checks appropriate to the team and work type.
  3. Apply the checks during refinement without treating them as proof that uncertainty is gone.
  4. Discuss exceptions explicitly when learning or urgency justifies starting earlier.
  5. Revise or remove checks that become ceremonial or delay valuable work.

05A practical example

Example

A payments team repeatedly selects integration stories without test credentials. It adds access to a sandbox, a clear user outcome, and manageable size to its readiness agreement, while allowing a time-critical investigation to begin with documented unknowns.

06Where it breaks

Readiness is contextual and cannot eliminate uncertainty. A rigid checklist encourages handoffs, specification theater, and blame, especially when imposed on the team. Scrum requires items to be sufficiently transparent for selection but does not prescribe a Definition of Ready.

Common mistakes

  • Presenting the Definition of Ready as a required part of Scrum.
  • Using it as a contract between product and engineering.
  • Demanding complete specifications before learning can begin.
  • Applying identical checks to defects, experiments, and product capabilities.

07Sources

  1. Walking Through a Definition of ReadyScrum.org · Professional practice articleWalking Through a Definition of Ready
  2. The 2020 Scrum GuideScrum Guides · Official framework guideThe 2020 Scrum Guide
View saved topics

Start typing to search titles, definitions, categories, and frameworks.