Pod Insights The Agile Daily Standup - AgileDad Dedicated vs. Rotating Scrum Masters About this episode Dedicated vs. Rotating Scrum MastersI spent my first five years as a Scrum Master primarily dedicated to one team. As a result, I got to know team members deeply. Even 10+ years after I left, I’m still in close contact with some of them. Due to frequent changes in the team — people come and go — improving team dynamics was a continuous effort. However, after a while, our team understood Scrum, and I could shift my focus towards the broader organization and our customers. 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:15 Speaker 00 Let's continue on a path of the things that are most commonly asked. So one of the questions I got recently is a common question and I kind of forgot about answering, to be honest. It's whether a Scrum Master should be a full-time dedicated position, or whether a rotating Scrum Master accountability was acceptable. This is a difficult one to swallow and I think you'll see where I'm going in a little bit here. It's one of those things where I understand how some organizations feel they have a need to have a rotating Scrum Master, one, to get everyone familiar with being able to handle objections or handle interference or interruptions or any kind of impediments,
0:57 Speaker 00 and getting everyone on a team involved in getting that understanding and gaining that leadership skill. But at the same time, how much of their dedicated focus does it take away from the things at hand that they need to work on? So it's one of those things where you've got to have some type of balance now. Also in startups, I've discovered where sometimes leaders end up fulfilling the role of Scrum Master because there's just not enough people on the ground for someone to take on that role and obviously they're not doing it full-time. So, I'll start with this. I spent the first many years of my career as a Scrum Master dedicated to one or two teams. As a result, I got to know every team member deeply. And even after 10 plus years, after I was long gone from this project,
1:43 Speaker 00 I can still be in close contact with some of those people because they built relationships with me. Due to frequent changes in the team, some people come and go. Improving team dynamics was a continuous effort. However, after a while, the team understood Scrum and I could start shifting my focus towards broader organizational excellence in Agile and focusing on our customers and improving communication with stakeholders.
2:07 Speaker 00 The following four years were probably mostly spent as what I would consider a freelance Scrum Master or hired via, you know, some type of consultancy or coaching contract. Consequently, I worked with dozens of different teams and organizations all over the world. Initially, I found it quite stressful, but after a while, I learned how quickly read the situation, become part of the team, and from the start, prepare the team to succeed with Scrum without me. How important those types of things were. So both types of experiences, the dedicated one or the rotating one, were tremendously valuable. I wouldn't have wanted to miss either of them.
2:47 Speaker 00 What I treasured the most from working with many different teams is how I learned to quickly assess what's going on, spot patterns, and offer experiments that I've seen work successfully in other contexts. So I see many Scrum Masters who work permanently for one organization and have been with the same team for a very long time. In certain domains, teams are stable, so they work with the same team members for years. Combining a role with another specific skill set needed for the team limits this flexibility. Given these insights, I was forced to wonder, could organizations benefit from a more flexible approach to Scrum Masters? An interesting experiment could be to work without dedicated Scrum Masters
3:31 Speaker 00 and instead create a flexible pool of Scrum Masters that people could pull from. But to make this work, potential agreements would be, Scrum Masters only work for one year with the same team to keep fresh ideas flowing. New teams always have a Scrum Master. If the team is relatively stable, they decide after a year whether to continue with a Scrum Master or self-manage with occasional guidance. Scrum Masters rotate across different types of teams and domains in large organizations. There are plenty of opportunities for this. And if Scrum Masters aren't assigned full-time to one team, they coach to broader organizations and stakeholders. This allows them to fulfill the role as needed. Now, What I can tell you is this is good from a sense of innovation and keeping things moving
4:16 Speaker 00 and keeping things interesting, but it's also bad news for the people on a team who may be introvert and build a relationship with a single person and aren't interested in building a relationship with an entire pool of people, right? So for some Scrum Masters, this will be completely outside of their comfort zone. But for other Scrum Masters, this will be a rock star opportunity. Isn't that what a real learning happens though, when you're in a little bit of discomfort? There are always reasons why it wouldn't work, and those are valid concerns, but opportunities to rethink about how we engage agility is a positive thing. What I'm trying to say is, if you find that a team isn't in high performing and they're starting to get complacent, or that a Scrum Master is not advancing in their career and
5:00 Speaker 00 learning new things, sometimes switching things up might be a good idea. But I'm more curious than ever about what your experience is with this. What have you seen? What I can tell you is, in most organizations, I just span the Scrum Master across multiple teams. So when they're starting out, it's one Scrum Master, one team. As they gain experience, it's one Scrum Master, two teams. And then when they become an expert, it's one Scrum Master with three teams. I never surpass three, even though it's possible to, I just don't. I'll use all their extra bandwidth to build that internal Agile Center of Excellence, like they were talking about, you know, like we were talking about earlier. So I think it's important for you to understand where you are on a spectrum, what type of organization you're operating, whether it's startup or something well established, how
5:43 Speaker 00 many people you have available, and how you align the Scrum Masters with the organization. Remember, Scrum Masters should be governing teams, not aligned with specific, with a specific product or service. You want to make sure product owners have multiple Scrum Masters they can go to to help resolve impediments, and that team members only have to worry about building relationships with a single Scrum Master. That's going to do it for this episode. I hope it helped you. If you have a topic you want us to discuss, learn more at agiledad.com. We would 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 Bring Focus to Your Refinement Meetings - Mike Cohn Next Top 5 Ways to Be Better at Giving and Receiving Praise Page updated November 6, 2026 · transcript and summary are machine-generated