In the Scrum Guide 2020, the Scrum Master was introduced as one of the three core roles (Accountabilities) in the Scrum Team, alongside the Product Owner and Developers. However, the description of this role remained brief, general, and somewhat basic. In the Scrum Guide Expansion Pack 2025, this picture has changed. The Scrum Master now appears with a more complete definition and a much deeper presence throughout the organization — from acting as a change agent to becoming a learning facilitator, from team coaching to collaborating with senior leadership. This article takes a clear and referenced look at this evolving role.

A Human Role with Clear Accountability

The very first sentence defining the Scrum Master in the Scrum Guide Expansion Pack 2025 not only positions the role but also emphasizes its human nature. It sets the foundation for understanding the distinction between a formal title and real accountability:

“The Scrum Master is a role and an accountability. The Scrum Master must be human.” -Scrum Guide Expansion Pack 2025

This simple statement holds two essential points:

  • First, the Scrum Master is not just a job title — it comes with a defined and professional responsibility to enable effectiveness.
  • Second, emphasizing “must be human” means no tool, system, or framework can replace the human qualities of facilitation, empathy, and leadership required in this role.

This understanding of Role + Accountability + Human Presence is the most basic requirement for anyone meaningfully stepping into the role of Scrum Master today.

The Scrum Master as a Change Agent

In the Scrum Guide Expansion Pack 2025, the Scrum Master is no longer just a simple facilitator — they are explicitly described as a change agent. This requires influence across multiple levels of the organization — from the development team to senior leadership, from stakeholder interactions to shaping organizational culture.

 

“The Scrum Master is a change agent who works at all organizational levels and across business areas.” -Scrum Guide Expansion Pack 2025

This sentence highlights four key responsibilities:

  1. Building communication and trust across all organizational layers
  2. Leading change, not just facilitating meetings
  3. Improving workflows, transforming mindsets, and supporting cultural shifts
  4. Holding a recognized and empowered position within the organization

This positions the Scrum Master as a servant-leader and organizational learning catalyst — someone who enables change rather than merely enforcing process.

 

The Many Roles(behaviors) of a Scrum Master

One of the most significant conceptual developments in the Scrum Guide Expansion Pack 2025 is a list of behaviors and roles the Scrum Master may adopt based on context. This role is no longer fixed; it adapts to team and situational needs.

“The Scrum Master should adopt appropriate behaviors depending on the situation; these include (but are not limited to) being a guide, coach, mentor, teacher, observer, impediment remover, agent of change, effectiveness facilitator, and continuous improvement champion.” -Scrum Guide Expansion Pack 2025

This list highlights how the Scrum Master must know:

  • When to coach
  • When to teach or guide
  • And when to simply listen or observe

Such diversity in roles demands more than Agile knowledge — it calls for interpersonal skills, active listening, empathy, and systems thinking.

Organizational Collaboration: Beyond the Development Team

In the Scrum Guide Expansion Pack 2025, the Scrum Master’s role is clearly extended beyond just supporting the development team. The Scrum Master must also collaborate with other Scrum actors, including the Product Owner, Stakeholders, Supporters, and even senior leadership. This collaboration is not just about coordinating events — it involves coaching, training, facilitation, and active support to ensure Scrum is effectively applied across the organization.

Below are direct excerpts from the official text, detailing the Scrum Master’s responsibilities with each group:

The Scrum Master works with the Supporters in several ways, including:

  • Leading, training, and coaching the Supporters in the Scrum adoption;
  •  Clarifying what is getting in the way of an effective Scrum adoption;
  • Facilitating disciplined emergent change in a direction to support the Scrum adoption; and,
  • Fostering organizational changes toward ease of delivery vs ease of management.

Scrum Guide Expansion Pack 2025

And,

The Scrum Master supports the Product Owner in several ways, including: 

  • Helping find techniques for effective Product Goal definition and Product Backlog management;
  • Helping establish emergent Product planning for a complex (30-35) environment;
  • Helping the Product Owner to express outcomes as measures through the Definition of Outcome Done;
  • Helping the Product Owner understand the need for clear and concise Product Backlog Items that deliver value; and,
  • Helping the Product Owner to Focus on value realization.

Scrum Guide Expansion Pack 2025

And,

The Scrum Master supports the Stakeholders in several ways, including:

  • Facilitating Stakeholder collaboration as requested or needed;
  • Helping Stakeholders understand the need for clear and concise Product Backlog Items that deliver value; and,
  • Helping the Stakeholders to Focus primarily on value realization.

Scrum Guide Expansion Pack 2025

 

Each of these responsibilities reflects that the Scrum Master is not just a team servant — but an orchestrator of alignment and collaboration across the entire system.

If You’re Not Ready to Change…

Throughout the Scrum Guide Expansion Pack 2025, the Scrum Master is described as a change agent — a role requiring courage, commitment, and maturity. But in one clear statement, the guide emphasizes that this role is not for those unprepared for true change.

“A Scrum Master who is neither willing, ready, nor able to be an agent of change should step down as a Scrum Master.” - Scrum Guide Expansion Pack 2025

This isn’t just a warning — it’s a professional standard. If someone isn’t prepared to guide, influence, and withstand organizational resistance, they shouldn’t hold this role. Because being a Scrum Master means building, leading, and enduring — not just facilitating meetings.

A Word of Caution About Junior Scrum Masters

In many organizations — especially those newly adopting Scrum — we often see the Scrum Master role assigned to junior team members with little experience or understanding of agility. This approach not only clashes with the spirit of Scrum but can also harm the team.

The role demands a mature individual — both in character and career. Someone who reacts emotionally to pressure or defaults to command-and-control cannot lead meaningful change.

Furthermore, skills like Active Listening and Powerful Questioning are core to effective coaching — and these require experience, self-awareness, and emotional maturity.

If a junior or inexperienced person enters the role without structured support or mentoring, they may not only struggle themselves but may also slow or misguide the team’s evolution.

Conclusion

The Scrum Master role in the Scrum Guide Expansion Pack 2025 is introduced with greater clarity and depth — more aligned with the realities of the modern Scrum environment.

The Scrum Master is now a human, adaptive, and multifaceted figure deeply embedded in learning, change, and value creation across both teams and organizations.

From coaching, to facilitating stakeholder collaboration, from leading supporters to aligning leadership with empirical thinking — all fall within this role’s scope.

But at the heart of it all lies a core truth: Without the willingness, readiness, and ability to act as a change agent, one should not remain in this role.

*** Note:

Some readers may notice that the term “role” was deliberately removed from the Scrum Guide 2020. However, in this article, we focused on the nature and function of the Scrum Master, rather than the terminology itself. Since the Scrum Guide Expansion Pack 2025 frequently uses the word “role” again in its descriptions, we did not strictly avoid it.