Scrum.org PSM I Cheat Sheet

Review a compact Scrum.org Professional Scrum Master I (PSM I) cheat sheet for Scrum theory, accountabilities, events, artifacts, Done, self-management, and empiricism traps.

Use this PSM I cheat sheet to review exact Scrum Guide logic before mixed practice. PSM I questions reward precise Scrum reasoning: empiricism, accountabilities, events, artifacts, commitments, self-management, and Done.

Open PSM I practice for the free 80-question diagnostic, topic pages, timed mocks, and the full PM Mastery Scrum.org bank.

Exam Snapshot

ItemPSM I cue
ProviderScrum.org
ExamProfessional Scrum Master I
Format focus80 questions in 60 minutes
Practice behaviorchoose the Scrum answer that preserves empiricism, accountabilities, event purpose, artifact transparency, and Done
PM Mastery statuslive practice available

Scrum.org Checklist

AreaWhat to knowCommon trap
Scrum theorytransparency, inspection, adaptation, values, and empirical controltreating Scrum as a delivery process with fixed steps
AccountabilitiesScrum Master, Product Owner, Developers, and Scrum Teamadding roles outside Scrum to solve accountability confusion
Eventspurpose, participants, timing, and outcomes of each eventturning events into reporting meetings
Artifacts and commitmentsProduct Backlog/Product Goal, Sprint Backlog/Sprint Goal, Increment/Definition of Doneconfusing artifact ownership and commitment intent
Done and Incrementusable Increment, shared Definition of Done, quality, and transparencycounting unfinished work as done because effort was spent
Self-managementDevelopers choose how to do work and adapt the planassigning tasks or having managers direct the Sprint

Must-Know Distinctions

  • Product Goal versus Sprint Goal: product direction versus short-term Sprint objective.
  • Product Backlog versus Sprint Backlog: ordered product work versus Sprint plan owned by Developers.
  • Sprint Review versus Sprint Retrospective: inspect product outcome versus inspect team process.
  • Definition of Done versus acceptance criteria: shared quality commitment versus item-specific expectations.
  • Accountability versus responsibility: Scrum defines accountabilities clearly; delivery tasks are not assigned by the Scrum Master.
  • Forecast versus commitment: forecasts are transparent plans, not guarantees.

Common Traps

  • Adding a project manager, team lead, or proxy Product Owner to solve a Scrum problem.
  • Treating Daily Scrum as a status report to the Scrum Master.
  • Allowing the Product Owner to change Sprint work unilaterally.
  • Skipping Retrospective because improvement feels obvious.
  • Releasing work that does not meet the Definition of Done.
  • Using velocity to compare people or force future commitments.

Practice Strategy

When you miss a PSM I item, rewrite the Scrum Guide rule in your own words and identify which Scrum element the distractor distorted. Move to mixed timed sets only after event purpose, accountabilities, artifacts, and commitments feel automatic.

Revised on Monday, May 25, 2026