Beyond Vanity Metrics—Defining Real Success for Scrum Masters | Darryl Wright

Summary

Podcast Summary: Beyond Vanity Metrics—Defining Real Success for Scrum Masters | Darryl Wright

Podcast: Scrum Master Toolbox Podcast: Agile storytelling from the trenches
Episode Date: October 30, 2025
Host: Vasco Duarte (B)
Guest: Darryl Wright (C), Agile Coach and Scrum Master

---

Episode Overview

This episode explores what constitutes true success for Scrum Masters and Agile coaches, moving beyond traditional vanity metrics. Darryl Wright shares his perspective on how success should be defined and measured, offering practical approaches to metrics, stakeholder alignment, and the human side of agility. The discussion is rich with actionable advice, memorable stories, and clear strategies for building healthy, high-performing teams.

---

Segment Breakdown & Key Discussion Points

1. Favorite Agile Retrospective Formats (01:21–05:57)

Darryl’s Top Retro Formats:

• Four Ls (Liked, Learned, Lacked, Longed for):

  • Great for learning environments to surface insights relevant to continuous improvement.

• Three Little Pigs Retrospective:

  • Uses metaphorical "houses" (straw, sticks, bricks) to help teams categorize their strengths and weaknesses.
  • Explicitly includes the “big bad wolf” (the scary or untouchable issues) to encourage addressing unspoken concerns.

  "You ask, what's the big bad wolf, the really scary thing, the elephant in the room that nobody wants to talk about? Let's talk about that."
  —Darryl (C), 02:32

Tips for Effective Retros:

• Vary Formats: Keeps retrospectives fresh and engaging.

• Act on Feedback: Always generate actionable outcomes. The absence of action leads to disengagement.

  "The best way to make sure no one ever comes up with a suggestion for improvement ever again is for them to see nothing happens."
  —Darryl (C), 03:46

Know Your Audience:
Tailor retrospective activities to the team's interests and culture (e.g., avoid playful formats with teams that may find them trivial).

Memorable Moment:
Darryl shares a story about a Scrum Master using the "sailboat" retro with a mainframe team, only for the team to reject it as being too childish (05:29).

---

2. Defining Success for Scrum Masters & Agile Coaches (06:01–09:12)

Misleading Metrics:

• Percentage of Agile Adoption

• Maturity Assessments

  "That's not a real success measure. That's a vanity metric. It shows something for its own sake."
  —Darryl (C), 06:36

Darryl’s Success Criteria:

• Multiple Measures: Avoid single targets; combine various metrics to prevent gaming.

• Quantitative and Qualitative Balance: Pair numerical data (like lead time, flow efficiency, and quality) with qualitative insights (e.g., team happiness, perceived productivity).

• Business vs. Humanity:

  • Measure both business outcomes (like customer satisfaction, revenue) and team health (progress toward high performance, morale).

• Team-Centric Approach:

  • Success is helping the team achieve their goals, not just what the Scrum Master wants.

  "If I'm in there to help the team, then I want my success measure to be, well, what is the team trying to achieve? What do they want to do? And then my success is how much have I helped them achieve what they want."
  —Darryl (C), 08:14

• Favorite Metrics: Flow efficiency and employee happiness.

---

3. Turning “More Story Points” into Real Value (09:12–12:00)

Common Pitfall:
Teams and stakeholders may define success as “delivering more story points,” which can become an empty target.

Darryl’s Approach:

• Output vs. Outcome:

  • “We could deliver more story points by just making the stories smaller. That doesn't help anyone, does it?”

• Refocus on Value:

  • Engage the team and stakeholders in a conversation about what “more story points” really means—usually it’s about business value, not just activity.

• Ask Impactful Questions:

  • “Would you be happy if your team checked off more boxes but your customers were less happy?”

  “Take something that people already want and then ask, how would that help us?...What would the impact be?”
  —Vasco (B), 11:25

---

4. The Human Side of Success & Balanced Metrics (12:00–13:15)

Balance Productivity and Wellbeing:

• Productivity shouldn’t come at the cost of burnout or low morale.

• Measure both customer value and employee happiness.

  "When we're working well in an agile team, we can be highly productive and highly successful and have high morale at the same time. We don't have to give up one to get the other."
  —Darryl (C), 12:29

Pairing Metrics:

• Like organizations balancing speed with quality, Scrum Masters should balance team outcomes with wellbeing.

---

5. Useful Resources & Final Thoughts (13:16–13:33)

Tool Recommendation:

• Sooner Safer Happier: A dashboard approach for measuring value holistically across multiple dimensions.

  "They have a dashboard for measuring value across all of those different domains...Check out Sooner, Safer, Happier."
  —Darryl (C), 13:16

---

Notable Quotes

• On retrospectives:
  "Every new set of questions is like a different lens to look through, gives you a different perspective and you'll generate fresh insights."
  —Darryl, 03:24

• On team engagement:
  "If you take actions that people are actually going to do something different, change the way we work and see, is that better? Those actions will make people want to come to the retro."
  —Darryl, 03:54

• On defining success:
  "It's not about what I want, it's about what the team needs to achieve."
  —Vasco, 09:12

• On metrics:
  "We want both. And this is the same. So yeah, more success and more humane. That's what I'm after."
  —Darryl, 13:11

---

Important Timestamps

| Timestamp | Topic | |-----------|-----------------------------------------------------| | 01:21 | Darryl's favorite retro formats | | 03:24 | Why variety and actions are crucial in retros | | 05:05 | Tailoring retros to your audience | | 06:27 | Vanity metrics vs. real success metrics | | 08:14 | Team-centric success measurement | | 09:53 | Handling “more story points” mindset | | 12:29 | Balancing productivity and team morale | | 13:16 | Recommendation: Sooner Safer Happier dashboard |

---

Final Insights

Success for Scrum Masters and agile coaches is not captured by adoption percentages or “more story points.” True impact is measured by how much the Scrum Master helps teams achieve their own goals, maintain high morale, and deliver real value to customers and the business—without sacrificing well-being. Pairing qualitative and quantitative metrics, customizing practices for your team, and continually focusing on both human and business outcomes are key themes throughout the episode.

---

This summary covers the episode’s main content, providing newcomers with a clear and comprehensive overview of the conversation and its practical takeaways.

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 war free 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 this 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 Daryl Wright.

[C]

Hey, Daryl, welcome back. Thanks, Vasco. I'm enjoying doing these.

[B]

Absolutely. It's been a pleasure to have you here so far and I'm sure it's going to be a blast from now on. So we'll talk about success in a minute, but before we dive into that, share with us. Darrel, what's your favorite agile retrospective format and why?

[C]

Thanks. I love this question. I'm actually going to be cheeky here and put two in the first one because they're in different contexts. If it's a learning environment, I really love the four Ls, which is liked, learned, lacked and longed for. And that's really great for finding what's going on in a learning environment. And then I have another one which I love for an operational environment, which is the three Little Pigs. Retro. So this one is asking like, what, as a team, what are we really strong at and what are our weaknesses? Right? So the three little pigs, they all build a house. So the house of straw, that's the things we're really weak at. Like, you know, nothing stands up, we just fall over. The house of sticks. These things we've put structure around but it doesn't really work. And then the house of bricks is like, what are we solid on? What can we count on every time? And so they're the three little pigs. And then you ask, and what's the big bad wolf, the really scary thing, the elephant in the room that nobody wants to talk about? Let's talk about that. So I love this for surfacing those, you know, things that would otherwise just go unspoken that no one ever wants to confront. So I love that one. So they're my two favorites and why I love them is that the two things that I've seen make the difference between successful like retros that are really valuable uses of people's time. There are two things. The first one is vary your formats. Don't just keep using the same format over and over again. You know, I run into teams and they're like, nobody wants to come to the retro. Because we just keep asking them the same questions over and over again. And they say to us, we already asked us that question. I gave you my answer, why are you asking me again?

[B]

Right.

[C]

So don't ask the same questions. Ask different questions. Every new set of questions is like a different lens to look through, gives you a different perspective and you'll generate fresh insights. So that's the first one. Vary agile retro formats. If you're ever looking for them and you don't know what to do, just Google agile retro formats and you'll get dozens and dozens of them.

[B]

Right.

[C]

You'll never run out. And then the second thing that I see is that retros don't have actions out of them. Right. So the best way to make sure no one ever comes up with a suggestion for improvement ever again is for them to see nothing happens. I make a suggestion, just goes into the void and there's no action. Well, they're not going to come up with another one next time. But if you take actions that people are actually going to do something different, change the way we work and see, is that better? Those actions will make people want to come to the retro. So they're the, they're the two reasons why I love those formats.

[A]

Yeah.

[B]

And I think the anti patterns you've mentioned are really worth kind of imprinting into our minds. Right. Like, always pay attention. Do people, Are people happy to come to the retro? If not, we need to come up with something because retros are the engine of improvement. In fact, going back to the example you used on Tuesday, I bet that team was not getting any value out of their retros because they were stuck in the same pattern and they weren't doing anything to get out of it.

[C]

That's right, 100%.

[B]

And then the other aspect is always make sure there's an improvement, no matter how small it is, and have a retro on the retro itself. Allow people to say that they don't like it, that they're missing something that's okay. It's not a judgment on us, it's input. It's information on which we can build and create better retros.

[C]

Absolutely. And one last tip. Know your team, find out what they're interested in, what they're passionate about, and, and then pick retro. Like, if you know they're all sports crazy, use sports retros. If they're all science fans, use SpaceX ones, whatever it is, like, pick things that they're into and they will love it. Don't do what one Scrum Master I know tried to do. She went into a mainframe team who were all in their mid-60s. They were about to retire. They were all very technical, introverted, highly like, you know, engineer people. And she wanted to run the sailboat retro, which is a beautiful retro about what's the sun on your face, what's the wind in your sails? And they, as soon as she started talking, they said, what do you think we are, kindergarten children? And they got up and walked out of the room.

[B]

Yeah. Always know your audience, always know your audience.

[C]

Read the room.

[B]

Yeah, talking about knowing our audience. A lot of our audience here is Scrum Masters, agile coaches, people who work with teams. And for us to succeed in these roles, we need to have a clear definition of what that is. And today we want to hear your definition. Darrell, how do you define success for yourself as an agile person? As Scrum Master and Agile coach?

[C]

Yeah, yeah. So firstly, let me just say what I think it's not. And because often I've gone into places and they're like, okay, your success measure as a Scrum Master or as an Agile coach is going to be the percentage of agile adoption across the organization. Or we're going to do a maturity assessment on the teams and that's going to be the success measure. Folks, that's not a real success measure. That's a vanity metric. It shows something for its own sake. I would say, if at all possible, don't use anything like that. What do I recommend? Firstly, I think there needs to be multiple measures, right? One measure is almost guaranteed that it's going to get turned into a target which will get game of like, it'll get gamed, right? So it needs to be firstly, a spread of things. Secondly, I would suggest always balancing quant versus qual, right? So quantifiable number metric things with, you know, qualitative things. So what is people experience? Like, what is their, you know, can you ask them to rate their happiness, how productive they're able to be, as well as things that you can quantify with numerics like lead time, flow, efficiency, you know, quality, those sort of things. And then the other thing I like to try and balance is business success, so outcomes. So are we, you know, improving things like customer satisfaction or you know, revenue versus humanity? Like, you know, how are the team progressing towards becoming a high performing team? Because ultimately, like from my point of view, what I want to achieve and what I would like my success measure to be is how much have I helped the team become a more high performing team. But that's what I want, that's not necessarily what the team wants. So if I'm in there to help the team, then I want my success measure to be, well, what is the team trying to achieve? What do they want to do? And then my success is how much have I helped them achieve what they want. Right. And so if what they want is to uplift quality or to reduce their time to market or something like that, well, then my success is helping them achieve that. And so yeah, often I like to try and negotiate what my success measure is going to be by asking the team or the organization or well, what are you trying to achieve? And so then I can measure how much I'm helping you to do that. That said, if they asked me what my favorite ones are, I would probably say flow, efficiency and employee happiness. Like if I could just pick two, it would be those.

[B]

Yeah, I like how you phrased it, that it's not about what I want, it's about what the team needs to achieve. And of course also the stakeholders. One caveat I would put there is that it's very easy for the team and the stakeholders to want things that we already know are going to be destructive for them. And I have some ideas of what to do in those cases. Like for example, you know, deliver more story points would be a great example. So what would you do in that case? Let's say you go to a team, you talk about what success means and everybody says more story points, more story points, more story points. How would you bring your own knowledge, experience and perspective to that conversation?

[C]

Well, firstly I would have the conversation with him about shifting from outputs to outcomes. I would say we could deliver more story points by just making the story smaller. That doesn't help anyone, does it? Because we're not actually delivering more value. What we want to do is deliver more value to our customers. Is that what you're trying to do? Is that what you're trying to measure with the more story points? Because if so, let's think about this In a way that actually measures value delivered. Like, could we work out value delivered in however much time? If we can deliver more value in less time, is that achieving what you want to achieve? Is that a better way of measuring that? So I would have that sort of conversation with them, and if the conversation was with the stakeholders as well, you know, I would say to them, you know, would you be happy if your team checked off more boxes but your customers were less happy? Would you be okay with that? Right. And usually they would say no. And I would say, okay, so what is it that you're really trying to do? What does more story points look like to you? What does it equate to? And maybe they would say, I want to release every two months instead of every three months.

[B]

So you would try to get them to translate the more story points into something. But that something, I hear you say it needs to be connected to somehow the impact of that something. So if we were to deliver story. Story points, how would that help us?

[C]

Yes, now we're trying to shift and convert that into value impact outcomes, those sort of things.

[A]

Right.

[B]

So I'm totally with you on that. And I think that kind of, let's call it that judo move, right? Like take something that people already want and then ask, how would that help us? It kind of frees them to stick to that idea. Yes, we still want that. But then start thinking, thinking without dropping the old idea, more story points, start thinking, but what does that mean? Why is that important? What would the impact be? And I think that's a very powerful kind of twist in the conversation that allows them to sit with what they want, but then imagine why that really matters.

[C]

Yes. And my, my mission, my purpose in life is to help organizations be not just more successful, but more humane as well. And so I would always be asking, okay, if we want to get, you know, more value out to our customers, but we burn out our teams and they all quit or go off on stress leave, is that really helping us be more successful in the long run? No. Okay, so then what about if we balance by having multiple measures, can we measure greater value to customers in shorter time and employee engagement, staff happiness, morale levels? Because truly, when we're working well in an agile team, we can be highly productive and highly successful and have high morale at the same time. We don't have to give up one to get the other. We can have both. And it's the same thing as, you know, an organization trying to get increased speed and increased quality. Right. They don't want increased speed at the cost of quality. They don't want to increase quality. The cost of speed.

[B]

Yeah. They're balancing metrics. Right. It's not just one. It's never just one metric anyway.

[C]

That's right. And it's not one at the expense of something else. Right. We want both. And this is the same. So yeah, more success and more humane. That's what I'm after.

[B]

Thank you for sharing that with us, Darrell.

[C]

I was going to say just there's one thing I love about the better Value Sooner, Safer, Happier. They have a dashboard for measuring value across all of those different domains. So if you're looking for an example of what might success measures look like, we can make a whole dashboard of it. Check out Sooner, Safer, Happier and the.

[B]

Link is in the show Notes Hey.

[A]

Alright, 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 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 details@screen scrummastertoolbox.org membership because listening is great. It's important. But doing it together, that's next level. I'll see you in the community.

[B]

Slack.

[A]

We really hope you liked our show.

[B]

And if you did, why not rate.

[A]

This podcast on Stitcher or itunes, Share.

[B]

This podcast and let other Scrum masters.

[A]

Know about this valuable resource from their work.

[B]

Remember that sharing is caring.