Pod Insights The Agile Daily Standup - AgileDad What If Scrum Masters Only Want To Act On A Team Level? About this episode What If Scrum Masters Only Want To Act On A Team Level? I recently had an interesting conversation with a manager at a large organization. We discussed the evolving role of Scrum Masters, the growing questions about their value, and whether organizations are seeing actual returns on these investments. 💰We agreed that the most significant impact for Scrum Masters is not within the team, but in the environment and the broader organization. Initially, I assumed that Scrum Masters in this organization were restricted from engaging beyond their teams. But I was wrong. They chose not to. How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:16 Speaker 00 Someone recently pointed out to me an article by Barry Overeem. Now, I've seen some of his articles before and so far I've been impressed with those. This one is called "What if Scrum Masters only want to act on a team level?" And I thought this was really interesting because it's a thought that frequently comes up, actually. It's not an uncommon one. So, he starts off his article with "I recently had an interesting conversation with a manager at a large organization. We discussed the evolving role of Scrum Masters, the growing questions about their value, and whether organizations are seeing actual return on investments. We agreed that the most significant impact from Scrum Masters is not within the team,
1:00 Speaker 00 but in the environment and the broader organization. Initially, I assumed the Scrum Masters in this organization were restricted from engaging beyond their teams, but boy, was I wrong. They actually chose not to. Many Scrum Masters were uninterested in navigating organizational politics, collaborating across departments, or engaging with management to address systemic challenges. Their focus remained firmly on their teams. This wasn't my first time encountering this, but it still caught me off-guard and surprised me. Can a Scrum Master truly be effective to operate only at the team level?" So, let's stop here. I love the diagram that comes next. So, in his article Barry points out that there's three levels of Scrum Master.
1:45 Speaker 00 Now, I often refer to this as three levels also. Now, for clarification, when I say three levels, I usually say... Well, first I remind people that product owners are responsible for organizing the backlog in such a way the work is easily consumable, and it makes it very easy and lightweight for the team to swarm and get the work done. So, the team members are responsible for adhering to the goal and, you know, setting a sprint goal, adhering to a sprint goal, and delivering products or services that meet the outcome needs of what the product owner is requesting. Now that we got that out of the way, that means that if I'm a team member, I only want to have to build a relationship with one Scrum Master. I don't want to have to build a relationship with many, many Scrum Masters.
2:29 Speaker 00 Likewise, if I'm a product owner, I might want to have many Scrum Masters at my disposal to say, "Hey, do any of you have teams that can come in and help?" And what I mean by that is, a single Scrum Master, if they're a Level 1 Scrum Master, brand new, they're just focused on that one Scrum Team, making them work, helping them get the things they need to get done, you know, chasing a dream, removing obstacles when necessary, helping facilitate meetings. It's a Level 1 Scrum Master, they're learning the ropes and doing the basic stuff. A Level 2 Scrum Master can usually be a Scrum Master for 2 teams, meaning that they have 1 team that's pretty smooth sailing and they have another team that maybe is learning the ropes, but they still have the capacity to handle 2 teams because they're experienced in what they do and they understand basically just what a Scrum Master does.
3:14 Speaker 00 In his diagram, he calls this "relationships." And then they have what's called the Level 3 Scrum Master, and he calls it "the entire system." Now, when I think of a Level 3 Scrum Master, I tell people all the time, "I never want a Scrum Master to govern more than 3 teams at any given time." So it's 1 team for a Level 1, 2 Scrum Teams for a Level 2, and up to 3 teams for a Level 3. A Level 3 Scrum Master usually has a year or more experience under their belt working as a Scrum Master. They feel like they understand the roles and accountabilities, and they also, this is interesting, he calls it "entire system", they engage with more than just the teams. So this is where they start engaging with stakeholders and start engaging with other people and helping establish an agile center of excellence within the organization.
3:57 Speaker 00 So this is where you're starting to see the benefits of having a Scrum Master. This is where you start to see the value. And I think that when organizations start saying they're not seeing value in a Scrum Master, it's typically the number 1 reason is because they're allocating or associating Scrum Masters with products or projects and not letting Scrum Masters govern teams. And they're making product owners limited to have 1 Scrum Master for their product or their project instead of letting product owners have free rein and talking to multiple Scrum Masters. So common pitfalls Scrum Masters is becoming too embedded in a single team's dynamics, sometimes to the point of limiting autonomy and ownership of the team.
4:38 Speaker 00 Meanwhile, the toughest impediments often lie beyond the team in outdated structures, policies, and leadership mindset that hinder their agility. If Scrum Masters don't step beyond the team boundaries, who will tackle these more profound challenges? Who will drive change at the organizational level? By the way, this is the reason why change management is so important. This is the reason why we're starting to see that shift, where people are saying, "We're getting rid of Scrum Masters and hiring change managers or agile project managers." You're starting to see that more and more. And it's not because it's a different role. It's because the accountabilities are more clear. So because the Scrum Master role isn't just about Scrum, it's about team and organizational development. It's about tweaking an entire system to create an environment,
5:22 Speaker 00 an ecosystem where teams can genuinely thrive and grow and do the things they need to do. Should an organization settle for just a Scrum Master who only wants to stay within one team's boundaries? If it's a brand-new Scrum Master, maybe. But if not, I'd argue you shouldn't. Although some of their work is valuable, I can understand the questions about value and impact of a Scrum Master if they're hyper-focused on one team only. Maybe it's just the gray winter days affecting my mindset, but I'm not feeling too optimistic about the state of the Scrum Master role in this case. More and more, it seems to be shrinking into a narrow team-only focus, when a real value lies in shaping the system around it. Or is it me that should reconsider the way that I'm thinking?
6:06 Speaker 00 And knowledge of Scrum Master role is primarily focused on teams, with an impact on the broader organization being an added bonus. Okay, so I can tell you right now. So Barry, I think that was tongue-in-cheek. I hope it was tongue-in-cheek. Because what I can tell you is Scrum Masters need to reach out beyond their comfort level. Meaning, Scrum Masters govern one team automatically, two teams typically, and up to three, but never more than three, because then they're spreading themselves too thin and they're not giving those teams the level of aptitude they need in order for everything to function properly. So there's just so many things that you have to take into account. But I think the big key here is, if Scrum Masters focus on learning their accountabilities and they can really deliver value, good value, great value,
6:50 Speaker 00 not Walmart great value, but anyway, if they could deliver great value. Then what you'll discover is that they can be most effective and that that's going to be what helps the most. So if you're a scrum master, understand change management, understand how to leverage AI, understand how to create an agile center of excellence, understand how to promote and support agile within the organization, and don't go chasing Scrum or Falls. You'll get stuck in the waterfall and cryptic things like Gantt charts that you're used to. That's going to do it for this episode. I hope you enjoyed it. If you have a topic you want us to discuss, learn more at agiledad.com. We'd love to hear from you. Thanks for a great article, Barry. And we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye now.
Previous Are You Chasing ScrummerFalls? Next 3 Critical Skills That I Have Learned as an Agile Coach Page updated November 6, 2026 · transcript and summary are machine-generated