Miguel shares with us his approach to define and reach a successful outcome of his work. We explore the role of metrics in defining what we should focus on and improve. After all, without data to backup your ideas, you are just another person with an opinion.
Featured Retrospective format for the week: Start-Stop-Continue
When looking at what to improve, what to amplify in our teams, the start-stop-continue retrospective format helps the team identify not only what they want to change or improve, but also those things that are working well. When we find what is working well, we can then amplify that. Select items from the Continue section of the retrospective and ask: how can we benefit even more from this technique?
About Miguel Santos
Miguel is a Brazilian living in Germany and currently Scrum Master for two teams at NewStore. He believes that there is no single methodology (agile or not) to lead projects and teams to success. Because of that, he would like Scrum Masters to be less biased when working with their teams.
Richard’s perspective is that our Scrum Master success is directly linked to the success of our teams. That much we can all agree. But how do we get there? We discuss the perspective that we need, as Scrum Masters, to help our teams achieve a successful outcome.
One possible tool to use when helping teams focus on the good things, and how to improve them further, is the practice of distributing Kudo Cards from Management 3.0.
Retrospective format of the week: The Perfection Game
The Perfection Game is also one of the Core Protocols that help teams focus on improvements, rather than what is not working in their teams. The process is:
Rate your team from 1 to 10, where 10 is best
Say what you like about the team at the moment
Describe what would be needed to get you to rate it as a 10
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.
At the start of her journey, Krisztina did not measure success. Later she started measuring many things and making those metrics visible. Over time, she realized that the team benefited from that information and she was also able to assess her own impact on the team. Listen in to learn how Krisztina started using the metrics for her, and her team’s success.
Retrospective format of the week: Simple, yet effective format and a special tip
Good facilitation is a major part of a good Retrospective. This week Krisztina introduces the Scrum Games format for the Retrospective, and shares a very special tip that makes Retrospectives the best moments of the Sprint for the team.
About Krisztina Sajgo-Kalo
Krisztina is a Senior IT manager with experience of several aspects of IT management on different levels as well as methodologies used. Originally from Hungary, she has worked in many countries. First as a tester, the project manager, test manager and many other roles.
When defining success we often look for metrics that help us assess the progress of the team. That’s ok, but are you looking at the “how”? How is the team achieving that success is also important? So Viyoma asks 4 different questions that help us ensure that not only are we getting the “measurable” success, but we are also helping the team find their “sustainable pace”.
Retrospective format: 3 questions with written answers
Viyoma’s go-to retrospective format is simple enough. But she uses a practice that helps the team members reflect ahead of the retrospective: write the answers down ahead of the retrospective session. This helps the team reflect with more impact, and come up with solutions that are developed over time, not just the last-minute ideas that many retrospectives end up producing.
About Viyoma Sachdeva
Viyoma has over 11 years of experience in Software and Product development across different domains and phases of software development cycle. She is a certified Scrum Master and Product Owner and has worked in an Agile delivery model for the last 6 years. Her experience includes many different domains like Marketing, manufacturing, retail and Public sector and she has worked in a patent of Epidemic disease predictions.
Viyoma believes that the Agile mindset and practices are keys to solve complex problems.
Our role as Scrum Masters is to help teams develop. Specifically, we need to help them become high-performing. Accomplish their mission in a way that they can be proud of. But how do we get there? How do we help teams develop that level of competence and action? In this episode we review how we can help teams grow and develop. We also discuss the tools we can use to help teams reach a high-level of performance.
Featured Retrospective format: The Starfish Exercise
For those moments when Start/Stop/Continue is not enough. The Starfish exercise can also think about what you want to do more of (amplify) and the things you need to continue to do, but may need to reduce (dampen). Check this episode for the detailed facilitation ideas.
About Susan McIntosh
Susan McIntosh is an agile coach and scrum master, especially interested in training and agile transformations – both fast and slow. She finds analogies to improving workplace culture in her experience in theater, teaching, cooking, and parenting. Susan is an active participant in the agile community in Denver, Colorado.
The “obsolete” Scrum Master is a definition of success that many of our guests have described in the past: the Scrum Master isn’t needed anymore. But Sebastian has a different take on it. And he also shares concrete tips on how to assess if a team has indeed out-grown their Scrum Master.
Featured Retrospective format: Sad/Neutral/Happy
In this episode we review Sebastian’s go-to retrospective format when working with the teams he supports. Listen in to learn how he runs this quick, yet effective retrospective format.
About Sebastian Hitzler
Sebastian works as a dedicated Scrum Master for two delivery teams at Fidor Solutions in Munich. The team members are from 10 different countries and spread into 3 different locations in Germany, Spain and Ukraine. Fidor enables clients to become digital banks based on their ecosystem. Sebastian also works with the wider organisation to help them transform with lean and agile.
What is success for a Scrum Master? This is the #1 question Barry gets in his trainings. In this episode we talk about his answer to that question and how we can enable one of they key patterns in Scrum: team self-organization.
Barry, the learning facilitator as he calls his blog, considers himself a 100% Scrum Master. It’s such a comprehensive and interesting role that he gives it his full focus and keeps learning and discovering new aspects every day!
As Scrum Masters we are intimately familiar with Retrospectives. We plan, organize and facilitate retrospectives for our team members and even larger chunks of the organization. But when was the last time you did your own personal retrospective? Leading by example is a concrete path for success so do the same things you ask the team to do. In this episode we discuss concrete examples of “leading by example” with Joe Anderson.
Ask the team to think of a movie that illustrates what happened in the previous sprint
Ask each team member to review the Sprint as if it was a movie
List down the “ups” and “downs” with the team member speaking
Dot-vote to select the concrete focus for the next Sprint
Help the team decide on a concrete action to tackle the key topic they identified in the retrospective
About Joe Anderson
Joe is a Scrum Master at a small travel technology company with a passion for bringing out the best in people and building deep relationships. He works hard to foster an environment of safety, fun and learning with a focus on relentless improvement.
We want to help teams and organizations succeed. This is the focus of our work as Scrum Masters. But here’s the thing, sometimes the team needs to risk failure to go beyond the established patterns of behavior. In this episode, Arif explains the role of discomfort in the growth of the team and the Scrum Master, as well how to avoid going beyond the breaking point.
In this episode, we discuss the technique of “Role Playing” as a method to help the team understand their own behaviors.
About Arif Bobat
Arif is an experienced Scrum Master with a passion for enabling teams to achieve their potential, Arif loves challenging situations. In the last 5 years, he has been made redundant twice and fired twice. He is not afraid of speaking up when he sees anti-patterns and/or a lack of willingness to change behaviors.
For more than 10 years, Don has been a scrum master and coach working in different sectors in London and across the UK as an independent consultant.
With a background of 10+ years in several development roles for web and finance systems, Donald has a good technical knowledge of modern development techniques, and can quickly build rapport and respect with development teams, understanding their issues and helping them to find the right solutions.