It’s time to ditch your Definition of Ready

Get rid of that dead weight if you want to be Agile

What is a Definition of Ready?

A contract that needs to be met before the team can start working on a Sprint Backlog Item

1. Scrum already prescribes what makes a Backlog Item “Ready” for Sprint Planning

Product Backlog items that can be “Done” by the Development Team within one Sprint are deemed “Ready” for selection in a Sprint Planning. — Scrum Guide

2. Product Backlog Items in Scrum already contain enough information to get started

Product Backlog items have the attributes of a description, order, estimate, and value. Product Backlog items often include test descriptions that will prove its completeness when “Done”. — Scrum Guide

3. Sometimes just a title may be enough to start working on something

4. It’s already up to the Development Team to change the Sprint Backlog during a Sprint

Only the Development Team can change its Sprint Backlog during a Sprint. — Scrum Guide

5. Definition of Ready conflicts with Agile way of working

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

A Definition of Ready creates more problems than it solves

Serious Scrum footer with link to Slack community
Do you want to write for Serious Scrum or seriously discuss Scrum?

130+ articles with > 1.4 million views on beating the Feature Factory and better ways of delivering value together.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store