Pre-reading for Session 1 · 5 minutes. These seven concepts anchor both sessions and serve as the foundational operating stance for the entire path.
All readings are original Helix Group intellectual property, informed by Scrum.org, Agile Alliance, and practitioner research. Read the Primer before Session 1. The remaining four before Session 2.
Servant leadership is one of the most frequently claimed and least frequently practiced orientations in Agile contexts. The claim is easy: say you serve the team, put the team first, remove impediments when asked. The practice is harder: it requires a specific set of behaviors that many practitioners know they should exhibit and consistently fail to prioritize when the organizational pressure runs the other direction.
The four behaviors that constitute servant leadership in Agile contexts are not attitudes — they are practices. Impediment removal means identifying and addressing the structural and political conditions that prevent the team from doing its best work, not just the immediate tactical blockers that appear in retrospectives. Condition creation means deliberately designing the organizational environment — the psychological safety, the information access, the protected time — that makes learning and experimentation possible. Organizational coaching means engaging with the leaders, stakeholders, and adjacent teams that constitute the system the team operates within, not just the team itself. Self-management development means every facilitation decision is evaluated against whether it builds the team’s capability or the team’s dependence.
Scrum’s accountability structure is explicit: the Scrum Master serves the Scrum Team by coaching the team members in self-management and cross-functionality, helping the Scrum Team focus on creating high-value Increments, removing impediments to the Scrum Team’s progress, and ensuring that all Scrum events take place and are positive, productive, and kept within the time-box. The Scrum Master serves the Product Owner by helping find techniques for effective Product Goal definition and Product Backlog management, helping the Scrum Team understand the need for clear and concise Product Backlog items, and helping establish empirical product planning for a complex environment. The Scrum Master serves the organization by leading, training, and coaching the organization in its Scrum adoption, planning and advising Scrum implementations within the organization, helping employees and stakeholders understand and enact an empirical approach, and removing barriers between stakeholders and Scrum Teams.
Most practitioners focus almost entirely on the first accountability set (serving the Scrum Team) and underinvest in the second (serving the Product Owner) and third (serving the organization). The practitioner whose effectiveness is bounded by the team boundary is fulfilling one third of the role. The practitioner who coaches the organization is the one who makes Agile adoption durable.
The servant leader cannot self-assess using intentions. The assessment is behavioral: what specific thing did I do in the last 30 days that built a team member’s capability? What specific organizational impediment — not a team-level blocker, but a structural or political condition — did I address? What specific conversation with a leader or stakeholder did I have that was not about the current Sprint but about the organizational conditions that either enable or constrain the team’s adaptive capacity? If the answers are vague, the practice is vague. The behavioral evidence requirement is not a judgment — it is the diagnostic instrument that distinguishes servant leadership as a practice from servant leadership as a self-concept.
In 2023, a Scrum Master at a mid-sized software company was, by any visible measure, indispensable. Her calendar was consistently full: daily standups facilitated, Sprint Planning run, backlog refinement organized, retrospective notes written and distributed, stakeholder updates drafted, impediments escalated. She was present in every team conversation of substance. The team spoke well of her. The delivery manager considered her one of the organization’s most effective Scrum Masters.
In March, she took two weeks of leave. In her absence, the team did not run a single ceremony independently. The daily standup was skipped on days when her co-facilitator was busy. The Sprint Planning was postponed until her return. Three impediments that the team had been aware of for the previous three weeks were not raised with anyone. The retrospective scheduled for week two was not held.
When the Scrum Master returned and reviewed what had happened, the pattern was clear: she had built a team that could not function without her. Every ceremony depended on her facilitation not because the team lacked the capability to run them, but because she had never stopped facilitating them long enough for the capability to develop. Every impediment was routed through her because she had established herself as the escalation point, and the team had learned that impediments raised outside of that channel went nowhere. The retrospective was not held because the team had never internalized the ownership of the retrospective as theirs.
The Scrum Master was not incompetent — she was effective at the wrong things. She had optimized for visible contribution (full calendar, active facilitation, detailed notes) rather than for the actual success criterion of the role: a team that could function independently. She had accumulated indispensability while believing she was building capability.
The Scrum Master spent the following quarter systematically handing back. She stopped facilitating the daily standup and coached one team member per Sprint to facilitate it instead. She ran the first ten minutes of Sprint Planning and then asked the team to continue without her, observing only. She drafted the retrospective agenda but handed facilitation to the team. She stopped being the first escalation point for impediments and instead coached the team member who raised each impediment to own its removal. At the end of the quarter, she took another two-week leave. Every ceremony ran. Every impediment was raised and tracked. The team noticed she was gone and continued anyway. That was the measure of success.
The Scrum.org and Agile Alliance anti-pattern literature identifies twenty recurring failure modes in Scrum Master practice. What makes the anti-pattern canon valuable is not that it names twenty problems but that it reveals the single underlying mechanism that produces all twenty: the practitioner has substituted visible activity for genuine influence. Every anti-pattern is a specific expression of that substitution.
The ticket taker. The Scrum Master who manages the team’s Jira board, tracks all tasks, and provides status updates to stakeholders has replaced the empirical transparency function of the Scrum artifacts with a personal reporting service. The team loses ownership of its own visibility. The Product Owner loses the ability to inspect the real state of the product. The stakeholders receive the Scrum Master’s interpretation of the team’s work rather than the Increment itself. The diagnostic: if the Scrum Master were unavailable, would stakeholders know what the team was working on? If not, the transparency infrastructure has been replaced by a person.
The process police. The Scrum Master who enforces Scrum rules rather than coaching the team to understand and internalize them has inverted the role. Process compliance produced by enforcement does not build the team’s adaptive capability — it builds the team’s compliance with the enforcer’s presence. The diagnostic: does the team follow the Scrum events and artifacts when the Scrum Master is not in the room? If compliance is contingent on presence, the coaching has not happened.
The absent-minded Scrum Master. The Scrum Master who attends ceremonies but is not genuinely engaged — checking email during retrospectives, answering Slack during Sprint Planning, multitasking during daily standups — models the exact behavior that produces low-quality ceremonies. The diagnostic: if the Scrum Master were filmed during the last three ceremonies, would the footage show someone whose full attention was on creating the conditions for quality conversation?
The schedule-driven facilitator. The Scrum Master who defines their success as running ceremonies on time and on schedule has optimized for the container rather than the content. A Sprint Review that runs exactly sixty minutes but produces no stakeholder inspection and no adaptation is a failure disguised as efficiency. The diagnostic: in the last three Sprint Reviews, what changed in the product’s direction as a result of what was inspected?
The team’s personal assistant. The Scrum Master who books all the meetings, manages all the logistics, and handles all the administrative coordination for the team has built a dependency on their operational support. When the Scrum Master is the person everyone goes to for scheduling, room booking, and tool access, the team has outsourced its organizational capability to a single person. The diagnostic: if the Scrum Master stopped booking meetings tomorrow, what would break?
Five anti-patterns are specifically about the Scrum Master’s organizational scope. The organizationally silent Scrum Master restricts their practice entirely to the team and never engages with the leaders, structures, and incentive systems that constitute the team’s organizational context. The impediment stacker maintains an impediment list that grows but never shrinks because the Scrum Master is escalating impediments to leadership rather than coaching their removal or structurally preventing their recurrence. The retrospective wallpaper producer facilitates retrospectives that generate action items posted to the wall and never actioned — the retrospective has become a ritual rather than an improvement mechanism. The velocity fetishizer uses velocity as a performance measure, reporting it to management as evidence of team productivity rather than coaching the team and stakeholders to understand it as a planning tool only. The Sprint scope defender treats the Sprint Backlog as a locked commitment rather than a living plan, protecting the Sprint from necessary changes and teaching the team that adaptation is a process violation rather than an empirical response.
The anti-pattern diagnostic is most useful when applied to specific recent behaviors rather than to general tendencies. For each of the twenty anti-patterns: name one specific instance in the last 30 days where you exhibited that behavior. Do not assess whether you “tend to” do it — assess whether you did it, specifically, recently. The anti-patterns that produce specific recent examples are the ones that require the coaching attention. The ones that feel safely abstract are the ones most worth examining for the self-protective blindspot they might represent.
The servant leadership behavioral inventory is a practical self-assessment designed to be completed daily rather than occasionally. Its premise: servant leadership is not what you believe about your role — it is what you do in your role, repeatedly, under the organizational conditions that most consistently tempt the anti-pattern. The inventory assesses six behaviors, each rated with a recent behavioral example rather than a general self-perception.
Behavior 1: Structural impediment removal. In the last 30 days, what structural or political impediment — not a team-level Sprint blocker, but a governance condition, funding constraint, stakeholder relationship, or organizational policy — did you address? What specifically did you do, and what changed as a result? If the answer is “nothing,” the impediment removal practice is operating exclusively at the team level and not at the organizational level where the most durable impediment work happens.
Behavior 2: Condition creation. What specific condition — time protection, information access, psychological safety, authority clarity — did you deliberately create in the last 30 days that made learning, experimentation, or genuine retrospection possible? Condition creation is distinct from facilitation: the facilitator runs the session; the condition creator designs the environment in which genuine sessions become possible.
Behavior 3: Organizational coaching. What conversation did you have in the last 30 days with someone outside your immediate team — a Product Owner, a department head, a stakeholder, a HR business partner — that was specifically about organizational conditions affecting Agile adoption? Not a status update, not a stakeholder management conversation, but a coaching conversation about how the organization operates.
Behavior 4: Self-management development. What specific facilitation or decision did you deliberately withhold in the last 30 days in order to create the space for a team member to develop a capability? Naming the specific instance is essential: “I generally try to coach rather than solve” is a self-concept, not a behavior.
Behavior 5: Anti-pattern recognition. Which of the 20 Scrum Master anti-patterns did you exhibit in the last 30 days, and in what specific situation? The inventory is most valuable here: the practitioner who cannot name a recent anti-pattern instance is either operating at a level of self-awareness that few practitioners achieve, or is applying the anti-pattern diagnoses to everyone except themselves.
Behavior 6: Make-yourself-unnecessary progress. What specific thing do you do today that you expect the team to be doing independently in 90 days? Name the capability, the team member most likely to develop it, and the first coaching step. If the answer is “nothing comes to mind,” the self-management development practice is aspirational rather than operational.
Rate each behavior 1–5 at the end of each week using the behavioral evidence from the week just completed. A rating of 5 requires a specific example from the current week. A rating of 3 requires a specific example from the current month. A rating of 1 or 2 is assigned when no specific example can be named. Track the pattern across four weeks: which behaviors consistently produce specific examples, and which consistently produce vague impressions? The vague impressions are the development priorities.
The most counterintuitive idea in servant leadership is the one that most clearly distinguishes it from every other leadership model: the measure of your success is your dispensability. Traditional leadership models produce leaders whose value is proportional to their necessity — the more the organization depends on them, the more they are rewarded. Servant leadership in Agile contexts inverts this: the practitioner’s value is proportional to the capability they have built in the people around them, not the capability they continue to provide directly.
This inversion has practical consequences that practitioners frequently resist. A Scrum Master who has successfully coached their team toward genuine self-management has, by definition, reduced the team’s need for facilitation, coaching, and impediment removal from that Scrum Master specifically. The team can run its own ceremonies, surface its own impediments, and hold itself accountable to its own commitments. From a traditional performance management perspective, the Scrum Master who achieves this outcome appears to have reduced their own contribution — the team no longer visibly needs them. From the servant leadership perspective, this is the highest-value outcome the role can produce.
The organizational implication: mature servant leaders do not accumulate team dependencies — they accumulate organizational impact. The practitioner who has coached one team toward self-management can bring that coaching capability to the organizational level: working with leaders, structures, and culture rather than with daily standups and Sprint Planning. The teams that have been coached well do not need a Scrum Master in every ceremony; they need a practitioner who is addressing the organizational conditions that will constrain their self-management capability over time.
The question every servant leader should be asking at the end of each Sprint: what did the team do this Sprint that they could not have done without me six months ago? And what am I still doing that I should be coaching the team to do without me six months from now? The first question measures development delivered. The second measures development still owed. The ratio between the two is the most honest assessment of servant leadership progress available.
Session 1 is reading discussion using the Primer and key takeaways. Session 2 is the anti-pattern diagnostic activity plus the behavioral inventory debrief. The Quest is launched at the end of Session 2.
A 50-minute group activity in which practitioners apply the behavioral inventory to themselves, receive paired anti-pattern feedback, and commit to one specific practice experiment for the next 30 days. The commitments become the Quest baseline.
Rate yourself 1–5 on each of the six servant leadership behaviors using behavioral evidence only. A rating is only valid if you can name a specific example from the last 30 days. If you cannot name a specific example, the rating is 1 or 2.
The behavioral evidence requirement is the antidote to aspiration-based self-assessment. The most important facilitation move in this exercise is the gentle refusal to accept general self-perceptions as evidence. When a participant rates themselves 4 on organizational coaching and then cannot name a specific recent conversation with someone outside their team, the honest rating is 2. This is not a judgment — it is a diagnostic. The participants who discover the largest gap between their self-perception and their behavioral evidence are the ones who will learn the most from this path.
Share your three highest-risk anti-patterns with your partner. For each anti-pattern: your partner asks “what is the servant leadership alternative in that same situation?” The answer must be a specific behavior, not a general principle.
The most valuable moment in this exercise is when a participant hears an anti-pattern observation from their partner that they had not recognized in themselves. The facilitator’s role is to ensure the conversation stays behavioral (what did you observe?) rather than evaluative (what do you think of it?). If a pair gets stuck on designing the specific alternative behavior, the coaching question is: “What would a servant leader do in that situation that would leave the team more capable after the interaction than before it?”
Each person shares their practice commitment in the format: “In [situation type], instead of [anti-pattern behavior], I will [servant leader alternative]. My accountability partner is [name]. We will check in at [date].”
Ask questions about servant leadership, the 20 anti-patterns, or how to apply this module’s concepts to your specific practice context. The coach knows this module and the full Agile Practitioner Uplift path.
Tools for session preparation and in-session support. Generate a customized session guide, fresh discussion questions, a post-session debrief summary, or a Quest nudge message. Each tool accepts cohort context to personalize the output.