Ryan Ripley

Best Features
· Dedicated chapters about 3-5-3 (roles, ceremonies, artifacts)

· Directness to talk about anti-patterns

· Scenario based references to Liberating Structures exercise.

What more I wanted?
· Different personality types within a Scrum Team (identify & exercises)

· Some more references to the Scrum Values- Scrum values in action & few exercises to do with the team.

"Fixing Your Scrum" was a great opportunity to "varnish" my Scrum perspective. It is a must read for those who are in pursuit of being truly self-organized and cross-functional. It walks us through 3-5-3 of Scrum with dedicated chapters, each chapter targets & has examples of "real Scrum world problems". Popularized with the term "anti-patterns", these have been discussed in a direct manner and suggests practical solutions. It details out underlying causes and tries to cure the problem and not just cure the symptom #unlikeCOVID19. Throughout the book, Ryan & Todd, talk about an anti-pattern, suggest ways to look at it while backing it up with the Scrum Value associated with it. These small bits reassure that no situation is unique or random. Coaches Corner provides valuable feedback and insightful tips to guide the reader further. The chapter about Sprint Retrospective is a real thought provoker.
Some more learnings and highlights:
· No time for Retro? A quick retro with available team members. A quick question round about what was wrong, how can we make sure it does not happen again & voila improvements for next sprint are ready to be added to product backlog. This can help meet the purpose of retro and in the shortest pocket of time.

· "Clean the plate" mentality during Sprint Planning - this anti-pattern struck a chord with me. In reality, it affects so many other areas- the reviews, backlog prioritization, feedback from stakeholders, etc.

· Exercise to identify Stakeholders. Based on our past discussions to involve stakeholders in our reviews is our next focal point. I am going to reread this chapter along with the Product Owners, work with & do the exercise together.

· Delete anything that’s older than six months, as you likely won’t ever do the work for those features. And if that work is important, it will reappear via feedback from customers and stake holders. This is a courageous move suggested in the book. The target areas in this theory are product backlog, feedback from stakeholders. It is a very strong idea to implement that will also lessen the degrees of distance between stakeholders and development team.… (altro)