There are many possible answers to the question: “what does Success mean for you as a Scrum Master”. And some of those answers can be very detailed and in-depth. But that’s not the only way to look at our success as Scrum Masters.
In this episode, we discuss a simple definition of success. Listen in to learn more about that simple definition, and see how that can help you improve your own work as a Scrum Master.
Featured Retrospective Format for the Week: Weather Report check-in
You use this exercise as a check-in (with a short phrase or two from each team member), or as a starter for a deeper conversation about what we might want to do differently in the next Sprint.
About Daniel Heinen
Daniel has been a Scrum Master since 2014 on a Scrum pilot at BMW. Since 2016 focusing on organizational change management, for example, facilitating communities of practices for Scrum adoption at BMW. Recently he started working as a Scrum Master and Agile Coach at Autonomous Driving BMW, who decided in 2017 to restructure according to the LeSS framework.
Scrum Masters can easily feel the Impostor Syndrome. After all, we are there to help a team, that usually works with a technology we don’t fully understand, and develops a product for a business we might not be familiar with. How can we them overcome the Impostor Syndrome? David suggests that we should focus on a set of simple questions that guide our actions. These questions help us focus on the core role of the Scrum Master, and help us acknowledge our strong points and main responsibilities as Scrum Masters.
Featured Retrospective Format for the Week: Using metaphors to help generate creative ideas
There are many metaphor formats for retrospectives. The Speed Boat Retrospective, the Amazon Product retrospective, the Sailboat Retro, the Hot-air Baloon Retro, etc. All of these formats help the team be creative about finding the impediments they want to focus on. It helps the team get out of their day-to-day scenarios and think deeper about the issues they want to tackle. Metaphors also help the teams discuss problems that they would otherwise hesitate addressing.
About David Denham
David Denham works as a Scrum Master in Workday in Dublin and is one of the leaders of the Agile-Lean Ireland community and co-organiser of the ALI conference. He previously worked as a UX lead and believes in the power of Product delivery teams being involved in Product Discovery, through practicing Design Sprints. He practices failure every single day by attempting to use his agile coaching skills with his 2 small daughters!
When thinking about what success means for Scrum Masters, David follows the ideas in the Scrum Guide. We reflect on the Scrum Artifacts, and how the Scrum Master’s job can be summarized as increasing transparency of the Scrum Artifacts.
Featured Retrospective Format for the Week: The Lean Coffee
In The Lean Coffee, a group of people select a set of topics they want to discuss, then prioritize those topics and discuss them one-by-one, ending with an action or conclusion for each item. For David, this is a technique that helps the team be fully focused on the discussion at hand. It can be a fast-paced conversation (set a shorter time-box) or a leisure-pace conversation (longer time-box) depending on how much time you have available.
About David Sabine
David is a Scrum trainer and an advisor to software development organizations. He is in demand among Canada’s largest enterprises including Scotiabank, Sun Life Financial, and Canada’s Federal Government. He formerly worked with DigitalOcean and Myplanet.com, among others. He’s been helping people with the ways they use Scrum since 2007.
As Scrum Masters, we must regularly reflect on the impact of our work. For that, Silvana suggests a few lagging indicators that can help us find out about our impact, and success as Scrum Masters. Looking and reflecting on team members change over time can help us assess and improve our work as Scrum Masters.
Featured Retrospective Format for the Week: Starfish
Silvana finds that many different possible formats can fit the teams we work with. She shares a resource (Retromat.Org) that helps us find ideas for new formats/exercises, and suggests a format that you can use this week: The Starfish Retrospective format.
About Silvana Wasitova
Silvana Wasitova, Enterprise Agile Coach, helps teams and companies achieve better results through applying and living Agile values and principles. Scrum practitioner since 2005. Silvana lives and breathes the agile value of “People over Process”, and brings that to the forefront of her coaching work with teams and companies, while focused on the client’s audacious goals and desired results. Silvana has aided multinational enterprise Agile transformations in United States, UK, Germany, Czech Republic, Slovakia, Indonesia and Switzerland with clients including Yahoo, Nestle, Skype, Microsoft, financial enterprises as well as startups.
In this episode, we explore 2 aspects of our success as Scrum Masters that Paulo developed in his career. These are simple aspects of success that, if we pay attention, can directly improve how we reflect on our work, and help us find better ways to help our teams.
Featured Retrospective Format for the Week: The Happiness Radar
Sometimes we need to help the team find the improvements that are not obvious. In this episode, Paulo shares a retrospective format that focuses on helping the team find the problems that affect their well-being, and how that can help find improvement ideas. This week The Happiness Radar is our featured retrospective format.
About Paulo Rebelo
Paulo Rebelo helps companies to improve using agile and lean principles like Scrum, XP, and Kanban. He currently works at Blackhawk Network in the U.S., helping teams succeed by building great products. His background is a developer, Scrum Master, product owner, project manager, and coach. Paulo is a CSP, CSPO and a CSM from the Scrum Alliance and PMP from the PMI.
When supporting a team with the adoption of Scrum, Liz had to consider what the goals of the team were. For that team, success was simply staying at the same level of performance. In this process Liz learned an important lesson about success for Scrum Masters: not all teams have the same definition of success, and we must be aware of what the team mates, how they contribute and accept that Scrum might not work out-of-the-box for all teams.
Featured Retrospective Format for the Week: Worked well / Didn’t work well / Continue / Goals for next Iteration
Elizabeth Christensen shares tales from the not-so-cutting-edge, bringing Scrum to Marketing. She is currently developing scrum practices for a marketing team. With a background in business management & team leadership this self-proclaimed scrappy new Scrum Master finds her way in a never-before-experienced opportunity.
In this episode, Kyle contributes some of his thoughts on metrics, and how they can help Scrum Masters measure their own, and the team’s success. This reflection has led him to define a set of metrics to assess the Agility in a team. Listen in to learn about the metrics that Kyle defines as the success barometer for him as Scrum Master, as well as for the team.
Featured Retrospective for the Week: Repeatable and focusing on positive energy
When Kyle reaches for his favorite retrospective formats he wants one that he is familiar with, and that improves the positive energy in the team. In the retrospective, as well as in other Scrum ceremonies he facilitates he asks 3 questions designed to assess how well that particular instance of the ceremony delivered value. Listen in to learn what are Kyle’s 3 questions.
About Kyle Aretae
Kyle has been programming since ’81. Teaching since ’91. Practicing Agile (Extreme Programming – XP) since 2000. Kyle is always interested first in better ways to understand things and systems. Especially interested in Complex (CAS/VUCA) Systems like building software or the economy at large.
When we discuss the success of a Scrum Master, happiness is a word that often comes up. Is the customer happy? Is the team happy? Are some of the questions we must ask ourselves, and in this episode, Faye reviews how we can ask, collect the answer for and use those to help our work as Scrum Masters.
Featured Retrospective Format for the Week: Single Word Retrospective
In the Single Word Retrospective, the team reflects on how one word impacts their way of working. In this episode, Faye shares one concrete example of what that could look like in practice.
About Faye Thompson
Faye calls herself a Scrum Master and agile coach, and she enjoys working with teams to solve cool business problems while not being jerks to one another.
As we evolve our practice, we help the team be self-sufficient. Over time, the team will be able to handle most of the Scrum process itself. But how do we detect when the team is ready for that final step in their maturity? In this episode we talk about the signs Scrum Masters can look for to detect when the team is mature enough to be self-sufficient.
Featured Retrospective Format for the Week: The Flexible Retro
When we focus on having the Retrospective as a “ceremony”, there’s a risk that it becomes just that: a ritual that has little impact. Ilya’s approach is different. In this episode we describes a very simple format, and how you can make retrospectives fun again. The Flexible Retrospective format.
About Ilya Bibik
Ilya has about 16 years experience in software development and more than 7 years experience in the Scrum Master role. On top of Software engineering, Ilya has also a background as a school teacher and military service that helps him with his Scrum Master role. Recently Ilya published a book “How to Kill the scrum Monster” that he wished he had read 8 years ago.
It’s clear that one of our jobs, as Scrum Masters is to help the team reflect. And, in this episode, Peter describes how he turns that expectation into a measure of his own success as a Scrum Master. Listen it to learn what are the signs, and symptoms that help Peter assess his own success as a Scrum Master.
Featured Retrospective Format for the Week: Oscar Academy Awards Retrospective
The Oscar Academy Awards Awards retrospective format helps the team find a new dynamic for the retrospective. It’s a fun, but insightful format that can then be followed up with an action-oriented finale that helps the team pick up the most important improvement items to, for example, avoid having an annoying story like the one that won the “Most Annoying Story of this Sprint” award.
About Peter Zylka
Peter is a freelancing Scrum Master who really loves what he does.
Peter is passionate about Agility and loves supporting teams and organizations on their way into the agile world. As a Scrum Master his goal is to enable each individual in the team to perform the best possible way and to actually understand what a team really is all about.
He starts every day with the goal to make the people around him better.