The Scrum Master is the protector of the team's focus and the guardian of the Scrum values.
1Coaching the Team
The SM helps the team grow. They observe dynamics, highlight anti-patterns (like long Daily Scrums), and help the team become more autonomous and self-sufficient every day.
2Coaching the PO
The SM assists the Product Owner with Backlog refinement techniques, helping them find ways to define clear goals and maximize the value delivered by the team.
3Coaching the Org
The SM isn't just for the team. They help the entire company understand Agile, working with leadership to remove organizational barriers to the team's success.
4Step-by-Step Breakdown
The Scrum Master (SM) is not a project manager. They don't track tasks; they track the health of the process and the team.
As a Facilitator, the SM ensures that all Scrum events happen and are productive. They keep the team focused on the goal and within the time-box.
The SM is an 'Impediment Remover'. If a broken laptop, a slow server, or a difficult stakeholder blocks the team, it's the SM's job to fix it.
Servant Leadership: The SM exists to serve the team. They lead through influence, empathy, and coaching, not through command and control.
What is the primary goal of a Scrum Master when they identify an 'impediment'?
- →To report it to the manager so someone gets in trouble
- →To fix it as quickly as possible so the team can continue working
- →To tell the developers to work around it
- →To wait until the next Retrospective to discuss it
Does a Scrum Master have the authority to tell a developer which task to work on next?
- →Yes, they are the team's boss
- →Only if the Product Owner is busy
- →No, the Developers are self-organizing and manage their own work
- →Yes, but only during the Daily Scrum
Level Up 🚀
Advanced cheat sheets, SEO tricks, and interview prep for this topic.
Browser Support
Fully supported.
Fully supported.
Fully supported.
Fully supported.
Accessibility (A11y)
1Facilitating Meetings Inclusively
A Scrum Master facilitating a Daily Scrum or Retrospective for a mixed in-person/remote team needs to actively call on remote voices and repeat things said only in the room, or those teammates are functionally excluded from the event.
// Facilitation checklist
// - Remote attendees speak first, not last
// - Repeat any comment made off-mic in the room
// - Use a shared doc so contributions aren't voice-onlySEO Implications
- 1
Role Confusion Queries
A large volume of searches ask 'is the Scrum Master a project manager' or 'what does a Scrum Master actually do'. Directly contrasting the SM's servant-leadership accountabilities against PM-style task assignment answers this confusion explicitly and matches that search intent.
Best Practices
Remove Impediments, Don't Just Log Them
Writing 'blocked on IT ticket' in a tracker isn't removing an impediment — it's documenting one. A good Scrum Master escalates, follows up, and drives it to resolution.
Coach Instead of Rescue
If the Scrum Master answers every process question by deciding for the team, the team never learns to self-manage. Ask questions that help the team reach their own conclusion instead of handing them the answer.
Frequent Bugs
The Scrum Master starts assigning tasks and making technical decisions when the team is under deadline pressure, quietly turning into a project manager.
Redirect decision-making back to the Developers even under pressure — coach them toward a decision instead of making it for them, and protect their self-management rather than overriding it.
Real-World Examples
An SM Who Became a Human Ticket Queue
A new Scrum Master was tracking every developer's individual tasks in a spreadsheet and assigning daily work, effectively acting as a project manager instead of a facilitator.
// Anti-pattern
// SM assigns: 'Alex, do ticket 402 today. Sam, do 403.'
// Corrected
// SM asks in Daily Scrum: 'What's blocking anyone from picking up the next item?'