I’ve been to the Scrum Gathering in
this year. In his keynote Jeff Sutherland describes how he gets Scrum teams hyper productive. Essentially, you need to get your stories to Done Done as fast as possible. However, often too many unknowns do exist when a user story is being played. To fix this problem Jeff introduced, as on of his key ingredients, the concept of Ready Ready. Ready Ready removed disruptions and waste caused by issues being clarified with customer or others. He even suggested the use of a Ready Ready checklist to make sure that stories to be implemented do comply with the definition of Ready. Looks like the ‘Definition of Done’ gets a sibling — ‘Definition of Ready’. The enforcement of DoR helped to increase the flow of stories to the anticipated state of Done Done and thereby increasing the productivity. Applying Ready Ready was core to create hyper productive Scrum teams. It came 2nd after ‘Everyone must be trained in the Scrum framework’. Munich
This is essentially what I have been doing or better trying to do in my last projects. However, the Ready Ready idea is very easy to explain and very convincing. Especially since it comes from Jeff Sutherland.
From now on my Product Backlog items will be Ready Ready before they can move into the Sprint Backlog.
Great post, but do you have an example, by any chance, of the checklist that Jeff suggested?
• Everyone must be trained in Scrum framework
• Backlog must be ready ready before taking into Sprint
• Software must be done done at the end of the Sprint
• Pair immediately if only one person can do a task
• No Multitasking
• Physical Scrum Board
• Short sprints (often 1 week)
• Burn down Story points only
• Everything (including support) is prioritized by PO
• Servant leadership – it’s not about you