What Does a Scrum Master Actually Do?
A Scrum Master helps a team use Scrum well: they facilitate the Scrum events, remove blockers, and coach the team and the wider organization. It's a servant-leadership and coaching role — they own the process, not the tasks and not the product.
"Scrum Master" is one of the most misunderstood titles in tech. It sounds like a boss or a project manager, but it's neither. The role exists to help a team get good at Scrum — and, done well, it's a coaching and facilitation job, not a command-and-control one. Here's what a Scrum Master actually does, in plain English.
The three directions they serve
The Scrum Guide describes the role as serving in three directions. This framing is the clearest way to understand the job.
- Serving the team: coaching them in self-management, helping them focus on high-value work, and removing impediments to their progress.
- Serving the Product Owner: helping with effective backlog management, clear goal-setting, and keeping stakeholder collaboration productive.
- Serving the organization: coaching the wider business in adopting Scrum, and helping remove barriers between stakeholders and teams.
A Scrum Master's day to day
In practice, the work is a mix of facilitation, unblocking, and quiet coaching. A typical week includes:
- Facilitating the Scrum events so they're useful and stay in their time-box
- Chasing down blockers — a delayed approval, a missing access, a dependency on another team
- Coaching the team on how to work together and improve, without telling them what to do
- Shielding the team from mid-sprint interruptions and scope changes
- Helping the Product Owner keep the backlog clear and prioritized
- Spotting patterns in what's slowing delivery and helping the team fix the root cause
| Event | What the Scrum Master helps with |
|---|---|
| Sprint Planning | A focused session that sets a clear Sprint Goal and plan |
| Daily Scrum | A short daily sync the team runs; the SM keeps it effective, not a status report |
| Sprint Review | Inspecting the increment with stakeholders and gathering feedback |
| Sprint Retrospective | Helping the team reflect honestly and commit to real improvements |
What a Scrum Master is NOT
Much of the confusion comes from what people assume the role includes. Being clear about what it isn't is just as important:
- Not the team's boss — a Scrum Master has no authority to assign tasks or manage people
- Not a project manager — they don't own scope, budget, or the schedule (see below)
- Not a secretary — they facilitate meetings, they don't just book rooms and take notes
- Not the decision-maker on the product — that's the Product Owner's accountability
Scrum Master vs project manager
This is the question that trips up most newcomers. A project manager is accountable for delivering a project — scope, timeline, budget. A Scrum Master is accountable for how well the team uses Scrum, and has no authority over people or budget. They can overlap in real jobs, but the mindset is different: directive delivery versus servant-leadership. If you're weighing the two paths, our guide to Agile vs Waterfall explains the two worlds these roles live in.
If this sounds like a role you'd want, we cover the practical steps in how to become a Scrum Master, which certification to start with in PSM vs CSM, and what the role pays in our Scrum Master salary guide.
Frequently asked questions
What does a Scrum Master do all day?
They facilitate the Scrum events, remove blockers slowing the team down, coach the team and Product Owner, and protect the team from mid-sprint interruptions. Much of the job is quiet facilitation and unblocking rather than directing work.
Is a Scrum Master a manager?
No. A Scrum Master has no authority to assign tasks, manage people, or set budgets. They're a servant-leader and coach who helps the team become self-managing — which is the opposite of a traditional boss role.
What's the difference between a Scrum Master and a project manager?
A project manager owns delivery — scope, timeline, and budget — with authority to match. A Scrum Master owns the team's effective use of Scrum, with no such authority. The roles can overlap in practice but differ in mindset. See Agile vs Waterfall for the bigger picture.