When we are starting our journey as Scrum Masters, one of the ceremonies that most scares us is the retrospective. There’s so much hanging on that ceremony, from the need to get an action that leads to improvement, to having the team engaged and everybody participating. In that context, it’s natural that we try our best and prepare extensively for the Retrospective. However, there’s a point when preparation is just too much! In this episode, we talk about what is that limit, and how to look at Retrospective facilitation in a way that leaves space for the team to take ownership, and be active in the Retrospective.
About Franziska Moenster
Franny (short for Franziska) loves seeing the power of building strong performing teams that build products in a customer centric way. She’s been working as a Scrum Master/Agile Coach for over 5 years. Profiting from her hands-on experience on scaling agile across teams and her joy of trying out new things she is always inspecting and adapting on an organizational level as well! On a personal note, she has recently moved to Tenerife to follow her passion of freediving.
Mher prepared a retrospective for his team, but 5 minutes past the starting time, there were only a few team members in the room. He looked around and saw that the team members that were present, were not fully engaged. “Something is wrong here, he thought… In this episode, we explore why sometimes team members don’t communicate and discuss what might be the reasons, and how to avoid it.
For Christmas week 2020, we have a special treat for you. Yves Hanoulle and I interview great Agilists and Scrum Masters that you will probably not hear from in your local Agile conference.
These are people that are really pushing the state of the practice, and we want to bring their forward-looking, and hopeful ideas to you in our Christmas Special Week for 2020.
When Yogini took on her Scrum Master journey, she noticed that there was more friction in the team. Curious, she looked into the reasons for that friction. After all, they had just left Waterfall-like ways of working behind. What was causing that friction? Was it Agile? As she looked more into it, she found that Agile had something to do with it, but the real reason for the friction between team members was that they were, for the first time, honestly discussing the problems they were facing. They were no longer apathetic, and that was visible in the level of friction between them.
Another side effect of Agile adoption, Yogini noticed, was that the team was much more productive, “they did more in a month, than I thought was possible in six!” Yogini shares.
A key lesson for Agile teams: speak freely
This story led to a key lesson for Yogini. Agile teams improve and transform their ways of working when they speak freely and aren’t afraid to tackle tough conversations.
When teams finally take on the difficult topics that are impeding their progress, they often fail to reach consensus. However, as Yogini reminds us, that’s no reason not to act. “Buy-in does not imply consensus!” She reminds us.
Retrospectives as the engine of growth and learning
Retrospectives are the aspect of Agile methodologies that Yogini wants to highlight as key for teams and individuals working in an Agile environment.
In the spirit of self-improvement, Yogini mentions and recommends the book Atomic Habits by James Clear. She reminds us that part of the Scrum Master’s responsibility is to improve herself, otherwise, improvements elsewhere are less likely to happen.
The Christmas Agile Message from Yogini Moodley
Yogini asks us, in this festive season, to take time to reflect, and practice being mindful of what we do, say, and feel. The challenge she leaves us with: “think about the habits you have at the moment, and what you’d like to leave behind, in 2020”
Merry Christmas friends!
Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today!The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experiences: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!
About Yogini Moodley
Yogini is a certified Scrum Master and agile practitioner, with extensive experience in the financial services industry, in roles that encompass both business and technology. She is passionate about enriching the lives of people and nurturing and growing teams to deliver value to their customers, and an active member of the agile community locally and globally.
When we start facilitating retrospectives (I still remember the first ones I facilitated), we are often focused on getting the structure right, and we may forget that we can uncover insights at any time during the retrospective. This module is all about increasing our chances of facilitating a productive and effective retrospective.
Team Norms, a productivity and engagement tool for Scrum Masters
In the second instalment of the Agile Retrospectives Masterclass with David Horowitz, we talk about the 5 phases of a successful retrospective, and share tips and ideas for each of those phases to ensure you are prepared and get the team to find and act on breakthrough improvements.
It all starts with a simple check-in: “Set the Stage”, Phase 1 of a successful retrospective
When we start a retrospective, usually at the end of a Sprint, the team member’s minds might be on that last bug they just closed, or the story that didn’t get delivered, or the feedback they just got from stakeholders. The Check-in phase of the retrospectives helps all the team members, and the facilitator to get into the retrospective mood. To forget the open threads that will need to be picked up later, and focus on the question: “How can we do even better in the next Sprint?”
Gathering Data and Generating Insights, the core of an Agile Retrospective
If we want to enable deeper conversations, we need to be aware that the information that is shared will directly affect the quality of the conversations. Therefore, Agile Retrospectives require special attention to the “gathering data” phase. There are many ways to gather data, and some might even happen during the Sprint, instead of during the retrospective.
During the retrospective, however, we will visualize that data and help the team make sense of it.
In this segment, we talk about the timeline exercise, and how to use emotional-queues to help uncover important pieces of information.
When the data is visible and understandable, then the team focuses on finding insights by analyzing the data and generating possible connections and causal links. Here the challenge for a Scrum Master is to prevent the team from jumping too early into solutions before they deeply understand the problem they are trying to solve.
David shares some tips to help prevent the team from discussing solutions before they have a shared understanding of the problem. We talk about The 5 Why’s technique, but there are many more.
Making Retrospectives Impactful: Deciding what to do
Many teams fail in Phase 4, Deciding what to do. But they might fail in quite different ways. For example, some teams might want to commit to too many items at once, while other teams might not commit to any improvement. And finally, the worst problem: those teams that commit to improvements, but work on none of them.
Great teams, understand well how many improvements they can take from a retrospective, and are clear on the commitment, maybe even including the improvement ideas as items on their Sprint backlog.
In this segment, we talk about the ICE method for prioritizing improvement ideas and the importance of brainstorming several solutions before deciding what to do. It’s also important to use methods of consensus generation when there are several options that seem equally valuable. The commitment of each team member to the solution to be tried will directly impact their commitment to the work to be done for that solution.
At the end of the retrospective, our goals are to provide closure, a sense of achievement, and energy for the work ahead.
How can we do that? In this segment, we talk about the “retro on the retro” and the “gif check-out”. Two simple approaches that help the team feel a sense of accomplishment, and also get better at doing future retrospectives.