Professional Scrum Master I

An exam based credential for Scrum Masters, assessed against the 2020 Scrum Guide and Scrum.org's published Professional Scrum Competencies.

At a glance
Cost
$200 The fee buys one attempt. A second attempt is charged again at the same price.
Format
80 scenario based questions in 60 minutes, set as multiple choice, multiple answer and true/false.
Pass mark
85%, which allows 12 incorrect answers out of 80.
Prerequisites
None. No course attendance and no logged experience are required to sit it.
Renewal
The credential does not expire. There is no annual fee and no continuing education requirement.
Based on
The 2020 Scrum Guide and Scrum.org's published Professional Scrum Competencies
What it covers

What it covers. The exam tests whether a candidate can apply the Scrum framework as written, from the position of a Scrum Master. Most questions describe a situation on a Scrum Team and ask what should happen next, so the candidate has to hold the three accountabilities, the five events with their timeboxes and the three artifacts with their commitments precisely.

The weight sits on the framework itself. A Scrum Master is asked to recognise what the Guide actually says against what teams commonly do instead, which is why the practice set here carries a page on anti patterns and a page separating the Definition of Done from acceptance criteria.

Developing people and teams is the competency that separates this assessment from the Product Owner ones. Facilitation, coaching and the handling of conflict are named in Scrum.org's competencies and are the part of the role the Scrum Guide describes least, so they need reading beyond the Guide.

Sixty minutes for eighty questions is roughly 45 seconds each, so pace matters as much as knowledge. Timed practice is the part of preparation people most often skip.

Much of this material is shared with the Product Owner assessments, because both test the same framework. The Scrum Master specific reading is the second module.

The syllabus3 domains · free

Scrum.org’s own domains. Each opens its own page listing the concepts beneath it, and each concept has a page of its own.

01Understanding and Applying the Scrum FrameworkEmpiricism and the values underneath the framework, the three accountabilities and what each one owns, the five events with their timeboxes, the three artifacts with their commitments, and the two places candidates most often lose marks, which are the Definition of Done against acceptance criteria and the practices teams adopt that the Guide does not describe.Empiricism and the three pillars · The Scrum Values · The Scrum Team · How the Scrum Master serves · The Product Owner accountability · The Developers · The Sprint · Sprint Planning · The Daily Scrum · The Sprint Review · The Sprint Retrospective · Timeboxes in Scrum · Cancelling a Sprint · The Product Backlog · The Sprint Backlog · The Increment · The Sprint Goal · The Definition of Done · Definition of Done and Acceptance Criteria in Scrum · Common Scrum Anti Patterns and What the Scrum Guide Says20 concepts
~50%
02Developing People and TeamsThe part of the role the Scrum Guide describes least. What self management actually requires, how a Scrum Master facilitates each event without owning it, the difference between coaching and telling, what to do when a team is in conflict, and how the accountability reaches the organisation around the team.Self-management · Cross-functionality · How a Scrum Master Facilitates Each Scrum Event · Coaching and mentoring · How a Scrum Master Handles Conflict on a Scrum Team · The Scrum Master and Organisational Change6 concepts
~30%
03Managing Products with AgilityWhat a Scrum Master needs to know about the product side without owning it. The Product Goal, how a Product Backlog is ordered and refined, forecasting from past delivery rather than from estimates, working with stakeholders and what changes when one product needs more than one team.The Product Goal · Ordering the Product Backlog · Product Backlog refinement · Forecasting and release planning · Stakeholders and collaboration · Scaling Scrum6 concepts
~20%
Try a question

A payments API team ends every Sprint Review with the stakeholders' concerns written into the Scrum Master's notes, and the Product Backlog looks the same the next morning as it did the day before. Which pillar is failing, and what should follow?

  • ATransparency, so the notes should be circulated to everyone who attended.
  • BInspection, so the review needs longer to reach every item in the Sprint.
  • CAdaptation, so the Product Backlog should change on what the review found.
  • DNothing is failing, since recording the concerns is the event's own output.
105 questions across the 3 domains.

One per page, with a worked explanation.

Start the set