Be the first to like this
"Never pull anything into a sprint that is not ready, and never let anything out of a sprint that is not done.”
Creating a comprehensive "Definition of Done (DoD)" is a widely accepted Agile practice that fosters a culture of accountability, minimizes rework, and reduces team conflict. However, when a team first establishes a DoD, things often get worse before they get better. Why? Because the team no longer gets credit for incomplete work. Committed stories are started but not finished, multiple stories are carried over to the next sprint, and the team's velocity decreases. So what can be done to overcome this common problem?
An important tool to ensuring that stories are completed is an unambiguous Definition of Ready (DoR). Many Scrum-team issues are rooted in misunderstood and poorly prepared stories. In fact, I believe that stories that are NOT ready, but have been COMMITTED to a Sprint, are the root of all Scrum evil. Stories that are "ready" need to be clear, concise, and actionable.
In this hands-on presentation and workshop, I will demonstrate the methods that I have used with multiple organizations to create stories that are truly ready for a Sprint, including:
Learn my three-touch refinement technique (speed refining, sprint refining, and sprint planning) that requires teams to "touch" a story three times before the sprint
Cultivate stories slowly and methodically to build shared vision
Use Story Mapping to visualize the backlog, find missing stories, and understand customer journeys
Write test cases before the sprint as a technique to decompose stories and uncover hidden questions
Establishing a team-level "Definition of Ready (DoR)"