Study guide

8.2 2020 Scrum Guide Rapid Review

PSM I — Professional Scrum Master I Scrum.org

Track your progress as you read

Finished sections get a check mark.

1 Introduction & PSM I Exam Overview

1.1 Current PSM I Exam Facts 1.2 Scoring & Time-Management Strategy 1.3 The 2020 Scrum Guide Is The Single Source Of Truth 1.4 A Realistic PSM I Study Plan

2 Scrum Theory, Empiricism & Values

2.1 What Scrum Is (and Is Not) 2.2 Empiricism and Empirical Process Control 2.3 The Three Pillars: Transparency, Inspection, Adaptation 2.4 Lean Thinking: Reduce Waste, Focus on Essentials 2.5 The Five Scrum Values

3 The Scrum Team & Accountabilities

3.1 The Scrum Team 3.2 The Developers 3.3 The Product Owner 3.4 The Scrum Master 3.5 Scrum Master Services to Team, Product Owner, and Organization

4 The Scrum Events

4.1 The Sprint 4.2 Sprint Planning 4.3 The Daily Scrum 4.4 The Sprint Review 4.5 The Sprint Retrospective 4.6 Timeboxing and Empiricism Across the Events

5 Scrum Artifacts & Commitments

5.1 Artifacts & the Transparency Mandate 5.2 Product Backlog & the Product Goal 5.3 Sprint Backlog & the Sprint Goal 5.4 The Increment & the Definition of Done 5.5 Commitments Summary & Exam Traps

6 Developing People & Teams

6.1 Self-Managing Teams 6.2 Facilitation 6.3 Scrum Master Stances 6.4 True Leadership That Serves 6.5 Conflict & Organizational Change

7 Managing Products with Agility

7.1 Product and Value 7.2 Product Goal Management 7.3 Product Backlog Management 7.4 Forecasting and Release Planning 7.5 Stakeholders, Evidence, and Business Agility

8 Final Review & Exam Strategy

8.1 Common Misconceptions & PSM I Traps 8.2 2020 Scrum Guide Rapid Review 8.3 Question Tactics & Time Management 8.4 Last-Minute Checklist

8.2 2020 Scrum Guide Rapid Review

Key Takeaways Explain This Topic AI

Scrum is a lightweight framework that helps generate value through adaptive solutions for complex problems, founded on empiricism and lean thinking.

Empiricism stands on three pillars: transparency, inspection, and adaptation; the five values are commitment, focus, openness, respect, and courage.

One Scrum Team (typically 10 or fewer people) holds three accountabilities: Product Owner, Scrum Master, and Developers — with no sub-teams or hierarchies.

There are five events (Sprint as container, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) and three artifacts each with one commitment.

Artifact ↔ commitment: Product Backlog → Product Goal, Sprint Backlog → Sprint Goal, Increment → Definition of Done.

Last updated: June 2026

Definition, Purpose & Foundations

Scrum is "a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems." It is purposefully incomplete — it defines only the parts required to implement Scrum theory, and the rest is left to the team. It is founded on empiricism (knowledge comes from experience, and decisions are made on what is observed) and lean thinking (reduce waste, focus on the essentials).

The Three Pillars of Empiricism

Pillar Meaning

Transparency The emergent process and work must be visible to those doing the work and those receiving it. Low transparency leads to decisions that diminish value and increase risk.

Inspection Scrum artifacts and progress toward agreed goals must be inspected frequently and diligently to detect undesirable variances or problems.

Adaptation If a process or product deviates outside acceptable limits, or the resulting product is unacceptable, the process or materials must be adjusted as soon as possible.

The Scrum events are deliberately designed to create transparency and the formal opportunity to inspect and adapt — that is why each event exists. Memorise the cause-and-effect: events → transparency → inspection → adaptation.

The Five Scrum Values

Commitment, Focus, Openness, Respect, Courage. The team commits to its goals, focuses on the work of the Sprint to make the best possible progress, is open about the work and the challenges, respects each other as capable and independent people, and has the courage to do the right thing and work on tough problems. Successful use of Scrum depends on people becoming more proficient in living these five values; they give direction to the team's work, actions, and behavior.

The Scrum Team & Its Three Accountabilities

There is one Scrum Team , typically 10 or fewer people , cross-functional (collectively has all skills needed each Sprint) and self-managing (internally decides who does what, when, and how). Within a Scrum Team there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal . The 2020 Guide uses accountabilities, not roles , and there is no separate "Development Team" — the people who do the work are simply the Developers .

Accountability Accountable for (exact emphasis) Notes

Product Owner Maximizing the value of the product resulting from the work of the Scrum Team One person, not a committee; develops and communicates the Product Goal; orders the Product Backlog

Scrum Master The Scrum Team's effectiveness A true leader who serves the Scrum Team, the Product Owner, and the organization; accountable for establishing Scrum

Developers Creating any aspect of a usable Increment each Sprint Own the Sprint Backlog, instill quality via the Definition of Done, and adapt their plan each day

The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. The accountabilities above are scopes within that shared accountability — they do not fragment the team into reporting lines.

The Five Events (Timeboxes for a One-Month Sprint)

The Sprint is the heartbeat of Scrum and the container for all other events; a new Sprint starts immediately after the conclusion of the previous Sprint. Each event is a formal opportunity to inspect and adapt, and each is timeboxed to a maximum duration.

Event Max timebox (1-month Sprint) Purpose / owner

Sprint One month or less (fixed, consistent length) Container event; creates consistency and predictable cadence

Sprint Planning 8 hours Addresses Why (Sprint Goal), What (selected items), and How (the plan); the Sprint Goal is created here

Daily Scrum 15 minutes The Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog; held same time and place each day

Sprint Review 4 hours The Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog; it is a working session, never a release gate

Sprint Retrospective 3 hours The team plans ways to increase quality and effectiveness; it concludes the Sprint

For shorter Sprints, the events are usually shorter — the maximums scale down proportionally. The only fixed value is the Daily Scrum at 15 minutes . Shorter Sprints generate more learning cycles and limit cost and effort risk to a smaller time horizon.

The Three Artifacts & Their Commitments

Each artifact contains exactly one commitment that provides information enhancing transparency and focus against which progress can be measured.

Artifact Commitment What the commitment means

Product Backlog Product Goal The single long-term objective the Scrum Team plans against; in the Product Backlog and acts as the team's target

Sprint Backlog Sprint Goal The single objective for the Sprint; created at Sprint Planning, it gives the Developers coherence and focus

Increment Definition of Done A formal description of the state of the Increment when it meets the quality measures required for the product

The Product Backlog is an emergent, ordered list of what is needed to improve the product; it is the single source of work for the Scrum Team, owned by the Product Owner. Refinement is an ongoing activity of adding detail, estimates, and order — not an event.

The Sprint Backlog is composed of the Sprint Goal (why), the set of items selected (what), and an actionable plan (how) . It is by and for the Developers and is updated throughout the Sprint as more is learned.

The Increment is a concrete stepping stone toward the Product Goal; each is additive to prior Increments and verified to ensure they work together. Multiple Increments may be created within a Sprint and delivered before the Sprint ends — the Sprint Review is not the moment of release. Work is only part of an Increment if it meets the Definition of Done ; if no organizational standard exists, the Scrum Team must create one.