Pod Insights The Agile Daily Standup - AgileDad What Makes a Great Scrum Master? About this episode What Makes a Great Scrum Master?
When people ask me, “What does it take to be a great Scrum Master?” my first response is always — In what kind of organization?
It’s not a dodge. It’s the most honest answer I can give.
We talk about Scrum Masters as if the role is universal — a fixed job description that applies equally everywhere. But the reality?
The Scrum Master navigating a twenty — person startup looks completely different from one guiding a 200-person enterprise team.
And both are doing the job right.
How to connect with AgileDad:
- [website] https://www.agiledad.com/ https://www.agiledad.com/
- [instagram] https://www.instagram.com/agile_coach/ https://www.instagram.com/agile_coach/
- [facebook] https://www.facebook.com/RealAgileDad/ https://www.facebook.com/RealAgileDad/
- [Linkedin] https://www.linkedin.com/in/leehenson/ https://www.linkedin.com/in/leehenson/
Transcript 0:15 Speaker 00 When people ask me what makes a great scrum master, my first response is always, what kind of organization is it? Because that actually makes a difference and people don't realize it. It's not a dodge. It's the most honest answer that I can give because all scrum masters and all organizations are not carved out to be the same. They're not carved out to be alike.
0:37 Speaker 00 We talk about scrum masters as if the role is just a universal, one size fits all role, a fixed job description that applies equally everywhere. But the reality? Scrum master navigating a 20-person startup company looks completely different from one that's guiding a several thousand-person organization. And both are doing a job right, both are doing the right thing. It's just they look different, complexion's different. What they do is different and how they behave is different. And I guess if I had to summarize it, here's what I've learned. So I put together a list of things that I learned and I want to review that list with you. Ceremonies don't make you a great scrum master. The impact that you have on a team, the organization and a leadership,
1:22 Speaker 00 the way that you impact change management, that makes you a great scrum master. Sure, you're going to run stand-ups and retrospectives and sprint planning meetings. Sure, you're going to be at reviews and demos. You'll help manage sprint backlogs with the team. You'll help protect the team's sprint goals and commitment. But every single one of those things are tools. They have nothing to do with the role itself. What truly matters is how you create space for your teams to thrive. And what that space looks like is radically different between organizations, depending on the environment, the culture and the types of products and services that you build. Think of it this way.
2:00 Speaker 00 A Scrum Master in a startup company might spend Monday coaching a team, Tuesday talking to the customers, and Wednesday helping debug deployment issues because everyone pitches in on a startup. A Scrum Master in an established company, a large organization, might spend those same three days navigating stakeholder politics, translating between departments using language, and advocating for team autonomy within existing structures and helping prevent interruptions to those teams by the people who are asking them to do the work. Both are valid, both are necessary, and both require certain skills. Both require a person to have a certain skill set. So in startup environments, fluidity is the norm. Resources like money and budgets are tight, the number of people you have available is
2:44 Speaker 00 also tight, priorities shift rapidly, and everyone does a little bit of everything. The Scrum Master here isn't just facilitating, they're building something. You might be clarifying acceptance criteria one hour and helping a UX person design a user flow the next hour. The lines between the roles and accountability start to blur because they have to, there's no other way to survive. There's no luxury of pure specialization when you're racing to find your product gets to market faster than the competitors. And startups, that's exactly what the story is. So what is the demand? It demands that you have comfort with ambiguity. Things are going to change fast, and your job is to help the team adapt without losing their momentum and make sure they can keep moving forward.
3:28 Speaker 00 You need to deal with hands-on problem solving. You can't just identify roadblocks. You need to help eliminate or help guide the team to eliminate those impediments quickly. You need to get them on board and move in that direction. When it comes to product thinking, you're close enough to the end customer that you need to understand what creates value for them so that you can drive things based on value or outcome instead of driving things based on output and what we can crank out. And resourcefulness, you have to learn how to work with limited budget constraints and you need to find creative solutions to solve our world problems. Those are the facts. The risk of doing this is that you lose sight of sustainable practice if you're trying to rush to ship or get something to market.
4:12 Speaker 00 Your job becomes protecting just enough of the process to keep quality high without slowing down the velocity of the team because that's an important metric for everyone else. Okay, let's talk about the corporate Scrum Master. In a larger, more established organization, the challenges shift dramatically. You're not trying to build things from scratch. You're often transforming what currently exists. You're taking a well-oiled machine, or a not-so-well-oiled machine, and making it well-oiled. In larger, established organizations, you have structures that are more rigid. Decision-making moves through multiple layers. Legacy systems that exist. Both technical and organizational resistance happens. You resist change. People resist change in those organizations.
4:57 Speaker 00 Your team might be ready to sprint, but you're surrounded by departments and partners and other people who are working in annual planning cycles. Happens all the time. The Scrum Master in this environment becomes something totally different. They become a translator, a shield, a culture warrior, and more often than not, a change manager. They need to figure out how to accept change management, how to do change management, and how to apply it inside of a large organization. So what does this demand? Right out of the gate, political savvy. You have to know how to understand and work with the different people, the different players, inside the system, within the system, while pushing for change across the board. It requires patience and persistence, because transformation happens so slow sometimes inside of large organizations because of the multi-tier approval system.
5:42 Speaker 00 You need to deal with stakeholder management, helping leadership understand why agile principles matter and why they should be paying attention. And then finally, you have to protect the team in a different way. Buffering on them from outside organizational chaos so that they can focus on delivery and focus on getting the things built that we actually need to get built. The risk here is becoming so caught up in organizational navigation that you lose touch with the team's actual needs. I've seen that happen a bunch of times. Your job is balancing advocacy upward with support downward and making sure you're hitting both sides of that equation. So there are a set, in my opinion, of universal qualities or unique qualities that transcend everything. So for example, having a servant leadership mindset, whether you're, whether
6:27 Speaker 00 you're working out of a garage or a high, high-rise glass tower, or working from home, your job is to make others successful and not to be the superhero. I've seen too many times where it's, you know, come on superhero, stay your stupid line, where they come in wearing the Lycra suit and the cape, I can do anything, I'm the Scrum Master. And it's like, oh, stop, right? You need to have a servant leadership mindset and push everyone else to do better. You need to have emotional intelligence. You need to be able to read the room. That matters. And you need to sense when a team needs encouragement versus when they need some tough love. Knowing when to push them, when to listen. You know, you got no one to hold them and no one to fold them, no one to walk away and no one to run. You never count your money while you're sitting at the table. There'll be time enough to count it when the dealing's done.
7:13 Speaker 00 That was as Kenny Rogers as I can get. All right. You need to have adaptability. This is a non-negotiable. The ability to shift your approach based on what the team's needs are right now, not what worked yesterday, last week, or last month. You need to be able to pivot quickly. How about focus on outcomes over outputs? In any and every environment, it's easy to mistake activity for progress. People do it all the time. Oh, we're active, we're moving. That means we're regressing. Not necessarily. Great Scrum Masters keep everyone anchored. And the question that they keep asking is, it's great that we're delivering things, but are they creating value? Are they delivering value? I think that's important. And then finally, a genuine curiosity. The best Scrum Masters I know are ones who ask powerful questions. And instead of giving a preformed
7:58 Speaker 00 answer, or a prescriptive answer, they create space for thinking and not compliance. They let people's thought processes roll before they give what will be the de facto answer, right? So if you're new to Scrum Master role, I have some advice for you. Be honest with yourself about which of these environments energizes you. Do you thrive in chaos? Do you love building something from nothing? Are you comfortable with the responsibilities if they shift daily? Then if that's the case, startups are your jam. You'll do it perfectly fine there. But if you enjoy more strategic thinking and you love to play the long game and you're energized by complex systems and leading change at scale within an organization, then working in a corporate environment might be more suitable for you. Neither is better, neither is more agile.
8:43 Speaker 00 They're just different games that require different strengths from people who can help you through and walk through these things. And here's the thing, whichever path you choose, remember you're not defined by the ceremonies you facilitate. You're defined by the teams that you empower, the obstacles you clear, and the culture of continual improvement that you help create within the organization. As you step into this role or grow within it currently, pay attention to the context that you're operating in. Pay attention to the ecosystem and the environment. Don't try to copy someone else's playbook without considering their environment. What worked for them may not work exactly the same for you. And that's okay. It's not that you're not agile. The question isn't, am I doing agile right or am I being a good Scrum Master?
9:28 Speaker 00 It's asking, am I creating conditions for my team and organization to be successful, given the reality that we're currently in? That should be the real question that's bouncing around in your mind. Now, I did create an essential Scrum Master playbook. And what I can tell you is the thing about that book that's so cool is right in the very beginning, one of the first pages says, "It's not intended to be a dogmatic or prescriptive approach to this. It's meant to be a guide that you can pull the best pieces from to help you and your organization be successful." And I think that if you approach it that way, there are a lot of good tidbits and small pieces of information in there. There's a beginner's checklist and advanced checklist. There's even an evaluation scorecard at the end that you can use to either evaluate yourself against the things you should know or to evaluate Scrum Masters within the organization to kind of see how things stack.
10:15 Speaker 00 All good tools, all current tools, and all things that you can get right now today. 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. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye now.
Previous The 7 Two-Minute Habits That Make People Actually Want to Follow You Next Story Point Estimations are failing your Team! - Here We Go Again... Page updated November 6, 2026 · transcript and summary are machine-generated