Pod Insights The Agile Daily Standup - AgileDad The Five Dimensions of Real Scrum Mastery About this episode The Five Dimensions of Real Scrum Mastery
The Courage to Have Uncomfortable ConversationsThe Art of Knowing When to Step In (And When to Step Back)Creating a Space Where People Feel Safe to Be HumanTeaching Teams to Fish (Instead of Giving Them Fish)Being the Change You Want to SeeHow 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:17 Speaker 00 A little bit ago, a short time ago, we recorded a podcast that was talking about the name Scrum Master and how it's shifting from servant to catalyst. And we had a lot of people reach out and ask, what does that actually look like day to day? So I thought I would kind of paint a picture of this, but someone sent me an article that was interrelated. It was adjacent, but interrelated. So I thought I'd take this opportunity to take both of these and talk about what this author refers to as the five dimensions of Scrum Mastery. Sounds like, you know, sounds like the five dimensions of Scrum Mastery. Sounds, sounds very psychoanalytic, but let's see where it goes.
1:01 Speaker 00 And I have a feeling based on the author that I'm gonna like these five. So, so let's see where it goes. The first one they point out is the courage to have uncomfortable conversations. During those initial months, one time our team's velocity dropped below, dropped in third sprint in a row. Easy path, run another retrospective, tweak the processes, hope for the best. The real path, walking into somebody's office to discuss how their urgent requests were destroying the team's focus. My palms were sweaty, my voice probably shook a little, but here's what I learned. Protecting your team sometimes being, sometimes means being uncomfortable so that they don't have to be uncomfortable.
1:44 Speaker 00 The conversation went something like this, when everything is urgent, nothing is urgent. Your team is drowning, not because they're not capable, but because they're being pulled in 17 different directions. Let me show you some data. Two weeks later, we had proper intake process, the team could breathe again, and everyone lived happily ever after. Sometimes being a Scrum Master means being the voice that says what other people are thinking, but don't feel comfortable saying. I like that one. Let's go number two, the art of knowing when to step in and when to step back. This might be the hardest one to master. Watching any parent teach their child to ride a bike. That's us with our teams. Too much help and they never learn to balance. Too little help, they'll fall and fall and fall and lose confidence.
2:29 Speaker 00 I used to jump in whenever I saw the team struggling. Now I take a moment and count to ten. I asked myself, is this a learning moment or a drowning moment? One time, two developers were stuck on a design decision. Old me would have facilitated the meeting immediately. New me, I watched them struggle for about forty minutes and then I saw something magical. They grabbed a whiteboard, started sketching and found their own solution. The pride on their faces was worth was worth way more than any of the quick fix options that I could have provided. Thanks. Number three, creating a space where people feel safe to be human. Psychological safety isn't just a buzzword. It's the difference between a team that functions and a team that flourishes. Here's what it really looks like.
3:14 Speaker 00 One of our usually stellar developers admitted she had been making mistakes because she was going through some personal difficult situation. The team didn't judge. They adjusted, they offered support, they covered for each other naturally without being asked. How do we get there? All the small things, celebrating failures in retrospectives. What do we learn? Sharing my own mistakes openly, making it okay to say, I don't know, or I need help. Innovation doesn't come from perfect people. It comes from imperfect people who feel safe enough to try and fail and then try again. All right, let's go to number four. Teaching teams to finish, teaching teams to fish instead of just giving them their fish. Oh, boy. The temptation to solve a problem for the team is real.
3:58 Speaker 00 You see, the issue is, you know, the answer, why not just fix it? Because that's not growth, that becomes dependence. Instead, I've learned to ask questions. What patterns are you noticing? What have you tried so far? What would happen if we didn't solve this right away? One of my proudest moments? Overhearing a team run their own improv to retrospective when I was out sick. They identified issues, proposed solutions, and even assigned some action items. They didn't need me to do this. They learned to think like problem solvers. I love that. And then number five, being the change you want to see. Teams watch what we do more than what we say. Want them to be transparent? Share your own challenges openly. Want them to embrace feedback? Ask for it publicly and act on it.
4:42 Speaker 00 Want them to respect work-life balance? Why don't you leave on time? I once worked late for weeks, thinking I was being dedicated. Then one of my team members said, "If you don't respect your own time, why would we respect ours?" And that hit hard. Now I model my behavior of what I want to see, to what I want to see, boundaries included. Some days, we end up facilitating ceremonies, but even that's teaching moments. I'm showing them how to run an effective meeting, so one day they won't need me to help them do it. Other days, I'm sitting with a product owner who's drowning in stakeholder demands, helping them find their backbone and their voice to say no. We role-play difficult situations. We create stakeholder maps together. We practice saying "not now", and sometimes even saying "no". I'm not telling them what to prioritize.
5:27 Speaker 00 I'm helping them build the confidence and frameworks to make those tough calls themselves. Sometimes, I'm shadowing a team during our technical discussions, not to contribute to code solutions, but to spot collaboration patterns. When I noticed two developers constantly talking past each other, I gently introduced them to techniques like "repeat back what you heard" or "visual modeling". It's like being a communication translator, helping brilliant minds connect better. Then there are days where I'm sitting in a customer feedback session, not to take over, but to help the team really hear what's being said beyond the words. Did you notice how three different customers mentioned in the same pain point in three different ways? Teaching the team to listen for patterns and not just problems.
6:11 Speaker 00 And yes, occasionally, I do become the shield between the team and the organization. When leadership wants to just add one more thing to the sprint, I'm the one who has to have those crucial conversations about sustainable pace and focus. I've learned to say, "We can do anything, but we can't do everything." What would you like for us to stop doing to make room for this? Because burned-out teams just simply don't deliver value. They just deliver bugs, technical debt, and eventually resignation letters. Every action, every decision, every uncomfortable conversation serves one purpose: helping the team discover how capable they really are. It's not about being the hero. It's about helping them realize that they don't need a hero.
6:56 Speaker 00 If you're a scrum master feeling stuck in facilitation route or wondering if there's just more to this role that you don't get, trust me, there is. You're not just running meetings, you're shaping culture, you're building capabilities, you're creating the conditions for extraordinary things to happen through ordinary people. Start small, pick one area. Maybe it's having a difficult conversation you've been avoiding, maybe it's stepping back when you need to step in. Whatever it is, remember, your role is not to be perfect, it's to be present, authentic, and committed to growth. Both your growth and their growth. You should also be focused on organizational change management and understanding how you can create an agile center of excellence that's going to greatly impact the ability for the organization to change.
7:41 Speaker 00 And finally, you should be focused on AI and mastering it, and teaching, mastery of prompt writing and learning and studying, so that you can improve your skills and add value to your team or organization, or both. 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 on agiledad.com, we would love to hear from you. As always, we encourage you, stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye now.
Previous Is Sprint Planning Quietly Hurting Teamwork? - Mike Cohn Next How Are You Today? I'm Fine, Thanks... Page updated November 6, 2026 · transcript and summary are machine-generated