Pod Insights The Agile Daily Standup - AgileDad Scrum Masters Are Useless — Product Managers Should Run Their Own Scrum About this episode Scrum Masters Are Useless — Product Managers Should Run Their Own ScrumWe’ve all been there. It’s 10:00 AM. You’re in a standup, sipping your third coffee, while the Scrum Master dutifully asks each developer, “What did you do yesterday? What are you doing today? Any blockers?”Someone mumbles something about JIRA tickets. Another person reports, “Same as yesterday.”Meanwhile, the Product Manager (PM) is frantically jotting notes, trying to connect the dots between what was promised and what’s actually happening. And the Scrum Master? They nod, write things down, and move on. Here’s the controversial take: Do we really need a dedicated Scrum Master for this? Or should Product Managers just run their own scrums? 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 The Daily Scrum, the 15-minute meeting that lasts a lifetime. We've all been there. It's 10:00 a.m., you're in stand-up, sipping your third coffee while the Scrum Master dutifully asks each developer, "What did you do yesterday? What are you doing today? Do you have any blockers?" Someone mumbles something about Jira tickets. Another person reports, "Same as yesterday." Meanwhile, the product manager is frantically jotting notes, trying to connect the dots between what was promised and what's actually happening. And the Scrum Master, they nod, write a few things down, and move on. Here's the controversial take: Do you really need a dedicated Scrum Master for this? Or should a product manager just run their own daily Scrum? Uh-uh. Here we go.
1:00 Speaker 00 Scrum Masters were born from the Agile Manifesto, a framework that aimed to reduce bureaucracy and improve collaboration. Ironically, in many organizations, they became exactly what Agile tried to avoid: the extra layer of process without clear value. Let me break it down for you. So I'm going to break it down into three simple statements. One, most Scrum Masters don't own the product vision, and this is what leads to their demise. A good product manager understands the why behind every feature. They know what's critical, what can wait, what aligns the company's goals. A Scrum Master? Not so much. Their job is to facilitate, not to decide, which means they run the scrums, but they
1:43 Speaker 00 may not be adding strategic value. So if you're a Scrum Master and you're trying to hold on for dear life, you need to find a way to add strategic value. Let's go to number two. A well-functioning agile team doesn't need a babysitter. Scrum masters often serve as the team therapist, helping unblock engineers and shield them from distractions. But in high-functioning teams, developers already raise concerns directly with other engineers or PMs or other people. So if a team is truly self-organizing, self-sustaining, and self-policed as agile suggests it should be, why do you need someone to remind us, "You gotta update your Jira tickets," right? And I think sometimes people, once again, look at the Scrum Master as just the secretary or glorified secretary.
2:28 Speaker 00 And they do so much more than that, but I think people miss the mark. Let's go to number three. Product managers are already doing the real work. In many teams, product managers already lead the conversation during stand-ups. They tend to clarify priorities, track dependencies, identify risks, escalate blockers. So what exactly is the Scrum Master doing in these cases besides keeping time, making sure we stay within 15 minutes? You know, I have a counter-argument. Scrum masters reduce the product manager's burden. Some people can argue that removing Scrum Masters would add more work for PMs. But here's the thing. Good PMs are already running a stand-up in practice.
3:12 Speaker 00 They know about the roadmap. They understand the impact of delay. They ensure the work's actually leading the team to a successful release. In fact, in fast-moving startups or lean teams, Scrum Masters are often non-existent. And you know, sometimes those teams still ship. I think for me, most people don't understand that 70%, 7-0% of what a Scrum Master does is intangible and can't be reported on. So as a result, people don't realize that the Scrum Master's primary role is to facilitate the clear engagement of the team and to open paths so that the team can directly interact with stakeholders and other key people to keep communication flowing so that the team avoids rework.
3:55 Speaker 00 And you know, increasing productivity of the delivery team in any way possible, making sure that they they have all the tools they need to be successful is not an easy job. And I think that sometimes the way I like to delineate it is I like to think of a product manager as the governor of the product. And I like to think of a Scrum Master as a governor of the people. You need both in order to have success, but they do play off of each other. So is there data to back any of this up? A lot of people say, give me data and it's real. So they had a state of agile report in 2023, found that 64% of teams said the Scrum Master role was unclear or overlap with other roles. Hence, this leads to the problem.
4:36 Speaker 00 Forty-seven percent of teams in small to medium sized companies don't even have a dedicated Scrum Master. Oftentimes, engineers step up and fill in the gap, right? Or engineering managers. High performing teams, as ranked by velocity and release cadence, were just as likely to have a PM run agile process as they were to have a dedicated Scrum Master. Uh, translation? The role of the Scrum Master is often either A, completely misunderstood, B, considered a nice to have and not a must to have. It's one of those two, right? So does that mean we should go and fire all the Scrum Masters? Do we have to be Capital One today? Not necessarily. Scrum Masters can still be valuable. If a team is new to agile and they need coaching,
5:21 Speaker 00 or they're a newly formed team and they're trying to work their way through storming, a Scrum Master is a great person to have on board. If there are organizational roadblocks that require a full-time advocate to open doorways with stakeholders and with leaders and to help people understand exactly where we're trying to go. You know, that that would be another good reason to have a Scrum Master. What about if product managers are overwhelmed with strategy? Or they have way too much whip, way too many things in progress? And the organization doesn't understand why everything's not going as planned and the team's not delivering to cadence? And part of that is because, well, there's too much whip.
6:00 Speaker 00 I think that if we get product managers and product owners to understand their role, it's going to make the role of the Scrum Master shine and be a lot easier to understand. However, when organizations don't understand the Scrum Master role, the product manager role gets overwhelmed and then you're trying to make them in charge of both strategy and execution. And it can create turmoil, direct nightmares. So if your team's experienced, collaborative and high functioning. I think, you know, they'll see less, I shouldn't say less use, but they will not see the full potential of having a strong Scrum Master. If your team is newer or focusing on things that could have high risk, or they just, they're really trying to get their agile wheels spinning,
6:44 Speaker 00 Scrum Masters are a critical part of the role. So I think that you need to remember the Scrum Master is not just a highly paid meeting facilitator or a secretary to take notes, and they're not there just to remove impediments. A Scrum Master is there to make sure that everything flows smoothly and that everyone has an opportunity to work together. Okay, so that's gonna do it. I hope you enjoyed this episode. If you have a topic you want us to discuss, learn more at agiledad.com. We'd love to hear from you. As always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care.
Previous The Time For You to Grow Next Are Story Points Helping Your Team? Page updated November 7, 2026 · transcript and summary are machine-generated