It’s fair to say that your organization may be inspired by scrum: You may use daily standups, cards on a wall (or virtual cards in a tool), periodic “sprints”, perhaps even demos and retrospectives.
Yet something conspires to make Scrum ineffective. Ken Schwaber, a co-creator of scrum, says that roughly 25% of teams trying the method realize the gains they had hope. More teams call themselves “Scrumbut”, “Scrumerfall”, or “Scrumish” than claim to be doing it right.
Put simply: Scrum is designed to expose problems. It does not, by itself, solve the problems. In theory, Scrum provides a framework for the team to work through the solution themselves. In practice, politics, rhetorics, and lack of training often get in the way.
This talk is about understanding common scrum problems and breaking through ruts.
In this presentation Matthew Heusser discusses the heart of scrum, where it goes wrong, how testing can enable Scrum success – and how testers can improve their visibility and role while contributing to Scrum and team long-term success.