There are many aspects that we must consider when evaluating our success as Scrum Masters. Bola reminds us that the way the team acts and behaves is a clear indicator of our influence on their progress as a team. We talk about how our different stances affect the team’s performance, and how we must deliberately move from one stance to the other when the team’s evolution so requires. Listen in to learn how Bola assesses and decides to move to the right stance as a Scrum Master.
Featured Retrospective Format of the Week: Mad/Sad/Glad technique
Bola is an experienced Business and Agile Transformation Consultant, Speaker and Coach with in-depth knowledge and experience working with businesses in implementing best practice frameworks, driving changes and solving complex business problems. Bola has worked on several transformation initiatives, coached teams and Scrum Masters. He’s an Agile Coach based in Toronto.
When all works well with a team, there’s the temptation for us as Scrum Masters to think that the “team gets it”, but even if that is the case, your role, and who you are is part of that system. When you leave things will be different. In this episode, we explore what happens when the Scrum Master leaves, and the previous technical lead takes over. In this story, we will hear the anti-patterns that can easily develop when the critical role of the Scrum Master is taken by someone else.
Mo started her career in education and program management before moving into digital delivery. She’s pretty sure she was a servant-leader before she had even heard the term. Her passion is to build healthy teams and foster the all-important relationship between business and team, which allows a safe space for the magic to happen.
Success is an endless journey for Scrum Masters, but there are tools that help us assess where we are, and also what are the areas we are already successful in. We discuss a Scrum Master self-assessment tool developed by Luca Minudel and refer to the Learning Guide for the Certified Team Coach program by Scrum Alliance (not freely available).
Featured Retrospective for the Week: Mad/Sad/Glad
The Mad/Sad/Glad retrospective format, inspired by the Core Protocols is a retrospective format that helps the team discuss the issues that are causing emotional reactions. Emotions are often symptoms of other problems the team needs to process, and this format helps address those problems.
Ivo is an Agile Coach at heart. He tries to live that role every day. His view is that to be somebody like an Agile Coach is a lifestyle, attitude across everything you do. Ivo has been in IT industry about 20 years and has been a Scrum Master and Agile Coach for the last 5 years.
When looking at the systemic causes for problems we see in the team, we need to take into account many aspects: trust, metrics, conversations, relationships. Where to start? Richard suggests that we look at the Comparative Agile diagnostic and the Agile Fluency model and diagnostic. But of course, those are just starting points. A lot of the work needed to identify systemic problems is to listen to the conversations happening in the team, and with stakeholders. In this episode, Richard describes the process he uses to observe and analyze the conversations happening in the team, so that he can pinpoint systemic problems.
About Richard Kasperowski
Richard is a speaker, trainer, coach, and author focused on high-performance teams. Richard is the author of The Core Protocols: A Guide to Greatness. He leads clients in building great teams that get great results using the Core Protocols, Agile, and Open Space Technology. Richard created and teaches the class Agile Software Development at Harvard University. Learn more and subscribe to Richard’s newsletter at www.kasperowski.com.