The Scrum Master as a Router, Redefining Success Through Efficient Communication | Wasim Osman

Summary

Podcast Summary: "The Scrum Master as a Router, Redefining Success Through Efficient Communication"

Podcast: Scrum Master Toolbox Podcast: Agile storytelling from the trenches
Host: Vasco Duarte
Guest: Wasim Osman
Date: August 13, 2026
Theme: Redefining success as a Scrum Master, the importance of efficient communication, and practical strategies for improvement.

---

Episode Overview

This episode centers on the concept of success for Scrum Masters, focusing on the importance of facilitating effective communication within teams and stakeholders. Wasim Osman shares his own approach to retrospectives, his self-management strategies, and how he fosters an open feedback culture. The conversation delivers actionable insights for Scrum Masters seeking to amplify their impact and reduce friction within their teams.

---

Key Discussion Points & Insights

1. Retrospective Formats: Adding "Outliers"

[01:21 – 04:08]
Wasim discusses his favorite retrospective structure:

• Questions Used:

  • What went well?
  • What went wrong?
  • What were the outliers?
  • Followed by an open discussion

• Rationale for Outliers:
  Adds a "bucket" for items not fitting into binary categories, capturing significant but non-polarizing events or concerns.

  “Outliers could be a little bit negative. It could be something about the future that we haven't discussed about yet. But we need to start the conversation early on so anybody is noticing anything that is an outlier.”
  — Wasim Osman [02:54]

• Metrics Integration:
  Highlights incorporating sprint metrics (completion rates, bottlenecks) to ground discussions.

2. The Scrum Master as a "Router"

[04:32 – 06:38]
Wasim introduces his metaphor for the Scrum Master role:

• Router Analogy:
  The Scrum Master is like a home internet router, efficiently handling communication between many "devices" (stakeholders/teams). If the Scrum Master slows down, they become a bottleneck.

  “You have to prioritize, schedule, and also be on time at communicating in the most efficient manner with all the different parties and stakeholders that you're involved with.”
  — Wasim Osman [04:41]

• Personal Organization:
  Outlines his personal Kanban board and twice-daily self-standups, which improved his effectiveness and prevented becoming a blocker.

  “After I started becoming more organized with my own self... I was not being a blocker at all.”
  — Wasim Osman [06:23]

3. Practical Self-Assessment and Tracking Success

[06:38 – 08:48]

• Feedback Challenge:
  Notes the rarity of honest feedback from engineers to Scrum Masters—especially negative or uncomfortable feedback.
• Self-Tracking Tools:
  Uses his Kanban board to watch for stagnating tasks as a proxy for his own performance.
• Efficient Meetings:
  Focuses on making meetings concise and purposeful to avoid time waste and resentment.

  “Longer conversations or meetings tend to zone people out. And... the longer it gets, the more resentful everyone would eventually start becoming.”
  — Wasim Osman [07:45]

4. Sourcing and Inviting Feedback

[08:48 – 11:59]

• Strategies for Gaining Feedback:

  • Directly asking for input, but recognizing initial resistance.
  • Demonstrates openness to critical feedback, noting the importance of non-defensive attitudes.
  • Introduces feedback in “low-stakes” forms initially, e.g., “What did you like about this meeting?”
  • Proactively admitting shortcomings to “break the ice” and encourage honest dialogue.

  “You cannot fear feedback. So even if you get [it]... it's only going to get better if you know about it.”
  — Wasim Osman [09:45]

  “Sometimes what I do is if I feel like the meeting was not as efficient... I voice it out before anyone else. It's like, ah, our meetings used to be better. What happened?... and then they start voicing out, yeah, you know what, thanks for saying that.”
  — Wasim Osman [11:25]

• Host's Advice:
  Vasco encourages gradual deepening of feedback questions, starting simple and building trust.

5. Psychological Safety and Validation

[11:37 – 11:59]

• Normalizing Honest Conversations:
  Both speakers agree that when you sense disengagement, naming it openly can validate others’ feelings and invite discussion.

  “It's like the psychologists call it validation. Right, like if you get the intuition people are bored. They probably are.”
  — Vasco Duarte [11:48]

---

Notable Quotes

• "You have to understand the feedback is already there, so you're just not hearing it."
  — Wasim Osman [09:56]
• "If you start becoming a little bit slower in terms of your work, you will eventually become a blocker."
  — Wasim Osman [06:28]
• "Try to be as mindful as possible so that all communications are super efficient."
  — Wasim Osman [08:35]
• “Just get practicing... start with simple things. What was the thing you most liked about this meeting?”
  — Vasco Duarte [10:10]

---

Memorable Moments

• Wasim’s “Self-Standup” Ritual:
  Sharing how he holds standup meetings with himself in the morning and evening, applying Scrum principles personally to keep on track and self-improve.
• Outliers Category:
  Adding "outliers" to retrospectives, creating room for nuance beyond “good” or “bad.”
• Validating Boring Meetings:
  Openly labeling a meeting as “boring” to invite honest reflections and shared improvement.

---

Timestamps for Important Segments

• [01:21] Retrospective format and rationale for “outliers”
• [04:32] Scrum Master as a “router” metaphor
• [06:38] Self-management techniques & tracking success
• [08:48] Challenges of gathering honest feedback
• [11:25] Proactively voicing meeting shortcomings to elicit team input
• [11:48] The value of validating team moods openly

---

Key Takeaways

• Success as a Scrum Master is rooted in enabling quick, clear, and efficient communication.
• Regular self-management and tracking prevent the Scrum Master from becoming a bottleneck.
• Honest feedback is crucial but often inaccessible; proactive, low-stakes invitations and personal vulnerability unlock valuable input.
• Retrospective formats that include a space for “outliers” foster broader and more inclusive discussions.

---

This episode is a must-listen for Scrum Masters and Agile Coaches looking for practical approaches to communication, feedback, and self-improvement in their roles.

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.

[B]

Hello everybody. Welcome to our success Thursday this week with Wasim Osman. Hey Wasim, welcome back.

[C]

Hey Vasco, good to be back.

[B]

So success is the topic of today, but before we dive into that, do share with us. Wasim, what's your favorite Agile retrospective format and why?

[C]

So my favorite, you can't follow a lot of different formats. For me, the longest period of time what happened was I've been following the format that says ask the question about what went well, what went wrong, and if there are any outliers, and then followed by an open discussion. This is the very bare bones format that I followed. But this had a few frills in the past as well. So where I used to put together a few metrics of how a sprint went in terms of completion rate, if there were any tickets that were kind of like sitting in any particular column, like if it was waiting in review for too long or in QA for too long. So we would explore that like those numbers and that would be interesting for a lot of the everybody actually in the team, because those were not areas that you'd necessarily notice during as a sprint goes on.

[B]

So you said what went well? I think that's clear. What went wrong? I think that's clear as well. But then you said what were the outliers?

[C]

Yes.

[B]

What's the core of that question? And why did you kind of crystallize and kind of converge on that question? Because what went well and what went wrong are obvious, but the outliers isn't the question we hear very often.

[C]

Yeah, that was something that I added years ago when I Found out, like in many of the retrospectives, there were talking points that team members would like to bring, but you cannot really necessarily say that that's a bad thing or a thing that went wrong or things that were good. But it was something that was significant for us to talk about. So outliers could be a little bit negative. It could be something about the future that we haven't discussed about yet. But we need to start the conversation early on so anybody is noticing anything that is an outlier. It also helped a lot of the engineers to kind of talk about things that they did not necessarily think was negative. It's the same kind of theme, but there were some concerns that came in there as well. So it gave everybody a bucket of sharing information that did not have any polarity.

[B]

Okay, well, that's a great point. When you first said the outliers, I was thinking more that it might refer to surprises or unexpected events. But I guess what you mean is what doesn't fit any of the other two categories, but you still want to talk about it?

[C]

Yeah.

[B]

Yeah. Awesome. Well, everybody try it out. Well, what went well, what went wrong? And what are the outliers? Plus, and I think that's an important part. Open discussion. Let's turn our attention to success and what it means for us as Scrum Masters. Now, Wasim, so for you, how do you define for yourself success as a Scrum Master?

[C]

So I. I take, like, like a big part of the. The role of a Scrum Master in that particular capacity is to work as a router. So a router in the house, for example, it's handling a lot of conversation with a lot of different devices, although the source of the Internet is coming using one cable. Right. So it's like you have to prioritize, schedule, and also be on time at communicating in the most efficient manner with all the different parties and stakeholders that you're involved with. If you get a little bit slow, if you. If you miss out on anything, it's your. It's kind of. I think, like, nobody else is kind of responsible for that. So I think it's. It's. It's a very easy kind of, like, thing to describe. But if you're, like, moving at a speed incredibly fast, then there are. You could probably lose out on information like that. So I think, like, it has been, like, it. It has transformed the way that I work over the years, because in the beginning, I was very confident, like, oh, okay, I got this. And then I would get overwhelmed with a lot of information because I was working with three or four different engineering teams. A lot of context. So that got me to have my own kind of like Kanban board to manage my own work. And I would have my own standup a little bit every morning to kind of like see what I'm doing right now, to get a perspective of that and prioritize that and the end of the day as well, another standup to see like what kind of moved and what was left and why. So I think after I started becoming more organized with my own self, I think it was very. Things kind of started becoming more satisfying for me as I was not being a blocker at all. Because if you get like as a scrum master, if you start becoming a little bit slower in terms of your work, you will eventually become a blocker.

[B]

Yeah, absolutely. So when you think about like the way you describe and interpret what success means for you, how do you keep track of it? Because of course one thing is to say, okay, these things I care about, these things I want to look at. But then another thing is to make this practical. And as we know, feedback is the beginning of the learning. Right? Like we need to create those moments for ourselves as well when it comes to success as a scrum master. So how do you keep yourself honest with your own definition of success?

[C]

I think feedback helps a lot and you will not get feedback honestly when you're the scrum master or the agile coach in a particular team. And then the engineers that you're working with, they will not tell it to your face. Most of the times if you're being difficult or if you're being, if you're slowing them down in any way, it like, so you have to be aware, I think you have to be aware of having a bird's eye view of your own self. So that, and that is not. That's easier said than done than done. So I think one of the success measures that I always kind of use is that the Kanban board that I have, I keep track of the things that are staying stagnant in my to do list. So those, you know, so those are things that I set out to do and those are just sitting there. And there is also another version of that that I keep in mind. That is whenever that I'm in a meeting and I'm calling a meeting, I try to make it as short as possible because there are talking points. If there's anything that is coming up as a result of this conversation that can be had in a different time. Longer conversations or meetings tend to zone People out. And the longer it gets, the more resentful everyone would eventually start becoming like, okay, so I learned nothing from this two hours, right? So I try to be as mindful as possible so that all communications are super efficient.

[B]

So you said something that is very important. People will not necessarily tell to your face what they think is going wrong. So how do you work around that? Because that feedback, what people think is going wrong, is very important for our own learning. Also, what's going right. So it's not just to focus on that, but of course what's going right is more easy to come out, even if not necessarily the way we expect it or can easily understand it. So how do you source that feedback?

[C]

So one way is that because you will not be told about it as frequently, is to ask the people that you're working with. And even if you ask people about how things can be done better, if you do not react in a favorable way or accepting manner, you will ask that. The first time they will tell you they'll give you the feedback, and the next time they will not because they

[B]

ignore you next time. Exactly.

[C]

Yes. So you have to understand that as a scrum master agile coach, you have to understand that you cannot fear feedback. So even if you get. Because you have to understand the feedback is already there, so you're just not hearing it. So if you hear it now, you have ammunition to be better. So it's only going to get better if you know about it.

[B]

Yeah. And I guess that one thing we can easily say here in this context is just get practicing. Right? Like, start with simple things. Right. Like, you know, one example is what was the thing you most liked about this meeting that's easily a low stakes kind of feedback. Right. And then maybe graduate to, hey, what, what is one thing you would have done differently? Yeah, right. And then, you know, over time we can ask, you know, what, what, what didn't you like, what, what was boring? What did you think was a waste of time? But you know, kind of growing up to it. Right? Like, don't start with the high stakes conversations immediately because that will alienate people and frankly kind of make them say things that don't mean anything because they just want to be polite and answer the question without causing any awkwardness.

[C]

100%. 100%, absolutely. And at the same time, just to add to that, when you said like, you know, you could like ask the participants, like, you know, if for their feedback. At the same time, I've also seen if you ask someone, then they still do not Share a lot. So sometimes what I do is if I feel like the team, like, sorry, the meeting was not as efficient. It could have been been better. I voice it out before anyone else. It's like, ah, this, like, our meetings used to be better. What happened? You know, and then they start voicing out, yeah, you know what, like, thanks for saying that. So, like, okay, so you feel the same.

[B]

Yeah, open the conversation. That's absolutely that. And it's like the psychologists call, call it validation. Right. Like if you get the intuition. People are bored. They probably are.

[C]

Yeah.

[B]

Why, why don't we just talk about it like, you know, honestly and just open it up like that. Yeah, that was really boring for me. How about you guys? How did you feel exactly?

[C]

Absolutely.

[B]

That was great, Wasim. Thank you for sharing that.

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