Servant Leadership Styles – Developing People and Teams (PSM II)
Introduction to Servant Leadership and Leadership Styles
Servant Leadership is a cornerstone philosophy within the Scrum framework, particularly for the Scrum Master role. Understanding servant leadership styles is essential for the PSM II exam because it reflects how a Scrum Master enables teams to thrive, grow, and deliver value. This guide covers why servant leadership matters, what it entails, how it works in practice, and how to confidently answer exam questions on this topic.
Why Servant Leadership Is Important
Servant leadership is important because it fundamentally shifts the leadership paradigm from command-and-control to empowerment and service. Here is why it matters:
• Empowers Self-Organization: Scrum teams are designed to be self-managing. A servant leader creates the conditions for teams to make their own decisions, solve their own problems, and continuously improve.
• Builds Trust: When a leader serves the team rather than directing it, trust flourishes. Trust is the foundation for psychological safety, which enables open communication, experimentation, and learning from failure.
• Maximizes Value Delivery: By removing impediments, coaching team members, and shielding the team from distractions, a servant leader ensures the team can focus on delivering the highest possible value.
• Develops People: Servant leadership prioritizes the growth and well-being of individuals. A Scrum Master who practices servant leadership helps team members develop new skills, take on challenges, and reach their potential.
• Supports Organizational Agility: Servant leadership extends beyond the team. By coaching the organization, the Scrum Master helps leaders, stakeholders, and other teams adopt agile values and principles.
What Is Servant Leadership?
Servant leadership is a leadership philosophy and set of practices where the leader's primary goal is to serve others. The concept was originally coined by Robert K. Greenleaf in 1970. In the context of Scrum, the Scrum Master is described as a servant leader for the Scrum Team.
Key characteristics of a servant leader include:
• Listening: Deeply and actively listening to team members, stakeholders, and the organization to understand needs, concerns, and aspirations.
• Empathy: Striving to understand and share the feelings of others, accepting people as they are while helping them grow.
• Healing: Helping people and teams recover from conflicts, setbacks, or dysfunctions by creating a safe and supportive environment.
• Awareness: Being self-aware and situationally aware, understanding the dynamics of the team, organization, and broader system.
• Persuasion: Influencing others through persuasion rather than authority. A servant leader convinces rather than coerces.
• Conceptualization: Thinking beyond day-to-day operations to envision the broader purpose and long-term goals.
• Foresight: Anticipating the likely outcomes of situations based on past experience, current realities, and future trends.
• Stewardship: Holding the team, organization, and Scrum values in trust for the greater good.
• Commitment to the Growth of People: Investing in the personal and professional development of every team member.
• Building Community: Fostering a sense of belonging, collaboration, and shared purpose within and across teams.
Understanding Leadership Styles in the Context of Scrum
While servant leadership is the foundational style for a Scrum Master, it is important to understand that effective leadership is situational. A mature Scrum Master adapts their approach based on the team's maturity, the situation, and the individuals involved. Here are key leadership styles relevant to PSM II:
• Teaching: When team members lack knowledge about Scrum, agile practices, or technical skills, the Scrum Master may adopt a teaching stance, providing information and explaining concepts.
• Mentoring: When individuals need guidance based on experience, the Scrum Master mentors by sharing insights, offering advice, and helping people navigate challenges based on their own experience.
• Coaching: When team members have the capability but need help unlocking their own solutions, the Scrum Master uses powerful questions, active listening, and reflection to help them discover answers themselves. Coaching is a core servant leadership skill.
• Facilitating: When the team needs to collaborate, make decisions, or resolve conflicts, the Scrum Master facilitates by creating a neutral space, guiding the process without dictating outcomes, and ensuring all voices are heard.
• Removing Impediments: Sometimes the Scrum Master must take direct action to remove organizational or systemic barriers that the team cannot resolve on its own.
• Leading by Example: Demonstrating Scrum values (commitment, courage, focus, openness, and respect) through personal behavior sets the tone for the team.
How Servant Leadership Works in Practice
In practice, a Scrum Master using servant leadership might:
1. Start with the Team's Needs: Rather than imposing an agenda, the Scrum Master asks the team what they need to be more effective. This might happen during Sprint Retrospectives, one-on-one conversations, or informal check-ins.
2. Adapt the Leadership Stance: If a team is newly formed and unfamiliar with Scrum, the Scrum Master may spend more time teaching and mentoring. As the team matures, the Scrum Master shifts toward coaching and facilitating, empowering the team to take ownership.
3. Create Safety for Experimentation: The servant leader encourages the team to try new approaches, even if they might fail. They protect the team from blame and help them learn from outcomes.
4. Challenge the Status Quo: Servant leadership is not passive. A Scrum Master challenges the team and the organization when behaviors or practices conflict with Scrum values and agile principles. This requires courage and persuasion.
5. Serve the Product Owner: The Scrum Master helps the Product Owner with stakeholder management, Product Backlog refinement techniques, and understanding empiricism.
6. Serve the Organization: The Scrum Master coaches the broader organization on agile adoption, helps remove systemic impediments, and advocates for changes that support agility.
7. Focus on Long-Term Growth: Rather than solving every problem for the team, the servant leader invests in building the team's capability to solve problems independently.
Common Misconceptions About Servant Leadership
• Misconception: Servant leaders are passive or weak. Reality: Servant leaders are courageous. They challenge teams, hold people accountable to Scrum values, and advocate for change even when it is uncomfortable.
• Misconception: The Scrum Master does whatever the team asks. Reality: Serving the team does not mean being subservient. A servant leader serves the team's needs, which may differ from their wants. Sometimes this means having difficult conversations or refusing to shield the team from necessary feedback.
• Misconception: Servant leadership means no authority. Reality: A servant leader uses influence, persuasion, and moral authority rather than positional authority. They have the authority of the Scrum framework and use it to ensure Scrum is understood and enacted.
• Misconception: One leadership style fits all situations. Reality: The best Scrum Masters are situational leaders who adapt their stance (teaching, coaching, mentoring, facilitating) based on context, team maturity, and individual needs.
Exam Tips: Answering Questions on Servant Leadership and Leadership Styles
The PSM II exam tests deep understanding and application of Scrum principles, including servant leadership. Here are detailed tips for answering these questions correctly:
1. Always Prioritize Empowerment Over Direction
When you see an answer choice where the Scrum Master tells the team what to do, directs their work, or makes decisions for them, this is almost always incorrect. The correct answer will involve the Scrum Master enabling the team to find their own solutions. Look for answers that include coaching, asking powerful questions, or facilitating discussions.
2. Understand the Difference Between Coaching, Mentoring, Teaching, and Facilitating
The exam may present scenarios where you need to determine the most appropriate leadership stance. Ask yourself: Does the team need knowledge (teaching)? Experience-based guidance (mentoring)? Help discovering their own answers (coaching)? Or a structured process for collaboration (facilitating)? Choose the answer that matches the situation.
3. Remember That Servant Leadership Requires Courage
Some questions will test whether you understand that a servant leader must sometimes have uncomfortable conversations, challenge organizational norms, or push back against stakeholders. Answers that avoid conflict or defer to authority figures are often incorrect. Look for answers where the Scrum Master acts with courage while remaining respectful.
4. Consider Who Is Being Served
The Scrum Master serves the Scrum Team, the Product Owner, and the organization. Some questions will test whether you understand that servant leadership extends beyond just the Development Team. If the scenario involves organizational impediments, the correct answer often involves the Scrum Master coaching the organization or escalating systemic issues.
5. Watch for Answers That Protect Team Self-Management
If a question scenario describes a manager, stakeholder, or Product Owner trying to tell the Developers how to do their work, the correct answer will typically involve the Scrum Master protecting the team's self-management while educating the interfering party about Scrum roles and responsibilities.
6. Look for Long-Term Solutions Over Quick Fixes
Servant leadership focuses on developing people and building capability. If one answer provides a quick fix (e.g., the Scrum Master solves the problem) and another develops the team's ability to handle similar situations in the future (e.g., coaching the team to solve it themselves), the latter is usually the better answer.
7. Understand That Servant Leadership Is Not About Being Liked
Some answer choices may describe a Scrum Master who avoids confrontation, agrees with everyone, or prioritizes harmony over effectiveness. These are traps. True servant leadership involves serving the team's actual needs, which sometimes means challenging them, holding them accountable, and making them uncomfortable in the service of growth.
8. Connect Servant Leadership to Scrum Values
The five Scrum values — Commitment, Courage, Focus, Openness, and Respect — are deeply connected to servant leadership. When evaluating answers, consider which option best embodies these values. The correct answer typically reflects openness (transparency), courage (addressing hard truths), and respect (valuing each person).
9. Recognize Situational Leadership Scenarios
The exam may present scenarios where a team is at different stages of maturity. A newly formed team may need more guidance and structure (teaching/mentoring), while a mature, high-performing team benefits most from coaching and facilitation. Choose the answer that matches the team's current state.
10. Eliminate Command-and-Control Answers
Any answer that suggests the Scrum Master assigns tasks, approves work, makes technical decisions, dictates process, or acts as a project manager is almost certainly wrong. These reflect a command-and-control style that contradicts servant leadership.
11. Pay Attention to the Wording of Questions
PSM II questions are often nuanced. Words like best, most appropriate, and first thing matter. Multiple answers might seem partially correct, but the best answer will align with servant leadership principles: empowering others, building capability, fostering self-management, and serving the team's genuine needs.
12. Practice Scenario-Based Thinking
PSM II is heavily scenario-based. For each question, put yourself in the Scrum Master's shoes and ask: What would a servant leader do here? What response serves the long-term growth of the team and organization? What aligns with Scrum theory and values?
Summary
Servant leadership is not just a nice-to-have — it is the defining leadership philosophy for a Scrum Master. It involves listening, empathizing, coaching, challenging, and empowering others. A great Scrum Master adapts their leadership style based on context while always grounding their actions in the principle of service. For the PSM II exam, remember that the best answers reflect empowerment over control, long-term growth over short-term fixes, courage over avoidance, and self-management over dependency. Master these principles, and you will be well-prepared to answer any question on servant leadership and leadership styles.
