Why Scrum Masters Should Be Measured on Outcomes, Impacts, and Team Happiness | Nigel Baker

Summary

Scrum Master Toolbox Podcast: Episode Summary

Episode: Why Scrum Masters Should Be Measured on Outcomes, Impacts, and Team Happiness | Nigel Baker
Date: March 5, 2026
Host: Vasco Duarte
Guest: Nigel Baker

---

Episode Overview

This episode explores what true success looks like for Scrum Masters, challenging the traditional emphasis on following process to the letter. Nigel Baker, an experienced Agile coach, offers practical insights into measuring success by team outcomes, impacts, and happiness, rather than process compliance. The discussion also includes engaging perspectives on how to keep retrospectives fresh and authentic, and why team engagement and stakeholder feedback are core to sustained agility.

---

Key Discussion Points & Insights

1. Keeping Retrospectives Fresh and Effective

Timestamps: 01:31 – 05:39

• Changing Formats Every Time:
  • Nigel avoids reusing retrospective formats, believing that teams become disengaged with repetition.
    • “You find a format you really like… but if you use it more than a few times, these things age like milk.” (Nigel Baker, 01:40)
  • Introduces a novelty factor each sprint—retrospectives are always changing to maintain team engagement.
• Team-Driven Retrospectives:
  • Invites teams to devise their own retrospective methods, sometimes leading to surprisingly thorough (“forensic”) sessions.
    • “I sometimes get the team to write them themselves... some teams invent retrospectives that were almost forensic in their intensity.” (C, 02:37)
• Focus on Authenticity Over Gimmicks:
  • Nigel dislikes “fake frivolity” such as heavily themed retrospectives (e.g., based on movies or games) feeling these lack authenticity.
    • “If you do that to me, I die inside. I'm a great believer in fun. But fake frivolity, anything fake, any facade, anything less than authentic, I get set off on.” (C, 03:47)
• Retrospective Techniques for Stakeholders:
  • Uses retrospective methods in Sprint reviews to ensure stakeholders provide active feedback rather than just observe.
    • “I like to get a little bit, some sort of formula in there... so the stakeholders can't sit there like Roman emperors in the Colosseum, watching the developers as gladiators.” (C, 04:52)
    • The technique flips the expectation: stakeholders must actively engage, increasing the value of the Sprint review.

---

2. Measuring Scrum Master Success: Outcomes and Team Happiness

Timestamps: 05:39 – 08:45

• Moving Beyond Process Fidelity:
  • Refers to old measures like the “Nokia test” as limited since they only assess process compliance.
    • “Compliance with a process isn't going to… No customer is going to come to you and say, do you know why I bought your product? Your remarkable compliance with your internal development process.” (C, 07:04)
• Focus on Outcomes and Impact:
  • True success for a Scrum Master should be based on outcomes (customer satisfaction, product impact, team efficiency) rather than metrics like velocity or number of stories completed.
    • “It's about outcomes. Things like customer satisfaction, things about revenue generation, efficiencies, that sort of thing.” (C, 07:29)
• Team Satisfaction as a KPI:
  • Argues that team happiness is a key indicator of sustainable success, as happy teams perform well and are less likely to leave.
    • “If my team is happy, they're not likely to leave. If my team is happy, they're likely to do a good job... It's an indicator towards success factors.” (C, 08:22)
• Stakeholder Orientation:
  • Scrum Masters should see the team as their primary stakeholders, focusing on their well-being and engagement as a driver for overall project success.

---

Notable Quotes & Memorable Moments

• On Preventing Retrospective Fatigue:
  • “These things age like milk.” (Nigel Baker, 01:44)
• On Authenticity:
  • “I'm a great believer in fun. But fake frivolity, anything fake, any facade, anything that feels less than authentic, I get set off on.” (C, 03:47)
• On Measuring Success:
  • “No customer is going to come to you and say, do you know why I bought your product? Your remarkable compliance with your internal development process.” (C, 07:04)
  • “It's about outcomes... not velocity or anything silly like that, or the amount of stories we've done—who cares?” (C, 07:19)
  • “Team happiness is... an indicator towards success factors.” (C, 08:22)

---

Important Timestamps

• 01:31 – 05:39: Discussion on retrospective variety, team involvement, and authentic formats.
• 05:39 – 08:45: Nigel’s views on what defines Scrum Master success—outcomes, impacts, team happiness.

---

Tone & Style

The tone is conversational, open, and pragmatic. Nigel brings humor and candor (“age like milk,” “die inside”) and speaks from deep experience while always returning focus to what actually drives meaningful, sustainable Agile transformation.

---

Summary Takeaways

• Avoid Stagnation: Keep retrospectives fresh to maintain team engagement—novelty trumps routine.
• Measure What Matters: Prioritize outcomes and impacts over strict adherence to process.
• Make Happiness a KPI: Team satisfaction isn’t just a nice-to-have; it’s critically linked to success.
• Authenticity Over Gimmicks: Opt for genuine engagement over forced fun or surface-level themes.
• Engage Everyone: Use retrospective techniques during reviews to involve stakeholders, not just observe.

This episode is a must-listen for Scrum Masters seeking to refocus their metrics and methods towards real, people-driven success.

Transcript

[A]

Hey there, agile adventurer, just a quick question. What if, for the price of a fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame warfree and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's the Scrum Master Toolbox membership. And it's your unfair advantage in the agile world. So if you want to know more, go check out scrummastertoolbox.org membership. That's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast.

[B]

Hello everybody. Welcome to our success. Thursday, the big question of the week. This week with Nigel Baker. Hey Nigel, welcome back.

[C]

I'm back again and my cup of tea's got cold after four days of doing this.

[B]

Yeah, we should have stopped at the end of every day to warm up

[C]

a cup of tea, coffee. Definitely, definitely should have done.

[B]

All right, so we'll talk about success for Scrum Masters in a minute. But Nigel, share with us first, what's your favorite agile retrospective format and why?

[C]

Okay, I'm going to be so controversial here. This is deep controversy, right? I've got in fact two favorite formats, right? Both are not formats, right, but they are different. And why? Okay, so my key thing is, here's the problem with the Scrum Master, right? You find a format you really like. Maybe it's doing silent writing, maybe it's post its on a wal the four quarters. But the trouble is, if you use it more than a few times, these things age like milk. You know, as a Scrum Master, your team are like, oh yeah, what should we do differently? And then Sprint 2, they're like, yeah, what should we do differently? Sprint 3, Sprint 4, Sprint 107. Oh, what should we do differently? This. So my key thing is different. I like different retrospective techniques each time, right? I like different ones each time. Something new, something different. Novelty factor. Scrum is a product like any other. And like any other product, people get bored with it, right? Unless you keep it interesting and engaged, right? So in a computer game that means dlc, adding new content. You know, in TV shows it's new episodes. In Scrum it's about changing the retrospective format. I change it every single sprint. Something new, something, something different to keep people engaged, interested. Sometimes they fall flat, sometimes they go, well. But the key thing is it's. People don't know what to expect. Something different and unusual. It gets energy in the room, it gets excitement in the room. I sometimes get the team to write them themselves. Come up with your own retrospective formula. You know, that's a great trick because they invent the most. I've had some teams invent retrospectives that were almost forensic in their intensity, of course, forgetting they're going to turn it on themselves. If you ever seen a bat, any film where there's some villain creating a super weapon, you know that super weapon's being used on the villain before the end of the film. That's what they do. This is really, oh my God, we're doing it to ourselves. Oh no. So that's what I really like. I vary what I would say is. And again, this is personal preference. I love theming on topics I like. Oh, we're gonna focus on billing or focus on this. Right. What I don't like, and I know a lot of people do them toe curlingly awful, is theming it on a, like a. Oh, we're gonna do one based on Super Mario Brothers or we're gonna do a Top Gun retro. And I just like, if you do that to me, I die inside. I'm like, do you know what? I don't really want to discuss who the maverick and who the goose is of this team. I like, I can't. I'm a great believer in fun. But fake frivolity, anything fake, any facade, anything that feels less than authentic, I get set off on. Right.

[B]

And that's why it's so important to also involve the team in that process. Because obviously we are just one person in the team.

[C]

Yeah. And you're not sort of imposing your taste on them like a middle aged father like me imposing my taste in music on my daughters. No, no. You will like New wave whether you like it or not. But there's one, one tip I wanted to give on retros I wanted to squeeze in here because I love doing retrospective techniques in the Sprint review. Right. On the stakeholders. Because secretly the review and retro are both retrospectives. It's just the retrospective is a process retrospective and the Sprint review is actually a product retrospective. So I like to get a little bit, some sort of formula in there, some sort of method in there just so the stakeholders can't sit there like Roman emperors. In the Colosseum, watching the developers as gladiators, like we are about to die. Salute thee. Instead I like to see like, okay, let's put a little bit of heat on the audience. Okay, you've seen this stuff. Stuff. Let's use some techniques to get some feedback on them. Hey, what would you do differently?

[B]

Right, so that's feedback. Source the feedback.

[C]

Yeah, exactly. So it's getting sweet, juicy, honey flavored feedback out there, stakeholders and using techniques for that as well.

[B]

Talking about getting juicy. Of course, the juiciest question of the week is what does success mean for a Scrum Master? So Nigel, give us your take.

[C]

What does success mean for a Scrum Master? Success. So if we were Ken Schwaber, Jeff Sutherland, right, who I'd know for year known for 25 years, it would all be about performance. Like, it would all be about performance, right? Famously, Sutherland did the was it double the work in half the time book, the worst name book in history because the last thing you want is double the work in half the time. You want double the value in half the time. So what I would do in terms of Scrum mastery, I would never be measuring success on things like process fidelity. So again, rewind 20 years, there was a lot of work done on. Okay, how do we judge the success of Scrum? And there's things like the Nokia test out there. And by the way, the Nigel scale I mentioned on a previous day was literally a joke on the Nokia test if you weren't around for the Nokia test. The best thing about it was it wasn't a test and it wasn't invented by Nokia. But anyway, it was a Nokia networks assessment. So it was a tool to assess your team's relative agility. So how agile is your team? Like what, what methods are they using? How are they using them? How are they engaging with customers? Why? And it was very nobly meant and it still exists out there in a variety of forms. The trouble is, is that it's not judging the right thing. Like, like compliance with a process isn't going to. No customer is going to come to you and say, do you know why I bought your product? Your remarkable compliance with your internal development process. What they're interested in is outcomes and impacts. So what I would do as a Scrum Master is you want to be measured on outcome and impacts. So that's things like not velocity or anything silly like that or the amount of stories we've done, who cares? We've done 10,000 tickets. They're all rubbish. No one wants them that's ridiculous. But it's about outcomes. So things about customer satisfaction, things about revenue generation efficiencies, that sort of thing. Just like a PO gets judged. But the other thing I would add in there is in terms of team satisfaction or team happiness, happiness factor, whatever you want to call it. In terms of team content, this as well. So not only am I interested in. So a good PO would be interested in like outcomes and impacts and like stakeholder satisfaction, you know, making my stakeholders not fire me. As a Scrum master, that's interesting. But my stakeholders are my team mainly, so I'm interested in them as well. So, okay, how do my team feel about this? There's no point us being hugely successful. If the team are deeply, deeply unhappy, they'll just leave. Because remember, team happiness is a lovely thing. As a business, it's not an end goal. As a business, it's an indicator to an end goal. So it's like a KPI. If my team is happy, they're not likely to leave. If my team is happy, they're likely to do a good job. These are all. It's an indicator towards success factors. So that's something I would always be paying attention on. Team contentness, outcomes of the team, impacts of the team, their results, their product are having.

[B]

Great way to look at it. Thank you for sharing that with us, Nigel.

[A]

All right, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast is powered by people like you, the members who wanted more than just inspiration. They wanted real tools and real connection to people who are practical, practicing agile. Every day we're talking access to over 700 hours of agile gold, CTO level strategy talks, summit keynotes, live workshops, E courses, deep dive interviews, books. And if you're into no estimates, we got the pioneers of no estimates in those deep dive interviews as well. Agile business intelligence, creating product visions, coaching your product owner courses, you name it. You'll get invites to monthly live Q&As with agile pioneers and practitioners, plus a private Slack community which is free of all of that AI slop you see everywhere. And of course, without the flame wars. It's a community of practitioners that want to learn and thrive together. It's the best place to connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast membership. So head on over to scrummastertoolbox.org membership and join the community that's shaping the future of Agile. We have so much for you. So check out all the [e-mail] membership because listening is great. It's important. But doing it together, that's next level. I'll see you in the community.

[C]

Slack

[A]

we really hope you liked our show. And if you did, why not rate this podcast on Stitcher or itunes? Share this podcast and let other Scrum masters know about this valuable resource for their work. Remember that sharing is key. Carry.