Professional Scrum Master Practice Test

โ–ถ

The Professional Scrum Master (PSM) certification from Scrum.org is one of the most rigorous and respected Scrum credentials available. Unlike other certifications that rely solely on attendance, PSM requires you to pass a challenging online assessment that tests deep knowledge of the Scrum framework, Scrum Master accountabilities, and empirical process theory. Preparing with targeted practice questions is essential to achieving the 85% passing threshold.

This page provides a free PSM practice test PDF you can download and print for offline study. The questions cover all three PSM levels โ€” PSM I, PSM II, and PSM III โ€” and are aligned with the 2020 Scrum Guide. Use this PDF alongside your other study materials to reinforce your understanding of Scrum events, artifacts, roles, and values.

PSM Certification Fast Facts

The Scrum Framework and Events

The Scrum framework is built on three pillars of empiricism: transparency, inspection, and adaptation. Scrum organizes work into Sprints โ€” time-boxed iterations of one month or less โ€” during which a Done, usable Increment is created. Understanding the framework means knowing not just what each event is, but why it exists and what accountability each role holds within it.

Scrum defines five events: the Sprint itself, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Each event is both an opportunity to inspect and an opportunity to adapt. Sprint Planning establishes what can be delivered in the Sprint and how that work will be achieved. The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. The Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog. The Sprint Retrospective gives the Scrum Team a chance to improve quality and effectiveness.

PSM exam questions frequently test whether candidates understand the purpose and time-box of each event. Common mistakes include confusing Sprint Review (external stakeholders, product focus) with Sprint Retrospective (internal team, process focus), or misidentifying who owns each event. The Sprint Review is not a sign-off meeting; the Scrum Team and stakeholders collaborate on what to do next.

Scrum Artifacts and Commitments

The 2020 Scrum Guide formalized three artifacts, each paired with a commitment to maximize transparency and focus. The Product Backlog is owned by the Product Owner; its commitment is the Product Goal, which describes the future state of the product. The Sprint Backlog is created by the Developers during Sprint Planning; its commitment is the Sprint Goal, a single objective for the Sprint. The Increment is the sum of all completed Product Backlog items; its commitment is the Definition of Done.

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Understanding when work is truly "Done" versus merely "finished" is a core PSM I concept that appears in multiple exam scenarios.

PSM II and PSM III questions go deeper โ€” they test your ability to coach teams on refining their Definition of Done, managing multiple teams sharing a Product Backlog, and scaling artifacts across large organizations. Practice questions at this level involve real-world scenarios where the right answer requires applying Scrum values rather than recalling rules.

The Scrum Master Accountability

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. This means the Scrum Master serves the Scrum Team and the organization in specific, well-defined ways. For the Developers, the Scrum Master coaches self-management and cross-functionality, removes impediments, and ensures all Scrum events take place and are productive. For the Product Owner, the Scrum Master helps with Product Goal definition, Product Backlog management techniques, and empirical product planning. For the organization, the Scrum Master leads and trains in Scrum adoption and works to increase the effectiveness of the Scrum Team.

A critical distinction tested on the PSM exam is the difference between a Scrum Master who facilitates versus one who manages. The Scrum Master does not manage the team, assign tasks, or make product decisions. Exam questions often present scenarios where a manager or stakeholder is pressuring the Scrum Master to add scope mid-Sprint, track individual velocity, or extend a Sprint. Knowing how a true Scrum Master responds in each scenario is essential.

Scrum Values and Empiricism

The five Scrum values โ€” Commitment, Focus, Openness, Respect, and Courage โ€” are not abstract ideals. They are the behavioral foundation that makes empirical process control possible. Without courage, teams avoid difficult conversations about impediments. Without openness, transparency breaks down. Without commitment to the Sprint Goal, adaptation becomes impossible.

Empiricism in Scrum means decisions are based on observation, experience, and experimentation rather than detailed upfront planning. The three pillars โ€” transparency, inspection, and adaptation โ€” work together as a feedback loop. Transparency enables inspection; inspection enables adaptation. If any pillar is weak, empiricism fails. PSM II and III questions test whether candidates can apply these principles in complex organizational situations involving distributed teams, conflicting stakeholder priorities, and dysfunctional team dynamics.

Studying the Scrum values alongside the framework events is one of the most efficient ways to increase your PSM I score. Many "trick" questions on the exam are resolved correctly by asking: which answer is most consistent with Scrum values and the empirical approach? Rote memorization of rules is not enough โ€” you need to internalize the reasoning behind each Scrum principle.

Read the 2020 Scrum Guide from cover to cover at least twice
Memorize the time-box and purpose of all five Scrum events
Understand the three artifacts and their paired commitments (Product Goal, Sprint Goal, Definition of Done)
Study the Scrum Master accountability for the team, Product Owner, and organization separately
Practice distinguishing Scrum Master facilitation from management or leadership
Review the five Scrum values and how they apply to real team scenarios
Complete at least 3 full-length PSM I practice tests under timed conditions
Study the Nexus Guide if targeting PSM II or PSM III
Review common PSM I failure points: Sprint length, who can cancel a Sprint, ordering vs prioritizing the Product Backlog
Check the Scrum.org open assessments (free) for immediate feedback on weak areas

Passing the PSM exam requires more than memorizing the Scrum Guide โ€” it requires the ability to apply Scrum principles in real-world scenarios under time pressure. The best way to build that skill is consistent practice with exam-quality questions. Start your preparation with our free Professional Scrum Master practice tests, which cover every section of the PSM I blueprint with detailed answer explanations to reinforce learning after each attempt.

Is PSM I harder than CSM, and which is more respected?

PSM I is generally considered harder than the Certified ScrumMaster (CSM) from Scrum Alliance. The CSM requires completing a two-day course and passing a relatively straightforward 50-question open-book exam with a 74% pass mark. PSM I requires no course but demands an 85% score on 80 questions in 60 minutes โ€” a higher bar. In hiring, both credentials are recognized, but PSM is often seen as more rigorous because it cannot be obtained simply by attending a course. Many practitioners hold both certifications.

What are the five Scrum events?

The five Scrum events are: (1) The Sprint โ€” the container for all other events, time-boxed to one month or less; (2) Sprint Planning โ€” where the team creates the Sprint Backlog and establishes the Sprint Goal; (3) Daily Scrum โ€” a 15-minute daily event for Developers to inspect progress and adapt the plan; (4) Sprint Review โ€” held at the end of the Sprint to inspect the Increment with stakeholders and adapt the Product Backlog; and (5) Sprint Retrospective โ€” where the team reflects on their process and creates a plan for improvement.

How does Sprint Planning differ from Sprint Review and Sprint Retrospective?

Sprint Planning happens at the start of the Sprint and is forward-looking โ€” the team decides what work to take on and how to accomplish it. Sprint Review happens at the end of the Sprint and is product-focused โ€” the team and stakeholders inspect the Increment and collaborate on what to do next with the Product Backlog. Sprint Retrospective also happens at the end of the Sprint but is process-focused โ€” the Scrum Team reflects on how they worked together and identifies improvements to make in the next Sprint. A common exam trap is confusing Review (external, product) with Retrospective (internal, process).

What does empiricism mean in Scrum?

Empiricism means that knowledge comes from experience and decisions are based on observable facts rather than speculation or detailed upfront plans. Scrum implements empiricism through three pillars: transparency (making the work and process visible to those responsible for outcomes), inspection (regularly examining progress toward goals), and adaptation (adjusting the process or the work when inspection reveals deviations). All five Scrum events are formal opportunities to inspect and adapt. When one or more pillars is weak โ€” for example, when a team hides impediments or skips the retrospective โ€” empiricism breaks down and the team loses the ability to improve.
โ–ถ Start Quiz