Coaching the Scrum Team: A Comprehensive Guide for PSM II
Introduction
Coaching the Scrum Team is a critical competency within the Developing People and Teams area of the Professional Scrum Master II (PSM II) certification. As a Scrum Master operating at an advanced level, your ability to coach — not just facilitate or teach — becomes the differentiating factor between teams that merely follow Scrum mechanics and teams that truly embody agile values and principles. This guide will help you deeply understand what coaching the Scrum Team means, why it matters, how it works in practice, and how to confidently answer exam questions on this topic.
Why Coaching the Scrum Team Is Important
Coaching is important because Scrum is not just a framework of events, artifacts, and roles — it is a mindset shift. Without effective coaching, teams often fall into the trap of mechanical Scrum, where they go through the motions without experiencing the benefits of empiricism, self-management, and continuous improvement.
Here are the key reasons coaching matters:
• Self-Management: Scrum Teams are expected to be self-managing. They don't arrive at this state automatically. A Scrum Master coaches the team to develop the skills, confidence, and accountability needed to manage their own work without being directed by others.
• Continuous Improvement: Coaching helps team members develop a growth mindset. Rather than providing solutions, the Scrum Master as coach asks powerful questions that help the team discover their own solutions, leading to deeper learning and sustainable improvement.
• Navigating Complexity: In complex environments, there are no predefined answers. Coaching helps the team develop the ability to inspect and adapt, experiment, and learn from outcomes — which is at the heart of empiricism.
• Building Trust and Psychological Safety: Effective coaching fosters an environment where team members feel safe to speak up, take risks, fail, and learn. This psychological safety is foundational to high-performing teams.
• Developing People: A Scrum Master who coaches develops people, not just processes. This means helping individuals grow their technical skills, interpersonal skills, and understanding of Scrum values.
What Is Coaching the Scrum Team?
Coaching in the Scrum context is a professional relationship where the Scrum Master helps team members and the team as a whole unlock their potential. It is fundamentally different from teaching, mentoring, or consulting:
• Teaching involves transferring knowledge — explaining what Scrum is and how its events work.
• Mentoring involves sharing personal experience and guidance — drawing on your own journey as a practitioner.
• Consulting involves providing expert advice and direct solutions to problems.
• Coaching involves helping the individual or team discover their own answers through active listening, powerful questioning, and facilitating self-awareness.
A skilled Scrum Master knows when to shift between these stances, but coaching is the stance that creates the most lasting change because it builds internal capability rather than external dependency.
Key characteristics of coaching the Scrum Team include:
• Non-directive approach: The coach does not tell the team what to do. Instead, they help the team explore options, understand consequences, and make informed decisions.
• Active listening: The coach listens deeply — not just to words, but to emotions, body language, and what is left unsaid.
• Powerful questions: The coach asks open-ended questions that challenge assumptions, provoke reflection, and lead to insight. Examples include: "What would happen if you tried a different approach?" or "What is preventing the team from achieving its Sprint Goal?"
• Observation without judgment: The coach observes team dynamics and behaviors and reflects them back to the team without blame or judgment.
• Goal-oriented: Coaching is focused on helping the team move toward its goals, whether those are related to product delivery, team collaboration, or adherence to Scrum values.
• Respect for the team's autonomy: The coach trusts that the team has the ability to solve its own problems and makes space for that to happen.
How Coaching the Scrum Team Works in Practice
Coaching the Scrum Team is not a one-time event — it is an ongoing practice that is woven into every interaction, every Scrum event, and every moment of collaboration. Here is how it works in practice:
1. Coaching During Scrum Events
Each Scrum event is an opportunity for coaching:
• Sprint Planning: Rather than directing the team on how to plan, the Scrum Master might ask, "How confident are you in achieving this Sprint Goal?" or "What dependencies might impact your plan?"
• Daily Scrum: If the Daily Scrum becomes a status report to the Scrum Master, the coach helps the team understand the purpose of the event and encourages them to own it. A coaching question might be: "Who is this event for, and how can it best serve you?"
• Sprint Review: The Scrum Master coaches the team to actively seek stakeholder feedback rather than just presenting a demo. They might ask, "What would make this Sprint Review more valuable for our stakeholders?"
• Sprint Retrospective: This is the primary event for coaching toward continuous improvement. The Scrum Master helps the team go beyond surface-level observations to root causes. Questions like "What patterns do you notice?" or "What experiment could we try next Sprint?" are powerful coaching tools.
2. Coaching for Self-Management
Self-management is a journey, not a destination. The Scrum Master coaches the team by:
• Resisting the urge to solve problems for the team, even when the answer seems obvious.
• Reflecting team dynamics back to the team: "I noticed that decisions tend to be made by one or two people. What do you think about that?"
• Encouraging the team to establish their own working agreements and hold each other accountable.
• Helping the team navigate conflict constructively rather than avoiding it or resolving it on their behalf.
3. Coaching Individuals
While much of coaching happens at the team level, the Scrum Master also coaches individuals:
• Helping a Developer who is struggling with giving or receiving feedback.
• Coaching the Product Owner on effective stakeholder management or Product Backlog refinement techniques.
• Supporting a team member who is resistant to change by helping them understand the underlying fear or concern.
4. Coaching Through Modeling Behavior
The Scrum Master coaches by example. By embodying the Scrum values of Commitment, Courage, Focus, Openness, and Respect, the Scrum Master sets the tone for the entire team. If the Scrum Master demonstrates vulnerability, asks for feedback, and admits mistakes, the team is more likely to do the same.
5. Coaching Toward Organizational Change
At the PSM II level, coaching extends beyond the team. The Scrum Master coaches the broader organization to understand and support Scrum. This includes coaching leaders on servant leadership, helping remove organizational impediments, and advocating for structural changes that enable agility.
6. Knowing When to Shift Stances
An advanced Scrum Master recognizes that coaching is not always the right stance. In a crisis, the team may need direct guidance. When the team lacks knowledge, teaching may be appropriate. When they need inspiration, mentoring may help. The skill lies in knowing when to coach and when to shift — and always returning to coaching as the default stance for long-term growth.
Common Coaching Models Used by Scrum Masters
While the PSM II exam does not test specific coaching models, understanding them enhances your ability to answer scenario-based questions:
• GROW Model: Goal, Reality, Options, Will — a structured approach to coaching conversations.
• Systemic Coaching: Looking at the team as a system and coaching the interactions between members, not just individuals.
• Appreciative Inquiry: Focusing on what is working well and building on strengths rather than only fixing problems.
• Clean Language: Using the coachee's own words and metaphors to deepen understanding without introducing bias.
Exam Tips: Answering Questions on Coaching the Scrum Team
PSM II exam questions on coaching are typically scenario-based and require you to demonstrate an understanding of why coaching is effective, when to coach versus use other stances, and how a Scrum Master coaches without being directive. Here are detailed tips:
Tip 1: Always Favor Responses That Empower the Team
The best answer is almost always the one where the Scrum Master helps the team discover the answer themselves rather than providing it. If an option says the Scrum Master tells the team what to do, that is likely wrong. If an option says the Scrum Master asks the team a question or facilitates a discussion, that is likely correct.
Tip 2: Understand the Difference Between Coaching, Teaching, Mentoring, and Consulting
Questions may present scenarios where you need to identify which stance is most appropriate. Remember: coaching is about unlocking potential through questions and reflection; teaching is about imparting knowledge; mentoring is about sharing experience; consulting is about providing solutions. Choose coaching when the team has the capability but needs help finding their own path.
Tip 3: Look for Answers That Promote Self-Management
If a question describes a team that is dependent on the Scrum Master for decisions, the correct answer will involve the Scrum Master stepping back and coaching the team to take ownership. Avoid answers where the Scrum Master takes on responsibilities that belong to the team or the Product Owner.
Tip 4: Recognize the Value of Powerful Questions
Many correct answers will involve the Scrum Master asking questions rather than making statements. Questions like "What do you think is the root cause?" or "What options have you considered?" are hallmarks of coaching. Answers that involve the Scrum Master making assertions or directives are typically less preferred.
Tip 5: Pay Attention to Context and Timing
Some questions test whether you know when coaching is appropriate versus when another approach is needed. For example, if the team is new to Scrum and doesn't understand the purpose of a Sprint Retrospective, teaching might be the right first step before coaching them to improve. However, if the team is experienced but complacent, coaching through powerful questions is the better approach.
Tip 6: Consider the Long-Term Impact
When evaluating answer choices, think about which option leads to the most sustainable outcome. Coaching produces long-term capability improvements, while telling or directing provides only short-term relief. The exam favors answers that build lasting capability.
Tip 7: Watch for Subtle Traps
Some answers may sound helpful but actually undermine coaching principles. For example, an answer that says the Scrum Master facilitates a retrospective and then tells the team which improvement to implement starts well but ends poorly. The team should decide which improvements to pursue. Read each answer option completely and carefully.
Tip 8: Remember That Coaching Applies to the Whole Organization
At the PSM II level, some questions may involve coaching stakeholders, management, or the Product Owner. The same principles apply — help them discover insights rather than dictating solutions. The Scrum Master coaches upward and outward, not just within the team.
Tip 9: Embrace the Scrum Values
Many coaching questions are ultimately about whether the Scrum Values are being lived. If a scenario describes a team that lacks openness, the coaching response would be to help the team reflect on why they are not being open and what they could do differently — not to force transparency through mandates.
Tip 10: Practice Scenario-Based Thinking
The best way to prepare is to practice reading scenarios and identifying: (a) What is the root issue? (b) What stance should the Scrum Master take? (c) What action best supports the team's growth? When in doubt, choose the answer that respects the team's intelligence, promotes empiricism, and supports self-management.
Summary
Coaching the Scrum Team is arguably the most important competency of an advanced Scrum Master. It is the mechanism through which teams evolve from following a framework to truly embodying agility. Effective coaching requires patience, skill, and a deep belief in the team's ability to solve their own problems. On the PSM II exam, questions about coaching will test your ability to choose responses that empower rather than direct, question rather than tell, and develop long-term capability rather than provide short-term fixes. Master this competency, and you will not only pass the exam — you will become the kind of Scrum Master that truly transforms teams and organizations.
