Product Owner and Scrum Master: two accountabilities, one decision

The Product Owner decides. The Scrum Master decides nothing. Both are accountable for something, neither commands anyone. But one of them rules on things, and the organisation must respect that ruling. The other has no decision to make, on any subject. The title containing the word Master is the one with no authority. Of our 2,504 practice questions, 133 involve one of the two accountabilities, spread across eight certifications. Only three compare them directly. The rest put you in a situation where somebody acts in another person's place. That is where the point is won or lost. ## Two accountabilities, no hierarchy The Scrum Team holds three accountabilities: one Product Owner, one Scrum Master, and Developers. The 2020 Scrum Guide states, in its Scrum Team section, that there are no sub-teams and no hierarchies. That sentence settles more questions than it looks. The Scrum Master is nobody's boss. Neither is the Product Owner. Neither of them manages the Developers. The word to hold on to is accountable, which the Guide uses for each of them. Being accountable for something is not commanding it. The Product Owner is accountable for product value without writing a line of code. The Scrum Master is accountable for the team's effectiveness without being able to order anyone about. This absence of a boss is not a Scrum invention. The Agile Manifesto stated back in 2001 that the best architectures emerge from self-organising teams, and that motivated individuals should be trusted. The Scrum Guide does not cite that text, but the kinship is plain. That is where the confusion comes from, and also what resolves it. ## What the Product Owner decides They are accountable for maximising the value of the product resulting from the Scrum Team's work. That runs through effective Product Backlog management, which covers four things. - Developing and communicating the Product Goal. - Creating and clearly communicating the items. - Ordering them. - Making the backlog transparent, visible and understood. Three details matter in the exam, and they all sit in the Product Owner section of the Guide. It is one person, not a committee. Anyone who wants to change the Product Backlog has no route other than persuading that person. The organisation must respect their decisions. This is not a courtesy recommendation. The Guide states it as a condition for the Product Owner to succeed. They can delegate the work, never the accountability. An analyst may write and order items day to day, and that stays compliant. The Product Owner remains the one accountable for the value produced and the order chosen. And they hold one decision nobody else can take: cancelling the Sprint, when the Sprint Goal becomes obsolete. Only them, and that is the only stated reason. ## What the Scrum Master does not decide They are accountable for two things: establishing Scrum as defined in the Guide, and the Scrum Team's effectiveness. The Guide describes them as a true leader who serves the team and the organisation. Serving, not directing. They do not assign work, do not approve what gets produced, do not settle technical choices and do not order the backlog. Hold on to the reflex. It covers a good half of the scenario questions. As soon as an answer has the Scrum Master deciding in someone else's place, it is nearly always wrong. In the Developers' place on the how, in the Product Owner's place on value, in the team's place on how it organises itself. One exception is worth knowing, because it turns up in the hard questions. Nothing stops the Scrum Master working on Sprint Backlog items. They then act as a Developer and take on those accountabilities. The one covering the team's effectiveness does not pause while they do. ## Serving the Product Owner without replacing them This is where the most interesting questions live, and the rule running through them never changes. Items at the top of the backlog arrive too vague to be selected. The Scrum Master helps the team understand why clear items are needed, and suggests refinement techniques. They neither write nor approve them. The Product Owner accepts everything and never orders by value. The Scrum Master helps them find ordering techniques, and makes the effect of the missing trade-off visible. Ordering in their place would strip them of the accountability instead of equipping them for it. The Product Owner has to be convinced to tackle technical debt. The Scrum Master translates the debt into measurable effect: testing time, defects customers live with, time to release. The Product Owner then decides knowing what is at stake. A purely technical argument leaves them with no criterion. The rule under all three fits on one line. The Scrum Master acts on what feeds the decision, never on the decision. It holds for everyone else too. A manager who thinks the Product Backlog is badly ordered does not get to reorder it. They can put the team in touch with users, or identify the stakeholders whose feedback is missing from the Sprint Review. They act on what feeds the decision, and the decision stays where it belongs. ## One example, the same situation from both sides Day three of a two-week Sprint. An incident hits an important customer. A director wants the team on it immediately. What the Product Owner does. They renegotiate the Sprint scope with the Developers to take the incident in, and see what it does to the Sprint Goal. If the goal becomes pointless, they can cancel the Sprint. Nothing forces them to wait for the next Sprint, but the call is theirs. What the Scrum Master does. They make the framework's options visible and get the right people together quickly. Then they make sure the decision is taken by whoever it belongs to. They do not decide. What the Developers do. They say what the incident costs and what it displaces. Nobody decides in their place how to handle it. Now the wrong version, the one the questions offer as a plausible answer. The Scrum Master tells the director the team will take care of it, and passes the instruction on. Three errors in one sentence. They decided in the Product Owner's place, who alone rules on scope. They decided in the Developers' place, who alone organise their work. And they let a request enter the Sprint without going through the trade-off the framework provides. ## What Scrum does not require Half the traps come from rules the framework states nowhere. The Scrum Master does not have to facilitate every event. They grow their facilitation skills, but the team is more effective when it shares them. They do not have to remove every impediment. Most are settled by whoever runs into them. They step in on the ones the team cannot clear alone. Neither of them needs to be technical. The Developers hold the craft. The Product Owner's expertise is about what creates value, the Scrum Master's is about Scrum. The Product Owner does not have to write every item. They are accountable for backlog management, which includes creating items, and they can delegate that work. Neither of them is a project manager. Scrum asks for no scope management, no budget, no deadline, no task supervision. "Product Owner" is not a job title. It is a set of accountabilities, which a Product Manager can carry. ## Recognising the question on exam day The questions will put you in front of a situation where somebody oversteps. Two questions are usually enough to settle it. Who is accountable for the matter at hand? And does the proposed answer respect that accountability, or work around it? - The Scrum Master decides, assigns or approves something: nearly always wrong. - Somebody wants to change the Product Backlog: they must persuade the Product Owner. - A committee wants to decide the product: the Product Owner is one person. - The Product Owner delegates work: compliant, as long as the accountability stays. - A hierarchy overrules the Product Owner: the framework asks for the opposite. - A Sprint has to be cancelled: the Product Owner, and only them. An answer that protects the Developers' self-management, the Product Owner's accountability and the Scrum Master's service role is nearly always the right one. It is the same reflex as on the ten most common traps, and it carries from one topic to the next. ## Frequently asked questions ### Is the Scrum Master the team's boss? No. The Scrum Guide writes that there are no sub-teams and no hierarchies in a Scrum Team. The Scrum Master is described as a leader who serves the team and the organisation. They have authority over nobody, and they assign no work. ### Can the Product Owner delegate their work? The work, yes. Writing items, ordering them day to day, all of that can be handed to someone else. What cannot be delegated is the accountability: the Product Owner remains the one answering for the value produced and the order chosen. ### Can the Product Owner be a committee? No, it is one person. They can represent the needs of many stakeholders in the Product Backlog. But anyone wanting to change it must persuade them, and the organisation must respect their decisions. ### Does the Scrum Master have to be technical? Nothing requires it. Their expertise is Scrum and the techniques that go with it. If they choose to work on Sprint Backlog items, they act as a Developer and take on those accountabilities. ### Who can cancel a Sprint? The Product Owner, and only them, when the Sprint Goal becomes obsolete. That is the only circumstance the framework provides for, and it stays rare. A Sprint that will not deliver all its scope is not a reason to cancel. ## Key points - The Scrum Team carries three accountabilities and knows no sub-team and no hierarchy. - The Product Owner is accountable for value, and their Product Backlog decisions must be respected. - The Scrum Master is accountable for establishing Scrum and for team effectiveness, with authority over nobody. - They act on what feeds a decision, never on the decision itself. - The Product Owner can delegate the work, never the accountability. - An answer where the Scrum Master decides in someone else's place is nearly always wrong. - Cancelling a Sprint falls to the Product Owner alone, and only if the Sprint Goal has become obsolete. These distinctions stick better in a situation than on a page. The free PSM I trial offers original questions with the answer explained straight away, and no account to create.