Use this for last‑mile review. Pair it with the Syllabus
for coverage and Practice
to lock in speed.
PSM I: what it really tests
PSM I rewards:
- Scrum Guide precision (terms and constraints)
- understanding purpose, not just definitions
- choosing actions that preserve empiricism and self-management
If an option reduces transparency, creates handoffs, or turns Scrum into a “status machine,” it’s often wrong.
Empiricism + Scrum values (must‑know)
Empiricism pillars: Transparency, Inspection, Adaptation.
Scrum values: Commitment, Focus, Openness, Respect, Courage.
Rule: The “best answer” usually increases transparency, enables inspection via working results, and adapts the plan without breaking quality.
Accountabilities (roles) — exam-grade wording
| Accountability |
Responsible for |
Not responsible for |
| Product Owner |
maximizing value, ordering Product Backlog |
managing the team’s work day-to-day |
| Scrum Master |
Scrum effectiveness; coaching; removing impediments |
being the team’s manager |
| Developers |
creating the Increment; Sprint Backlog |
having work assigned by others |
Rule: Scrum is built around one Product Owner and one Product Backlog.
Events — purpose beats ritual
| Event |
Purpose (1 sentence) |
Common trap |
| Sprint |
a timebox to create a Done Increment |
treating Sprint length as flexible |
| Sprint Planning |
set Sprint Goal + plan work |
picking too much work without capacity thinking |
| Daily Scrum |
adapt the plan for the next 24h |
status report to stakeholders |
| Sprint Review |
inspect Increment + adapt backlog |
turning it into a demo-only meeting |
| Retrospective |
improve process + relationships |
producing no actionable improvement |
Timeboxes (1‑month Sprint baseline): Planning 8h, Daily 15m, Review 4h, Retro 3h.
Artifacts + commitments — what to say in answers
| Artifact |
Commitment |
“Best answer” cue |
| Product Backlog |
Product Goal |
clarify value, order by risk/value |
| Sprint Backlog |
Sprint Goal |
adapt plan, keep goal stable where possible |
| Increment |
Definition of Done |
quality is non-negotiable |
Definition of Done (DoD)
- A DoD creates a shared quality bar.
- If work doesn’t meet DoD, it’s not part of the Increment.
- Repeated quality problems → improve the system / DoD, not heroics.
DoD vs acceptance criteria (common trap)
- Acceptance criteria are specific to a Product Backlog Item (PBI) and clarify what “acceptable” means for that item.
- Definition of Done is the shared quality bar for the Increment; it makes “Done” transparent.
- “Definition of Ready” is not a Scrum artifact/commitment; treat it as an optional checklist, not a gate that replaces refinement.
Sprint mechanics (high-yield rules)
- A Sprint can be canceled only by the Product Owner.
- Scope can be clarified/re-negotiated during the Sprint as long as the Sprint Goal isn’t endangered.
- The Sprint Goal provides flexibility; the plan evolves.
Scenario pickers (fast elimination)
When something is unclear
- Choose: ask clarifying questions, make assumptions explicit, split into smaller increments.
- Avoid: “start building” without shared understanding.
When stakeholders interrupt developers daily
- Choose: Scrum Master coaches stakeholders to use Sprint Review and agreed channels.
- Avoid: adding more meetings or a “daily status report.”
When work is late
- Choose: re-plan, make work visible, negotiate scope with PO.
- Avoid: extend Sprint length or cut quality.
Multiple teams on one product
- Choose: one Product Backlog and one Product Owner; coordination happens without fragmenting value ownership.
- Avoid: multiple competing backlogs/POs for the same product.
Quick glossary (must-know)
- Empiricism: decisions based on evidence and feedback.
- Self-management: team decides how to do the work.
- Transparency: visible work and constraints (no hidden queues).
Ready to drill? Open PSM I practice →
or jump into the app: /app/pmp-exam-prep/#/topic-selection/scrumorg-psm1
.