Izis Filipaldi: The importance of action points as an Agile Retrospective outcome

As Scrum Masters, we aim to help teams progress in their ability to deliver value. However, it is important that we ask a few questions about the team behavior when reflecting on our own performance. We discuss some of the questions that Scrum Masters can ask to assess their own impact on the teams they serve.

Featured Retrospective Format for the Week: Focusing on action points

Although Izis prefers to use the 3-question retrospective format, she tends to not follow that format strictly. In this segment, we also discuss the importance of having a strong focus on defining and following-up on the action points from retrospectives.

About Izis Filipaldi

Izis’ mission is to help people to improve their knowledge and professional value inside organizations, applying the agile way of working. She has been working as an Agile Coach for more than 7 years, helping people to deliver products, developing an environment free of judgments where they can fail fast and learn faster. Continuous improvement of: people knowledge, product delivery, and work environment, are her 3 main focus on work. And she loves what she does!

You can link with Izis Filipaldi on LinkedIn and connect with Izis Filipaldi on Twitter.

Nick Stewart: Focus on people to define and measure success as a Scrum Master

When asking his own success questions, Nick prefers to focus on the people in the team and the team’s direct environment. He asks questions about how those people feel or act, and from that, he derives his own self-evaluation for the role of Scrum Master.

Featured Retrospective Format for the Week: The Sailboat Retrospective

There are many reasons why we prefer one or the other Retrospective format. And Nick’s perspective is no different. He has many reasons to like the sailboat retrospective format, and explains why in this episode.

Follow this link, if you want to explore how a previous guest used this specific sailboat agile retrospective format.

About Nick Stewart

Nick has worked in the “Projects Space” for the last 5 years, initially working with business change, then in IT using Prince 2, Waterfall and ultimately found Agile organically through pain of delivering projects using the other methodologies. More recently he has taken on a Delivery Lead role which allows him to continue to learn whilst helping teams deliver continuous value.

You can link with Nick Stewart on LinkedIn and connect with Nick Stewart on Twitter.

Sebastian Reverso: Liquid Organizations and how they help shape your Agile Retrospectives

Are you a Scrum mom? When assessing our own success as Scrum Masters, we must look not only at how the team performs but also how we get there. How we contribute to that team’s success. 

In this episode, we talk about some of the questions you can ask to learn if you are transitioning from that initial Scrum Mom role to an approach that allows the team to grow and continue on their own when you are not available.

Featured Retrospective Format for the Week: Liquid organizations, and how to adapt

When we reflect on our success or actions, we often focus on the task, and its success (or not). However, the way people contribute to the team may often be ignored. For example, a team member that is focused on helping others succeed may feel they are “not contributing”. In this episode, we discuss a different approach to retrospectives. An approach inspired by the concept of Liquid Organizations by Stelio Verzera, and that focuses on recognizing the contribution of each team member to the common success. Team members evaluate their peers’ contribution, so that the person who was focused on helping, may feel they contribute, even if they don’t work on many stories.

About Sebastian Reverso

Sebastian is from Tucuman, Argentina. He has been working as a software developer since 2012 and as a Scrum Master since 2017. 

Among his favorite activities are mountain biking and football (soccer).

You can link with Sebastian Reverso on LinkedIn and connect with Sebastian Reverso on Twitter.

Jaime Bartol: The Starfish Agile retrospective, and how it helps your team reflect

It is usually a sign of progress and success when the team is able to execute the Scrum process without needing the presence of the Scrum Master. However, that’s only part of the success definition we discuss in this episode. We also talk about the need to focus on value and to have the team feel that they own the solution they are working on. 

Featured Retrospective Format for the Week: The Starfish retrospective

When we start experimenting with new retrospective formats, the Starfish retrospective is a good place to start. It allows for several “degrees” in the responses we get from team members, and can easily be adapted for different team contexts. The 5 categories, help consider different aspects from the more traditional: what went well? Not so well? What should we try?

About Jaime Bartol

Jaime has been a ScrumMaster/Agile Coach for 6 years with experience in large organizations as well as startup teams! She has worked with frontend and data engineering teams and even brought Agile to awesome marketing teams! Jaime’s passion is about teams and using Agile/Scrum fundamentals to elevate efficiency, productivity, and joy!

You can link with Jaime Bartol on LinkedIn.

Rachel Martz: how to motivate people for change

When change processes get started, it is usually because of one or more individuals taking ownership and putting their own effort in that change process. Scrum Masters can start the process, but we quickly need to find our first “allies” or the “guiding coalition” for change. In this episode, we talk with Rachel about how we can help those individuals join the guiding coalition, and how to motivate them to help the change process progress.

Featured Retrospective Format for the Week: A Sprint Goal focused retrospective

Rachel has slowly moved away from pre-formatted retrospectives and found that fostering conversations around the Sprint Goals is the way she can help teams more effectively. In this segment, we talk about what that looks like for Rachel’s teams and share some insights on how that approach might also work for you.

About Rachel Martz

Rachel has been in digital product development for over 20 years, having performed every role imaginable. She entered the agile space 13 years ago, doing hands-on product strategy and development modernization. 

Rachel is in the data and analytics industry at the moment and loves being a Scrum Master because it’s the most impactful role she can have for helping improve people’s lives.

You can link with Rachel Martz on LinkedIn.

Angeliki Hertzfeldt: 3 aspects to keep in every Agile Retrospective

Is the team swarming? Are they talking to each other face-to-face, instead of e-mail? Those are just some of the questions that Angeliki asks when assessing the team’s ability to continue to work without the daily presence of the Scrum Master.

We also talk about some of the worrying signs that sometimes Scrum teams show. 

Featured Retrospective Format for the Week: 3 aspects to keep in every retrospective

Angeliki uses many different formats for the Retrospectives she facilitates. But in all of those she tries to keep certain aspects fixed. She shares with us 3 aspects that help her constantly change the format, but keep certain things the same so that the retrospective also feels familiar. 

About Angeliki Hertzfeldt

Angeliki finds that Scrum has transformed her into a better person: in the working environment, with friends and strangers, in social activities, and with her family, as a new mum.

You can link with Angeliki Hertzfeldt on LinkedIn and connect with Angeliki Hertzfeldt on Twitter.

Joost Mulders: Self-reflection using the Lego Agile Retrospective

According to Joost, seeing our own value is a hard task. How to reflect, what to look at, and how to be sure? 

In this episode, we discuss how Scrum Masters can reflect on their contribution to the team, and what kind of behavior to look for that helps Scrum Masters be sure that they are having a positive impact on the team.

Retrospective Format for the Week: The Lego retrospective that uses self-reflection

When teams enter a retrospective, they usually expect to work on the process. Find improvements, plan some changes, and move on to action. In this segment, we discuss a different type of retrospective, one that focuses on the team’s own self-image, and how it helps the team learn about its team members in-depth.

About Joost Mulders

Joost has been an agile practitioner since 2008 and is continuously uncovering new ways to help teams and organizations on their agile journey. He’s taken several roles in that journey, such as Scrum Master, agile coach or management coach. He strives to create work-life fusion with agile, ultrarunning and filmmaking as the main ingredients.

You can link with Joost Mulders on LinkedIn and connect with Joost Mulders on Twitter.

Remy Fletcher: The Lean Coffee as an Agile Retrospective format

Can the team work well without you? This is only one of the questions that Remy asks when evaluating his own contribution to the team’s progress. But there are other questions. In this episode, we discuss questions we can ask ourselves that help us understand how autonomous the team really is. 

Featured Retrospective Format of the Week: Lean Coffee

The Lean Coffee format has been a regular on the podcast. In this episode, we discuss how this format can help teams execute a retrospective in a short time, but still be focused on creating concrete improvement ideas to take on.

In this segment, we also refer to the Kudos practice whereby the team members highlight positive behavior and attitude by other team members.

About Remy Fletcher

Remy is a Scrum Master at a Fin-Tech corporation outside of Boston. Currently working with 3 scrum teams with a focus of migrating individual products onto a centralized, scalable platform.

You can link with Remy Fletcher on LinkedIn and connect with Remy Fletcher on Twitter.

Micah Stamper: 2 types of questions to assess Scrum Master success

The process of reflection Scrum Masters go through, helps us find our own personal and contextual definition of success. In this episode, Micah describes the types of questions he asks of himself when assessing his success as a Scrum Master.

Featured Retrospective Format for the Week: The 3 questions that focus teams on concrete changes

Micah likes simple formats, and he recommends a format where we focus on 3 questions that help the team members reflect on concrete things they’d like to change. Listen in to learn about what questions he asks his teams.

About Micah Stamper

Micah worked in technology for about 7 years. He has a background in lean principles and how to bring that to technology. Has done everything from Project Management to Software Engineering, Leadership, and Scrum Master.

You can link with Micah Stamper on LinkedIn and connect with Micah Stamper on Twitter.

Rahul Bhattacharya: Follow Scrum team progress with the Agile Fluency Model

In this episode, we review 5 different aspects that Rahul follows with each team he works with. From how the team delivers each Sprint, to the interaction with the Product Owner, we discuss different aspects that Scrum Masters should pay attention to.

In this episode, we also refer to the Agile Maturity Model. There are several maturity models you can follow, I’d recommend starting with the Agile Fluency Model by Diana Larsen and James Shore, which has been introduced here on the podcast.

Featured Retrospective Format of the Week: Radar chart for team self-evaluation

There are many different exercises for teams to run a self-evaluation exercise. The Radar chart helps the team choose several (typically 5-7) items they want to follow-up on, and evaluate themselves in each topic. If you collect similar charts over time, you will have a graphical representation of how the team has evolved in those core skills or aspect.

About Rahul Bhattacharya

Rahul Bhattacharya is currently working as an Agile Coach at trivago. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback.

He is also the host of a podcast about Agile, called the Agile Atelier.

You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya on Twitter.