Skip to content
PMPCAPM

Scrum Master

The Scrum Master is the accountability within Scrum responsible for establishing Scrum as defined in the Scrum Guide, helping the team and organization understand Scrum theory and practice, and removing impediments.

Share:

Know it well enough for the exam? Questions on Scrum Master are scenario-based, not definitional.

Practice it free

Explanation

The Scrum Master serves the Scrum team by coaching team members in self-management and cross-functionality, helping the team focus on creating high-value increments, removing impediments, and ensuring all Scrum events are productive and timeboxed. The Scrum Master is not a traditional project manager and does not assign tasks or direct the team.

The Scrum Master also serves the Product Owner by helping find techniques for effective Product Backlog management, facilitating stakeholder collaboration, and helping establish empirical product planning. At the organizational level, the Scrum Master leads and coaches in agile adoption, helps employees and stakeholders understand Scrum, and removes barriers between stakeholders and the Scrum team.

PMI frames the Scrum Master as a servant leader, someone who leads by serving the team. On the exam, look for answers that emphasize coaching, facilitating, and removing impediments rather than directing or managing people.

Key Points

  • •Accountable for establishing Scrum as defined in the Scrum Guide
  • •Acts as a servant leader and coach, not a traditional manager
  • •Removes impediments that block the team from delivering value
  • •Facilitates Scrum events and helps the organization adopt agile practices

Exam Tip

When a question asks what the Scrum Master should do, favor answers about coaching, facilitating, and removing impediments over directing or making decisions for the team.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Part of

Agile & Hybrid

Study full domain →

Practice Scrum Master

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.