Servant Leadership for Scrum Masters: Leading Without Commanding

A Scrum Master is a leader, but not a traditional command-and-control manager. Scrum encourages leadership through service, coaching, facilitation and support.

The goal is to help the Scrum Team become more effective and increasingly self-managing.

What Is Servant Leadership?

Servant leadership means putting the needs and effectiveness of the team and organization ahead of personal authority.

A servant leader helps people succeed rather than controlling every decision they make.

Scrum Master as a Servant Leader

A Scrum Master serves the Scrum Team, Product Owner and organization in different ways.

Coach Helps people improve their understanding and capabilities.
Facilitator Helps discussions and Scrum events achieve their purpose.
Teacher Helps people understand Scrum and effective ways of working.
Impediment Remover Helps the team address obstacles affecting progress.

Servant Leadership vs Command and Control

Command and Control
Servant Leadership
Manager makes most decisions.
Team is encouraged to make appropriate decisions.
Focuses on assigning work.
Focuses on enabling effective collaboration.
Measures compliance.
Encourages ownership and self-management.
Leader provides most solutions.
Leader helps people develop solutions.

Example

A Scrum Team repeatedly misses its Sprint Goal.

Command-and-control response:

"From now on, everyone must complete their assigned tasks by Wednesday."

Servant-leadership response:

"What is preventing us from achieving the Sprint Goal? What can we learn and change?"

Serve Without Becoming a Personal Assistant

Servant leadership does not mean doing every task the team asks the Scrum Master to perform.

The Scrum Master should help the team become capable of handling appropriate responsibilities itself.

Important:

Serving the team does not mean doing everything for the team.

How Can a Scrum Master Demonstrate Servant Leadership?

  • Listen before responding.
  • Help people understand problems.
  • Encourage self-management.
  • Remove organizational obstacles when needed.
  • Facilitate rather than dominate discussions.
  • Protect the team's ability to focus on its goals.
  • Help create an environment where problems can be discussed openly.

Servant Leadership Does Not Mean Weak Leadership

A servant leader can still challenge unhealthy behavior, address problems and have difficult conversations.

Being supportive does not mean avoiding accountability.

Example: Difficult Conversation

Two team members repeatedly interrupt each other during discussions.

A Scrum Master should not simply ignore the behavior in the name of being "servant-oriented."

The Scrum Master can address the behavior respectfully, facilitate a conversation and help the people involved find a healthier way to collaborate.

Signs of Good Servant Leadership

Team Ownership People increasingly solve problems themselves.
Open Communication Problems can be raised without fear.
Less Dependency The team does not need the Scrum Master for every decision.
Better Collaboration People work together rather than waiting for instructions.

Common Mistakes

Doing Everything The Scrum Master becomes the team's personal assistant.
Avoiding Difficult Conversations Problems are ignored to appear supportive.
Micromanaging The Scrum Master controls how Developers perform their work.
Creating Dependency The team cannot make decisions without the Scrum Master.

Useful Questions

Ownership "How can the team take ownership of this?"
Improvement "What could we do differently?"
Support "What support do you need?"
Learning "What can we learn from this?"

Key Takeaway

Servant leadership is about enabling people rather than controlling them.

A successful Scrum Master gradually helps the team become more capable, confident and self-managing.