Agile Delivery Kit for Software Organisations


How to work in an agile way. This starter kit provides the strategies, recipes. workshops, technologies, practices, and guides that will help you and your people create a way of work that enables success.


Does having a definition of ready a good idea?



1 minute to read

Last Updated: Thu 9 May 2024 08:36


Does having a definition of ready a good idea?

Short Answer

No. Having a definition of ready can lead to gating of work for a team.

Long Answer

In the Scrum Guide there is the idea of “ready” that is associated with the Product Backlog.

[!Quote] Product Backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event.
Scrum Glossary -

This reflects the shared understand that is necessary for a Scrum Team to take on work.

[!Quote] Ready: a shared understanding by the Product Owner and the Developers regarding the preferred level of description of Product Backlog items introduced at Sprint Planning.
Scrum Guide

While the intent behind a definition of ready is laudable the outcome is mostly an “us vs them” attitude between the Developers and the Stakeholders, or worse the Product Owner. Rather than having a checklist, definition of ready, or DOD, just get the Scrum Team together and come to an agreement of which items in the Backlog are “ready” for us to attempt.

References: Related papers and Articles

Recommended Content

Join the Community
The league of extraordinary lean-agile practitioners is a group of peers and seasoned practitioners that continuously learn, share emergent practices, and discuss topics with courage, commitment, focus, respect, & openness!