Nisha Balwatkar on 2 tools to help measure your Scrum Master success

Who to involve when evaluating our success as Scrum Masters? In this episode, we review the critical stakeholders, and how to involve them in our own self-evaluation.

In this episode, we refer to the Niko-Niko Calendar and the Happiness timeline, two of the tools you can you to evaluate your success as a Scrum Master.

Featured Retrospective format for the Week: What was good / bad and what actions should we take?

The Good/Bad/Actions format is a simple, yet effective format. Nisha explains how to facilitate this format in a short time frame and how Scrum Masters can prepare to host the retrospective.

About Nisha Balwatkar

Nisha started her career as a programmer for the love of logical reasoning and technology and soon found herself trapped in the mismanagement of software teams affecting the work and efforts put in by the teams. She always had a feeling she could fix it and eventually moved to be a scrum master. She enjoys helping out teams and see the joy of success by identifying and fixing small things.

You can link with Nisha Balwatkar on LinkedIn and connect with Nisha Balwatkar on Twitter.

Eddie Kenny: a simple success definition for Scrum Masters

When we can help a team get to a point where they can release software “on demand”, that’s when we’ve had an impact on the team and been successful in our role of Scrum Master. But that’s just the end goal. As Scrum Masters there are a lot more issues to consider, and Eddie explores those in this episode.

Featured Retrospective Format for the Week: What went well / not so well

Eddie is a fan of changing the format of the retrospective often. However, when he needs to go back to a familiar format he prefers the “What went well / no so well” simple Retrospective format.

But beware of the “too many actions” anti-pattern!

About Eddie Kenny

Eddie is an agile coach who has been working with Agile since 2004 using XP, Scrum, Lean, Kanban & Scaled Agile. He coaches teams, scrum masters, product owners, leaders, coaches, organizations and little humans. He likes teaching agile with Lego & games and is also co-founder of the LeanAgileBrighton conference.

You can link with Eddie Kenny on LinkedIn and connect with Eddie Kenny on Twitter.

Ivo Peksens on tools for defining Scrum Master success

Success is an endless journey for Scrum Masters, but there are tools that help us assess where we are, and also what are the areas we are already successful in. We discuss a Scrum Master self-assessment tool developed by Luca Minudel and refer to the Learning Guide for the Certified Team Coach program by Scrum Alliance (not freely available).

Featured Retrospective for the Week: Mad/Sad/Glad

The Mad/Sad/Glad retrospective format, inspired by the Core Protocols is a retrospective format that helps the team discuss the issues that are causing emotional reactions. Emotions are often symptoms of other problems the team needs to process, and this format helps address those problems.

We also talk about Kudo Cards from Management 3.0 as a way to help teams increase empathy and energy.

About Ivo Peksens

Ivo is an Agile Coach at heart. He tries to live that role every day. His view is that to be somebody like an Agile Coach is a lifestyle, attitude across everything you do. Ivo has been in IT industry about 20 years and has been a Scrum Master and Agile Coach for the last 5 years.

You can link with Ivo Peksens on LinkedIn and connect with Ivo Peksens on Twitter.

Richard Griffiths on 4 clear success signs for Scrum Masters

When thinking about the role of the Scrum Master, Richard comes up with 4 clear signs that indicate we are on the right path with the teams we work with. In the end, Richard says, we must do ourselves out of a job to be successful Scrum Masters.

Featured Retrospective of the Week: The Amazon Product Review retrospective

Richard suggests the Amazon Product Review retrospective format. And although Retromat suggests this can be used as a “check-in” exercise, we can also use it as the core exercise for the retrospective.

In this episode, we refer to the Agile Retrospectives book and the retrospective outline defined in the book.

About Richard Griffiths

Lapsed software developer, agile and scrum learner, tenor, drummer.
Richard guides and coaches Scrum Teams and organizations on how to use Agile/Scrum practices and values. Helping to teach, facilitate, collaborate & mentor software development teams, enhancing their agile maturity through coaching technical practices as well as the ceremonies and techniques. Richard likes to help teams and organizations obtain higher levels of maturity, at a pace that is sustainable and comfortable for the team and organization.

You can link with Richard Griffiths on LinkedIn and connect with Richard Griffiths on Twitter.

Rade Zivanovic on success metrics for Scrum Masters

When thinking about the aspects that define our success, measuring the critical aspects of our work needs to be part of it. Rade challenges us to try to measure those things that we think we need to improve. We talk about how to measure interactions and the right kind of interactions in the team and between team and stakeholders. Are you measuring the key aspects of your contribution as a Scrum Master?

Featured Retrospective format for the week: Three little piggies

The Three Little Piggies retrospective format focuses on risk management. Asking us to consider what are our Houses of straw, Houses of sticks and the solid House of bricks. And why not ask: who or what is our big bad wolf?

About Rade Zivanovic

Rade is a compassionate Scrum Master, who enjoys helping and supporting teams in their work and seeing them succeed.

You can link with Rade Zivanovic on LinkedIn and connect with Rade Zivanovic on Twitter.

Massimiliano Fattorusso shares 3 aspects to help you create your Scrum Master success definition

When it comes to being a successful Scrum Master, we need to have a clear definition that helps us make regular decisions about where to put our focus. In this episode, Max shares with us 3 aspects that he has in mind and reflects on when it comes to assessing his progress as a Scrum Master. We also talk about concrete practices that Max has found help reach his own definition of success.

Featured Retrospective Format for the Week: The Pre-mortem

Retrospectives are usually about what has happened. How the Sprint went. How the release went. However, sometimes it is useful for the team to reflect on their near future. The Pre-Mortem Retrospective format focuses on that near future. In this episode, Max explains how you can use that format to help improve cross-team collaboration in a multi-team environment

About Massimiliano Fattorusso

Massimiliano has a strong interest in agile methodologies and lean principles. He is keen on sharing lessons learned as a speaker at international and local conferences. Empathy, creativity and drive to innovate is part of his identity. Massimiliano is not afraid of addressing the uncomfortable truth, that’s how he helps bring teams forward.

You can link with Massimiliano Fattorusso on LinkedIn and connect with Massimiliano Fattorusso on Twitter.

Donna Marie Lee: Is the team facilitating their Scrum ceremonies when the Scrum Master is away?

A quick way to check if our work as Scrum Masters is having the needed impact is to check if the team is still hosting the Scrum Retrospectives when we are away. If that’s the case, then it is likely that the Scrum Master has done a fairly good work. In this episode, we discuss this and other approaches Scrum Masters can use to assess their contribution to the team.

Featured Retrospective Format for the Week: Retro Beers

When we think of retrospectives we typically think of a meeting room, people sitting down (or standing) and executing some prepared exercises over the course of the meeting. But that’s not what a retrospective is about. It’s simply a possible format. In this episode, we discuss the 5 stages of retrospectives and how those can be implemented in many different ways.

In this episode, we refer to Retromat, a useful resource to help you plan your retrospective.

About Donna Marie Lee

Former software engineer turned pragmatic change agent working in Tokyo. Enthusiastic about inspiring teams to be great and achieve their goals.

Certified Scrum Professional with more than 5 years experience in training, facilitating and coaching agile and scrum practices.
Previously worked as a Line Manager and Team Lead responsible for nurturing the growth and maturity of teams and individuals within the company.

You can link with Donna Marie Lee on LinkedIn and connect with Donna Marie Lee on Twitter.

Daniel Heinen: a simple Success definition for us as Scrum Masters

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

The Weather Report retrospective format is a metaphor-based format that helps the team highlight the “clouds” or “storms” they faced in the previous sprints.

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.

You can link with Daniel Heinen on LinkedIn.

David Denham on how Scrum Masters can overcome the Impostor Syndrome

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!

You can link with David Denham on LinkedIn and connect with David Denham on Twitter.

David Sabine on the core job of the Scrum Master

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, among others. He’s been helping people with the ways they use Scrum since 2007.

You can link with David Sabine on LinkedIn and connect with David Sabine on Twitter.