← Agile and Scrum: Flexible Project Management
Lesson
Lesson 3.2 — Scrum Master: servant leader, not a boss
Explain the Scrum Master's accountability and why a Scrum Master is a servant/true leader, not the team's manager or task dispatcher.
The Scrum Master: True Leader, Not Manager
What the Scrum Master Actually Does
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, and for the Scrum Team's effectiveness. The Scrum Guide 2020 describes Scrum Masters as 'true leaders who serve the Scrum Team and the larger organization.' This is what servant leadership means in practice: the Scrum Master serves the team by removing obstacles (impediments), coaching team members in self-management and cross-functionality, and fostering an environment where the team can do its best work.
The Scrum Master is NOT a boss, project manager, or task dispatcher. The Scrum Master does not tell Developers what to do, does not assign tasks, and does not manage the team's performance in a traditional sense. This is one of the most common misconceptions about the role.
Another key anti-myth: the Daily Scrum is a 15-minute event for the Developers — it is NOT a status report to the Scrum Master. The Scrum Master does not run the Daily Scrum as a check-in to themselves; the Developers own and run it. The Scrum Master's influence comes from coaching, facilitation, and removing what blocks the team — not from authority or control.
Lesson notes
What the Scrum Master Actually Does
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, and for the Scrum Team's effectiveness. The Scrum Guide 2020 describes Scrum Masters as 'true leaders who serve the Scrum Team and the larger organization.' This is what servant leadership means in practice: the Scrum Master serves the team by removing obstacles (impediments), coaching team members in self-management and cross-functionality, and fostering an environment where the team can do its best work.
The Scrum Master is NOT a boss, project manager, or task dispatcher. The Scrum Master does not tell Developers what to do, does not assign tasks, and does not manage the team's performance in a traditional sense. This is one of the most common misconceptions about the role.
Another key anti-myth: the Daily Scrum is a 15-minute event for the Developers — it is NOT a status report to the Scrum Master. The Scrum Master does not run the Daily Scrum as a check-in to themselves; the Developers own and run it. The Scrum Master's influence comes from coaching, facilitation, and removing what blocks the team — not from authority or control.