How Scrum Masters Can Measure Their Own Impact, Practical Self-Assessment Metrics

Summary

Podcast Summary: How Scrum Masters Can Measure Their Own Impact, Practical Self-Assessment Metrics

Podcast: Scrum Master Toolbox Podcast: Agile storytelling from the trenches
Host: Vasco Duarte
Guest: Junaid Shaikh
Date: March 12, 2026

---

Episode Overview

This episode focuses on practical ways Scrum Masters can define and measure their own success and impact within agile teams. Vasco Duarte and guest Junaid Shaikh delve into retrospective formats, the core principles behind them, and discuss clear, actionable self-assessment metrics for Scrum Masters who aim to continuously improve in their role.

---

Key Discussion Points & Insights

1. Retrospective Formats: Principles over Process

[01:21 – 04:06]

• Junaid's Key Insight:
  Junaid emphasizes that while there are many catchy and creative retrospective formats ("Three Ls: Liked, Learned, Lacked," "Three Little Pigs," "Sailboat," "Car"), the foundational principle is more important:

  • “Whatever retrospective format I choose, the core principle remains the same. It's basically what went well, what could have gone better and what to do, what to do better next.” — Junaid [01:38]
  • Frequent format switching can distract; stick to a rhythm that works for the team.
  • Key is to match the format to the team’s current mood and needs.

• Appreciation as a Retrospective Element:
  Junaid stresses the importance of integrating appreciation:

  • “The most important component that I would add to any of the format is the appreciation part… that's also a moment to reflect on how another team member or a PO or a Scrum Master helped you during that sprint.” — Junaid [03:41]

  • Appreciation builds trust, respect, and openness, fueling future sprints.

---

2. Measuring Scrum Master Success

[04:06 – 09:11]

• Defining Success through Measurement:
  Junaid references Peter Drucker:

  • "You cannot improve something that you cannot measure." [04:39]
  • Recommends developing explicit success criteria for both personal performance and team performance.

• Agile Maturity & Metrics:

  • Use tools like the Agile Team Maturity Index (e.g., spider graph) to assess the team's progress.
  • Transparently display maturity status and inspect/adapt regularly.
    • “So have those metrics realized, like we have the Agile Team Maturity Index. Like, where are we on the spider graph with respect to certain criteria? …having that transparency board and frequently inspecting and adapting would really help you there.” — Junaid [05:00]

• Translating Retrospective Insights into Action:

  • Don’t assume; involve those affected in creating trial solutions.
  • Track whether issues highlighted in retrospectives are trending downward over time.

• Sprint Goals and Shared Outcomes:

  • Critiques teams with too many (individualistic) sprint goals:
    • “I saw with one of the teams, they had nine sprint goals. Come on, you cannot have nine sprint goals for a two or three week sprint… A sprint goal should be something that multiple team members can work together to achieve a common outcome. It has to be shared.” — Junaid [06:40]
  • Facilitating shared sprint goals is a key Scrum Master success factor.

• Building Self-organizing Teams:

  • A real sign of success: the team’s ability to function smoothly without constant Scrum Master intervention.
    • “If you are being missed a lot in your… when you are absent for a sprint and the work is not getting done, then there is a problem.” [07:17]
  • The goal is to coach toward self-organization.

• Diagnosing Team Communication Health:

  • High volume of emails may signal hidden conflict or trust issues.
  • Robust direct communication in daily standups is a positive indicator.

• Scrum Event Participation:

  • Canceling Scrum events too often suggests a regression to old (non-agile) habits.
    • “Another sign that might tell you that you are not being successful is… a lot of times I see the events, the Scrum events getting canceled too many times… that's another sign that the team is switching back to their traditional way of working.” — Junaid [08:13]

---

3. Continual Self-Assessment and Growth

[08:46 – 09:11]

• Adapting Metrics to Context:
  • Not all suggested metrics will fit every Scrum Master or team.
  • The process is ongoing: start somewhere, experiment, and refine your own measures of success.
    • “…it is that self assessment that we constantly do that allows us to grow as professionals. So even if this might not be the right metrics for every one of us, it's a great place to start and then we learn what actually is the right metric.” — Vasco [08:46]

---

Notable Quotes & Moments

• On Retrospective Simplicity:
  “If you expose your team to a certain format repeatedly, they get much better. So they don't have to try to adjust themselves to the new concept because ultimately the outcome is the same.”
  — Junaid Shaikh [02:19]

• On the Value of Team Appreciation:
  “Please appreciate that because that builds in the feeling of, you know, trust and respect and openness and appreciation, which feeds into the subsequent sprints.”
  — Junaid Shaikh [03:48]

• On Shared Sprint Goals:
  “A sprint goal should be something that multiple team members can work together to achieve a common outcome. It has to be shared.”
  — Junaid Shaikh [06:55]

• On Recognizing When Things Go Wrong:
  “If your communication in the team is happening in the dailies… if your team is leaning a lot on the left [of the Agile Manifesto], then you're successful.”
  — Junaid Shaikh [07:54]

---

Key Timestamps

• 01:21 — Starting discussion on retrospective formats
• 03:41 — Importance of appreciation in retrospectives
• 04:36 — How to define and measure Scrum Master success
• 05:00 — Using Agile Team Maturity Index for transparency
• 06:40 — The problem with too many sprint goals
• 07:17 — Self-organization as a Scrum Master success trait
• 08:13 — Cancelation of Scrum events as warning sign
• 08:46 — Continual self-assessment and adapting metrics

---

Summary

This episode offers a pragmatic and principle-driven approach to measuring Scrum Master effectiveness. Junaid Shaikh lays out a foundation for self-assessment grounded in simple, actionable metrics: team maturity, shared sprint goals, self-organization, team communication, and healthy Scrum event participation. Above all, Junaid and Vasco reinforce the importance of self-reflection, adaptation, and the subtle art of appreciating team contributions as core to enduring agile success.

Transcript

[A]

Hey there, agile adventurer, just a quick question.

[B]

What if, for the price of a

[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.

[C]

Hello, everybody.

[B]

Welcome to our success Thursday this week with Junaid Shaikh. Hey, Junaid, welcome back.

[C]

Hello, Osco. Thank you for having me here.

[B]

Absolutely. So, Junaid, Thursday success Thursday. We'll talk about that in a minute. But it's also retrospective day. So tell us, what's your favorite agile retrospective format and why?

[C]

That's a super interesting question, Vasco. I mean, all of the community would be having a lot of thoughts around that, but throughout my experience, I've realized that whatever retrospective format I choose, the core principle remains the same. It's basically what went well, what could have gone better and what to do, what to do better next. Right. So there are hundreds of different formats with different naming conventions, very catchy phrases like, you know, the three Ls, liked, learned, lacked. And then there is this, the three, you know, the three little pics, for example, that my kids view the story on YouTube. They have. Then we have the sailboat, then we have the car. So all of this are good, you know, you know, in the sense of a slight change, but the principle remains the same. So I would go mostly with the plane. What went well, what could have gone better, and what to do better next, it's again about the rhythm. So if you expose your team to a certain format repeatedly, they get much better. So they don't have to try to adjust themselves to the new concept because ultimately the outcome is the same. Of course, it's a lot about, we spoke in the previous days. It's a lot about understanding where the mood of the team is and based on that, exposing that sort of a retrospective to them. So if I have to again summarize this, I've tried many formats and I like the Three Little Pigs, I like the three L's and the vanilla. What went well? What could have gone better on what to do better next? One important, most important component that I would add to any of the format is the appreciation part. You know, people always, you know, in our day to day work, we always focus on the process side of things. What went well, what did not go well, what could have gone better. But that's also a moment to reflect on how another team member or a PO or a Scrum Master helped you during that sprint. So please appreciate that because that builds in the feeling of, you know, trust and respect and openness and appreciation, which feeds into the subsequent sprints.

[B]

Absolutely. And I like that that focus on core principles, right? Like what are we trying to achieve, what makes retrospectives productive for team out there and what can we learn from it? Of course we also run these retrospectives because we want to help teams succeed, which is how we succeed. So, Junette, share with us. When you think about your role as a Scrum Master, how do you define success for yourself?

[C]

That's a very broad question. And we could go hours talking about Avasco, but just with the interest of time, I'll try to keep it short. So I always believe that, you know, you cannot improve something that you cannot measure. I'm quoting Peter Drucker here. Right. So I always say as a Scrum Master, please define those success criteria for, for yourself and the team. Like, if we achieve this, then we define that we are working well as a team. So have those metrics realized, like we have the Agile Team Maturity Index. Like where are we on the spider graph with respect to certain criteria? And if we are lacking on certain things or we are very low, what can we do to make that better? So having that transparency board and frequently inspecting and adapting would really help you there. The other is the retrospective that we spoke about. The teams bring out a lot of good information in the retrospective and as a Scrum Master, if you along with the team, don't assume, right, like, like I said on the first day, don't assume, make tiger teams, get in the participation of the people who are actually affected by that thing and create smaller iterative solutions, trial experiments to solve that issue and measure in the future retrospective. If that graph is going down, then you are doing good as a Scrum Master and a team, a lot of times I also feel that, you know, like we spoke about in the previous Days we follow Scrum. Ideally, a team should be cross functional and it should have shared goals. But if you go into the real reality, you know, if you go to the teams, there are like eight to nine sprint goals. I saw with one of the teams, they had nine sprint goals. Come on, you cannot have nine sprint goals for a two or three week sprint. Right. Those are basically individual tasks accumulated together and said, oh, this is a sprint goal for the team. Sorry. A sprint goal should be something that multiple team members can work together to achieve a common outcome. It has to be shared. So if you as a Scrum Master are able to create those or facilitate the creation of those shared goals, I think you have, you are in the right direction for success. Self organizing teams as Scrum Master. If you are being missed a lot in your. When you are absent for a sprint and the work is not getting done, then there is a problem. You know, teams, you should coach them to self organize. So if I find a team that is self organizing, I think that's a success pattern for a Scrum Master. And we always also find these small cues like, you know, if you see too many emails floating around here and there, that is also a sign for a Scrum Master that there is something hidden, either a hidden conflict or a hidden, you know, trust barrier or something. So if you're, if, if your communication in the team is happening in the dailies is happening, you know, as per the Agile Manifesto, you know, individuals and interactions over processes and tools, if your team is leaning a lot on the left, then you're successful. Another sign that might tell you that you are not being successful is, you know, a lot of times I see the events, the Scrum events getting canceled too many times, too frequently. That's another sign that, you know, the team is switching back to their traditional way of working. So if, if your teams are doing these things in the right way, then, I mean, of course, like I said, there can be many other things, but these are the things that I could have at the top of my mind right now.

[B]

Absolutely. And it's important to have at least some of those ideas and I appreciate you sharing them because it is that self assessment that we constantly do that allows us to grow as professionals. So even if this might not be the right metrics for every one of us, it's a great place to start and then we learn what actually is the right metric. So perfect. Thank you for sharing that with us, Junaid.

[C]

Thank you, Oscar.

[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 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.

[B]

Slack. 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 caring.