Agile Coaches and Scrum Masters play a unique role: they help teams grow, adapt, and work more effectively without relying on authority or command-and-control tactics. To do this well, they must be able to support teams in different ways depending on the situation. The four core stances of Agile Coaching – Coach, Mentor, Facilitator, and Teacher – represent these different modes of helping. Each stance serves a distinct purpose, and learning to use them intentionally allows a Scrum Master to guide a team’s development with greater impact. Understanding these stances is the foundation for helping teams become more capable, collaborative, and self-sufficient.
These four core stances enable an Agile Coach to develop teams and organizations without stepping into directive consulting. The emphasis is on empowerment, capability-building, and effective collaboration. A mature Agile Coach chooses each stance deliberately based on context, readiness, and desired outcomes.
#1 Coach (Professional Coaching Stance)
Coaching’s purpose is to develop self-awareness, autonomy, and insight in individuals and teams.
How it works:
Uses powerful questions, active listening, reflection, and reflection techniques.
Helps individuals or teams unlock their own thinking instead of giving answers.
Encourages the team to generate its own solutions and commitments.
Focus: Awareness, self-discovery, growth.
When to use:
Leadership development, conflict resolution, decision ownership, mindset shifts.
Primary value: Builds long-term capability and accountability.
#2 Mentor
Mentoring’s purpose is to accelerate learning through shared experiences and practical guidance based on the expertise of the mentor.
How it works:
Shares stories, patterns, options, and lessons learned.
Draws from personal experience and offers guidance on how to approach problems.
Offers informed perspectives without prescribing decisions.
Helps others accelerate learning based on the mentor’s expertise.
Focus: experience transfer.
When to use:
When the team is inexperienced or exploring new practices.
To reduce avoidable errors and speed up skill acquisition.
#3 Facilitator
The facilitator’s goal is to enable effective collaboration and help the team achieve its outcomes.
How it works:
Designs and leads workshops, meetings, and structured discussions.
Ensures participation, creates psychological safety and ensures productive participation.
A facilitator uses timeboxes, creates a shared a purpose, and proposes a structure to drive the group toward effective outcomes.
Adopts facilitation techniques and decision-making frameworks to guide the team to explore options, discuss ideas, and making decisions.
Focus: Collaboration and effective group dynamics.
When to use:
Workshops, planning sessions, retrospectives, prioritization discussions, conflict-heavy sessions, alignment work.
To improve team cohesion and support high-quality group decisions.
#4 Teacher
The teacher builds foundational knowledge and understanding of principles and practices. The teacher explains concepts, shares knowledge, and promotes the adoption of frameworks.
How it works:
Provides structured instruction, frameworks, exercises, and examples.
Ensures clarity on roles, workflows, processes, and ways of working.
Focus: Knowledge transfer and skill building.
When to use:
Onboarding, introducing new practices, correcting misunderstandings.
Primary value: Establishes shared knowledge and consistent execution across the team.
Why the Scrum Master Cares
These four stances are important for a Scrum Master because they provide different ways to help a team grow, depending on what the team needs in the moment. Sometimes a team needs clear explanations and shared understanding, which is where the Teacher stance is useful. Other times they need someone with experience to offer guidance without taking over, which is what the Mentor stance provides. When the team is trying to work together, make decisions, or navigate conflict, the Facilitator stance helps them collaborate effectively and stay aligned. And when the goal is to build real ownership and problem-solving ability, the Coach stance encourages deeper reflection and helps the team discover its own solutions.
A Scrum Master who can move between these stances intentionally becomes far more effective than someone who relies on a single way of working.
Practicing these stances brings significant benefits to both the team and the broader organization. Teams become more capable, more confident, and less dependent on the Scrum Master to “run everything” for them. They collaborate better, surface issues sooner, and take more ownership of their work. Over time, this leads to greater trust, stronger delivery performance, and a healthier team culture. For the organization, these stances support a more successful and sustainable adoption of Agile ways of working, because they build internal capability rather than relying on external authority or command-and-control behaviors. In short, the four stances enable a Scrum Master to help a team become more agile.
#5 Consultant
In addition to the 4 core stances, the Agile Coaching Wheel introduced a fifth stance: Consultant.
The “Consultant” stance represents moments when an Agile Coach provides direct expertise, assessment, or recommendations rather than guiding the team to discover answers on their own. It is more directive than the other stances and is used when the organization needs clarity, specialized knowledge, or a faster path to a decision. This fifth stance was added to the original four because real-world Agile coaching often requires stepping beyond facilitation and teaching into advising—especially during complex transformations where teams and leaders need informed guidance to avoid costly mistakes or misunderstandings. It acknowledges that effective coaching sometimes means offering expert input, not just enabling others to find their own way.
How it works:
Provides expert advice, recommendations, and sometimes direction.
Helps diagnose problems and propose solutions.
Focus: guidance and organizational problem-solving.
How the Different Stances Work Together
A strong Agile Coach / Scrum Master shifts intentionally between stances based on need. For example, moving from one stance to another, he or she leverages coaching to empower, mentoring to guide, teaching to build knowledge, and facilitating to enable collaboration. The overall approach should be to avoid overly prescriptive interventions, and instead to enable teams to evolve sustainably.
These stances are also a central part of the Agile Coaching Growth Wheel, a framework that describes the skills, behaviors, and competencies an Agile Coach develops over time. The Wheel helps coaches understand where they are strong, where they need to grow, and how the different aspects of coaching fit together. The four stances sit at the heart of this model because they describe the practical ways a coach shows up in day-to-day interactions. In other words, the Growth Wheel provides the full map, and the stances are the key modes of travel across that map.
How the Scrum Master / Agile Coach Role Evolves
The Scrum Master Competency Ladder shows the progressive growth of a Scrum Master’s skills, moving from basic team support (level 1) to coaching multiple teams, facilitating organizational change, and becoming an Agile leader or coach (level 3). The Scrum Master / Agile Coach adopts the four stances in different moments, moving from event facilitation to deep organizational transformation, often categorized by focus (team, multiple teams, organization) and stances (teacher, coach, facilitator, mentor). Key areas include coaching, facilitation, technical awareness, servant leadership, and scaling agile, with models like Dreyfus or Burch’s stages often inspiring these progression levels.
Learn more about the Scrum Master Competency Ladder.
