The Scrum Master: A Coach, Not a Manager
A Scrum Master is a servant-leader who coaches a team on Scrum practices, not a project manager who assigns tasks. They facilitate events and remove impediments. The footgun is treating them as a team admin, which undermines the team's self-organization.
THE MENTAL MODEL: Think of a Scrum Master not as a project manager, but as a coach for a professional sports team. The coach doesn't play the game, but they ensure the team understands the rules, uses the best strategies, and has everything it needs to win. The Scrum Master's authority comes from their expertise in Scrum, not from a hierarchical position.
HOW IT WORKS: The Scrum Master's role is defined by service to three groups. First, they serve the Developers by coaching them in self-management, helping them focus on creating valuable increments, and removing impediments that block their progress. Second, they serve the Product Owner by helping with backlog management techniques and ensuring the Product Goal is clear to all. Third, they serve the organization by leading Scrum adoption, planning implementations, and helping stakeholders understand the empirical nature of Scrum.
WHEN TO USE IT: A dedicated Scrum Master is a core component of the Scrum framework. The role is essential when a team or organization is adopting Scrum to manage complex work. They are most effective in environments where leadership is committed to agile principles and empowers the team to self-organize and improve.
WHEN NOT TO USE IT: The role is ineffective if the team is not actually practicing Scrum. If you are using a different framework like Kanban or a traditional waterfall model, the responsibilities don't align. The role also fails if the organization treats the Scrum Master as a project manager, scribe, or administrative assistant, or if they are not empowered to help remove organizational impediments outside the team's direct control.
ONE CANONICAL EXAMPLE: A team consistently misses its sprint goals because another department is slow to provide required API access. A project manager might buffer the schedule. A Scrum Master, however, identifies this as an organizational impediment. They facilitate a meeting between the teams, help them establish a Service Level Agreement (SLA) for API requests, and make the dependency cost visible to leadership. They coach the team to solve the problem, rather than solving it for them.
Read the original → en.wikipedia.org
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.