TL; DR: Skipping Retrospectives?
There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. One area where Scrum’s nature of being intentionally incomplete causes issues regularly is whether Scrum teams shall stick to the event schedule even if the team’s life is uneventful? For example, is skipping Retrospectives okay?
Join me and delve into the consequences of skipping Retrospectives in less than 90 seconds.
TL; DR: The Blame Game Retrospective
There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. Turning the Sprint Retrospective into a Blame Game Retrospective demonstrates a Scrum team’s lack of skills and professionalism.
Join me and explore the reasons and the consequences of this Sprint Retrospective anti-pattern in 83 seconds.
TL; DR: Data-Informed Retrospectives
In their book Agile Retrospectives, Esther Derby and Diana Larsen popularized the idea that a Sprint Retrospect comprises five stages. The second stage refers to gathering data so that the Scrum Team can have data-informed Retrospectives.
As I have observed in practice, many Scrum Teams either limit the data gathering part of the Retrospective, thus lacking vital information. Or they invest too much time doing so, leaving little capacity to analyze the data and come to conclusions on how to best improve as a team.
Read on and learn how you can avoid falling victim to both scenarios by gathering data continuously and asynchronously.
TL; DR: A Remote Retrospective with a Distributed Team
We started this series on remote agile with looking into practices and tools, followed by exploring virtual Liberating Structures, how to master Zoom as well as common remote agile anti-patterns. This fifth article now dives into organizing a remote Retrospective with a distributed team: practices, tools, and lessons learned.
TL; DR: The Liberating Structures Immersive Workshop for Scrum
Why running a Liberating Structures immersive workshop? Since the beginning of 2019, the Hands-on Agile meetup in Berlin has been exploring how to apply Liberating Structures to Scrum. Beyond the basics, we have addressed the Sprint Retrospective, the Sprint Planning, the Product Backlog as well as the Daily Scrum.
While the initial meetups went smoothly, the last two meetups felt rushed given that we usually have about two hours. Also, the changing composition of the meetup attendees has become more challenging; less than 10 percent of the approximately 150 participants so far have attended meetups.
So, I thought it might be a worthwhile experiment to aggregate the previous meetups into a one-day immersive workshop on Liberating Structures for Scrum, built around climate change and MegaBrain.io, a struggling startup with little runway left and in desperate need of two successful Sprints. We ran that workshop last week, and this is what we learned.
TL; DR: Liberating Structures for Scrum: The Sprint Retrospective
Liberating Structures Sprint Retrospective: A few weeks ago, I started an event series with my Berlin-based Hands-on Agile Meetup group on how to improve Scrum events utilizing Liberating Structures — a set of easy to learn, yet powerful ways to collaborate as a team. The results have been fantastic so far, and I like to share these outcomes with those who cannot participate in person.
In this first post, learn more on how you can use Liberating Structures strings to improve the level of collaboration and engagement at Sprint Retrospectives.