Servant Leadership and Team Development
Serving first
Servant leadership inverts the traditional hierarchy of attention: the Scrum Master's job is to remove impediments, build capability, protect focus and create psychological safety so the team can self-manage. Crucially, servant leadership is not passivity. You still hold the boundary of Scrum, give direct feedback when behaviour undermines the team, and let the team experience the consequences of its choices.
Stages of team development
Tuckman's model is a practical map: forming (polite, dependent, needs direction), storming (conflict over roles and ways of working - normal, not a failure), norming (agreements solidify), performing (self-managing, high trust), and adjourning. Situational leadership complements it: directing, coaching, supporting, delegating as capability rises. Motivation theory (autonomy, mastery, purpose) explains why removing control often increases output.
Traps
- Treating storming as a defect to be suppressed; unaddressed conflict resurfaces later as disengagement.
- Shielding the team from all organizational friction - teams need to learn to negotiate with their environment.
- Using "servant leadership" to avoid hard conversations; that is abdication.
- Assuming a quiet team is a high-performing team.
- Applying the same leadership stance regardless of the team's stage.
Rule of thumb
Match your stance to the stage: be more directive while forming and storming, more coaching and delegating once norming and performing. If a team cannot describe its own working agreements, it is not yet performing.