On day four of a two-week Sprint, a department head tells one of the five Developers to spend the rest of the week on a customer escalation for another product. The Sprint Goal depends on that Developer's work. What should the Scrum Master do?

Professional Scrum Master I, objective 2. Developing people and teams medium

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

The options

Not correct Accept it and have the Developers re-plan quietly, since line management outranks a Sprint

Wrong, and it is what usually happens. Absorbing the loss silently hides the cost of the interruption from everyone who could have prevented it, which is precisely the transparency the framework exists to create.

Correct Work with the department head and the Scrum Team on the impact to the Sprint Goal, and coach the organisation on why it structures and empowers the team to manage its own work

Correct. Serving the organisation by leading, training and coaching its Scrum adoption is squarely the Scrum Master's, and this is the occasion for it: Scrum Teams are structured and empowered by the organisation to manage their own work, so an organisation that pulls a Developer mid-Sprint is undoing something it set up. That is a coaching conversation, not a scheduling one.

Not correct Refuse on the Scrum Team's behalf and forbid the reassignment

Wrong, and tempting because the instinct is right. A Scrum Master has no authority to veto a manager, and asserting one would replace one command relationship with another rather than making the impact visible.

Not correct Cancel the Sprint, since the plan can no longer be met as written

Wrong on two counts. Only the Product Owner may cancel a Sprint, and the trigger is a Sprint Goal that has become obsolete — not a Sprint that has become harder.

Why

Self-management is not something a team declares; it is something the organisation confers and then has to keep honouring. Pulling a Developer out mid-Sprint is the commonest way that grant is quietly withdrawn. The move to remember for the exam is neither to veto the manager nor to absorb the loss quietly, but to make the consequence to the Sprint Goal visible to the person making the decision and let them decide with the cost in front of them.

Where this comes from

Cited
Scrum Guide section Scrum Master
What it says
Leading, training, and coaching the organization in its Scrum adoption;

Practise this

Reading one question is not practice. The trainer will draw a set from objective 2 and space the ones you get wrong.

Practise Professional Scrum Master I

More questions on this objective

All questions on Developing people and teams