Complete Scrum Guide Summary for PSM I: Key Concepts You Must Know

Why the Scrum Guide Is Your #1 Study Resource

If you are preparing for the Professional Scrum Master I (PSM I) certification from Scrum.org, there is one document that supersedes every other study material: The Scrum Guide. Written by Ken Schwaber and Jeff Sutherland, this free, 13-page reference is the definitive source for every single question on the PSM I exam. Every PSM I exam question traces back to its content, language, and principles.

This article is your complete Scrum Guide summary optimized for PSM I success. Whether you are working through a PSM I practice test or building your foundation before attempting the real exam, understanding the Scrum Guide at a deep conceptual level - not just surface memorization - is what separates candidates who pass from those who fail.

Many candidates underestimate PSM I exam difficulty because the Scrum Guide is short. But the questions are designed to test application of concepts, not recall. You need to understand why Scrum works the way it does, not just what each artifact is called.

Scrum Framework: The Complete Overview

Scrum is a lightweight framework that helps teams, organizations, and individuals generate value through adaptive solutions to complex problems. That definition alone contains exam-worthy language. Notice the word framework - not a process, not a methodology. This distinction shows up in PSM 1 exam questions regularly.

Scrum is intentionally incomplete. It defines only the parts that are required to implement Scrum theory. The framework consists of three pillars, five values, three accountabilities, five events, and three artifacts - each with a corresponding commitment.

What Scrum Is Not

The Scrum Guide explicitly states that Scrum does not provide complete instructions. It is a container for other techniques, methodologies, and practices. Many candidates lose points by assuming Scrum prescribes specific engineering practices. It does not. Scrum's rules are minimal and designed to be implementable in almost any environment.

Scrum Theory and Principles

Scrum is founded on empiricism and lean thinking. Empiricism holds that knowledge comes from experience and that decisions are made based on what is observed. Lean thinking reduces waste and focuses on essentials.

The Three Pillars of Empiricism

Every PSM I candidate must be able to recite and explain these three pillars without hesitation:

1. Transparency - The emergent process and work must be visible to those performing the work and to those receiving it. Important decisions are based on the perceived state of the formal artifacts.
2. Inspection - Scrum artifacts and the progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances.
3. Adaptation - If any aspect of a process deviates outside acceptable limits, or if the resulting product is unacceptable, the process or the material being processed must be adjusted.

These three pillars are not just theory - they are the justification for every Scrum event. The Daily Scrum enables inspection and adaptation of the Sprint. The Sprint Review enables inspection and adaptation of the product. The Sprint Retrospective enables inspection and adaptation of the process. If you understand this relationship, you will answer a significant portion of PSM 1 exam questions correctly.

The Five Scrum Values

Scrum succeeds only when the team embodies five core values:

• Commitment - Team members personally commit to achieving team goals.
• Courage - Scrum Team members have courage to do the right thing and work on tough problems.
• Focus - Everyone focuses on Sprint work and goals of the Scrum Team.
• Openness - The Scrum Team and stakeholders agree to be open about all work and challenges.
• Respect - Team members respect each other as capable, independent people.

Questions about Scrum values often appear in scenario-based formats. You may be asked which value is being violated in a described situation, or which value most directly supports a specific behavior.

The Scrum Team: Roles, Accountabilities, and Responsibilities

The 2020 Scrum Guide made a significant shift in language: it moved away from "roles" and toward accountabilities. This is not cosmetic - it reflects a deeper philosophical stance on how Scrum defines responsibility. The Scrum Team consists of exactly three accountabilities:

1. The Scrum Master

The Scrum Master is accountable for the Scrum Team's effectiveness. They do this by enabling the team to improve its practices within the Scrum framework. The Scrum Master serves the Scrum Team, the Product Owner, and the organization. Key responsibilities include:

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

2. The Product Owner

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They manage the Product Backlog, which includes: creating and communicating Product Backlog Items, ordering them, and ensuring the backlog is transparent, visible, and understood.

3. The Developers

In the 2020 Scrum Guide update, "Development Team" was replaced with simply Developers. Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. They are responsible for creating the Sprint Backlog, adhering to the Definition of Done, and adapting their plan every day toward the Sprint Goal.

Developers are self-managing - they decide how to do the work. This is distinct from self-organizing (the older term). The Scrum Team as a whole is cross-functional and self-managing.

Scrum Events: What Every PSM I Candidate Must Know

Scrum prescribes five formal events. Each event is both an opportunity for inspection and adaptation and a container for all other events. Missing or shortening Scrum events is a violation of the Scrum framework - a concept that appears frequently in scrum guide quiz-style questions.

Event	Purpose	Timebox	Who Attends
The Sprint	Container for all events; delivers value	≤ 4 weeks (fixed)	Entire Scrum Team
Sprint Planning	Plan the Sprint; define Sprint Goal	≤ 8 hours (4-week Sprint)	Entire Scrum Team
Daily Scrum	Inspect progress toward Sprint Goal	15 minutes	Developers (PO/SM optional)
Sprint Review	Inspect Increment; adapt Product Backlog	≤ 4 hours (4-week Sprint)	Scrum Team + stakeholders
Sprint Retrospective	Inspect team process; plan improvements	≤ 3 hours (4-week Sprint)	Entire Scrum Team

Key Points About the Sprint

The Sprint is the heartbeat of Scrum. Sprints are fixed-length - once chosen, the length does not change mid-Sprint. A Sprint can be cancelled only by the Product Owner, and only if the Sprint Goal becomes obsolete. This is a frequently tested fact. Sprints should be short enough to keep risk manageable - the Scrum Guide recommends no longer than one calendar month.

Sprint Planning: Three Key Questions

Sprint Planning addresses three questions: Why is this Sprint valuable? What can be Done this Sprint? How will chosen work get done? The Sprint Goal is created during Sprint Planning and represents the team's commitment for the Sprint.

The Daily Scrum

The Daily Scrum is a 15-minute event for Developers. It is not a status meeting - it is an inspection and adaptation event. The Scrum Guide removed the old three-question format in 2020. Developers can use whatever structure works, as long as the meeting focuses on progress toward the Sprint Goal.

Scrum Artifacts and Their Commitments

One of the most significant updates in the 2020 Scrum Guide was the addition of commitments to each artifact. This is heavily tested on the PSM I exam:

Definition of Done and Undone Work

The Definition of Done (DoD) is a formal description of the state of an Increment when it meets the quality measures required by the product. The DoD creates transparency and a shared understanding of what "complete" means.

If an organization has a DoD, all Scrum Teams must follow it as a minimum. Teams may adopt a stricter DoD but never a weaker one. If no organizational standard exists, the Scrum Team must create its own.

"Undone" work refers to Product Backlog Items that were not completed during a Sprint. They return to the Product Backlog. They are not added to the next Sprint automatically - the Product Owner reprioritizes them.

High-Value Areas on the PSM I Exam

Based on the exam domains and feedback from thousands of candidates, certain areas of the Scrum Guide generate a disproportionate number of questions. If you are using a PSM I practice test platform to prepare, make sure your practice questions emphasize these topics:

Domain 1: The Scrum Framework

This is the largest domain. Questions test your knowledge of every event, artifact, accountability, and commitment. You need to know timeboxes, who attends each event, who is accountable for each artifact, and what happens when rules are broken. For deeper preparation, check out our PSM I Study Guide 2026: How to Pass Without Training.

Domain 2: Scrum Theory and Principles

These questions are often scenario-based. You will be presented with a team situation and asked which pillar of empiricism is being violated or upheld, or which Scrum value is at risk. Read the scenarios carefully - the answer often hinges on a single word.

Domain 3: Cross-functional, Self-managing Teams

Questions test whether you understand what "self-managing" means (teams decide how to do the work) versus what Scrum does not prescribe (who to hire, how to structure the organization). Many candidates confuse self-management with autonomy from the Product Owner, which is wrong.

Domain 4: Coaching and Facilitation

The Scrum Master as a servant leader and coach is a major theme. Questions ask what the Scrum Master should do in specific conflict, impediment, or dysfunction scenarios. The correct answer almost always involves coaching and empowering the team rather than solving the problem directly. See our article on PSM I Exam Tips: 12 Mistakes That Cause People to Fail for common traps in this domain.

Domain 5: Done and Undone (Scaling Scrum)

This domain includes questions about multiple Scrum Teams working on the same product. Key facts: multiple teams share one Product Backlog and one Product Owner. Each team has its own Scrum Master and Sprint Backlog. All teams must use the same Definition of Done.

If you are considering advancing beyond PSM I, our guide on PSM I to PSM II: What Changes and How to Prepare for Level 2 explains how scaling Scrum concepts deepen significantly at the next level.

PSM I Exam Quick Facts

The PSM I exam is administered online with no scheduling required - you can take it anytime. There are no prerequisites or mandatory training courses. The exam is based entirely on the Scrum Guide. You must score at least 85%, meaning you can miss no more than 12 questions out of 80. This tight margin is why deep understanding matters more than casual reading.

There is no official PSM 1 pass rate published by Scrum.org, but the consensus from the community is that the exam is moderately difficult for self-study candidates who read the Scrum Guide only once. Candidates who practice with scenario-based questions - similar to what you find in a quality professional scrum master practice exam - perform significantly better.

PSM I vs Other Certifications

A common question among candidates is how PSM I compares to other credentials. If you are weighing your options, our detailed breakdown in PSM I vs CSM: Which Scrum Certification Is Better? Honest Comparison covers the key differences in cost, rigor, recognition, and renewal requirements. The short version: PSM I never expires, does not require renewal fees, and is universally respected for its knowledge-based approach.

If you are interested in product ownership or considering the PSPO I path after PSM I, keep in mind the exams share significant overlap in Scrum Guide knowledge but diverge significantly in focus area. You can explore those differences in detail at our guide on scrum-related product certifications.

Time Management on Exam Day

Eighty questions in sixty minutes means you have an average of 45 seconds per question. That is tight. Questions are scenario-based and often lengthy. You need a strategy - flag difficult questions, answer what you know, and return to flagged items. Never leave a question blank. For a complete breakdown of how to pace yourself, read our PSM I Exam Format: 80 Questions in 60 Minutes Time Management Strategy.

Frequently Asked Questions