3.1 Core Enabling Stances: Servant Leader & Manager
Key Takeaways
Servant leadership, originated by Robert K. Greenleaf, prioritizes the growth, autonomy, and well-being of people over command-and-control authority.
The Scrum Master acts as a servant leader across three distinct tiers: serving the Scrum Team, serving the Product Owner, and serving the wider organization.
Scrum Masters actively manage boundaries, empirical processes, organizational impediments, and environmental conditions without managing people or assigning tasks.
Leading without positional authority requires cultivating professional credibility, empathy, consistency, and transparent alignment with Scrum values.
In advanced PSM II scenarios, any action where the Scrum Master unilaterally directs solutions or dictates task execution undermines team self-management.
3.1 Core Enabling Stances: Servant Leader & Manager
The Professional Scrum Master II (PSM II) assessment marks a deliberate departure from foundational framework mechanics. While introductory certifications validate familiarity with events, artifacts, and accountabilities, the advanced practitioner is evaluated on situational judgment, interpersonal agility, and systemic impact. At the center of this advanced competency is the practitioner's ability to navigate the multi-dimensional stances of the Scrum Master. Originally conceptualized in agile literature by Barry Overeem and embraced by Scrum.org, these stances define the repertoire of behavioral roles a Scrum Master adopts to cultivate high-performing, self-managing teams and agile organizations.
Two stances serve as the core enablers of the entire framework: the Servant Leader and the Manager. Far from being contradictory, these two stances work in tandem to establish the psychological foundation and operational boundaries necessary for empirical process control.
The Philosophy of Servant Leadership: Robert K. Greenleaf's Paradigm
The concept of servant leadership was first articulated by Robert K. Greenleaf in his seminal 1970 essay, The Servant as Leader. Greenleaf proposed a profound inversion of traditional industrial hierarchies: leadership is not a privilege of rank, positional entitlement, or top-down coercion, but an act of service dedicated to empowering others.
Greenleaf articulated the fundamental criterion of servant leadership through his famous test:
"Do those served grow as persons? Do they, while being served, become healthier, wiser, freer, more autonomous, more likely themselves to become servants? And, what is the effect on the least privileged in society; will they benefit, or, at least, not be further deprived?"
In complex product development, traditional command-and-control leadership fails because no single individual possesses complete knowledge of the problem space, technological landscape, or market dynamics. When leaders impose directives, micro-manage tasks, or enforce compliance through fear, they suppress collective intelligence, undermine psychological safety, and destroy self-management. Servant leadership counters this dysfunction by shifting the leader's focus from directing people to cultivating an environment where cross-functional professionals can self-organize, innovate, and make empirical decisions.
Core Characteristics of Servant Leadership in Scrum
- Empowerment Over Control: Distributing authority to the people closest to the technical and business problem rather than concentrating it at the top.
- Active Listening and Empathy: Seeking first to understand the perspectives, frustrations, and motivations of team members and stakeholders before offering guidance.
- Stewardship: Holding resources, team well-being, and organizational trust in stewardship for the long-term benefit of the product and people.
- Commitment to Growth: Measuring success not by personal prestige or output metrics, but by the increasing autonomy and capability of the team.
The Scrum Master as Servant Leader: Three Levels of Service
The 2020 Scrum Guide formalizes this philosophy by stating: "The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide... Scrum Masters are true leaders who serve the Scrum Team and the larger organization." This service manifests across three distinct, interconnected levels.
1. Serving the Scrum Team
Within the team boundary, the Scrum Master fosters self-management and cross-functionality. Rather than solving problems on behalf of Developers or dictating how work should be decomposed, the Scrum Master:
- Coaches Developers in self-organization, peer accountability, and technical excellence.
- Helps the team establish and uphold ambitious quality standards through the Definition of Done.
- Identifies and neutralizes internal relational frictions, protecting psychological safety.
- Holds an objective mirror up to the team during Sprint Retrospectives so they can inspect their interactions, processes, and tools without bias.
2. Serving the Product Owner
The relationship between the Scrum Master and the Product Owner is a collaborative partnership built on mutual respect and shared accountability for value. The Scrum Master serves the Product Owner by:
- Guiding techniques for effective Product Goal definition and empirical Product Backlog management.
- Facilitating collaborative backlog refinement sessions so that backlog items are clear, concise, and value-focused.
- Assisting the Product Owner in understanding and practicing empirical product planning in complex, unpredictable environments.
- Protecting the Product Owner from organizational pressures to treat the backlog as a fixed-scope, fixed-date project management gantt chart.
3. Serving the Wider Organization
A Scrum Master whose influence stops at the team perimeter is severely constrained. Organizational dysfunctions—such as siloed departments, misaligned governance, and traditional performance appraisals—inevitably press against the Scrum Team. The Scrum Master serves the wider organization by:
- Leading, training, and coaching leadership and stakeholders in adopting empirical thinking.
- Planning and advising on agile implementations across interdependent departments.
- Helping employees and external stakeholders understand and enact empirical product development.
- Removing systemic organizational impediments that block value flow across value streams.
| Level of Service | Primary Focus | Typical Scrum Master Actions | Anti-Pattern to Avoid |
|---|---|---|---|
| The Scrum Team | Self-management & Quality | Coaching Developers to resolve their own technical disagreements; holding the mirror in Retrospectives. | Directing architectural decisions or distributing work tasks. |
| The Product Owner | Value Delivery & Backlog Health | Introducing story mapping, user journey slicing, and empirical hypothesis framing. | Prioritizing backlog items or acting as a proxy Product Owner. |
| The Organization | Cultural & Systemic Agility | Engaging HR and Finance to align policies with agility; removing cross-departmental bottlenecks. | Isolating the team in an agile bubble while ignoring organizational friction. |
The Manager Stance: Debunking the Myth That "Scrum Masters Do Not Manage"
A persistent, damaging misconception in the agile community is that "Scrum Masters do not manage." In his foundational whitepaper The 8 Stances of a Scrum Master, Barry Overeem addresses this myth directly. While Scrum Masters do not manage people, tasks, or performance reviews in the classical sense, they are active, authoritative managers of the agile framework, its boundaries, and the enabling environment.
If a Scrum Master abdicates all managerial responsibility, the team is left vulnerable to organizational chaos, creeping scope, unmanaged impediments, and progressive framework erosion. A Scrum Master manages purposefully and transparently—not by wielding administrative power over individuals, but by stewarding the systemic conditions for success.
What Does a Scrum Master Manage?
Overeem's white paper lists five things a Scrum Master manages (he credits Gunther Verheyen's essay on the Scrum Master as a manager as inspiration):
- Managing impediments and eliminating waste: Removing impediments that limit the progress of the Developers in areas beyond the reach of their self-management, and stripping out waste in the process.
- Managing the process: Supporting the team in optimizing its process, facilitating, keeping Scrum events purposeful and effective, and ensuring people, teams, and the organization realize the benefits of Scrum.
- Managing the team's health: Creating a trusting environment with quality interactions between team members and supporting the team in achieving its objectives.
- Managing the boundaries of self-organization (self-management): Guarding the boundaries Scrum provides—timeboxes to limit risk, focused effort, cross-functional collaboration, releasable results, and validated learning.
- Managing the culture: Making room for failure and managing the cultural change the organization needs so that teams can flourish.
Continuous improvement runs through all five. Note the 2020 Scrum Guide's wording on Retrospective outcomes: the most impactful improvements are addressed as soon as possible and "may even be added to the Sprint Backlog for the next Sprint." Adding them is a strong practice, not a mandatory rule (the 2017 Guide's requirement to include at least one improvement in the next Sprint Backlog was removed in 2020).
| Management Dimension | Traditional Command-and-Control Manager | Scrum Master (Manager Stance) |
|---|---|---|
| Focus of Authority | Direct authority over people, job roles, and career advancement | Authority over the empirical process, Scrum boundaries, and enabling environment |
| Work Allocation | Assigns tasks, dictates schedules, and sets individual deadlines | Empowers Developers to pull work and forecast their own Sprint capacity |
| Problem Resolution | Decides solutions unilaterally and instructs subordinates to execute | Facilitates problem exploration, coaches root cause discovery, and removes systemic blockers |
| Performance Metric | Individual task completion, resource utilization rates, and hours worked | Delivery of valuable, usable Increments that satisfy the Definition of Done |
| Accountability Style | Enforces compliance through hierarchical status reporting | Fosters peer accountability, transparent inspection, and team ownership |
Leading Without Positional Authority: The Currency of Influence
Perhaps the greatest challenge tested on the PSM II assessment is the Scrum Master's lack of positional authority. A Scrum Master cannot fire a recalcitrant stakeholder, issue disciplinary warnings to disengaged team members, or mandate that an engineering director change enterprise architecture standards. Operating without hierarchical power requires mastery of non-authoritarian leadership.
True leadership influence is cultivated through four foundational pillars:
- Professional Competence and Domain Insight: Demonstrating profound mastery of empirical principles, systems thinking, and product development dynamics. When a Scrum Master articulates why a practice damages flow using concrete empirical evidence, stakeholders listen.
- Empathy and Perspective-Taking: Understanding the legitimate fears and pressures experienced by traditional managers, stressed Product Owners, and overworked Developers. Empathy builds bridges where dogmatic lecturing creates defensiveness.
- Radical Consistency and Integrity: Modeling the five Scrum Values—Commitment, Courage, Focus, Openness, and Respect—consistently, especially during organizational crises. When pressure mounts to compromise quality or falsify status reports, the Scrum Master courageously defends transparency.
- Alignment with Shared Goals: Framing every agile intervention around shared organizational objectives—such as time-to-market, customer retention, defect reduction, and product value—rather than ideological purity.
When navigating complex PSM II scenario questions, remember that the Scrum Master never issues orders, never punishes, and never assumes ownership of decisions that belong to the Developers or Product Owner. Instead, the Scrum Master manages the empirical process, holds stakeholders accountable to their commitments, and leads through collaborative service.
A newly hired Scrum Master tells the team, 'Scrum Masters are servant leaders, so I don't manage anything—management is what we left behind.' A month later, Retrospective actions are never followed up, the team is visibly exhausted, and other departments routinely bypass the Product Owner. Which statement best reflects Barry Overeem's Manager stance?
The Scrum Master should manage the people on the team, including assigning work and running their performance reviews, because servant leadership alone has clearly failed here.
The Scrum Master manages impediments and waste, the process, the team's health, the boundaries of self-organization, and the culture—never the people or their tasks.
The Scrum Master should hand all management duties to the Product Owner, who is accountable for maximizing the value of the work of the Scrum Team.
Management in Scrum belongs only to the Developers, who manage their own work, so the Scrum Master's role is limited to booking Scrum events and keeping the Sprint board up to date.
A functional department manager repeatedly approaches Developers directly during the Sprint, assigning them 'urgent production fixes' that bypass the Product Backlog. This causes constant context switching and threatens the Sprint Goal. What should the Scrum Master do in the Manager stance?
Permit the Developers to absorb the urgent requests if they have spare capacity, provided they record the spent hours in the company's ticketing software so the work stays visible to management.
Meet the manager to explain how side-door work undermines forecasting and value, and route every request through the Product Owner.
Confront the functional manager publicly during the Daily Scrum to enforce framework rules and demonstrate zero tolerance for boundary violations.
Instruct the Developers to ignore all communications from the functional manager and report any future infractions directly to the human resources department for formal follow-up.
A Product Owner is overwhelmed by dozens of aggressive stakeholders, each insisting their feature request is top priority. The Product Owner begins accepting all requests, resulting in a bloated, fragmented Product Backlog with no coherent direction. How can the Scrum Master best serve the Product Owner in this situation?
Take over ownership of the Product Backlog temporarily, reprioritizing items based on technical dependencies until the Product Owner regains control of the stakeholders.
Direct the stakeholders to submit their requests directly to the Developers during the Sprint Review rather than contacting the Product Owner.
Coach the Product Owner to define a clear Product Goal and to order the Product Backlog by value, and offer to facilitate stakeholder alignment workshops that help the Product Owner say no.
Appoint an assistant Product Owner from the development team to manage stakeholder communications and approve incoming requirements on the Product Owner's behalf.
Sections you finish are checked off in the contents.