Is there any prerequisite to be Ready in Agile?
As Scrum defines, there are two critical stages in the process:
READY & DONE. The Product Owner can easily double the velocity of
a Scrum team by getting Product Backlog to a high READY state.
Team can easily double story process efficiency by delivering as
per their agreement of DONE. Individual self-organization can further
enhance team velocity. Let’s focus on prerequisite of starting a sprint
i.e. being READY.
To help with this, our teams work with the PO to agree on what defines a
“ready” state of a backlog item. This will vary by project, but below are
some elements to seed the discussion:
- Story defined and written
- Story traceable to source document (where appropriate)
- Acceptance criteria defined
- Dependencies identified
- Size estimated by delivery team
- User experience included (where appropriate)
- Performance criteria identified (where appropriate)
- Person who will accept the user story is identified
- Team has a good idea about how to demo the user story
A User Story (backlog item) can be considered READY if:
• It is defined as need, conversations, and confirmations [reference].
• It follows INVEST (independent, negotiable, valuable, estimable,
and testable) principals [reference].
• It is small enough to fit inside a sprint. Larger stories should be
reformulated and splitted before the sprint planning to be considered “Ready”.
• It has unique priority in relation to every other story in the product backlog.
• It has been estimated (in story points) by the team.
• It does not have any known dependency that can block the completion of story.
Don’t let anything that’s not READY into your Sprint, and let nothing escape that’s not DONE.