Simyl
simylflow
Course Home
Module 6: Coaching & Continuous Improvement
Lesson 1 of 4
20 min

The Scrum Master's Stances

Different modes for different situations.

1Four Stances of the Agile Coach

Based on Lyssa Adkins' work, Scrum Masters shift between stances:

Teacher: Sharing knowledge they don't have. "Let me explain how Sprint Planning works."

Mentor: Sharing experience and guidance. "When I've seen teams struggle with this, they often..."

Facilitator: Making group processes easier. "Let's hear from everyone on this topic."

Coach: Helping people find their own answers. "What do you think is causing that?"

Each stance is appropriate in different contexts. The key is intentional choice, not defaulting to your comfort zone.

Default to Coach

When unsure, default to coaching (asking questions). It builds capability rather than dependency. Teach and mentor when the person truly lacks knowledge or experience.

2When to Use Each Stance

Teaching is appropriate when:

  • The person genuinely doesn't know something
  • Speed is important (crisis situations)
  • You're an expert and they're beginners

Mentoring is appropriate when:

  • They need context or perspective
  • Your experience is directly relevant
  • They're seeking advice, not just answers

Facilitating is appropriate when:

  • The group needs to make a decision together
  • You need to remain neutral
  • Multiple perspectives need to be heard

Coaching is appropriate when:

  • They have the capability but not the clarity
  • You want to build their problem-solving skills
  • The answer should come from them

3The Coaching Conversation

A coaching conversation follows a pattern:

1. Build context "Tell me about what's happening." "What have you tried so far?"

2. Explore with questions "What would success look like?" "What's the real challenge here?" "What options do you see?"

3. Generate possibilities "What else could you try?" "If resources weren't limited, what would you do?"

4. Commit to action "What's your next step?" "What might get in the way?" "How will you know if it's working?"

Key principle: Resist the urge to give answers. Even when you know the "right" answer, the learning comes from them finding it.

Coaching Response

Developer: 'The standup takes too long.' SM: 'What's making it take so long? What have you tried? What else could work?'

Non-Coaching Response

Developer: 'The standup takes too long.' SM: 'Here's how to fix it: use a timer and limit each person to 30 seconds.'

Key Takeaways
  • Scrum Masters use multiple stances: teacher, mentor, facilitator, coach
  • Default to coaching—it builds capability
  • Use teaching and mentoring when knowledge/experience is truly missing
  • Great coaching asks questions rather than giving answers