5 Things a Scrum Master Does NOT Do

The role of a Scrum Master is often misunderstood. While they are a crucial part of any Scrum team, there’s a lot of confusion about what they should—and shouldn’t—do. Let’s clear up the misconceptions by exploring five things a Scrum Master does NOT do.

---

1. Product Management

A Scrum Master is not a Product Manager.
These are entirely different roles with distinct responsibilities. While the Product Owner (the role Product Managers take on in a Scrum Team) focuses on defining what the team works on and ensuring it delivers value to customers, the Scrum Master focuses on enabling the team to succeed within the Scrum framework.

It’s also important to understand that Scrum doesn’t dictate how teams work or implement solutions. The developers decide how to work and implement things, based on their expertise and discussions with the Product Owner. The Scrum Master’s role is to facilitate this process by creating an environment where collaboration can thrive, not by dictating the “how.”

---

2. Managing the Team

A Scrum Master is not the manager or boss of the team.

In Scrum, the team is self-managing. That means the developers decide how to organize their work and achieve their goals. The Scrum Master’s role is to serve the team as a leader, not to manage or control them.

Scrum Masters play a key role in addressing obstacles, but it’s crucial to note that they are not the only ones responsible for removing impediments. Depending on the issue, the Product Owner, the Developers, or other stakeholders may be better positioned to resolve it. The Scrum Master’s primary responsibility is to identify and highlight impediments and help ensure they are addressed appropriately, enabling the team to focus on their work.

---

3. Quitting When Everything’s Going Well

A common misconception is that Scrum Masters are only needed when things are going badly. This couldn’t be further from the truth.

Even when a team seems to be firing on all cylinders, a Scrum Master plays a critical role:

• Facilitating retrospectives to ensure continuous improvement.
• Maintaining the team’s Scrum discipline to prevent small cracks from becoming big problems.
• Supporting the team in identifying opportunities for growth, even when things seem perfect.

In fact, “having no problems” can be a red flag. The best teams constantly see opportunities for improvement and embrace a mindset of continuous evolution. The idea that a truly agile team would have no problems is, frankly, hilarious.

Pulling the Scrum Master out of the equation when things look smooth is a surefire way to invite problems. Their consistent presence ensures sustained success.

---

4. Planning the Sprint

Scrum Masters do not plan the sprint. That responsibility lies with the Developers and the Product Owner.

Here’s how sprint planning works:

• The Product Owner provides priorities and context.
• The Developers decide how much work they can take on and how they’ll accomplish it.

The Scrum Master’s job? Facilitating the process. They moderate the discussion, keep the session focused, and ensure all voices are heard, but they do not plan the sprint themselves.

---

5. Excluding the Product Owner from Retrospectives

There’s a strange myth floating around that the Product Owner (PO) should be excluded from sprint retrospectives. Let’s set the record straight: The PO is part of the team and should absolutely participate in retrospectives.

This myth often stems from former project managers or team bosses transitioning into the Product Owner role. If the team still sees the PO as “above” them rather than as a team member, this misunderstanding can arise.

In Scrum, the Product Owner is an equal part of the team, collaborating alongside developers and the Scrum Master. Excluding the PO breaks the spirit of collaboration and creates unnecessary silos.

---

What a Scrum Master Actually Does

The Scrum Master is the team’s secret weapon—not a manager, not a boss, but a coach, guide, and catalyst for growth. Here’s what they really do:

1. Help the Team Help Themselves ​
   Teach the team to manage themselves, collaborate better, and work as a true cross-functional unit. It’s about enabling—not controlling.
2. Keep Scrum Events on Point ​
   Make sure Scrum events aren’t just happening but are actually productive, time-boxed, and valuable. No wasted hours here!
3. Focus on Real Value ​
   Keep the team’s eyes on delivering meaningful results—Increments that meet the Definition of Done and actually matter.
4. Clear the Path, Together ​
   Spot the blockers holding the team back and facilitate their removal. But it’s not just the Scrum Master’s job—everyone pitches in to solve problems.
5. Support the Product Owner ​
   Help the Product Owner sharpen their backlog, define clear goals, and collaborate effectively with stakeholders. Great products need great alignment!
6. Champion Experimentation ​
   Encourage the team (and the organization!) to embrace learning through experiments, feedback, and data. No guesswork—just growth.
7. Spread Agile Thinking​
   Work with the organization to embed Scrum and agile principles, fostering an environment where teams and stakeholders can thrive.

The Scrum Master’s role isn’t about telling people what to do—it’s about creating the conditions where the team can shine. It’s leadership, service, and innovation rolled into one. 🚀

---

Conclusion

Scrum Masters play a unique and essential role in helping teams succeed, but they aren’t the product manager, the team’s boss, or a substitute for team autonomy. By understanding what a Scrum Master doesn’t do, we can better appreciate what they actually bring to the table: guidance, support, and the tools teams need to thrive.

What misconceptions about Scrum Masters have you encountered? Let me know by replying to this email!