Start with the decision the people need to make
A request for facilitation can hide several different needs. Developers might need to inspect a coordination problem, a Product Owner might need better stakeholder evidence, or a Scrum Team might need a productive improvement discussion. Name that need before choosing a technique. The Scrum Master is accountable for establishing Scrum and for Scrum Team effectiveness by enabling improvements in practices within the framework. That does not make the Scrum Master the owner of every product or technical decision. A productive intervention should help the relevant people inspect information and act within their accountabilities.
Support self-management rather than substitute a dispatcher
The Scrum Team is self-managing: it decides internally who does what, when and how. The Scrum Master coaches self-management and cross-functionality and helps cause the removal of impediments. Facilitation can make constraints, dependencies and differing observations understandable without taking permanent control of implementation choices. Asking people to explain an assumption is an original practical suggestion; it is not a mandatory Scrum script. Likewise, a team may choose a local coordination technique, but it should distinguish that choice from the framework. Counting assignments does not by itself establish that team effectiveness improved.
Keep stakeholder collaboration and product decisions visible
The Product Owner remains accountable for effective Product Backlog management, including ordering. Stakeholders can bring evidence, needs and disagreements, and those inputs should be discussed transparently rather than silently turned into a competing hidden backlog. The Scrum Master can facilitate stakeholder collaboration as needed and help remove barriers between stakeholders and Scrum Teams. This service does not transfer product ordering to the Scrum Master or authorize an automatic override of every organizational policy. Identify the barrier and work with the relevant people toward an arrangement that preserves a useful inspection opportunity.
Worked example: remove a barrier without changing the purpose
A fictional organizational meeting policy prevents several relevant stakeholders from joining the Sprint Review. The case establishes that a suitable arrangement is possible if the barrier is addressed. The Scrum Master helps surface the constraint, supports stakeholder collaboration and works on the barrier so the Review can inspect outcomes and discuss adaptation. Replacing the Review with one-way status slides would not preserve that collaborative purpose. This example does not prescribe a particular meeting platform or grant blanket policy authority. It shows why a logistical obstacle should be handled in relation to the event purpose and relevant accountabilities.
Treat improvement and shared quality as concrete work
The Retrospective identifies helpful changes to improve quality and effectiveness. Address the most impactful improvements as soon as possible; an improvement may be added to the next Sprint Backlog. A disagreement about such work is information to inspect, not automatic proof that the event should be cancelled. For several Scrum Teams working on one product, the shared product commitments and common Definition of Done also matter. A local label such as complete does not substitute for a usable Increment meeting that quality boundary. Facilitation should make the real condition visible rather than manufacture agreement or a completion label.
Transfer check: preserve the right accountability
Developers ask for help discussing an integration problem. Before hearing their evidence, a manager asks the Scrum Master to assign a mandatory solution to each person. Explain what evidence should first be made visible, why permanent task dispatch would replace self-management, and what impediment-removal support could still be appropriate. Then consider a stakeholder request to reorder product work: identify who remains accountable and how the request can be discussed without creating a hidden competing backlog. These are different decisions even if the same people attend both conversations. Use the linked original questions and retrieval cards to explain those boundaries before reading feedback.
A Scrum Team finds that stakeholder access is restricted by an organizational meeting policy. Several key stakeholders can participate in a suitable Review arrangement if the policy barrier is addressed. Which TWO Scrum Master services are relevant? Select exactly TWO.
- The Scrum Master services include facilitating stakeholder collaboration and removing barriers between stakeholders and Scrum Teams, along with supporting positive productive events within their timeboxes. The case says a suitable Review arrangement is possible if the policy barrier is addressed.
- Work on that barrier and preserve the Review opportunity to inspect outcomes and adapt with stakeholders. A one-way or internal-only status replacement postpones that collaboration, and meeting logistics do not transfer Product Owner ordering accountability. This does not grant authority to override every organizational policy.
Compare the other answer choices
A one-way status presentation does not preserve the collaborative inspection and adaptation purpose described for the Review.
Meeting access problems do not transfer Product Backlog ordering accountability.
This bypasses the available solution to the stated access barrier and removes the Review stakeholder inspection and adaptation opportunity.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
The Scrum Guide — November 2020