The Scrum Master

PSM I PSM I · Scrum Team & Accountabilities

By Abu Anns · Last updated 20 November 2026Exam version: PSM I (Scrum Guide 2020)

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. That means helping everyone understand Scrum theory and practice, both within the Scrum Team and in the wider organization. The Scrum Master is also accountable for the Scrum Team's effectiveness, which they support by enabling the team to improve its practices within the Scrum framework. These two accountabilities — establishing Scrum and enabling effectiveness — are the whole job description. Notice what is not in it: the Scrum Master does not manage the team, does not assign work, does not make product decisions, and does not own any backlog. The Guide calls Scrum Masters true leaders who serve the Scrum Team and the larger organization. That phrase, servant leadership, is the key to almost every exam question about this accountability: the Scrum Master leads by serving, coaching, teaching, and removing obstacles — never by commanding.

The Guide describes the Scrum Master's service in three directions: to the Scrum Team, to the Product Owner, and to the organization. Serving the Scrum Team means coaching team members in self-management and cross-functionality; helping the team focus on creating high-value Increments that meet the Definition of Done; causing the removal of impediments to the team's progress; and ensuring that all Scrum events take place and are positive, productive, and kept within the timebox. Note the wording on impediments: the Scrum Master causes their removal, which often means helping the team remove them itself or escalating to someone who can — not personally fixing every problem. And note the wording on events: the Scrum Master ensures events happen and stay within their timeboxes, but does not run them all. The Daily Scrum, for example, belongs to the Developers.

Serving the Product Owner means helping find techniques for effective Product Goal definition and Product Backlog management; helping the Scrum Team understand the need for clear and concise Product Backlog items; helping establish empirical product planning for a complex environment; and facilitating stakeholder collaboration as requested or needed. The Scrum Master is the Product Owner's coach and thinking partner on the product side of Scrum — not a second Product Owner, and not someone who orders the backlog on the Product Owner's behalf. When a Product Owner is new and struggling to write clear items or to say no to stakeholders, the Scrum Master helps them build those skills rather than taking the work over.

Serving the organization means leading, training, and coaching the organization in its Scrum adoption; planning and advising Scrum implementations within the organization; helping employees and stakeholders understand and enact an empirical approach for complex work; and removing barriers between stakeholders and Scrum Teams. This is the part of the role that extends beyond one team. A Scrum Master who only focuses on their own team's ceremonies is doing half the job. The organizational work — teaching managers what self-management means, helping departments stop demanding detailed upfront plans, clearing the path between stakeholders and the team — is where experienced Scrum Masters spend much of their time, and it is tested on the exam through scenarios about organizational impediments.

Authority: the exam's favorite trap

The single most-tested idea about the Scrum Master is what authority they do not have. The Scrum Master has no authority over team members: they cannot hire, fire, appraise, or discipline Developers, and they cannot tell Developers what to work on. They cannot overrule the Product Owner on backlog ordering, and they cannot cancel a Sprint — only the Product Owner can do that. They cannot extend a Sprint, skip events, or change the Definition of Done unilaterally. What they can do is coach, teach, facilitate, and remove impediments — and hold the team and the organization accountable to the Scrum framework itself. Exam questions exploit this relentlessly: any option where the Scrum Master directs, decides, assigns, or approves is almost always wrong, while options where the Scrum Master coaches, facilitates, teaches, or helps the team find its own answer are usually right. The one partial exception is events: the Scrum Master is accountable for ensuring events take place and stay within their timeboxes, so stepping in when a Daily Scrum runs to 45 minutes is legitimate — but even there, the aim is to coach the team to keep its own timebox, not to police it forever.

Worked scenario

A new Scrum Team keeps skipping the Sprint Retrospective because the Developers say they are too busy. The Product Owner is happy because more time goes to building features. What should the Scrum Master do? The Guide's answer: the Scrum Master is accountable for ensuring all Scrum events take place and are positive and productive. Skipping the Retrospective removes the team's main opportunity to inspect and adapt its own way of working — the very mechanism by which it improves. The Scrum Master should coach the team on why the Retrospective matters, facilitate one that is genuinely useful rather than a ritual, and help the team see that the time spent is an investment, not a cost. What the Scrum Master should not do is simply order the team to attend, or cancel the Retrospective themselves, or escalate to a manager to force attendance. Authority is not the tool; teaching and facilitation are.

Coaching, not doing

The hardest part of the Scrum Master role is restraint. When a team struggles, the instinct is to step in and fix the problem — write the Sprint Goal, order the backlog, resolve the conflict, chase the stakeholder. Every time the Scrum Master does the team's work, the team learns a little less and depends a little more. Coaching means asking the question that helps the team find its own answer, facilitating the conversation the team is avoiding, and teaching the idea the team has not yet grasped. It also means knowing when to step back: a mature, self-managing team needs less from its Scrum Master, not more, and a good Scrum Master lets the team own its successes. The Guide's language points in this direction throughout — helping, coaching, facilitating, enabling, causing the removal — never directing, deciding, or controlling. The exam rewards this understanding: when a scenario offers the Scrum Master a choice between doing something for the team and helping the team do it itself, the second option is almost always correct.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.What is the Scrum Master accountable for?

Report an error

Q2.A Developer asks the Scrum Master to decide which Product Backlog item they should work on next. What is the BEST response from the Scrum Master?

Report an error

Q3.Which of the following is a service the Scrum Master provides to the Product Owner?

Report an error

Q4.The Daily Scrum regularly runs for 30 minutes instead of 15. What should the Scrum Master do?

Report an error

Q5.Which statement about the Scrum Master's authority is TRUE?

Report an error

Q6.A team's progress is blocked because another department will not give them access to a test environment. What is the Scrum Master BEST positioned to do?

Report an error

Q7.Which of the following is a service the Scrum Master provides to the organization?

Report an error

Q8.A Scrum Team has stopped holding Sprint Retrospectives, saying they are too busy. What should the Scrum Master do?

Report an error

Q9.Which statement BEST describes how the Scrum Master helps the Scrum Team become more effective?

Report an error