Your Scrum Master Is Not Your Project Manager
Scrum has no Project Manager role. The Scrum Master exists because traditional command-and-control management kills self-managing teams. One role is a servant-leader; the other is a command-and-control director.
Scrum Master: Servant-Leader
The SM serves the team. They coach, facilitate, and remove blockers — but they never tell anyone what to do.
| Responsibility | What It Actually Means |
|---|---|
| Coach | Teaches Scrum, self-management, and cross-functionality |
| Facilitator | Runs Sprint events so they’re productive and timeboxed |
| Blocker Remover | Shields the team from interruptions; clears organizational impediments |
| Process Owner | Ensures the Scrum framework is followed correctly |
Authority: Zero formal authority. The SM cannot hire, fire, assign tasks, or override team decisions. Their power is influence through trust.
“The Scrum Master is a true leader who serves the Scrum Team and the larger organization.” — Scrum Guide 2020
Project Manager: Command & Control
The PM owns the outcome. They direct, assign, and report — everything flows through them.
| Responsibility | What It Actually Means |
|---|---|
| Director | Assigns tasks to individuals and tells them how to do it |
| Budget Owner | Manages the budget, timeline, and resource allocation |
| Risk Manager | Identifies and mitigates risks to the project plan |
| Stakeholder Reporter | Communicates status upward and keeps execs informed |
Authority: Full formal authority. The PM can hire, fire, make scope decisions, and overrule team estimates.
Side-by-Side Comparison
| Dimension | Scrum Master | Project Manager |
|---|---|---|
| Leadership style | Servant-leader | Command & control |
| Decision-maker | The Developers (self-managing) | The PM (top-down) |
| Task assignment | None — team pulls work | Assigns tasks to individuals |
| Budget | Not involved | Owns it |
| Timeline | Scrum events are fixed; delivery is empirical | Gantt charts, deadlines, milestones |
| Authority | Influence only | Formal authority |
| Team asks | “How can I help?” | “Report your status” |
| Primary tool | Coaching questions | Status reports, risk registers |
The Hard Truth
A Scrum Master can’t fix a toxic PM-driven culture by holding retrospectives. And a PM can’t drive agile transformation by emailing Gantt charts. These are opposite operating systems.
Your Scrum Master is not your Project Manager. If you’re being assigned work and asking permission, you have a PM wearing an SM hat — and that’s a problem.
Scrum Master serves the team. Project Manager serves the plan. Know which one you need.