3.5 Scrum Master Services to Team, Product Owner, and Organization

Three Audiences the Scrum Master Serves

The 2020 Scrum Guide enumerates concrete services the Scrum Master provides to three audiences: the Scrum Team, the Product Owner, and the organization. PSM I commonly gives a scenario and asks which audience a particular service belongs to, so the exam skill is learning the groupings, not just the flat list. A recurring trap pairs a real service with the wrong audience (for example, calling an organizational service a "service to the team").

A theme cuts across all three audiences: the Scrum Master delivers every service as a true leader who serves — through coaching, teaching, facilitating, advising, and removing barriers, never by exercising command authority. The Scrum Master is explicitly not a secretary, scribe, or project manager. None of the listed services grant authority over scope, schedule, or people.

Keep one precise distinction in mind before the details: causing the removal of impediments to the Scrum Team's progress is a Scrum-Team service, while removing barriers between stakeholders and Scrum Teams is an organization service. The two sound alike and are a favorite PSM I discriminator.

Service to the Scrum Team and to the Product Owner

The Scrum Master serves the Scrum Team in several ways:

• Coaching the team members in self-management and cross-functionality
• Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done
• Causing the removal of impediments to the Scrum Team's progress
• Ensuring that all Scrum events take place and are positive, productive, and kept within the time-box

The Scrum Master serves the Product Owner in several ways:

• 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
• Helping establish empirical product planning for a complex environment
• Facilitating stakeholder collaboration as requested or needed

Notice that "facilitating stakeholder collaboration" sits under the Product Owner — not the organization — because it supports the Product Owner's value and backlog work. And note the Scrum Master helps establish empirical product planning; they do not do the product planning themselves, which would usurp the Product Owner's accountability.

Service to the Organization

The Scrum Master serves the organization in several ways:

• 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 for complex work
• Removing barriers between stakeholders and Scrum Teams

What the Scrum Master Is NOT

None of these services make the Scrum Master a project manager (no authority over scope, schedule, or people), a team secretary (not there to take notes or book rooms), or a gatekeeper (does not approve Increments or backlog content). " Both contradict self-management and the Scrum Master's serve-first stance. When a scenario describes the Scrum Master doing the Developers' or Product Owner's accountable work rather than coaching them to do it, that is the wrong answer.

Mapping Scenarios to the Right Audience

The exam skill for 3.5 is fast, accurate routing: read a described action and assign it to the Scrum Team, the Product Owner, or the organization. The wording in the question usually mirrors the Guide closely, so anchoring on a few keywords pays off.

• Anything about events (Daily Scrum, Sprint Planning, Review, Retrospective) being positive, productive, and time-boxed → service to the Scrum Team.
• Anything about self-management, cross-functionality, focus on Done Increments, or impediments to the team's progress → service to the Scrum Team.
• Anything about the Product Goal, Product Backlog techniques, clear and concise items, empirical product planning, or facilitating stakeholder collaboration → service to the Product Owner.
• Anything about Scrum adoption, planning/advising implementations, teaching the empirical approach organization-wide, or barriers between stakeholders and teams → service to the organization.

The two most-confused pairs:

Worked routing examples

1. A new department keeps imposing a waterfall stage-gate on the Scrum Team. → Organizational service: lead and coach the organization in its Scrum adoption and help it enact an empirical approach.
2. The Product Owner struggles to write clear backlog items. → Service to the Product Owner: help the team understand the need for clear and concise Product Backlog items.
3. The Daily Scrum routinely runs 45 minutes and turns into a status report to a manager. → Service to the Scrum Team: ensure events are positive, productive, and within the time-box.
4. Developers keep waiting on a hand-off from an external team. → Service to the Scrum Team: cause the removal of impediments to the team's progress (and, if structural, an organizational barrier to remove).

Throughout, the Scrum Master serves — none of these examples involve giving orders. That serve-first quality is itself a frequently tested theme, so when two answers fit the audience, prefer the one phrased as coaching, helping, facilitating, or removing barriers over the one phrased as directing or controlling.