Coaching, Mentoring, and Servant Leadership
Three related stances
The Scrum Master is a true leader who serves. Three modes:
- Coaching - asking powerful questions, raising awareness, helping the team find its own answers; non-directive.
- Mentoring - sharing experience and guidance; more directive, useful when knowledge gaps exist.
- Servant leadership - putting the team's growth and the customer's value first; removing impediments, shielding from distraction, and building capability.
What the Scrum Master serves
Serves the Scrum Team (coaching self-management and cross-functionality), the Product Owner (finding techniques for backlog management), and the organization (leading Scrum adoption, removing barriers between stakeholders and teams).
Stances and traps
- Choosing directive answers (tell them what to do) when the team is capable; coaching is preferred for capable teams.
- Confusing servant leadership with passivity - it is active: removing impediments, teaching, and challenging the status quo.
- Assuming the Scrum Master is the team's secretary, note-taker, or quality gate.
- Overlooking that the Scrum Master also coaches the organization and Product Owner, not just Developers.
- Treating impediments as someone else's problem; the Scrum Master actively works to remove them.
Rule of thumb
Match stance to need: teach when knowledge is missing (mentoring), ask when capability exists (coaching), and act on impediments (servant leadership). Capable team + willing Scrum Master = coach, don't command.
Worked example
A team repeatedly misses the Sprint Goal. A directive fix ("work harder, here is the plan") creates dependence. Coaching: ask what the team observes about its planning and capacity, then let them choose an adaptation - building lasting capability.