Home/ agile-scrum/ Professional Scrum Master I/ Cheat Sheet
Professional Scrum Master I· Exam reference card · 2026 · Edureify AI
Professional Scrum Master I

Professional Scrum Master I Cheat Sheet

PSM I Tests Pure Scrum — Not Hybrid, Not Agile in General

Scrum.org doesn't test what you think works. It tests the Scrum Guide verbatim. Any deviation is wrong.

Check Your Readiness →
Among the harder certs
Avg: Approximately 65–70%
Pass: 750 / 1000
Most candidates understand Professional Scrum Master I concepts — and still fail. This exam tests how you apply knowledge under pressure.
Core Framework

The Scrum Framework: Pillars, Values, and Accountabilities

PSM I is based on the 2020 Scrum Guide. Know it word for word. The exam penalizes common practice answers that deviate from the Guide. There is no partial credit for approximately Scrum.

  1. 01
    Pillars: Transparency, Inspection, Adaptation
  2. 02
    Values: Commitment, Focus, Openness, Respect, Courage
  3. 03
    Accountabilities: Scrum Master, Product Owner, Developers
  4. 04
    Events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective
  5. 05
    Artifacts with Commitments: Product Backlog (Product Goal), Sprint Backlog (Sprint Goal), Increment (DoD)
Scenario Traps

Wrong instinct vs correct approach

Developers can't complete all Sprint Backlog items by Sprint end
✕ Wrong instinct

Extend the Sprint or move incomplete items to the next Sprint as-is

✓ Correct approach

Incomplete items return to the Product Backlog to be re-estimated and re-prioritized by the Product Owner; the Sprint ends on schedule

A stakeholder asks the Scrum Master for a status update on the project
✕ Wrong instinct

Provide the update since the Scrum Master coordinates communication

✓ Correct approach

Direct stakeholders to the Sprint Review and Product Backlog for transparency; the Scrum Master facilitates visibility, not reporting

The team is not following the Definition of Done
✕ Wrong instinct

The Scrum Master should enforce the DoD by reviewing all work

✓ Correct approach

The Scrum Master coaches the team on why the DoD matters; the Developers own and enforce the Definition of Done for each Increment

Quick Rules

Know these cold

  • ▸ Developers self-organize — no one assigns work to them
  • ▸ Sprint length is fixed; it cannot be extended under any circumstance
  • ▸ The Daily Scrum belongs to Developers — not the Scrum Master
  • ▸ Sprint Backlog is owned by Developers; Product Backlog is owned by the Product Owner
  • ▸ Only the Product Owner can cancel a Sprint — no one else
  • ▸ The Increment must meet the Definition of Done every Sprint
  • ▸ Sprint Review = inspect product; Retrospective = inspect team process
Self Check

Can you answer these without checking your notes?

In this scenario: "Developers can't complete all Sprint Backlog items by Sprint end" — what should you do first?
Incomplete items return to the Product Backlog to be re-estimated and re-prioritized by the Product Owner; the Sprint ends on schedule
In this scenario: "A stakeholder asks the Scrum Master for a status update on the project" — what should you do first?
Direct stakeholders to the Sprint Review and Product Backlog for transparency; the Scrum Master facilitates visibility, not reporting
In this scenario: "The team is not following the Definition of Done" — what should you do first?
The Scrum Master coaches the team on why the DoD matters; the Developers own and enforce the Definition of Done for each Increment
Failure Patterns

Common Exam Mistakes — What candidates get wrong

Assigning tasks to Developers during Sprint Planning

The Scrum Guide says Developers select their own work from the Product Backlog. No one assigns work to Developers — they self-manage. The Scrum Master facilitating task assignment is a trap answer.

Treating the Daily Scrum as a status meeting for the Scrum Master

The Daily Scrum is for Developers to inspect progress toward the Sprint Goal. The Scrum Master doesn't run it and doesn't need to attend.

Allowing the Product Owner to change the Sprint Backlog mid-Sprint

Only Developers can modify the Sprint Backlog during a Sprint. The Product Owner can negotiate scope with Developers but cannot unilaterally add or remove work.

Thinking the Scrum Master manages the team

The Scrum Master is a servant-leader who coaches, facilitates, and removes impediments. They do not manage Developers, make technical decisions, or direct Sprint work.

Confusing Sprint Review with Sprint Retrospective

Sprint Review is about the product (inspect the Increment, adapt the Product Backlog) with stakeholders. Sprint Retrospective is about the team's process and is internal to the Scrum Team.

Believing a Sprint can be extended if the Sprint Goal isn't met

Sprints have a fixed timebox — they cannot be extended. If the Sprint Goal cannot be met, the Product Owner may cancel the Sprint. Sprints are never extended.

PSM I's 85% threshold leaves no room for Scrum misunderstandings. Test your Scrum Guide accuracy now.

Start Diagnostic Test → View all exams