Skarp
Professional Scrum Master I (PSM I) Complete Exam-Ready Mastery Course
A deep, exam-focused journey through the Scrum Guide 2020 and Scrum.org’s Professional Scrum Master I (PSM I) blueprint. This course builds rigorous, test-ready understanding of the Scrum framework, theory, artifacts, events, and the Scrum Master’s leadership role using scenarios, traps, and exam-style reasoning.
Course Content
21 modules · 9h 27m total
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.
Scrum Foundations: Framework, Empiricism, and Scrum Values
Trace the roots of Scrum in complex work, see how empiricism shapes every part of the framework, and connect the five Scrum values to real behaviors inside a Scrum Team.
The Scrum Team: One Cohesive Unit Focused on the Product Goal
Meet the Scrum Team as the core unit of Scrum, unpack how its size, composition, and focus drive agility, and confront common exam traps about sub-teams and reporting lines.
Scrum Accountabilities I: Product Owner and Product Backlog Ownership
Step into the Product Owner’s shoes and see how owning the Product Backlog, Product Goal, and value decisions shapes every Sprint and every exam scenario.
Scrum Accountabilities II: Scrum Master as True Leader and Servant-Leader
Look beyond the title to understand how the Scrum Master establishes Scrum, coaches the organization, and navigates common misunderstandings about authority and control.
Scrum Accountabilities III: Developers and Creating the Increment
Zoom in on Developers as the people who turn ideas into value each Sprint, and clarify how their accountability differs from the older ‘Development Team’ concept.
The Sprint: Heartbeat of Scrum and Container for All Work
Enter the Sprint as the fixed-length heartbeat of Scrum, explore its rules and constraints, and dissect tricky questions about changes, cancellation, and multiple Sprints.
Sprint Planning: From Product Goal to Sprint Goal and Sprint Backlog
Watch the Scrum Team design a Sprint from scratch, connecting the Product Goal to a clear Sprint Goal and an actionable Sprint Backlog that Developers truly own.
Daily Scrum: Inspect-and-Adapt Engine for Developers
Step into a focused 15‑minute Daily Scrum and see how Developers use it to adapt their plan toward the Sprint Goal, avoiding status-report anti-patterns that the exam loves to test.
Sprint Review: Inspecting the Increment and Adapting the Product Backlog
Join the Scrum Team and stakeholders at Sprint Review to inspect the latest Increment, gather feedback, and adapt the Product Backlog in response to new information.
Sprint Retrospective: Continuous Improvement for the Scrum Team
Sit in on a Sprint Retrospective where the Scrum Team inspects itself, chooses concrete improvements, and strengthens how it lives the Scrum values.
Artifacts I: Product Backlog, Product Goal, and Product Backlog Refinement
Trace how ideas become ordered Product Backlog items guided by a clear Product Goal, and unpack why refinement is ongoing work rather than a formal Scrum event.
Artifacts II: Sprint Backlog, Sprint Goal, and Adapting the Plan
Watch Developers transform selected Product Backlog items into a living Sprint Backlog anchored by a Sprint Goal, and see how this plan evolves as new information emerges.
Artifacts III: Increment, Definition of Done, and Ensuring Quality
Follow work as it becomes a usable Increment that meets the Definition of Done, and see how this commitment protects transparency, quality, and long‑term sustainability.
Scrum Theory in Action: Empiricism Across All Events and Artifacts
Walk through a full Sprint and pinpoint how transparency, inspection, and adaptation appear in each event and artifact, strengthening your ability to reason through tricky theory questions.
Product Backlog Management in Practice: Estimation, Ordering, and Adaptation
Observe how a Product Owner and Scrum Team refine, estimate, and reorder Product Backlog items as they learn, and examine how Product Goal and Sprint Goals guide these decisions.
Self-Managing Teams: Who Decides What, When, and How
Step inside a truly self-managing Scrum Team to see how decisions about work, collaboration, and quality are made without a traditional manager pulling the strings.
Scrum Master Services: To the Product Owner, Developers, and the Organization
Follow a Scrum Master through a Sprint as they coach, facilitate, and remove impediments for the Product Owner, Developers, and the wider organization—without becoming a task manager.
Transparency and Quality: Making Work and Progress Visible
See how artifacts, commitments, and the Definition of Done create transparency, and explore how weak transparency leads to poor decisions, rework, and exam trick questions.
Integrating Scrum Theory, Values, and Practice for Exam Scenarios
Bring together theory, values, events, and roles to reason through nuanced PSM I-style questions where more than one answer looks plausible at first glance.
Final Review and PSM I Exam Tactics
Consolidate your knowledge with a structured review of all domains, then sharpen your timing, guessing, and stress‑management tactics for the 80‑question, 60‑minute PSM I exam.
Read the Textbook
Read every chapter for free, right here in your browser.
Welcome to your starting point for the Professional Scrum Master I (PSM I) journey.
In this module, you will get three things: A clear picture of the PSM I exam as it exists today (Scrum.org information up to 2026). A mental map of the Scrum Guide 2020, which is the canonical reference for Scrum in the exam. A practical, realistic study strategy designed so you can aim for a first‑attempt pass without hunting for extra materials.
This course is already aligned with the current exam focus, so you can treat it as your primary preparation path. You will see how each later module, mock exam, and diagnostic in the Skarp path connects back to the core of Scrum.
Study Flashcards
Key concepts from this course as flashcard pairs.
Orientation: PSM I Exam, Scrum Guide 2020, and How to Study
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.
+7 more flashcards
Scrum Foundations: Framework, Empiricism, and Scrum Values
Scrum (definition)
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
Empiricism in Scrum
Scrum is founded on empiricism and lean thinking. Empiricism means decisions are based on what is known through transparency, inspection, and adaptation.
Three pillars of empiricism
Transparency, inspection, adaptation.
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.
+9 more flashcards
The Scrum Team: One Cohesive Unit Focused on the Product Goal
Scrum (definition)
Scrum: "Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems."
Scrum Team (definition)
Scrum Team: "The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal."
Product Owner (definition)
Product Owner: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."
Scrum Master (definition)
Scrum Master: "The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide."
Developers (definition)
Developers: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."
Product Goal (definition)
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."
+6 more flashcards
Scrum Accountabilities I: Product Owner and Product Backlog Ownership
Canonical definition of Product Owner (must know for PSM I)
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
Canonical definition of Product Backlog
The Product Backlog is an emergent, ordered list of what is needed to improve the product.
Who is accountable for ordering the Product Backlog?
The Product Owner is accountable for ordering the Product Backlog.
Who estimates the effort of Product Backlog items?
Developers are accountable for estimates, because they do the work and understand the effort.
What does the Product Goal describe?
The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
Who can decide to change the Product Goal?
The Product Owner decides to change the Product Goal, considering input from the Scrum Team and stakeholders.
+4 more flashcards
Scrum Accountabilities II: Scrum Master as True Leader and Servant-Leader
Scrum Master (canonical definition)
"The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide."
Servant-leadership in Scrum
A leadership stance where the Scrum Master serves the Scrum Team, Product Owner, and organization by coaching, facilitating, and removing impediments rather than using positional power.
One thing the Scrum Master SHOULD do
Coach the Scrum Team and organization in understanding and applying Scrum, including empiricism (transparency, inspection, adaptation) and Scrum values.
One thing the Scrum Master should NOT do
Assign tasks to Developers or manage their individual performance reviews; Developers self-manage and line management is a different role.
Scrum value most needed to challenge anti-Scrum practices
Courage: the Scrum Master needs courage to challenge harmful practices, surface problems, and protect the team’s focus on the Sprint and Product Goals.
Service to the Product Owner
Coaching on Product Backlog management, facilitating stakeholder collaboration, and helping communicate clear Product and Sprint Goals.
+1 more flashcards
Scrum Accountabilities III: Developers and Creating the Increment
Canonical definition of Developers
Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
Who owns the Sprint Backlog?
Developers own the Sprint Backlog, including the selected Product Backlog items and the actionable plan for delivering the Increment.
What is an Increment?
An Increment is a concrete stepping stone toward the Product Goal.
What 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.
Who is accountable for the quality of the Increment?
Developers are accountable for ensuring the Increment meets the Definition of Done and is usable.
Who decides what to build and in which order?
The Product Owner, who is accountable for maximizing the value of the product and owns the Product Backlog.
+4 more flashcards
The Sprint: Heartbeat of Scrum and Container for All Work
Sprint (canonical definition)
Sprints are the heartbeat of Scrum, where ideas are turned into value.
Maximum Sprint length
One month or less. The Scrum Team should keep Sprint length stable to support empiricism and predictability.
Sprint Backlog (canonical definition)
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).
Who can cancel a Sprint?
Only the Product Owner can cancel a Sprint, and only when the Sprint Goal becomes obsolete.
What happens to Done work when a Sprint is cancelled?
Work that meets the Definition of Done becomes part of the Increment and may be released; incomplete work returns to the Product Backlog.
Can scope change during a Sprint?
Yes. The Product Owner and Developers can clarify and renegotiate scope as long as changes do not endanger the Sprint Goal and quality does not drop.
+4 more flashcards
Sprint Planning: From Product Goal to Sprint Goal and Sprint Backlog
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.
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.
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.
Daily Scrum: Inspect-and-Adapt Engine for Developers
What is the timebox of the Daily Scrum?
15 minutes, held every working day of the Sprint.
Who is required to attend the Daily Scrum?
Developers. The event is for Developers of the Scrum Team.
Primary purpose of the Daily Scrum?
To inspect progress toward the Sprint Goal and adapt the Sprint Backlog, adjusting the plan for the next 24 hours.
Who owns and can change the Sprint Backlog during the Sprint?
Developers. They own the Sprint Backlog and adapt it as they learn.
What must discussions in the Daily Scrum focus on?
Progress toward the Sprint Goal and the plan to achieve it, not individual status reporting.
Is the three-question format mandatory in the Daily Scrum?
No. Developers choose the structure as long as they inspect and adapt toward the Sprint Goal.
+1 more flashcards
Sprint Review: Inspecting the Increment and Adapting the Product Backlog
Purpose of Sprint Review
To inspect the outcome of the Sprint (the Increment) and determine future adaptations by collaborating with stakeholders, primarily by updating the Product Backlog and product direction.
Timebox for Sprint Review (one‑month Sprint)
A maximum of 4 hours. For shorter Sprints, the Sprint Review is usually shorter.
Who attends the Sprint Review?
The entire Scrum Team (Product Owner, Scrum Master, Developers) and invited stakeholders who are needed to provide feedback and collaborate on product direction.
Main output of Sprint Review
An updated Product Backlog that reflects the latest information about the product, market, and environment, potentially including changes to priorities or even the Product Goal.
Difference: Sprint Review vs Sprint Retrospective (focus)
Sprint Review: focuses on the product and Product Backlog. Sprint Retrospective: focuses on how the work is done (process, tools, team interactions, and Definition of Done).
Role of stakeholders in Sprint Review
They actively inspect the Increment, give feedback, share market and user insights, and collaborate with the Product Owner to influence Product Backlog ordering and product direction.
+3 more flashcards
Sprint Retrospective: Continuous Improvement for the Scrum Team
Sprint Retrospective – main purpose
An opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
Sprint Retrospective – timebox for a 1‑month Sprint
Maximum of 3 hours.
Who attends the Sprint Retrospective?
The entire Scrum Team: Product Owner, Scrum Master, and Developers.
Empiricism in Scrum (canonical phrase)
Scrum is founded on empiricism and lean thinking.
Areas commonly improved in Retrospectives
Processes, tools, relationships, communication, skills, and the Definition of Done.
Definition of Done (canonical)
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
+2 more flashcards
Artifacts I: Product Backlog, Product Goal, and Product Backlog Refinement
Product Backlog (canonical definition)
The Product Backlog is an emergent, ordered list of what is needed to improve the product.
Product Goal (canonical definition)
The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
Scrum Team focus (canonical phrase)
The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
Emergent (in context of Product Backlog)
Emergent means the Product Backlog is continuously evolving: items are added, split, refined, reordered, or removed as the Scrum Team learns and conditions change.
Ordering vs prioritization
Ordering is a clear sequence (1, 2, 3, ...), owned by the Product Owner, used to decide what to do next. Prioritization alone (e.g., High/Medium/Low) is often too fuzzy and is not the Scrum term.
Who is accountable for ordering the Product Backlog?
The Product Owner is accountable for ordering the Product Backlog to maximize the value of the product.
+2 more flashcards
Artifacts II: Sprint Backlog, Sprint Goal, and Adapting the Plan
Sprint Backlog – canonical definition
"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)."
Sprint Goal – canonical definition
"The Sprint Goal is the single objective for the Sprint."
Who owns the Sprint Backlog?
Developers own the Sprint Backlog. They create and update the plan for delivering the Increment and achieving the Sprint Goal.
Can the Sprint Backlog change during the Sprint?
Yes. It is a living plan that Developers update as they learn more, as long as changes still support achieving the Sprint Goal.
What stays stable vs. flexible during a Sprint?
The Sprint Goal is normally stable; the scope (selected items and tasks in the Sprint Backlog) is flexible and can be adapted.
How does the Sprint Backlog support the Daily Scrum?
It provides a transparent view of current work so Developers can inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours.
+1 more flashcards
Artifacts III: Increment, Definition of Done, and Ensuring Quality
Increment (canonical definition)
An Increment is a concrete stepping stone toward the Product Goal.
Definition of Done (canonical definition)
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
Who may define the Definition of Done?
It may be defined by the organization. If the organization does not have one, the Scrum Team must define a Definition of Done that is appropriate for the product. The team can make it more stringent than the organizational standard, but not weaker.
Commitment for the Increment artifact
For the Increment artifact, the commitment is the Definition of Done. The Scrum Team commits to ensuring each Increment meets this Definition.
Usable / potentially releasable Increment
An Increment is usable when it meets the Definition of Done and is integrated so it could be released. The Product Owner decides whether to actually release it.
Handling unfinished work at Sprint end
If work does not meet the Definition of Done, it is not part of the Increment. It returns to the Product Backlog for re‑ordering; Sprints are not extended to finish it.
+2 more flashcards
Scrum Theory in Action: Empiricism Across All Events and Artifacts
Empiricism in Scrum
Scrum is founded on empiricism and lean thinking. Empiricism means decisions are based on observation, experience, and evidence, supported by transparency, inspection, and adaptation.
Three Pillars of Empirical Process Control
Transparency (true state is visible), Inspection (frequent checks of artifacts and progress), Adaptation (changes made when inspection shows deviation from goals or expectations).
Sprint (definition)
Sprints are the heartbeat of Scrum, where ideas are turned into value.
Product Backlog (definition)
The Product Backlog is an emergent, ordered list of what is needed to improve the product.
Sprint Backlog (definition)
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 (definition)
An Increment is a concrete stepping stone toward the Product Goal.
+5 more flashcards
Product Backlog Management in Practice: Estimation, Ordering, and Adaptation
Product Backlog
The Product Backlog is an emergent, ordered list of what is needed to improve the product.
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.
Increment
An Increment is a concrete stepping stone toward the Product Goal.
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).
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.
+4 more flashcards
Self-Managing Teams: Who Decides What, When, and How
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.
+9 more flashcards
Scrum Master Services: To the Product Owner, Developers, and the Organization
Scrum
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
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.
Scrum Team
The Scrum Team is a cohesive unit of professionals focused on one objective at a time, 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.
Product Backlog
The Product Backlog is an emergent, ordered list of what is needed to improve the product.
+6 more flashcards
Transparency and Quality: Making Work and Progress Visible
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 Backlog
The Product Backlog is an emergent, ordered list of what is needed to improve the product.
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 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).
Sprint Goal
The Sprint Goal is the single objective for the Sprint.
+4 more flashcards
Integrating Scrum Theory, Values, and Practice for Exam Scenarios
Empiricism in Scrum
Scrum is founded on empiricism and lean thinking. Empiricism means decisions are based on transparency, inspection, and adaptation in complex, uncertain environments.
Definition of Done (exam importance)
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. Options that weaken or bypass it are usually wrong.
Sprint Backlog ownership
The Sprint Backlog belongs to the Developers. It includes the Sprint Goal (why), selected PBIs (what), and plan (how). Others can influence, but Developers decide how to achieve the Sprint Goal.
Scope change during a Sprint
While the Sprint Goal is fixed, scope can be negotiated between Product Owner and Developers during the Sprint, as long as the Sprint Goal remains achievable.
Scrum Master accountability
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, primarily through coaching, facilitation, and enabling organizational change, not command-and-control.
Scrum vs. organization-specific practices
Scrum defines accountabilities, events, artifacts, and commitments. Practices like story points, standing meetings, or specific tools are optional and must not be treated as Scrum rules in exam answers.
+2 more flashcards
Final Review and PSM I Exam Tactics
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.
+7 more flashcards