One way to look at success for Scrum Masters is to ask the team about the contribution of the Scrum Master. Asking them directly, however, can lead to “polite” answers, and avoiding the problems that need solving. In this episode, we talk about other signs that tell us that the team appreciates the contribution of the Scrum Master, and we talk about concrete tools Scrum Masters can use to continue to grow and succeed with their teams.
Featured Retrospective Format for the Week: The Wonder Question Agile Retrospective Exercise
When a Scrum team is stuck and needs help to find improvements, we can ask them to imagine that something “magic” has happened. Then, we ask what does the team look like now that the “wonder” has happened. With this exercise, we help teams “think outside the box”, without ever having to bring them outside the box. This exercise appeals to the imagination and helps teams imagine a better team that they are all part of.
About Ines Stuppacher
Ines Stuppacher is a passionate team coach and Scrum Master. Working with people challenges and inspires her every day. Her coaching mentality is an important pillar of her life and work. Ines does not impose things on people but rather sees herself as a waiter of options. She strives to show up as her full human self in all kinds of situations and with that fosters real connections with other people.
Featured Retrospective Format for the Week: The Sailboat Retrospective Format
Using the Sailboat Agile retrospective exercise helps teams get out of the “clinical” mindset and find improvement opportunities. When we use the drawing of the sailboat as a fun check-in exercise we also get the team in the mood to explore their ways of working in a relaxed atmosphere. These make the Sailboat Agile retrospective exercise a complete retrospective for the team.
About Ben Clark
Ben’s career has spanned from working assembly at Ford Motor Co, IT consulting, DSL Internet provider using wireless building-to-building antennas, systems administration and engineering, data center floor work, DevOps, cloud engineering, cloud architecture, scrum master, people-leader, and agile coach.
When it comes to being a successful Scrum Master, a happy team is arguably the most common answer. However, for Scrum Masters, that is not enough. In this segment, we talk about how Scrum Masters should also focus on the product the team is developing. Is the product being successfully developed as well?
In this segment, we refer to a tool that helps the team focus on the impactful ways to help the product succeed: Impact Mapping.
Featured Retrospective Format for the Week: Guess Who? A game to learn more about the Sprint
It is sometimes hard to focus on the details of what happened during the Sprint. However, when we fail to do so, the team and the organization lose out on a big opportunity to improve how they work. With the “Guess who?” Agile Retrospective exercise Dragana helps the teams – in a fun and entertaining way – explore the detailed events of the Sprint, so that they are ready to discuss improvements and take concrete actions out of the retrospective.
About Dragana Hadzic
Dragana is an agile enthusiast who believes communication is critical for success in everything, including software projects. A Scrum Master and an Agile Coach with broad experience in IT industry and different leadership roles. Passionate about everything that brings positive energy and enables people to achieve great results.
Isaac focuses on the team’s self-image as a way to reflect on his success as a Scrum Master. For that he uses a survey-style NPS questionnaire where he asks the team members how likely they are to ask other people to join their team.
Featured Retrospective Format of the Week: Tools for dynamic retrospectives
For Isaac, Agile Retrospectives are not only about finding the next improvement actions. They are also about building a team spirit that carries the team forward into the next sprint in a state of energized motivation. In this segment, we talk about many tools that you can use to keep your Agile Retrospectives fresh and high-energy. We refer to Retromat.org and Tastycupcakes.org, two sites that you can use to find formats that work in your team and your organization.
About Isaac Garcia
Isaac is a passionate Agilist who builds teams with heart and walks their journey together. His driving goal in life is to invest in and impact world changers. He has a lot to learn but is enjoying the discovery in the journey.
Is your team more like a Golf team or a Hockey team? That’s one of the questions David asks himself when assessing his impact as a Scrum Master. Checking the Scrum Guide, for a list of responsibilities may also be a good way to get started assessing your success as a Scrum Master, but don’t forget to adapt to the local reality, a core idea of Agile that also applies to the Scrum Master work.
Featured Retrospective Format for the Week: The Starfish Retrospective
The Starfish retrospective is a format that David finds leads more often to concrete actions, the final goal of a retrospective. In this segment, we also talk about the importance of having many formats in your toolbox, so that the retrospectives don’t get boring and stop delivering results.
About David Gentry
David Gentry is an Agile Coach and Scrum Master. He has served in a variety of other roles in his career including developer, data analyst, business analyst, quality analyst, and project manager. In his free time, he can be found playing bass guitar and interpreting how groove applies to life and agility.
Long suggests that Scrum Masters collect feedback from the team to assess their success. The method he suggests is the team NPS: “How likely are the team members to recommend that others join the team?” We also talk about how it is important to measure and reflect to reach a successful outcome for our work as Scrum Masters.
Featured Retrospective format of the Week: Liberating Structures
Retrospectives follow a specific set of activities, from the check-in to get everybody focused and in the mood to reflect, to the data gathering. These activities can be organized in many ways. In this episode, we talk about Liberating Structures, a set of activities that you can use in any of the steps of the retrospective.
About Long Suciu
Long is driven by a passion to help people unlock their potential and discover their own capacities. He has spent the past 20 years helping teams and organizations find and put in place better ways of working.
Scrum Master’s success is dependent on the team’s approach to solving their own problems. In this episode, we talk about how teams that take ownership of the process, make decisions on their own and find their own incremental improvements are a sign of a successful Scrum Master. But how do we get there? In the episode, we talk about tools that help Scrum Masters succeed.
Featured Retrospective Format of the Week: Wow, Wandering, Worried. Artifacts, events, roles
The second agile retrospective format is the “Picture retrospective” (example: The Sailboat Retrospective exercise). In this segment, we specifically talk about the use of pictures or drawings as check-in as well as data gathering and decision exercises.
About Katy Cabral & Joseph Contreras
Katy has over 14 years of software delivery experience, serving in roles ranging from analyst to developer, project manager and for more than 6 years, also Scrum Master. Her Scrum experience has been mostly with distributed teams working across multiple time zones. She hopes to someday have the opportunity to travel to meet her colleagues in China, but for now, Katy enjoys reading about creative methods to keep her team engaged.
Featured Retrospective Format for the Week: The Island Expedition metaphor format
Nick likes to focus on creativity for the retrospectives he facilitates. He’s found several metaphor-focused formats that work, but one he especially likes is The Island Expedition.
Metaphor-focused formats help the teams be more creative by taking them out of their regular context and pushing them to imagine themselves in a different context.
About Nick Vitsinsky
Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.
One of the most common, and sometimes forgotten, sensors for a Scrum Master is the daily meeting. Mili asks us to consider how the team members show up for the daily. Are they excited about the day that is starting? Or happy about the results of the day that is ending?
How are you using the Daily stand-up to assess your impact on the team?
Featured Retrospective Format for the Week: KALM
Keep your teams focused on the problems they want to solve with this simple format. KALM stands for Keep, Add, Less, More. These are the keywords that Mili asks the team to consider when reflecting on the previous Sprint.
About Mili Shrivastava
Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.
Continuing the thread from Monday’s episode with Jassy, we discuss how feedback from the team is a critical source of information and inspiration for Scrum Masters. In this episode, we discuss how to collect feedback from the team, so that the feedback is not biased by your presence, and what are the 4 dimensions of Scrum Master success for Jassy
Featured Retrospective for the Week: Games that inspire insights
Jassy calls himself “not a friend of retrospectives by the book”. He claims to rarely use a “vanilla” format from somewhere else, but prefers to facilitate retrospectives that feel like a game, like a fun thing to do. We discuss metaphor games, and how they help teams find insights they would not find otherwise.
About Jassy (Jan-Simon Wurst)
Jassy moved from developer to being a Scrum Master and then a freelancer. He calls himself: the person to contact for help in On-Boardings, as well as a friend of bottom-up, power to the people! No top-down, no micro-management. No despotism in agile software development.