Definition
Scrum Master
A scrum master is the person accountable for a team's effective use of Scrum. They are a facilitator and coach, not a manager: they run the sprint events, remove impediments blocking the team, shield it from outside disruption, and help the organization adopt agile practices. They have no authority over priorities or who does what work.
Key takeaways
- A scrum master is the person accountable for a team's effective use of Scrum. They are a facilitator and coach, not a manager: they run the sprint events, remove impediments blocking the team, shield it from outside disruption, and help the organization adopt agile practices. They have no authority over priorities or who does what work.
- The scrum master is one of Scrum's three roles, and the most often misunderstood.
- In Planoda, the facilitation work a scrum master does — surfacing blockers, tracking impediments, running retrospectives — lives alongside the team's issues, so process health is visible next to the work itself.
The scrum master is one of Scrum's three roles, and the most often misunderstood. The title sounds managerial, but the role is the opposite: a servant leader who serves the team rather than directing it. Their job is to make the team effective at Scrum, not to assign tasks, set deadlines, or own outcomes — those belong to the product owner and the developers.
Day to day, the work is facilitation and unblocking. They run sprint planning, the daily standup, the review, and the retrospective so the team doesn't have to police its own process. They chase down impediments — a stalled dependency, a missing approval, an unclear requirement — and clear them. They protect the team from mid-sprint scope changes and external interruptions.
Beyond one team, an experienced scrum master coaches the wider organization: helping stakeholders interact with the team productively, improving how the backlog is refined, and championing empirical practice over command-and-control habits. The role is about influence, not authority.
In Planoda, the facilitation work a scrum master does — surfacing blockers, tracking impediments, running retrospectives — lives alongside the team's issues, so process health is visible next to the work itself.
Related terms
- ScrumScrum is an agile framework for delivering work in fixed iterations called sprints. A small cross-functional team plans a sprint, works without mid-sprint scope changes, then inspects and adapts through review and retrospective. Defined roles, events, and artifacts give the framework structure while leaving the actual engineering practices up to the team.
- Product OwnerA product owner is the person accountable for maximizing the value a Scrum team delivers. They own and order the product backlog, decide what gets built and in what sequence, and translate stakeholder needs into clear, prioritized work. They are a single, empowered decision-maker — not a committee — so the team always has one authoritative source of priority.
- AgileAgile is a family of software-development approaches built on the 2001 Agile Manifesto, which values working software, customer collaboration, and responding to change over rigid plans and documentation. Rather than one process, it is a set of principles — short iterations, continuous feedback, and incremental delivery — that frameworks like Scrum and Kanban put into practice.
- BlockerA blocker is anything that prevents an issue from progressing until it is resolved — a dependency on unfinished work, a pending decision, a missing access, or an external delay. Marking work as blocked makes hidden stalls visible so the team can clear them deliberately, rather than letting issues quietly age in progress.
- RetrospectiveA retrospective is a recurring meeting, usually at the end of a cycle, where a team reflects on how it worked — what went well, what didn't, and what to change. Its output is a small set of concrete improvements to try next. The retrospective is the engine of continuous improvement, turning experience into deliberate process change.