Does a Scrum Master Really Need to Facilitate Every Scrum Event?
Fact or Myth
Have you ever wondered if a Scrum Master is just a meeting host? If you’re a manager or Scrum enthusiast, you’ve probably seen countless job descriptions insisting the Scrum Master “facilitates all Scrum events.” It’s almost an expectation that the Scrum Master will run every Daily Stand-up, Sprint Planning, Review, and Retrospective. But is that really what Scrum intended? 🤔 In this post, we’ll debunk the common misconception that a Scrum Master must be the default facilitator in every Scrum meeting. We’ll explore why this belief became so widespread, how it can hurt your team, and why letting the team run their own events can be a game-changer. Let’s dive in!
The Problem
Many organisations have hardcoded the idea that the Scrum Master should lead every Scrum event. It’s a familiar scene: one person (often the Scrum Master) kicks off the Daily Scrum, walks the team through Sprint Planning, and guides discussions in the Retro. This expectation is so ingrained that Scrum Master job postings routinely list “facilitate Scrum events” as a primary responsibility. Why is this belief so common?
For one, having a clearly identified facilitator gives managers a sense of control and structure. Early in a team’s Agile adoption, a Scrum Master taking charge of all events can show quick results. In fact, many new Scrum Masters jump in and lead the five Scrum events to “show the way” and demonstrate immediate value to stakeholders. It’s a visible, tangible contribution – the meetings start and end on time, and someone seems to be “driving” the Agile process. Companies also invest in Scrum Masters’ facilitation training, so naturally they expect those skills to be “put to use”. All of this reinforces the notion that the Scrum Master = meeting facilitator. Over time, it’s no surprise that everyone just assumes “the Scrum Master runs all the meetings” – that’s how they’ve always seen it done.
Breaking the Myth
Before we even get into facilitation, let’s get something straight: Scrum Master is an accountability, not a role or job title. The Scrum Guide does not define it as a full-time position, nor was it ever meant to be. In fact, Ken Schwaber and Jeff Sutherland originally envisioned the Scrum Master accountability being taken on by one of the Developers in the team. It was never intended to be a separate career path. But over time, misinformed interpretations of Scrum led to the creation of job titles like Scrum Master or Iteration Manager, which completely blurred the true intent of the role. These job titles fuel the misconception that a Scrum Master is a permanent facilitator, when in reality, Scrum simply expects someone in the team to uphold the accountability—often alongside other work. If the Scrum Master accountability is held by a Developer, the entire notion of the Scrum Master facilitating every event becomes irrelevant. Why would a Developer running Scrum events for their own team need a dedicated meeting facilitator?
A dedicated Scrum Master that often imposes and facilitates every meeting and event will be stepping over the line of empowering and enabling the team to be self-managing. There is this illusion that the Scrum Master must be in control and manage the team. Even with good intentions, it often leads to teams not taking ownership, not growing into self-organising then self-managing; thus, keeping the team in control and managed. This puts the breaks on teams’ growth and progression to become hyper productive. When you start digging into this deeper, this is more a manager mindset than one of servant-leadership; it has a hint of command-and-control.
Nowhere does the Scrum Guide 2020 require the Scrum Master to personally facilitate every event. 📜 The Scrum Master is accountable for ensuring Scrum events happen and meet their purpose – but that’s not the same as literally running them. The Scrum Guide says the Scrum Master is responsible for “ensuring that all Scrum events take place and are positive, productive, and kept within the timebox.”
Notice it doesn’t say “Scrum Master must facilitate” each one. It simply means the Scrum Master makes sure the team holds the event, and it stays on track. The “how” of the event can be (and often is) handled by the team itself.
Take the Daily Scrum as an example. The 2020 Scrum Guide defines the Daily Scrum as a 15-minute planning event for the Developers on the team. If the Scrum Master (or Product Owner) isn’t actively working on items in the Sprint, they don’t even need to attend that meeting! This clearly shows that the Developers can run the Daily Scrum on their own. A common phrase we taught in the PSM I course was “for the developers by the developers”. The Scrum Master’s role is to ensure that daily planning happens, not to stand at the board asking each person to give a status update based on the three questions. In other words, the Scrum Team doesn’t require a designated “boss” for their daily sync – they can self-organize that discussion.
In fact, Scrum.org directly calls out the idea that “The Scrum Master facilitates all Scrum Events” as a myth. In PSM II classes we played a game call Myth Busters as an ice breaker, and this was one of the questions we asked. Yes, Scrum Masters are skilled facilitators and often help teams, especially new teams, have effective meetings. However, this doesn’t mean the Scrum Master is required or expected to lead every session. The 2020 Scrum Guide encourages teams to share these responsibilities. A Scrum Team is self-managing, meaning members internally decide who does what, when, and how– and that includes how they conduct their meetings. Any team member can step up to facilitate an event if it makes sense.
When I was a Professional Scrum Trainers, I and other PSTs warn that treating the Scrum Master as the default event leader is a trap. As a fellow trainer puts it, “Believing that event facilitation is the Scrum Master’s exclusive duty couldn’t be further from the truth”. The Scrum Master should always keep the development of the team’s self-management in mind. In PSM I training, we show the growth and maturity model of a Scrum Master and over time the aim is to be “invisibly present” – guiding the team without dominating every conversation. The bottom line: Scrum does not mandate that the Scrum Master must facilitate all events. That’s a misunderstanding of the role.
Why This Mindset Causes Problems
So, what’s the big deal if the Scrum Master runs all the meetings? It might feel efficient, but it can actually backfire. Here are some ways this mindset creates issues for your team and organization:
Stifled self-management and team growth: When the Scrum Master always takes charge, the team doesn’t get to practice self-organizing their work. It limits the team’s ability to manage themselves and learn how to collaborate without external control. Over time, team members become dependent on the Scrum Master to drive every discussion. This crutches their growth – instead of stepping up, they wait to be directed.
The Scrum Master becomes a bottleneck: Relying on one person for all facilitation makes that person a single point of failure. If the Scrum Master is sick, on vacation, or double-booked, does work grind to a halt? It often does when the team hasn’t learned to run events on their own. Ironically, a well-intentioned Scrum Master who persistently facilitates everything can turn into the bottleneck and a weak link in the team’s progress scrum.org
.
Scrum Master overload (and loss of focus): Facilitating every meeting can consume a huge chunk of the Scrum Master’s time and attention. This leaves less bandwidth for them to tackle impediments, coach team members, or drive improvement initiatives – which are actually some of the most valuable parts of their job! Instead of observing team dynamics and working on organizational challenges, the Scrum Master is tied up preparing agendas or herding the meeting along. The team loses out on a lot of servant leadership value because the Scrum Master is busy being a meeting moderator.
Misunderstanding the Scrum Master’s role: Always putting the Scrum Master at the front of the room can reinforce the false idea that they are just a meeting administrator. This is a narrow (and incorrect) view of the role. The Scrum Master is much more than an event facilitator – they are a coach, a mentor, a change agent. In fact, focusing only on event facilitation is “the biggest misunderstanding” of the facilitator stance. If management and teams expect nothing beyond “helicoptering” meetings, they’ll undervalue the real contributions a Scrum Master should be making.
In short, a Scrum Master who micromanages every event can inadvertently create a passive team and become overworked (and underutilized) themselves. It effectively puts the brakes on a team to learn ownership and self-organisation and to grow into self-managing. It’s a classic case of good intentions leading to unintended consequences. As the saying goes, the road to Agile hell is paved with micromanaged ceremonies! 🔥
Encouraging Self-Management
Scrum thrives when the team shares ownership of its events. A self-managing Scrum Team is empowered to run discussions and make decisions without waiting for a designated facilitator at every turn. The Scrum Master’s prime directive is to foster this self-sufficiency. The Scrum Master coaches the team in self-management and cross-functionality, nudging them to take charge of their own process. By stepping back, the Scrum Master creates space for the team to step up.
So how can teams handle events without relying on the Scrum Master to lead? Here are some tips to build that muscle of self-management and reap the benefits for everyone:
First, focus on having the right conversations and stop caring about who facilitates the event. We are dealing with professional adults who have likely been in hundreds of meetings in their career and they know how to converse.
Rotate meeting facilitators within the team. Have a Developer figure out how they run their Daily Scrum as a 15-minute event does not require facilitation. Ask a team member to lead the Sprint Retrospective discussion. Rotating these roles spreads skills around and signals that the meeting belongs to the team, not to the Scrum Master. The Scrum Master can attend as a peer or coach but let someone else hold the marker or drive the screen share.
Clarify the purpose and agenda of each event. Ensure the team knows why they are meeting and what outcome they need from each Scrum event. When the purpose is clear, the team can collectively keep themselves on track. For example, if everyone understands the Sprint Review is about inspecting the product and adapting the backlog, they can self-facilitate that conversation towards those goals. The Scrum Master might give a gentle reminder, but they shouldn’t need to direct every question.
Scrum Master as a teacher, then observer. In the early stages, a Scrum Master might demonstrate effective facilitation techniques – e.g. show the right conversation to have in Daily Scrum or introduce a format for Retrospectives. But this should be a temporary training wheels phase. Pretty quickly, they can hand over the facilitation to team members as a deliberate strategy to spur learning . A great Scrum Master will even teach the team facilitation skills and then fade into the backgroundscrum.org. They might run a workshop on collaborative decision-making or share some Liberating Structures, then encourage the team to use those without the Scrum Master leading every time.
Intervene only when necessary. If the team is running an event, the Scrum Master’s stance can be “active listener” instead of “leader.” Don’t jump in at every silence or minor tangent. Give the team a chance to self-correct – that’s how they learn. Step in only if the event is really going off the rails or if someone asks for help. For instance, if a discussion in Sprint Planning becomes completely blocked, the team might invite the Scrum Master to facilitate a quick exercise to resolve it. That’s “as needed” facilitation, not default facilitation. The difference is the team drives by default, and the Scrum Master offers a safety net.
When teams start owning their meetings, magic happens. 🌟 The Developers feel more accountable and engaged, because they’re not just attending a meeting – it’s their meeting. Ideas and solutions come more freely when team members don’t feel like they must defer to the Scrum Master. Meanwhile, the Scrum Master can focus on higher-value activities. Instead of obsessing over the next meeting agenda, they can spend time removing impediments, working with stakeholders, or coaching the Product Owner. (One Scrum.org trainer quips that a Scrum Master can use the time not spent preparing to facilitate events like the Daily Scrum – where their participation isn’t needed – to act as a true change agent and tackle organizational obstacles scrum.org.) In other words, everyone benefits: the team grows more self-sufficient and effective, and the Scrum Master amplifies their impact beyond just running meetings.
Conclusion
In a nutshell, the idea that “Scrum Masters must facilitate all events” is a well-intentioned myth. It became popular because it’s visible and comforting to have one person steering every meeting, especially early on. But the 2020 Scrum Guide and experienced agilists agree that this isn’t a requirement – and clinging to that mindset can hold your team back. A Scrum Master is far more valuable as a coach and catalyst than as a meeting MC. The true measure of a Scrum Master’s success is a team that can run with Scrum on their own, with the Scrum Master guiding from the side when needed.
So, if you’re a manager or Scrum Master, here’s a thought to take away: next time an important Scrum event comes up, challenge yourself not to automatically assign the Scrum Master as the facilitator. Instead, empower your team to take the wheel. You might be surprised at the confidence and creativity that emerge. The Scrum Master is still there, but more as a guardian of the process and a mentor – exactly where they provide the most value. Remember, the goal of Scrum (and the Scrum Master) is to build a self-managing team that can adapt, improve, and deliver value autonomously. You’re not losing control by letting the team facilitate their own Scrum events; you’re helping them gain control of their work. And that ultimately is a win for everyone involved. 🎉
Please share your thoughts in the comments below. Even better, share this post with your network.
References
Schwaber, K. & Sutherland, J. (2020). The 2020 Scrum Guide. scrumguides.org
Scrum.org. Common Myths about Scrum Masters (Scrum.org resource). https://www.scrum.org/resources/common-myths-about-scrum-masters
Overeem, B. (2015). The Scrum Master as a Facilitator. https://www.scrum.org/resources/blog/scrum-master-facilitator
· Ledru, O. (2023). What if the Scrum Master Wasn't the Event Facilitator?. https://www.scrum.org/resources/blog/what-if-scrum-master-wasnt-event-facilitator.