6.2 Facilitation

Facilitation as a Scrum Master Stance

The 2020 Scrum Guide states the Scrum Master is accountable for the Scrum Team's effectiveness and helps everyone ensure all Scrum events take place and are positive, productive, and kept within the timebox. Facilitation is the professional practice the Scrum Master uses to make that real. The Guide names facilitation as one of the ways the Scrum Master serves the Scrum Team; the specific techniques below are widely accepted Scrum.org competency content, not extra Scrum rules.

A facilitator is responsible for the process of a conversation, not its content. The facilitator stays neutral on the decision itself and helps the group surface options, hear every voice, and converge on a decision the group owns. A Scrum Master who pushes a preferred answer has stopped facilitating and started directing — a distinction PSM I tests repeatedly. Facilitation is fundamentally about making it easier for the group to think and decide together; the facilitator adds structure, not opinions.

Who Facilitates

The Scrum Master does not have to run every event personally. Any Scrum Team member can facilitate an event, and over time the team often facilitates its own events. What stays fixed under the Scrum Guide is the purpose and accountability of each event — not who holds the marker. For example, the Daily Scrum is for the Developers; even if the Scrum Master once set it up, the Developers own it. Confusing "facilitates" with "owns" or "attends" is a frequent exam trap: the Scrum Master may attend or facilitate the Daily Scrum but must not run it as a status meeting.

Facilitating the Five Scrum Events

Notice that good facilitation is event-specific. In Sprint Planning the facilitation goal is a crisp, testable Sprint Goal and a plan the Developers believe in. In the Sprint Review the goal is genuine two-way collaboration with stakeholders so the Product Backlog is actually adapted — not a one-way demo. In the Retrospective the goal is psychological safety strong enough that real problems surface and turn into concrete improvements the team will act on next Sprint.

Neutral Process Ownership

• Separate process from content. The Scrum Master decides how the conversation runs; the team decides what they conclude.
• Make participation visible. Draw out quiet voices and prevent a single voice from dominating, which protects transparency.
• Hold the timebox without cutting a conversation off mid-decision — negotiate the scope of the discussion, not the Scrum Guide timebox itself.
• Test for real agreement rather than assuming consensus from silence (silence often hides disagreement, not consent).
• Stay outcome-agnostic. If you find yourself steering toward your own answer, you have left the facilitation stance.

Common Techniques (Professional Practice, Not Scrum Rules)

• Working agreements: the team writes its own ground rules for how events run.
• Round-robin / silent writing: every person contributes before open discussion to reduce anchoring and groupthink.
• Dot voting / fist-of-five: lightweight convergence and consent checks.
• Liberating Structures / powerful questions: structured prompts that broaden participation.

These are facilitation tools. They are useful, but a PSM I answer should never claim the Scrum Guide requires a specific technique — the Guide is intentionally minimal and prescribes events and their timeboxes, not facilitation recipes.

A Simple Facilitation Arc and Common Traps

A reliable structure for any facilitated session is: open (clarify purpose and desired outcome), diverge (generate options, gather every voice), converge (narrow toward a decision), and close (confirm the decision and next steps). The Scrum Master designs and holds this arc while the team supplies the content.

Frequent PSM I facilitation traps to recognize and reject:

• Facilitator-as-decider. Choosing the answer 'to save time' abandons neutrality and self-management.
• Status-meeting Daily Scrum. A round of reports to the Scrum Master replaces Developer inspection toward the Sprint Goal.
• Demo-only Sprint Review. Treating the Review as a presentation rather than a working session that adapts the Product Backlog.
• Cutting the timebox short. Ending mid-decision instead of tightening the discussion's scope; the timebox is a maximum the team works within, not a guillotine.
• Technique-as-rule. Insisting a team must use a specific tool (dot voting, planning poker) as if the Scrum Guide mandated it.

Good facilitation is invisible: the group does the thinking and owns the outcome, while the Scrum Master quietly ensures the event is positive, productive, and on purpose.