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.
As the team takes more initiative and responsibility, the Scrum Master role changes. That, in itself is a measure of success for us as Scrum Masters. However, the real measure of success comes from the team delivering consistently value to the market, and following the Scrum values.
Paulo has worked in the IT industry for 15 years. He started as a web developer for a local bank. His Agile journey began in 2015 and he’s been a Scrum Master for 3 years. Paulo is also a Certified Professional Scrum Master from Scrum.org (PSM I).
As Scrum Masters the ultimate sign of a successful impact on the team we serve is that they are able to tackle the obstacles they face on their own. They may request help from the Scrum Master, but are confident they can solve their own problems without external help if that is needed. When trying to help the team be independent however, we must help them through the multiple challenges, and pitfalls that they will face. In this episode we talk about how Claudia focuses on helping teams get to a point where they can act on their own, independently, even without a Scrum Master.
Featured Retrospective Format for the Week: Powerful Questions
In this episode we explore a format around the Powerful Questions coaching approach, and how that can help teams go deeper into their own thoughts and beliefs. It is by questioning our beliefs that we can truly evolve in our practice. The Powerful Questions format that Claudia suggests is one possible trigger to start questioning beliefs that are no longer serving us as we expected.
About Claudia Toscano
Claudia is an Agile Coach and Scrum Master since 2014, she in charge of the Agile Transformation at EPM with a team of 5 other people. Agile and being Mom are the things she enjoys the most.
We hear it often: success is when the Scrum Master is no longer needed. Is it though? In this episode we explore what the Scrum Master responsibility is when the team starts “flowing”. The role of the Scrum Master is not restricted to dynamics of the team, it also includes the collaboration aspects with the rest of the organization, and many other “enabling” factors.
Listen in to learn about Darryl’s experience.
Featured Retrospective Format for the Week: The Lean Coffee Format
In this episode we talk about a Retrospective format called Lean Coffee, a format that focuses on surfacing and tackling the issues that teams want to focus on. It’s a great format to host without much preparation, as the team comes up with their own ideas and prioritizes the topics to discuss, having the timeboxed conversations drive them to the actions they want to take during the next sprint to improve their work. In this episode we also mention the Starfish retrospective format.
About Darryl Sherborne
Darryl is an IT professional specialising in Kaizen (continuous improvement), Agile delivery and coaching, Lean Thinking implementations and more recently applications of DevOps and Data Science. Darryl can also be found singing in rock/pop choirs, and watching or reading anything in the realm of Sci-Fi / Marvel.
Featured Retrospective Format for the Week: The Ice Breaker challenge
Instead of focusing on one single format, Joanna inspires us to look at the “ice breaker” exercises we use and seek new ones. After listening to this episode, I’m sure you will want to try several different ice breakers for your next retrospectives!
About Joanna Koprowicz
Joanna is an Agile Enthusiast with a burning passion to help organizations work smart not hard. She is one of the co-organizers of Agile-Lean Ireland Community. Currently she works as a ScrumMaster in Dublin.
“Don’t get frustrated, progress takes time”, that’s a line Max wants you to remember when you start looking into more detail to what it means to be successful as a Scrum Master.
Set aside a time, and follow Max’s approach to evaluating your progress, as well as the team’s progress. In this episode we discuss some of the aspects you may want to consider when evaluating your work, and success as Scrum Master.
Featured Retrospective Format for the Week: Identify Boring Stories
This Retrospective format helps the team find the not-so-obvious problems that they often face when implementing stories. By identifying boring stories they are finding problems in collaboration as well as the enabling practices that are missing, and would make work more fun if they were there.
About Maximilian Fritzsche
Maximilian worked as a Scrum Master for several years and believes that the way to look at the role is to always have in mind the following quote: “Keep moving forward” – his favorite quote, and what he tries to do every day. “One step at a time!”
Scrum Master is a relatively new role, Scrum itself started the rise to popularity in the early 2000’s. That means that, as Scrum Masters, we are performing a relatively undefined role.
Abbas suggests that, as part of our understanding and definition for success we should ask a few questions that help define the role for us and the organization we work with.
Abbas suggests we consider the role from 3 different perspectives: The tactical side; the strategic side; and the culture side.
Listen in to learn more about what each of these perspectives entails.
Featured Retrospective Format for the Week: MAD/SAD/GLAD retrospective and other techniques
The MAD/SAD/GLAD exercise is a simple approach to cover the different aspects of the previous sprint in a way that elicits emotional thinking. The emotions we have towards the sprint events will help elicit problems, as well as achievements the team experienced during the Sprint.
During the retrospective discussion we also mention other simple, yet powerful techniques that you can use when planning your next retrospective.
About Abbas Ghahremani
Abbas is a Scrum Master who enjoys coaching individuals and teams who are on a journey of developing an agile mindset, focusing on values and principles which will make them work lean, collaborate and generally enjoy work more!
He calls himself an agile and product person focusing on delivering value early and often to customers.