Mike Lyons explains the Scrum Master as a servant leader who shields teams from distractions, removes impediments, and coaches them toward self-organization. The role is full-time and distinct from project management: Scrum Masters teach agile practices, create visible status boards, and push organizations toward evidence-based decision-making.
You know, in addition to being a product owner, I've also served it as a Scrum Master. I was a Scrum Master at a large global nonprofit. So this Scrum Master role, one of the three roles on a team, the Scrum Master is really a servant leader who coaches the team and fosters self organization at the team level. They're considered an expert in all things agile, but especially Scrum, the Scrum framework and all of its intricacies. The Scrum Master is the team level coach. They help everyone understand Scrum theory and agile practices. Their goal is to help teams become highly effective and high performing. And they do this by enabling the Scrum teams to improve their practices within the Scrum framework, of course, but also coaching the team members in self management and cross functionality. So let's get into a little more detail here. Tactically, the Scrum Master shields the team from distractions and other interruptions. They remove impediments. They also create information radiators. Now these are just really, you know, highly visible status update boards. You know, Scrum Masters also help the team focus on creating that thing of value increment that meet the definition of done. And then of course they support the product owner as well by helping the product owner create and maintain the product backlog. They also can facilitate stakeholder collaboration as needed. Scrum Masters, they're masterful facilitators and they also serve the larger organization by regularly training and promoting agility across the enterprise. They help employees and stakeholders understand empirical approach to work. They base decisions on evidence and data. They consistently remove barriers between stakeholders and teams. Listen, the Scrum Master, it's a full time role. It's not something that can just be done in the spare time of a lead developer. That's a common anti pattern that we see. Get this role right, it's critical. And finally, just remember, Scrum Masters are not project managers. No, there's not really a fit for the sort of traditional project manager assigning work and checking status and updating kind of legacy. Red, yellow, green, dashboardy of reports. There's not really a space for that on Scrum teams. Autonomous empowered teams, they don't need to be told what to do. Give them a vision, set them loose, let them go, fulfill it. Scrum Masters really understand this.
