September 8, 2026 · 8 min read
TL;DR: The scrum master appears in thirty-four options in this bank and is keyed six times, so this term is a distractor far more often than an answer. Every wrong placement shares one shape: it gives the scrum master authority over something the role does not hold. Estimates belong to the team that will do the work. Backlog order and product decisions belong to the product owner. The team's own work belongs to the team. The scrum master owns the process, coaches the framework, clears impediments and protects a sustainable pace, and questions where that is the gap are the ones where the role is keyed.
The pattern is easy to state and hard to apply under time pressure, because a scrum master stepping in to settle a disagreement always reads as helpful. The bank builds most of its distractors out of that instinct.
Process, coaching, impediments, and pace.
The bank keys this most directly in a record about a newly formed agile team that is exhausted after twelve-hour days meeting its sprint commitments. Whose duty has not been discharged? The options name the team members, the product owner, the scrum master and the project manager. Keyed is the scrum master, and the explanation states the ownership plainly: the scrum master owns the process and the team's ability to work at a pace it can sustain, so a new team over-committing and burning itself out points squarely at that role.
It then rules out the others in one line each. The members did the work that was asked of them. The product owner is accountable for the product rather than the team's working pattern. An agile team may have no project manager at all.
A second record confirms the coaching half. A new team member asks the product owner to explain the agile roles. Two answers are keyed: the product owner explains their own accountability, ordering the backlog and clarifying stories, and refers her to the scrum master, who owns the process and coaches the team on the framework. Each role explains the part it holds.
Three places, and the bank tests each of them repeatedly.
Estimates first. A development team estimates a task at 8 points, the product owner at 3, and the scrum master splits the difference at 5. What did the scrum master do wrong? Keyed is that the figure should be the team's 8. The explanation refuses the arithmetic framing entirely: the defect is not arithmetic, it is authority. Estimates belong to the people who will do the work, because the estimate is a statement about their capacity and their understanding of the item, and a number produced by anyone else is a target dressed up as an estimate.
The same rule appears from the other direction in a record where the scrum master notices the product owner sizing the user stories. Keyed is explaining that agile teams self-organise, so the team should be estimating. Two distractors are nearly right and fail on detail: proposing firm dates instead of relative sizing attacks the wrong thing, since relative sizing is standard practice, and having the product owner seek buy-in afterwards still leaves the product owner making the estimate. A third distractor says estimating is the scrum master's job. The bank rules it out in half a sentence.
Product decisions second. Most of a cross-functional team wants a logo enlarged twenty per cent, the scrum master wants ten, and the product owner is happy as it is. Keyed is leaving it unchanged. The explanation is one of the clearest statements of role design in the bank: this is a decision about what the product should be, and on an agile team that authority is deliberately concentrated in one role. Distributing it to a majority vote, to the facilitator, or to whichever specialist feels most strongly is exactly what the role exists to prevent, because a product with several owners has none.
The team's own work third. When a scrum master tags backlog items short, mid and long term and the product owner emails asking to remove them with no explanation, keyed is simply remove the tags. The product owner owns and orders the backlog. Asking for the reasoning can happen afterward, but it should not block carrying out the owner's decision about their own backlog.
As an option that puts the scrum master in charge of something.
| Scenario in the bank | Scrum master option offered | What is actually keyed |
|---|---|---|
| New team burning out on twelve-hour days | Scrum master's duty not discharged | Scrum master's duty not discharged |
| Team 8 points, product owner 3, split to 5 | Any figure the scrum master picks | The team's 8; estimates belong to the doers |
| Confusion over who sizes story cards | The scrum master sizes on the team's behalf | The team sizes, mainly developers and testers |
| Product owner sizing stories at a workshop | Product owner estimates, then gets buy-in | The team should be estimating |
| Team, scrum master, product owner disagree on a logo | Enlarge ten per cent per the scrum master | Leave it unchanged per the product owner |
| Product owner asks for backlog tags removed | Wait until sprint planning to change them | Remove the tags |
| No single point of contact for product questions | Scrum master is the missing role | Product owner is the missing role |
| Team blames each other in a retrospective | Scrum master should have removed obstacles | The team should have collaborated to solve it |
| XP team let no defects reach users | Doing exactly what the scrum master says | Refactoring and daily integrated deployment |
The missing-role record is a neat inversion. An agile coach observes a cross-functional team with no single point of contact for product questions and asks which role is missing. The scrum master is offered. Keyed is the product owner, and the explanation defines product questions as decisions: what a story should do, which behaviour is right when stakeholders disagree, whether something is worth building at all. That is authority, which is why the role is deliberately one person.
Common trap: answering with the scrum master whenever a team is struggling, because the role sounds like the adult in the room. The bank's fintech retrospective record is built precisely on that reflex. A team has not completed its planned stories and members begin blaming one another. Two distractors put it on the scrum master, one for not removing obstacles and one for not staffing senior developers. Keyed is that the team should have recognised the problem and collaborated to solve it, because on an agile project the team, not the scrum master or product owner, is accountable for its own work. When you see a scrum master option that reads as taking charge, check whether taking charge is what the role is for. The explanations in this bank name that boundary rather than only marking the choice wrong.
Not necessarily, and the bank keys the pragmatic answer.
A project manager is staffing a new Scrum project with minimal resources and no hiring budget. A preassigned person who has worked on Scrum projects but never held the role asks to serve as scrum master. Keyed is pairing her with an experienced agile coach.
The explanation weighs the alternatives rather than asserting a rule. Finding someone experienced is not feasible with no budget and limited resources. Training is a reasonable option, but since she already has Scrum project experience she is likely familiar with the role, so ongoing support from a coach beats a course. Refusing her and going to the functional manager both ignore the constraints the stem has already set.
This is the exception that proves the pattern. The scrum master is keyed here because the question is about the process and how the team is supported, which is exactly the territory the role owns.
What does the scrum master actually own on the PMP exam? The process and the team's ability to work sustainably. The bank keys the scrum master's duty as the one not discharged when a new team burns itself out on twelve-hour days, and separately describes the scrum master as the person who owns the process and coaches the team on the framework. Nothing about the product, the backlog order, or the estimates belongs to the role.
Can the scrum master decide a story's estimate? No, and the bank tests this twice. When a scrum master splits the difference between the team's 8 points and the product owner's 3 and assigns 5, the keyed answer is that the figure should be the team's 8, because estimates belong to the people who will do the work. A separate record names the scrum master sizing cards on the team's behalf as a distractor.
Who decides a product question when the team, the scrum master and the product owner disagree? The product owner. In the bank's logo record, most of the cross-functional team wants a twenty per cent enlargement and the scrum master wants ten, but the product owner is content as it is, and the keyed answer leaves it unchanged. The explanation notes that distributing product authority to a majority vote or to the facilitator is exactly what the role exists to prevent.
If the team is blaming each other in a retrospective, is that the scrum master's failure? The bank keys the team, not the scrum master. In its fintech record the keyed answer is that the team should have recognised the problem and collaborated to solve it, because on an agile project the team is accountable for its own work, and the finger-pointing shows it took no corrective action during the sprint.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 Exam Content Outline, and every wrong answer is explained, not just marked wrong, so a role-boundary question teaches you the boundary rather than a single fact. Start the free 20-question sample — no card, no signup required to try it.
What does the scrum master actually own on the PMP exam?
The process and the team's ability to work sustainably. The bank keys the scrum master's duty as the one not discharged when a new team burns itself out on twelve-hour days, and separately describes the scrum master as the person who owns the process and coaches the team on the framework. Nothing about the product, the backlog order, or the estimates belongs to the role.
Can the scrum master decide a story's estimate?
No, and the bank tests this twice. When a scrum master splits the difference between the team's 8 points and the product owner's 3 and assigns 5, the keyed answer is that the figure should be the team's 8, because estimates belong to the people who will do the work. A separate record names the scrum master sizing cards on the team's behalf as a distractor.
Who decides a product question when the team, the scrum master and the product owner disagree?
The product owner. In the bank's logo record, most of the cross-functional team wants a twenty per cent enlargement and the scrum master wants ten, but the product owner is content as it is, and the keyed answer leaves it unchanged. The explanation notes that distributing product authority to a majority vote or to the facilitator is exactly what the role exists to prevent.
If the team is blaming each other in a retrospective, is that the scrum master's failure?
The bank keys the team, not the scrum master. In its fintech record the keyed answer is that the team should have recognised the problem and collaborated to solve it, because on an agile project the team is accountable for its own work, and the finger-pointing shows it took no corrective action during the sprint.