This is the story of a team that, even if they had a long history of working together, was faced with a new reality: remote work! During the pandemic years, many teams had to change from co-located work to remote work, and that change had big impacts on their work, and relationships. We discuss the lessons learned by Franny about teams that made that transition, and what is usually missing that leads to problems!
Featured Book of the Week: The Five Dysfunctions Of A Team by Lencioni
In The Five Dysfunctions Of A Team by Lencioni, Franny found a reminder that conflict is a necessary, and – if managed correctly – productive part of the team’s development. We discuss how everyone in the team has a different relationship with conflict, and why Scrum Masters should take that into account when observing, and intervening in team conflicts.
How can Angela (the Agile Coach) quickly build healthy relationships with the teams she’s supposed to help? What were the steps she followed to help the Breeze App team fight off the competition? Find out how Angela helped Naomi and the team go from “behind” to being ahead of Intuition Bank, by focusing on the people!Download the first 4 chapters of the BOOK for FREE while it is in Beta!
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.
Dana Pylayeva, will host the coaching track at the summit, where we explore some of the hard lessons we need to be aware of when adopting coaching in our practice
Ayodeji Ishola, hosts a track on the state of Agile in the African continent, and will be showcasing talks that address the cultural specific aspects of Agile in Africa
Mariana Trigo, will have 6 sessions on career advice for Scrum Masters and hiring advice for those hiring Scrum Masters. She’ll have a special focus on how you can get into the Scrum Master role even if you don’t have a tech background.
Yves Hanoulle, the co-author of the Tips from The trenches audiobook, hosts a track on Hybrid work, very topical now that we have our teams remote most of the time
Martin von Weissenberg, will share patterns of scaled agile. Not the frameworks we always hear about, but rather practical, down-to-earth advice for specific needs when we scale agile
Accepting and learning to deal with Social Complexity in Agile adoption
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.
In the first installment of the Agile Retrospectives Masterclass with David Horowitz, we talk about the basic setup for a successful retrospective. It all starts with what David calls the triangle of success: People, Process/facilitation, and Follow-through.
How to set up your Agile Retrospectives for success with the right people