Scrum Master as Coach and Mentor: Coaching Skills Explained

Coaching and mentoring are important skills for a Scrum Master. They help people understand Scrum, improve their way of working and gradually become more self-managing.

The Scrum Master should not become the person who solves every problem for the team.

What Is Coaching?

Coaching helps a person or team discover solutions by asking questions, listening and encouraging reflection.

Instead of saying:

"You should do this."

A coach might ask:

"What options do you see?"

What Is Mentoring?

Mentoring involves sharing knowledge, experience or guidance to help someone develop a skill or capability.

A Scrum Master may mentor team members when they need help understanding Scrum practices or the Scrum Master's role.

Coaching vs Mentoring

Coaching
Mentoring
Helps people discover their own solutions.
Shares knowledge, experience or guidance.
Uses questions and reflection.
Can include advice and examples.

Coaching Example

A Developer tells the Scrum Master:

"The team always has too much work in progress."

Instead of immediately providing a solution, the Scrum Master might ask:

  • What do you think is causing it?
  • What have you already tried?
  • What could the team change?
  • What would you like to experiment with?

Teaching vs Coaching

Sometimes people simply need information. In that situation, teaching may be more appropriate than coaching.

Teaching "Let me explain how this works."
Coaching "What do you think would work?"

When Should a Scrum Master Coach?

Coaching can be useful when:

  • The team needs to solve a problem.
  • People have different viewpoints.
  • The team is becoming dependent on the Scrum Master.
  • A person needs help developing confidence.
  • The team needs to improve its way of working.

When Should a Scrum Master Teach?

Teaching may be more appropriate when there is a clear knowledge gap.

For example:

  • Explaining a Scrum concept.
  • Explaining the purpose of a Scrum event.
  • Helping a new team understand Scrum terminology.
Good Scrum Master judgment:

Don't coach when someone simply needs a clear explanation. Don't give instructions when a coaching conversation would help the person learn.

Avoid Creating Dependency

One of the biggest mistakes a Scrum Master can make is becoming the team's permanent problem solver.

If the team asks the Scrum Master for every decision, the Scrum Master should gradually help the team develop the confidence and capability to make those decisions itself.

Useful Coaching Questions

Explore "What is happening?"
Understand "What do you think is causing it?"
Options "What could you try?"
Action "What will you do next?"

Common Mistakes

Giving Answers Too Quickly The team loses opportunities to develop its own solutions.
Always Coaching Some situations simply require teaching or direct information.
Acting Like the Manager The Scrum Master starts controlling people's decisions.
Creating Dependency The team cannot make progress without the Scrum Master.

Key Takeaway

An effective Scrum Master knows when to coach, when to mentor, when to teach and when to simply facilitate.

The ultimate goal is to help people and teams become more capable, confident and self-managing.