What Does a Scrum Master Do? The Role, the Daily Work, and the Mistakes to Avoid

By Chris Daily · Updated October 2026

Chris Daily is a former CTO at Angie's List and Experian with 30+ years in technology leadership, a longtime Agile and Scrum trainer, and a Certified AI Master Trainer.

The word "master" trips people up every time I explain this role. It sounds like authority — like someone in charge. It's almost the opposite.

Quick answer: A Scrum Master helps a Scrum team work well. They coach the team and the organization on Scrum, run or facilitate the team's events, remove obstacles that slow the team down, and protect the team from interruptions. They don't assign work or manage people. Their job is the process, not the people.

If you're new to Scrum and trying to figure out what this role actually does, here's how I explain it when I'm training someone into it for the first time.

Who Is the Scrum Master?

The Scrum Master is one of the three accountabilities on a Scrum team defined in the Scrum Guide, alongside the Product Owner and the Development Team (called Developers in the 2020 Scrum Guide). The Product Owner decides what gets built and in what order. The Development Team decides how to build it and does the work. The Scrum Master looks after the way the team works — making sure Scrum is understood, practiced, and actually helping.

In practice, the Scrum Master is often a former developer, tester, business analyst, or project manager who has been trained in Scrum. The background matters less than the mindset.

Not a Manager, Not an Authority Figure

The Scrum Master doesn't have positional authority over the team. What they have is influence — over the process, over the team's habits, over how stakeholders engage with the work.

I teach servant leadership as the operating model for this role: the Scrum Master serves the team first, which means coaching, teaching, and removing obstacles rather than directing tasks or evaluating performance. That's a different muscle than most people bring from a traditional management background, and it's the single most common thing I have to un-teach when someone moves into this role from a project-manager job.

Why the Role Exists at All

I get asked this constantly by skeptical leadership teams: if the Scrum Master doesn't have real authority, what are we paying for?

Here's my answer. A self-organizing team still needs someone whose job is watching for what's slowing them down — bad handoffs, unclear requirements, a stakeholder who keeps changing the ask mid-sprint — and clearing it before it becomes a crisis. A good Scrum Master does this proactively, not reactively. They're not showing up after the roadblock stops the team; they're clearing the path in advance because they've learned to see it coming.

That's not dead weight. That's the difference between a team that spends its energy on the work and a team that spends half its energy fighting its own process.

What Does a Scrum Master Do Every Day?

No two days are identical, but most days in a two-week sprint look something like this:

• Morning: the Daily Scrum. The Scrum Master makes sure the 15-minute daily meeting happens, stays short, and stays focused on the sprint goal. They listen for blockers. They don't run it as a status report to themselves.
• Late morning: clearing blockers. Chasing the approval that's been stuck for three days, getting a tester access to the environment, talking a stakeholder out of a mid-sprint scope change.
• Midday: working with the Product Owner. Helping keep the backlog in shape — stories small enough to finish, clear enough to estimate, ordered by value.
• Afternoon: coaching. A one-on-one with a developer who's frustrated, a quick session on writing better acceptance criteria, or a conversation with a manager outside the team about why pulling people off the sprint hurts delivery.
• End of day: watching the flow. A look at the board or burndown. Is work piling up in one column? Is something stuck in review? That's tomorrow's first conversation.

And on the days the bigger events land:

Event	What the Scrum Master does
Sprint Planning	Facilitates so the team commits to a realistic sprint goal; keeps the conversation from going in circles
Daily Scrum	Makes sure it happens and stays under 15 minutes; notes blockers to clear
Sprint Review	Helps the team show real, working results to real stakeholders and capture their feedback
Sprint Retrospective	Facilitates an honest look at how the team worked and makes sure at least one improvement is carried into the next sprint
Backlog Refinement	Supports the Product Owner and team in breaking down and clarifying upcoming work

The Different Flavors of the Role

Not every Scrum Master looks the same, and I think that surprises people who assume it's a single fixed job description.

Some are part-time — a working member of the team who also carries the Scrum Master responsibilities, which is a real balancing act between participating in the work and staying objective about the process.

Some are full-time and dedicated to a single team. Some are full-time across multiple teams, rotating their attention. Some organizations use a rotating model, where team members take turns in the role each sprint — which has the upside of building empathy for the role across the whole team, and the downside of inconsistent coaching quality sprint to sprint.

And then there's the Agile Coach, a step up from Scrum Master, working across multiple teams with no dedicated assignment beyond coaching and mentoring at the organizational level.

None of these is objectively "more correct." Which one fits depends on your team's maturity and your organization's structure.

What the Job Actually Involves

Removing impediments is the most visible part of the job — anything slowing the team down, from a broken build pipeline to an approval process nobody remembers the reason for. The best Scrum Masters I've coached don't wait for these to surface; they're actively looking for what's about to become a problem.

Building the team's environment is the least tangible part, and the part people underrate. It means encouraging learning, modeling agile thinking rather than just preaching it, giving feedback in the moment instead of saving it for a retro, and sharing tools and techniques as the team needs them — not according to a fixed curriculum.

Supporting team dynamics means being embedded in the team, not observing it from outside. Coaching individuals, mediating actual conflict when it comes up — this only works if the team trusts the Scrum Master as one of their own, not as management in a different outfit.

Managing the relationship with the Product Owner deserves its own line item, because when it breaks down, the whole team feels it. The Scrum Master advocates for the team; the Product Owner is the voice of the customer. When those two aren't in sync, the tension shows up in every planning meeting.

A Scrum Master's Weekly Checklist

If you're new to the role, run through this every week:

• Did every Scrum event happen, start on time, and end on time?
• Is there a clear sprint goal, and can every team member say what it is?
• What's the oldest open blocker, and what am I doing about it today?
• Is the top of the backlog ready for the next Sprint Planning?
• Did last retro's improvement actually happen?
• Has anyone outside the team tried to add work mid-sprint? Did I handle it?
• Who on the team have I not talked to one-on-one this week?

Where I've Seen This Role Go Wrong

Two mistakes account for most of the Scrum Masters I've had to coach back on track.

Getting too invested in the outcome. The moment a Scrum Master starts pushing the team toward the solution they personally think is best, they've stopped being a coach and started being a shadow manager — and self-organizing teams can tell the difference immediately, even if nobody says it out loud.

Absorbing the Product Owner's job. A Scrum Master doesn't need deep product or customer knowledge to do their job well, and trying to acquire it usually means they're drifting into territory that isn't theirs. If a Scrum Master finds themselves making product calls, that's the signal to step back, not lean in.

The role works when it's held with a light hand — present, watching, ready to clear a path, but never trying to steer the ship itself. That's harder than it sounds, and it's most of what I actually spend my time coaching people through.

Frequently Asked Questions

What does a Scrum Master do in simple terms?

They help the team use Scrum well: they facilitate the team's meetings, remove obstacles, coach people on how to work together, and shield the team from interruptions. They don't assign tasks or manage performance.

Is a Scrum Master the same as a project manager?

No. A project manager typically plans the work, assigns tasks, and is accountable for delivery. A Scrum Master has no authority to assign work — the team organizes itself — and focuses on helping the team work better.

Who is the Scrum Master on a team?

Whoever holds that accountability, often a trained Scrum Master who is full-time or part-time on one or more teams. Some teams rotate the role between members. The Scrum Master works alongside the Product Owner and the Development Team, but doesn't manage either.

Does a Scrum Master need technical skills?

It helps to understand the team's work, but it isn't required. Facilitation, coaching, and the ability to spot and clear obstacles matter far more.

Can a Scrum Master work with more than one team?

Yes. Many experienced Scrum Masters support two or three teams, though the more teams they cover, the less time each team gets.

---

Lead the work without taking it over

Want to run projects in your own business with the same light touch? Project Management Essentials walks you through running a project from kickoff to close, with an AI tool to help at each stage.

See the course →