The Servant Who Leads
How Prosocial Behavior & Servant Leadership Unlock the True Potential of Agile Teams
Introduction: When Agile Fails, It’s probably a People Problem
If you were to ask any seasoned Scrum Master about a time when they experienced a failed Agile transformation, they would remark in the post-mortem that rarely is there any blame on the framework. The ceremonies were followed, the backlog was groomed, the sprints were time-boxed but the team never quite came together. Progress stalled retrospectives grew tense, and collaboration became more transactional. All the tools were right but the people dynamic was not. So what happened?
This experience is more common than practitioners like to think or admit. Agile frameworks like Scrum, Kanban, and SAFe provide excellent structure for the iterative process of delivery, however they do not automatically produce the human behaviors that make the best high-performing teams possible. And perhaps most importantly they do not guarantee prosocial behavior or the disposition to act in ways that benefit others, build trust, share knowledge, and check their individual ego in order to benefit the team.
Prosocial behavior is not a soft, optional add-on to Agile rather it is a foundational requirement. The most powerful incentive for prosocial behavior in Agile environments is supportive and consistent servant leadership. When Scrum Masters and Agile leads genuinely embody servant leadership principles and practices, they have the opportunity to create prime conditions where prosocial behavior can flourish, and where Agile can deliver results effectively.
Part 1: Understanding Prosocial Behavior in a Team Context
What Do We Mean by Prosocial Behavior?
Prosocial behavior, as defined in organizational psychology, encompasses three interrelated concepts.
Types of Prosocial Behavior
Altruism: Helping others with no expectation of reciprocation.
Reciprocal altruism: Helping others with the expectation that the favor may be returned.
Cooperation: Working together toward shared goals.
In a team setting, prosocial behavior shows up as spontaneous helping, voluntary knowledge sharing, covering for a teammate under pressure, speaking up constructively in retrospectives, and mentoring without being asked.
An engineer who writes clean, well-documented code because the team agreed to standards is following norms. But an engineer who pauses their own sprint work to help a struggling colleague debug a problem without being asked, or without it counting toward their deliverables is acting prosocially. The distinction matters because Agile’s iterative, self-organizing model depends on the latter. It is always people over process.
What the Research Shows
Teams that demonstrate high levels of citizenship and prosocial behavior consistently outperformed peers on productivity, efficiency, and customer satisfaction. Research specifically on Agile teams with strong norms of psychological safety and mutual support demonstrate higher sprint predictability, lower defect rates, and better retrospective outcomes. These findings are not surprising when you consider what Agile actually requires.
Self-organization assumes team members will step up, fill gaps, and share context without being directed to.
Cross-functionality assumes people will learn outside their comfort zones and teach what they know.
Continuous improvement assumes individuals will be honest about failure and generous with insight. Every one of these behaviors is prosocial.
Part 2: Servant Leadership as the Architecture of Prosocial Culture
The Servant Leader Defined - A Rising Tide Lifts All Boats
The concept of servant leadership, introduced by Robert Greenleaf in the 1970s, inverts the traditional leadership hierarchy. Rather than leading from the top down, the servant leader places themselves in service of those they lead by removing obstacles, developing capabilities, sharing power, and prioritizing growth and wellbeing of the team over personal status or authority. This philosophy found a home in Agile, where the Scrum Guide describes the Scrum Master role through the lens of servant leadership.
“The servant-leader is servant first… It begins with the natural feeling that one wants to serve, to serve first.”
- Robert K. Greenleaf
But servant leadership in Agile is more than a role description. It is a behavioral choice that, when authentically practiced, can fundamentally reshape team culture. A servant leader, in an Agile context, actively models those prosocial behaviors they wish to see and by doing so, can create the psychological and structural environment for others to do the same.
How Servant Leadership Produces Prosocial Teams
Research on servant leadership in project-based organizations consistently shows its positive relationship with organizational citizenship behaviors which are, the voluntary, prosocial acts that go beyond formal job requirements. Servant leaders create prosocial cultures by demonstrating the following:
Psychological Safety: By demonstrating consistently that it is safe to take risks, admit mistakes, and disagree respectfully and in this way servant leaders remove the fear that might stop spontaneous prosocial behavior. When your team members trust that helping a colleague will not be penalized or exploited, they will help. When they trust that speaking up in a retrospective will be valued rather than judged, they will speak up.
Role Modeling: Servant leaders who consistently put team needs over personal recognition signal that prosocial behavior is expected, valued and rewarded. The behavior of the leader sends this message and the setting of this norm in teams has been well documented. The leader sets the tone.
Removing Friction: A servant leader who shields their team from organizational bureaucracy, clears blocks, and advocates for resources is enabling team members to focus their energy in each other rather than in navigating obstacles. This is prosocial infrastructure.
Coaching for Growth: Servant leaders invest in the individual development of their team members, which can build both commitment and the capability of the individual. Research confirms prosocial motivation by modeling can strengthen commitment to the team and to the organization. Managerial support is the key factor.
The Scrum Master is the Prosocial Architect
The Scrum Master occupies the unique position in Agile teams. Unlike a traditional project manager, the Scrum Master has no formal authority over team members. Their influence is entirely relational and cultural. This makes the role a study in servant leadership rather than hierarchical ones.
An truly effective Scrum Master does not tell a developer to help a struggling teammate rather they create the team norms, the sprint rituals, and the interpersonal trust and a safe non judgemental environment that make such help feel natural. They do not force transparency they model vulnerability and openness until transparency becomes the team’s default. They don’t mandate continuous improvement but they cultivate the psychological safety and retrospective culture that makes genuine reflection possible and safe and continuous improvement follows naturally.
The Scrum Master’s primary deliverable is not sprint velocity or burndown charts. It is a prosocially capable team where the members choose to act in service of each other and their shared mission, not because they are required to, but because the culture makes it the obvious thing to do for the team.
Part 3: Prosocial Behavior in Practice — Real Agile Scenarios
Sprint Planning: Generosity with Capacity
One of the most revealing moments for prosocial behavior in Agile is sprint planning. Watch how a team handles an uneven workload. Do senior engineers volunteer to take on less glamorous work items so that juniors get growth opportunities? Does someone flag that a colleague’s estimate seems too optimistic and offer support preemptively? Does the team collectively rebalance the sprint when one member reveals a personal constraint? These acts of planning generosity are all great examples of prosocial behavior. Servant leaders can facilitate this by making the team’s collective outcome the measure of success, and by celebrating collaborative behaviors during sprint reviews.
Daily Standups: The Prosocial Signal
The daily standup, limited to fifteen minutes, is one of Agile’s most misunderstood rituals. In low-trust teams, it devolves into a status report to management — each person defending their progress and minimizing impediments. In prosocially oriented teams, the standup becomes a brief but genuine daily offer: ‘I am here, I see what you are working on, and I am available if you need me.’
This shift is cultural, not procedural. The servant leader Scrum Master cultivates it by asking questions in standups that orient the team toward each other rather than toward the board “Does anyone see a risk to what Jackie is building?’ or ‘Who might be able to unblock Marco today?’ These small linguistic moves signal that the standup is a collective check-in, not an individual performance review.
Retrospectives: Prosocial Honesty
Retrospectives are Agile’s most powerful improvement mechanism — and the one most dependent on prosocial behavior. A team that lacks psychological safety will produce polite, superficial retrospectives. Real retrospectives require members to give honest feedback about process failures, team dynamics, and individual behaviors, delivered in a spirit of genuine care rather than blame.
The servant leader Scrum Master creates the conditions for prosocial honesty by: consistently framing retrospectives as learning exercises rather than performance reviews; modeling self-disclosure by sharing their own missteps as a facilitator; and following up systematically on action items to demonstrate that honesty leads to improvement, not just exposure.
Cross-Team Knowledge Sharing
In scaled Agile environments, one of the most impactful prosocial behaviors is voluntary cross-team knowledge transfer. Engineers who document their architectural decisions for other teams, designers who share user research findings proactively, and product owners who maintain a shared terminology guide are all acting prosocially. They are investing time and effort that will benefit others with no immediate personal return.
Research on social sustainability in large-scale Agile implementations identified trust, clear communication, and a culture of learning as critical success factors. These are the behavioral fruits of prosocial culture, and they are the specific outputs that servant leaders must tend to in scaled environments. A Community of Practice facilitated by servant-led Scrum Masters is a structural prosocial mechanism that institutionalizes knowledge generosity.
Part 4: Actionable Recommendations for Scrum Masters and Agile Leads
1. Audit Your Team’s Prosocial Health
Before you can strengthen prosocial culture, you need to assess where your team currently stands. Consider these questions:
In the last three sprints, did anyone voluntarily help a teammate outside their assigned work?
Do team members share impediments proactively, or do they hide problems to protect their metrics?
Are retrospectives generating genuine behavioral change, or cycling through the same surface-level observations?
Does the team celebrate collaborative wins, or only individual technical achievements?
If the answers you find are concerning, do not reach for a new ceremony or a new tool. Consider using the relational and cultural levers that servant leadership provides.
2. Make Service Visible Through Your Own Behavior
The most powerful intervention available to a Scrum Master is their own behavior. If you want your team to act prosocially, act prosocially yourself and make it consistent and visible. This means:
Taking on administrative burden to protect team focus time
Publicly crediting team members for ideas and solutions
Following up on blocked colleagues before being asked
Admitting your own facilitation failures in retrospectives
Advocating loudly for team wellbeing with organizational stakeholders
Servant leaders do not demand prosocial behavior from teams, they demonstrate it until teams internalize it as the local norm.
3. Redesign Your Ceremonies Around Prosocial Intent
Every Agile ceremony can be reoriented around prosocial purpose. Practically, this means:
Sprint Planning: Add an explicit question: Who might need support this sprint?” And let the team self-organize around the answer
Daily Standup: Replace the three traditional questions with team-oriented alternatives: “What am I contributing today? What am I struggling with? Who can I help?”
Sprint Review: Showcase team collaboration stories, not just feature demos Highlight moments of mutual support
Retrospective: Open with a gratitude round where each team member names one prosocial act they witnessed from a colleague in that sprint
4. Build Psychological Safety Systematically
Psychological safety is not built through a single team-building exercise. It is built through hundreds of small, consistent interactions in which the servant leader demonstrates that the team environment is safe for honesty, risk-taking, and vulnerability. Specific practices include:
Respond to mistakes with curiosity rather than blame, “What did we learn?” rather than “What went wrong?”
Actively solicit dissenting views in sprint planning and design discussions
When someone raises an uncomfortable truth in a retrospective, visibly protect and reward their honesty
Create explicit space for junior team members to speak before seniors in discussions and this prevents dominant voices from crowding out prosocial contributions
5. Measure What Matters — Including the Human Dimension
Most Agile metrics measure output: velocity, cycle time, defect rate. Few measure the prosocial health of the team. Consider tracking:
Frequency of unassigned help during sprints (peer-reported)
Cross-functional collaboration events per sprint
Team morale and psychological safety through regular pulse surveys
Quality and depth of retrospective action items over time
What gets measured gets valued. If you never ask about prosocial behavior, the team will correctly conclude it is not a priority.
Conclusion: The Servant Leader’s True Deliverable
Agile frameworks work best when your team has developed the kind of culture where people genuinely want to serve each other. The framework provides the structure; prosocial behavior provides the spirit and the most reliable pathway to prosocial teams is servant leadership which should be treated as a lived commitment to subordinating one’s own interests to the growth, safety, and success of the people one serves.
For Scrum Masters and Agile leads, this is both a responsibility and an opportunity to serve and lead. Every interaction is a chance to build or erode the prosocial foundation that high-performing teams require. Teams that consistently deliver extraordinary outcomes are rarely the most technically skilled however, they are the most prosocially developed.
That culture does not emerge by accident. It is built, deliberately and consistently by servant leaders who understand that their most important output is a team that thrives.
Key Takeaways
Prosocial behavior means helping, sharing, covering, collaborating beyond formal requirements. It is a foundational prerequisite for Agile success
Servant leadership is the most effective architecture for cultivating prosocial behavior in Agile teams, operating through psychological safety, role modeling, friction removal, and growth coaching
Every Agile ceremony can be reoriented to reinforce prosocial norms like gratitude rounds in retrospectives to team-oriented standup questions
Scrum Masters who act prosocially themselves are the most powerful force for prosocial culture change.
Organizations should measure prosocial health alongside output metrics to signal its importance and track progress over time.
Selected Research & Further Reading
The following sources informed the research foundation of this article:
Grant, A. M., & Berg, J. M. (2011). Prosocial motivation at work. Academy of Management Annals.
Podsakoff, N. P., et al. (2009). Individual- and organizational-level consequences of organizational citizenship behaviors. Journal of Applied Psychology.
Lenberg, P., & Feldt, R. (2025). Social sustainability in large-scale agile software development. Taylor & Francis / Software Engineering Journal.
Greenleaf, R. K. (1977). Servant Leadership: A Journey into the Nature of Legitimate Power and Greatness. Paulist Press.
Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly.