The Four Stances of an Agile Coach

THE MENTAL MODEL: An Agile Coach is not a single role but a blend of four distinct stances: Teacher, Mentor, Facilitator, and Professional Coach. The goal isn't just to "run Agile" but to develop the team's own capability to be agile. An effective coach's job is to make themselves progressively less necessary by building the team's competence and self-sufficiency.

HOW IT WORKS: The coach consciously chooses a stance based on the team's immediate needs and context. The four primary stances are: first, Teaching, which is imparting new knowledge to fill a clear gap. Second, Mentoring, which involves sharing personal experience to guide someone developing a skill. Third, Facilitating, which means holding a neutral space for a group to have a productive conversation and reach their own conclusions, without injecting the coach's opinion. Fourth, Professional Coaching, which focuses on helping the team or an individual unlock their own potential by asking powerful questions, assuming the answer lies within them, not with the coach.

WHEN TO USE IT: This framework is a diagnostic tool for coaches to assess their own actions: "Which stance am I in now? Is it the right one for this situation?" It's especially useful for experienced Scrum Masters or consultants looking to level up from managing ceremonies to truly shifting team behaviors and fostering a growth mindset. It provides a language for describing the complex work of developing agile teams.

WHEN NOT TO USE IT: This is a model for human and team development, not a technical problem-solving framework; it won't tell you how to configure a CI/CD pipeline. Misusing the model involves staying in one stance regardless of context. A coach who only asks Socratic questions when the team has a genuine knowledge gap is being ineffective, just as a coach who only teaches creates dependency.

ONE CANONICAL EXAMPLE: A team's velocity is erratic. A coach using the four stances might: 1) Teach a session on the principles of sustainable pace. 2) Mentor the Product Owner by sharing a story about how a previous team improved predictability. 3) Facilitate a retrospective to help the team discover the root cause themselves. 4) Coach the Tech Lead by asking, "What outcome do you want for the team's predictability, and what's one step you could take to make that happen?"