Scrum Guide 2020: What Changed and What It Means for Your PSM I Exam

The Scrum Guide 2020 is the version that matters for your PSM I exam. If you have studied Scrum before — or read articles, took a course, or worked in a Scrum team before November 2020 — there is a real chance some of what you know is out of date. The 2020 revision was the most significant update since 2016, and several changes directly affect how exam questions are answered. Here are the 7 main changes, what each means, and what to unlearn if you are coming from the 2017 version.

The 7 Changes in the Scrum Guide 2020

1. "Development Team" Removed — Now Just "Developers"

2017 Guide: The Scrum Team consisted of a Product Owner, a Scrum Master, and a Development Team — a distinct sub-group responsible for delivering the Increment.

2020 Guide: The "Development Team" as a separate entity is gone. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. All members of the Scrum Team may contribute to development work.

PSM I exam implication: Questions that refer to the "Development Team" as a separate group are referencing outdated language. The correct term is Developers. If an exam question asks who creates the Sprint Backlog or who is responsible for the Increment, the answer is Developers — not the Development Team.

2. Three "Roles" → Three "Accountabilities"

2017 Guide: Scrum defined three roles: Product Owner, Scrum Master, and Development Team.

2020 Guide: These are now three accountabilities within the Scrum Team. The language shift is intentional — these are not job titles or org chart positions. They are sets of responsibilities that must be fulfilled.

PSM I exam implication: The word "accountability" appears throughout the 2020 Guide in specific, precise ways. The Scrum Master is accountable for the Scrum Team's effectiveness. The Product Owner is accountable for maximising the value of the product. Understanding accountability language — not just role definitions — is essential for answering questions correctly.

3. Product Goal Added as the Commitment for the Product Backlog

2017 Guide: The Product Backlog was described as an ordered list of everything needed in the product. No formal "goal" concept was attached to the backlog itself.

2020 Guide: The Product Goal is introduced as a new concept — the long-term objective for the Scrum Team. It is the commitment associated with the Product Backlog. The Scrum Team works toward the Product Goal one Sprint at a time.

PSM I exam implication: This is a net-new concept that did not exist in 2017. Questions about the Product Goal, its relationship to the Product Backlog, and who is responsible for it (the Product Owner) are fair game on the exam. Know that the Product Goal is described as the commitment of the Product Backlog.

4. Sprint Goal and Definition of Done Explicitly Named as Commitments

2017 Guide: Sprint Goal and Definition of Done existed but were not grouped together under a shared concept.

2020 Guide: Each Scrum artifact has a corresponding commitment: the Product Backlog has the Product Goal, the Sprint Backlog has the Sprint Goal, and the Increment has the Definition of Done. This three-part structure — artifact plus commitment — is explicit and symmetrical.

PSM I exam implication: Memorise the artifact-to-commitment mapping. Questions may ask which commitment belongs to which artifact, or what the purpose of the commitment is (to measure progress and reinforce empiricism). The Definition of Done, in particular, is described as a formal commitment — not merely a team convention.

5. Self-Organising → Self-Managing

2017 Guide: Scrum Teams were described as self-organising — they chose how best to accomplish their work.

2020 Guide: Scrum Teams are self-managing. The distinction is deliberate and meaningful. Self-managing means the team internally decides who does the work, when they do it, and how they do it. This is a broader and more explicit grant of autonomy than self-organising implied.

PSM I exam implication: If you see "self-organising" in an answer option on the PSM I exam, treat it with caution — it is 2017 language. The correct 2020 term is self-managing. Questions testing whether someone external to the Developers (including the Scrum Master or Product Owner) can assign tasks to Developers are testing this principle directly.

6. Release Planning and Release Sprint Removed

2017 Guide: The Guide made references to release planning and, in some interpretations, the concept of a Release Sprint.

2020 Guide: These concepts are gone entirely. Scrum does not prescribe when releases happen. A usable Increment must exist at the end of every Sprint, but the decision to release it is separate from the Scrum framework. Releases can happen at any time — including multiple times within a Sprint.

PSM I exam implication: Do not confuse the Sprint Review (an inspect-and-adapt event) with a release gate. The Increment must be usable at the end of each Sprint, but "usable" does not mean "released." Questions about release cadence have a consistent answer: Scrum does not define it.

7. Less Prescriptive — Applicable to Any Domain

2017 Guide: The Scrum Guide contained language and examples oriented toward software development.

2020 Guide: Software-specific language was removed. Scrum is now explicitly presented as a framework applicable to any complex work — not just software. References to engineering practices, testing, and software delivery were stripped out or generalised.

PSM I exam implication: The exam will not assume a software context. Questions may describe Scrum applied to marketing, operations, research, or any other domain. The framework behaves identically regardless of context — the same accountabilities, events, artifacts, and commitments apply.

What to Unlearn If You Studied the 2017 Guide

If your Scrum knowledge comes from pre-2020 training, courses, or the previous Guide, these are the specific things to actively replace:

• "Development Team" → replace with "Developers"
• "Roles" → replace with "accountabilities"
• "Self-organising" → replace with "self-managing"
• No concept of Product Goal → learn it as the commitment of the Product Backlog
• Artifacts without named commitments → learn the three artifact-commitment pairs
• Release Sprint as a Scrum concept → remove entirely

The Scrum Guide 2020 is 13 pages and available free at scrumguides.org. Reading it directly — even if you have studied Scrum extensively — is the single most reliable way to calibrate your knowledge to the version the PSM I exam actually tests.