Chapter 1 of 21
Orientation: PSM I Exam, Scrum Guide 2020, and How to Study
Step into the world of Professional Scrum Master I with a clear map of the exam, the Scrum Guide 2020, and a practical study strategy so you know exactly how to invest your time for a first‑attempt pass.
Big Picture: Your PSM I Orientation
Your PSM I Starting Point
In this module you will get: a clear picture of the current PSM I exam, a mental map of the Scrum Guide 2020, and a practical study strategy aimed at a first‑attempt pass.
This Course Is Your Main Path
This Skarp course is already aligned with the present PSM I focus, so you can treat it as your primary prep path. Later diagnostics, mocks, and gap guides build directly on what you learn here.
Three Anchor Ideas
1) Scrum is a framework, not a checklist. 2) Scrum is founded on empiricism and lean thinking. 3) The Scrum Guide 2020 is the single source of truth for all Scrum framework questions on the exam.
PSM I Exam Format, Timing, and Scoring (Current View)
Core Exam Stats
Today PSM I is 80 questions in 60 minutes. Most are single‑answer multiple choice, with some multiple‑answer and true/false. You must score at least 85% (68 correct) to pass.
Closed Book in Practice
The exam is designed as closed book. With 80 questions in 60 minutes, you have less than a minute per question. You need the ideas in your head, not in another tab.
Key Content Clusters
Questions cluster around: Scrum theory and values; Scrum Team accountabilities; events; artifacts and their commitments; and applying Scrum in realistic situations.
Scrum Guide 2020: Your Canonical Reference
Why 2020 Matters
The Scrum Guide 2020 is the current official version and the foundation for all Scrum framework questions on PSM I. It is short, dense, and every sentence can matter.
Updates in 2020
The 2020 Guide removed terms like “Development Team”, introduced a single Scrum Team with Developers, and stressed one team, one Product Goal, using less IT‑specific language.
Source of Truth
If your workplace practice conflicts with the Guide, the exam expects the Guide. When in doubt between options that could work, pick the one strictly aligned with Scrum Guide 2020.
Core Scrum Building Blocks You Must Know Cold
Canonical Definitions
PSM I questions lean heavily on the exact Scrum Guide 2020 definitions for the Scrum Team, roles, artifacts, and events. These phrases are your reference points on the exam.
Team and Roles
Key definitions: Scrum Team, Product Owner, Scrum Master, and Developers. Each describes a specific accountability, not job titles. The whole team shares focus on one Product Goal.
Artifacts and Goals
You must know Product Backlog, Sprint Backlog, Increment, Product Goal, Sprint Goal, and Definition of Done, and be able to spot answers that misuse or blur these concepts.
Real-World Scenario: When the Exam Disagrees With Your Workplace
Your Workplace vs. Scrum
Many organizations say they use Scrum but keep project managers assigning tasks, limit access to stakeholders, or treat Scrum Masters as tool admins. The exam does not accept that as Scrum.
Sample Scenario
In a typical exam‑style scenario, a project manager assigns tasks, the Scrum Master just reports status, and the Product Owner does not manage the Product Backlog. You must judge this by the Guide.
Choosing the Best Answer
Using the official accountabilities, you conclude that key Scrum responsibilities are not fulfilled, so the best answer is that this is not Scrum, regardless of what the company calls it.
Thought Exercise: Map Your Current Understanding
Use this short reflection to calibrate where you are starting from. Pause after each question and answer honestly for yourself.
- How familiar are you with Scrum right now?
- Never used it
- Worked in a team that claimed to use Scrum
- Acted as Developer, Product Owner, or Scrum Master
- Which of these can you already explain, without notes, in 2–3 sentences?
- Scrum Team
- Product Owner
- Scrum Master
- Developers
- Sprint
- Product Backlog, Sprint Backlog, Increment
- Product Goal, Sprint Goal, Definition of Done
- Where do you feel least confident?
- Theory (empiricism, lean thinking, pillars, values)
- Accountabilities (who is accountable for what)
- Events (what happens, who attends, timeboxes)
- Artifacts and commitments
- Applying Scrum in “messy” real‑world situations
- Time reality check:
- How many hours per week can you realistically invest in the next month?
- On how many days per week can you do at least 20 focused minutes?
Write down your answers. You will use them to customize your study plan in a later step. In the Skarp system, your upcoming diagnostic will also help confirm (or challenge) this self‑assessment by showing how you perform across domains.
The more honest you are now, the more efficiently you can use the rest of this course.
Designing a Study Plan That Fits PSM I (and Your Life)
How Much Study Time?
Most learners need roughly 15–30 focused hours over 2–4 weeks for a solid first‑attempt shot. The exact number depends on your background with Scrum and agile work.
Three Main Phases
1) Foundation: learn core theory and definitions. 2) Deep dives: accountabilities, events, artifacts. 3) Practice and feedback: diagnostics, mocks, and gap‑driven review.
Spaced Reinforcement
Use Skarp’s spaced review and short daily sessions to keep ideas fresh. Regular 5–10 minute reviews are more powerful than one big last‑minute cram.
Sample 2-Week Study Plan (Adapt It to Your Schedule)
Week 1 Focus
In week 1, build foundations: orientation, Scrum theory and values, team accountabilities, events, and artifacts. Aim for 30–60 focused minutes on most days.
Week 2 Focus
In week 2, shift toward diagnostics, mocks, and targeted review. Use your gap guide to focus on weaker domains rather than re‑reading what you already know.
Adapt to Your Life
Use this 2‑week plan as a template, not a rule. Move sessions around, shorten or lengthen them, but keep the structure: learn, practice, diagnose, then reinforce.
Quick Check: Exam and Guide Orientation
Test your understanding of key orientation facts before we go deeper.
Which statement best reflects how you should treat the Scrum Guide 2020 when preparing for PSM I?
- It is one of several optional references; the exam mostly tests company-specific practices.
- It is the canonical reference for the Scrum framework; when in doubt, answers must align with it even if your workplace differs.
- It was replaced after 2022, so only older questions still use it.
- It is mainly background reading; the exam ignores its exact wording.
Show Answer
Answer: B) It is the canonical reference for the Scrum framework; when in doubt, answers must align with it even if your workplace differs.
For PSM I, the Scrum Guide 2020 is the canonical, current reference for the Scrum framework. If an answer conflicts with it, that answer is wrong for the exam, regardless of what any specific organization does.
Flashcards: Core Scrum Definitions
Use these cards to start locking in the canonical Scrum Guide 2020 definitions that the exam leans on.
- Scrum
- Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
- Scrum Team
- The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
- Product Owner
- The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
- Scrum Master
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
- Developers
- Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
- Sprint
- Sprints are the heartbeat of Scrum, where ideas are turned into value.
- Product Backlog
- The Product Backlog is an emergent, ordered list of what is needed to improve the product.
- Sprint Backlog
- The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
- Increment
- An Increment is a concrete stepping stone toward the Product Goal.
- Product Goal
- The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
- Sprint Goal
- The Sprint Goal is the single objective for the Sprint.
- 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.
- Empiricism (Scrum foundation)
- Scrum is founded on empiricism and lean thinking.
Quick Check: Study Strategy and Common Traps
Confirm that you understand how to aim your study time and avoid frequent mistakes.
Which preparation approach is MOST aligned with succeeding on PSM I?
- Memorize a list of “correct” meeting lengths and obscure rules, and hope similar questions appear.
- Focus on deeply understanding Scrum’s principles, accountabilities, events, and artifacts, then use diagnostics and mocks to reveal and close your gaps.
- Ignore practice questions and just read the Scrum Guide 2020 once the night before.
- Study only how your current company does “Scrum”, since that is the most realistic.
Show Answer
Answer: B) Focus on deeply understanding Scrum’s principles, accountabilities, events, and artifacts, then use diagnostics and mocks to reveal and close your gaps.
The exam tests deep understanding and application of Scrum, not shallow memorization or company-specific practices. Combining conceptual learning with diagnostics, mocks, and targeted review is the most effective strategy.
Next Steps: How to Use This Course From Here
Where to Go Next
Next, move into the Scrum theory and values module. Many exam questions depend on a solid grasp of empiricism, lean thinking, and the Scrum pillars and values.
Use Diagnostics Early
Take the first diagnostic soon after the core modules. Let the gap guide show you which domains to focus on, rather than waiting until you “feel ready”.
Connect Everything Back
As you continue, keep mapping scenarios to the core definitions and artifacts. This habit turns scattered facts into an integrated understanding that PSM I is designed to test.
Key Terms
- Scrum
- Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
- Sprint
- Sprints are the heartbeat of Scrum, where ideas are turned into value.
- Increment
- An Increment is a concrete stepping stone toward the Product Goal.
- Developers
- Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
- Empiricism
- Scrum is founded on empiricism and lean thinking.
- Scrum Team
- The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
- Sprint Goal
- The Sprint Goal is the single objective for the Sprint.
- Product Goal
- The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
- Scrum Master
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
- Product Owner
- The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
- Sprint Backlog
- The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
- Product Backlog
- The Product Backlog is an emergent, ordered list of what is needed to improve the product.
- 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.