Scrum Master Facilitation and Coaching: Helping Teams Decide
Introduction
Scrum Master facilitation and coaching help a team make its own decisions. When one person dominates Sprint Planning, facilitation can give everyone a chance to surface risks. When Developers already have the knowledge to solve a problem, coaching can help them examine options and decide what to try.
This PSM I lesson covers Facilitation and Coaching in the Developing People and Teams focus area. You will distinguish these practices from teaching and mentoring, and choose a response when an event stalls, a stakeholder needs help, or a team disagrees.
Learning objectives
- Explain facilitation and its purpose in the Scrum events.
- Explain coaching and how it differs from teaching, mentoring and consulting.
- List the Scrum Master services to the Scrum Team, the Product Owner and the organisation that involve teaching and coaching.
- Apply facilitation techniques: preparing, timeboxing, keeping focus, drawing out quieter voices and handling conflict.
- Decide when to step in and when to let the team solve a problem itself.
- Recognise typical anti-patterns: the Scrum Master as decision maker, minute-taker or referee.
1. What facilitation means in Scrum
A facilitator helps a group have a purposeful, inclusive discussion and leaves decisions with the people accountable for them. The Scrum Master ensures the Scrum events happen and use their time well. Depending on the situation, the Scrum Master or another participant can facilitate. The facilitator can help surface difficult facts without choosing an outcome on behalf of the group.
A facilitator typically does the following:
- Clarifies the purpose. Every event in Scrum has a purpose, for example the Sprint Retrospective plans ways to increase quality and effectiveness. The facilitator makes sure participants know it.
- Prepares just enough. A venue, material, tools for remote participants, and a rough shape for the conversation. Over-preparation removes the team's ownership.
- Guards the timebox. The facilitator signals time and helps the group decide what to do when the topic is larger than the time available, for example by choosing the most valuable topic first.
- Includes everybody. The facilitator invites quiet participants, prevents one person from dominating, and makes it safe to disagree.
- Keeps the discussion on topic. Side conversations are noted and offered another place, but the facilitator does not decide what is important.
- Makes outcomes visible. The group states its decisions and next steps clearly, so that the result is a plan rather than a pleasant talk.
Facilitation and accountability
The facilitator manages how the discussion happens. The Developers conduct the Daily Scrum, and the Scrum Master helps them keep it useful and within 15 minutes. If the Scrum Master is working on a Sprint Backlog item, they participate as a Developer. For other events, the team can ask a participant with the right skills to facilitate.
Example: facilitating a Sprint Retrospective
A Scrum Team with six Developers, a Product Owner, and a Scrum Master has discussed about the same slow code reviews in three consecutive Retrospectives without anything changing. The Scrum Master prepares the event differently:
- They open by restating the purpose and the timebox (three hours at most for a one-month Sprint, with a shorter event usual for shorter Sprints).
- They ask each person to write, silently, the one thing that most reduces quality or speed. Writing first lets people form a view before hearing the most outspoken participant.
- The group sorts the notes and picks the most impactful topic by dot voting.
- They explore causes, not blame: reviews wait because only two Developers know the payment module.
- The group chooses one experiment: pair on payment changes for the next Sprint, and agree a review turnaround of one working day.
- The team agrees how to start promptly. The Developers can include the experiment in their next Sprint Backlog and check how long reviews wait before and after the change.
The Scrum Master helped the team make the decision and agree on how to check the result. Dot voting and silent writing were choices for this situation.
2. What coaching means
Coaching is a conversation that helps a person or a team find their own answers and take their own actions. A coach asks questions, reflects what they hear, offers observations, and holds the person accountable for the actions they choose. The Scrum Guide lists coaching the team members in self-management and cross-functionality as a core service of the Scrum Master to the Scrum Team, and coaching the organisation in its Scrum adoption as a service to the organisation.
Useful coaching questions are open (they cannot be answered by yes or no) and neutral:
- "What would success look like for this Sprint?"
- "What have you already tried?"
- "What is stopping the team from deciding this today?"
- "Which options do you see, and what are the consequences of each?"
- "What is the smallest step you could take before the next Daily Scrum?"
Comparison: five stances of a Scrum Master
| Stance | What it means | Typical sentence | When it is a good fit |
|---|---|---|---|
| Facilitating | Guides the process of a conversation without steering the content | "Let's make sure everyone has a chance to speak." | Events, workshops, conflict between team members |
| Coaching | Asks questions so the person finds their own answer | "What options do you see?" | Team is capable but stuck; building self-management |
| Teaching | Explains Scrum and its rules | "The Sprint Goal is the commitment of the Sprint Backlog." | Misunderstandings about the framework, new members, stakeholders |
| Mentoring | Shares personal experience and advice | "In a similar situation I tried this." | The person asks for experience and is open to it |
| Consulting / advising | Gives an expert recommendation, while the relevant people retain decision authority | "I recommend splitting this item." | The team lacks knowledge and requests it; keep the decision with the team |
Choose a stance based on the gap you observe. Teach a rule when people misunderstand it. Coach when the team has the knowledge to decide. Facilitate when the conversation keeps people from contributing. These are practical stances, and the Scrum Guide does not prescribe a sequence for them.
3. Teaching Scrum
The guide states that the Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organisation. Teaching is therefore a continuous activity, not an onboarding session.
Examples of teaching situations:
- New Developers join. The Scrum Master explains the events, the Definition of Done and the Sprint Backlog, preferably through practice rather than slides.
- A stakeholder wants to add work mid-Sprint. The Scrum Master explains that the Sprint Goal does not change, that scope may be clarified and renegotiated between the Product Owner and the Developers as more is learned, and that new requests go through the Product Owner into the Product Backlog.
- Management wants to compare teams by velocity. The Scrum Master explains that Scrum does not require story points or velocity. If teams use them, their scales and contexts can differ. Compare progress toward goals using observed outcomes instead.
- The Product Owner works alone on the Product Backlog. The Scrum Master helps the Product Owner see how collaborating with the Developers makes items clearer.
When teaching a Scrum rule, explain how it helps the team inspect what is happening and decide what to change. See empiricism and the Scrum Values for examples of those principles.
4. Choosing a stance: when to step in
Two mistakes are common and equally harmful.
Over-intervening. The Scrum Master solves each problem, which keeps the team dependent and signals that they cannot manage themselves.
Under-intervening. The Scrum Master watches the team break the rules, such as skipping the Retrospective, and calls it self-management. The Scrum Master is accountable for the Scrum Team's effectiveness and for establishing Scrum as defined in the guide, so ignoring a violation is not neutral.
Use the following questions to decide what help would be appropriate. See how self-managing teams make decisions for where decision authority sits.
- Is it a Scrum rule or a teaching gap? Teach it. Example: a stakeholder believes the Product Owner must write all items alone.
- Is the team capable but unsure? Coach. Example: the Developers cannot agree on how to split an item.
- Is the issue outside the team's reach? Cause the removal of the impediment. Example: a procurement delay for a licence.
- Is the problem harming transparency, safety or the Sprint Goal right now? Act quickly and openly, while respecting the roles. Example: a manager is bypassing the Product Owner and assigning work to Developers directly.
Worked example: the dominating senior Developer
Situation. In Sprint Planning, the most senior Developer proposes the plan and the others quietly agree. Two Sprints later, three items stall because less experienced Developers had doubts they did not voice. The Scrum Master is asked by the Product Owner to "tell the senior Developer to stop".
Reasoning.
- The issue is about how the team communicates, which is within the Scrum Master's service to the team, so the Scrum Master should act.
- Telling the senior Developer to stop is a directive and treats the symptom. It also positions the Scrum Master as a supervisor.
- A better approach is to change the process, which belongs to a facilitator: start the planning with silent individual thinking, ask each Developer to say how they would approach the first item, or use a technique where everyone reveals an estimate at the same time.
- In parallel, the Scrum Master can coach the senior Developer privately: "What would help the team own the plan?" and coach the quieter Developers on speaking up early.
- The Scrum Team can inspect the pattern at its next Retrospective and check whether the new Planning format surfaces risks earlier.
Solution. Facilitate Sprint Planning so each Developer can raise concerns. Coach individuals if useful, and leave the technical plan with the Developers.
Why the other options are weaker. Telling the senior Developer to stop only addresses one person and can create resentment. Leaving it to the team without any change in how the event is run ignores the Scrum Master's accountability for productive events. Asking the Product Owner to decide the plan removes the Developers' ownership of the Sprint Backlog.
5. Facilitating conflict
Conflict is normal in a team of capable people. A Scrum Master treats it as information, not as a failure. The Scrum Values help: respect for each other as capable, independent people, openness about the work and challenges, and courage to do the right thing and work on tough problems.
Practical steps:
- Notice early. Silence in a meeting, repeated rework, jokes with an edge are all signals.
- Separate the person from the problem. Restate the disagreement in terms of needs and facts: "One of you needs fast delivery, the other needs a design that can be extended. Is that right?"
- Check that each concern is understood. Invite each person to restate the other person’s concern and correct misunderstandings before evaluating options.
- Look for options and experiments. A small, time-boxed trial often resolves what debate cannot.
- Let the decision belong to the people who must live with it. If it is a technical choice, the Developers decide. If it is about order or value, the Product Owner decides. If there is disagreement about the framework, consult the Scrum Guide together.
- Follow up. The Scrum Master asks later how the agreement is working.
6. Facilitation across the whole Scrum Team and stakeholders
The Scrum Master also serves the Product Owner and the stakeholders. The guide lists, among other things, that the Scrum Master helps find techniques for effective Product Goal definition and Product Backlog management, helps the Scrum Team understand the need for clear and concise Product Backlog items, and facilitates stakeholder collaboration as requested or needed.
Examples:
- A Product Owner overwhelmed by requests. The Scrum Master helps the Product Owner try a lightweight way to visualise options and trade-offs with stakeholders, such as a shared story map, while the Product Owner remains the one who orders the Product Backlog.
- Stakeholders who disagree on priorities. The Scrum Master can facilitate a workshop with the Product Owner so that the stakeholders understand constraints. The decision on order remains with the Product Owner.
- A Sprint Review that has become a demo with a passive audience. The Scrum Master coaches the team to turn it into a working session: what was learned, what changed in the market, what to do next.
Comparison: who does what in a facilitated event
| Event | Who conducts it | What the Scrum Master does |
|---|---|---|
| Sprint Planning | The whole Scrum Team | Ensures it takes place, is productive and time-boxed; facilitates if requested |
| Daily Scrum | The Developers | Ensures it takes place; teaches the Developers to keep it within 15 minutes; takes part as a Developer when working on Sprint Backlog items |
| Sprint Review | The Scrum Team with stakeholders | Ensures it is positive and productive; facilitates stakeholder collaboration if needed |
| Sprint Retrospective | The Scrum Team | Ensures it takes place and is productive; participates as a team member and ensures a safe space |
7. Common pitfalls and exam tips
- "The Scrum Master decides" is almost always wrong. The Scrum Master facilitates, coaches, teaches and serves; the Developers, the Product Owner or the Scrum Team decide within their own accountabilities.
- Doing nothing is also wrong. When a rule of Scrum is being broken or an impediment is blocking the team, the Scrum Master acts. Look for the option that teaches and coaches, not for the option that ignores or enforces.
- Facilitation is for the process. An option where the Scrum Master suggests the content of a technical solution is weaker than an option where the Scrum Master asks questions to help the Developers find it.
- Escalating over the team's head is rarely first. The better first step is usually to talk with the people involved, then involve others.
- Address the behavior respectfully. A private conversation can help someone reflect. If an interaction is unsafe or silences another participant, intervene during the discussion.
- Help remove impediments. Ask what the team can resolve, then help bring in people with the authority or skills to address the rest.
- The Scrum Master is not the only person who may facilitate. The guide says the Scrum Master ensures events take place and are productive; the team can facilitate itself.
Exam tip. In a "what should the Scrum Master do first?" question, rank the options. Direct inspection of the situation and a conversation with the people involved usually comes before reporting, enforcing or changing the framework.
8. Mini case study
Situation. A Scrum Team of seven building a logistics app has a Sprint Retrospective every Sprint, but the same three topics come back each time: unclear Product Backlog items, late feedback from a key stakeholder, and a flaky test environment. The Developers say retrospectives are a waste of time and two of them have started to skip. The Product Owner suggests dropping the event to save three hours per Sprint.
Question. How should the Scrum Master respond?
Solution.
- Seek to understand. The Scrum Master has individual conversations: "What would make the Retrospective worth your time?" The answers show that actions are agreed but never done, because nobody owns them and none enter the Sprint Backlog.
- Teach the purpose. The Retrospective exists to plan ways to increase quality and effectiveness. An event that produces no change is not doing its job, but that is a reason to fix the event, not to remove it. Removing it would remove the framework's main inspection point for the team itself.
- Change the facilitation. The Scrum Master proposes a different format for the next Retrospective: review the actions of the last one first, let the team select one or two improvements, and ask the Developers how they will act on them. They may add an improvement to their next Sprint Backlog.
- Cause the removal of impediments. The flaky environment and the stakeholder delay are impediments the team cannot resolve alone. The Scrum Master takes the first to the infrastructure group and helps the Product Owner arrange a regular feedback slot with the stakeholder.
- Follow up. After two Sprints, the team checks whether it completed the improvements and whether the test environment became more reliable. It adjusts the format based on the results.
Why not the alternatives. Dropping the event follows a symptom and breaks the framework. Forcing attendance without changing the event treats people as the problem. Telling the Developers which improvements to make removes their ownership.
Key terms
- Facilitation: guiding the process of a conversation without deciding its content.
- Coaching: helping a person or team find their own answers by asking questions and reflecting.
- Teaching: explaining Scrum theory, rules and values.
- Mentoring: sharing personal experience and advice on request.
- Impediment: anything the team cannot resolve alone that blocks its progress.
- Timebox: a fixed maximum duration for an event.
- Servant leadership: leading by serving the team and the organisation.
Summary checklist
- I can explain that a facilitator is responsible for the process, not the content or the decision.
- I can state that the Scrum Master ensures the events take place and are positive, productive and time-boxed.
- I can distinguish facilitating, coaching, teaching, mentoring and consulting.
- I know the Daily Scrum belongs to the Developers.
- I can describe a calm sequence for handling conflict and name who owns each type of decision.
- I know why doing nothing and taking over are both wrong answers.
- I can explain how a Scrum Master facilitates stakeholder collaboration without taking the Product Owner's decisions.
Sources
- The Scrum Guide, November 2020: https://scrumguides.org/scrum-guide.html (opens in a new tab) (sections "Scrum Master", "Scrum Events", "Sprint Retrospective").
- Scrum.org, Professional Scrum Master I assessment: https://www.scrum.org/assessments/professional-scrum-master-i-certification (opens in a new tab)
- Scrum.org, Developing People and Teams: https://www.scrum.org/resources/professional-scrum-competency-developing-people-and-teams (opens in a new tab)
- Scrum.org, Comparing Facilitation, Coaching, Mentoring and Teaching: https://www.scrum.org/resources/comparing-facilitation-coaching-mentoring-and-teaching (opens in a new tab)
