HKSM

A servant-leader who enables Scrum by coaching the Product Owner and team, facilitating Scrum events, and removing impediments. In SBOK, the Scrum Master is identified during Initiate and then functions as a recurring input across processes to uphold Scrum rules, transparency, and continuous improvement.

Key Points

• Role-based ITTO: identified as an output in Initiate and used as an input across multiple Scrum processes.
• Servant-leader who coaches, facilitates, and removes impediments without directing how the team builds the product.
• Ensures timeboxes, transparency, and adherence to Scrum values and practices.
• Owns facilitation of Scrum events and maintains focus on outcomes and flow.
• Maintains and works through the Impediment Log to improve throughput.
• Supports scaling via Scrum of Scrums for inter-team coordination when needed.

Purpose

The Scrum Master exists to make Scrum work in practice by creating conditions where the team can self-organize and deliver value consistently. The role protects the team from distractions, enables collaboration with the Product Owner, and ensures empirical process control through transparency, inspection, and adaptation.

In SBOK process terms, the Scrum Master ties events and artifacts together, ensuring that cadence, definition of done, and working agreements are respected so that each sprint yields potentially shippable deliverables and actionable learning.

Key Terms & Clauses

• Servant leadership: lead by service, coaching, and influence rather than authority.
• Impediment: anything that slows or blocks progress, tracked in an Impediment Log.
• Facilitation: neutral guidance of Scrum events to achieve outcomes within timeboxes.
• Timebox enforcement: keeping events and sprints within agreed durations.
• Working agreements: team rules for collaboration, quality, and tools that the Scrum Master helps uphold.
• Scrum of Scrums: cross-team synchronization event facilitated or supported by Scrum Masters in scaled contexts.

How to Develop/Evaluate

Selection criteria should include strong facilitation, conflict resolution, coaching, and practical Scrum knowledge. Prefer candidates empowered to escalate and remove organizational blockers, with availability aligned to the team’s cadence.

• Indicators of effectiveness: reduced cycle time, stable or improving velocity, faster impediment resolution, and healthier event participation.
• Behavioral signals: asks coaching questions, promotes self-management, and prevents scope or process bypassing.
• Organizational fit: credible with leadership to address systemic impediments and nurture continuous improvement.

How to Use

As an ITTO, the Scrum Master is produced and then consumed across SBOK processes:

• Initiate: output of Identify Scrum Master and Stakeholder(s); participates in Form Scrum Team and Develop Epic(s).
• Plan and Estimate: facilitates Create User Stories, Approve-Estimate-Commit User Stories, Create Tasks, Estimate Tasks, and Create Sprint Backlog.
• Implement: facilitates Conduct Daily Standup and manages the Impediment Log to clear blockers quickly.
• Review and Retrospect: facilitates Demonstrate and Validate Sprint and Retrospect Sprint to surface insights and agree on improvements.
• Release: supports transition activities by ensuring definition of done and acceptance criteria are met and visible.
• Scaling: coordinates with other Scrum Masters in Scrum of Scrums to manage cross-team dependencies and impediments.

Example Snippet

Assigned Scrum Master: Priya Shah.

• Availability: full-time to the team for the product release train.
• Primary responsibilities: facilitate Scrum events, maintain Impediment Log, support backlog refinement, coach on definition of done.
• Authority: escalate organizational impediments to department heads; adjust team working agreements with consent.
• Tools: digital Scrum board, impediment tracker, simple flow metrics dashboard.

Risks & Tips

• Risk: acting as a project manager directing tasks undermines self-organization. Tip: coach outcomes and constraints, not task assignments.
• Risk: part-time Scrum Master delays impediment removal. Tip: ensure adequate availability and escalation paths.
• Risk: skipping timeboxes causes drift and hidden work. Tip: enforce event durations and visible boards.
• Risk: unresolved systemic blockers stall multiple teams. Tip: use Scrum of Scrums and leadership coaching to address root causes.
• Risk: tool obsession over people and interactions. Tip: favor lightweight metrics and frequent conversation.

PMP/SCRUM Example Question

In an SBOK-aligned project, which process formally outputs the Scrum Master role that will then facilitate subsequent Scrum events?

1. Create Sprint Backlog
2. Conduct Daily Standup
3. Identify Scrum Master and Stakeholder(s)
4. Demonstrate and Validate Sprint

Correct Answer: C — Identify Scrum Master and Stakeholder(s)

Explanation: SBOK identifies the Scrum Master during Initiate in the process that names the Scrum Master and key stakeholders. The other options are processes where the Scrum Master acts, not where the role is created.