Cheat sheet
PSM I Cheat Sheet
Scrum Framework
- 60% of exam
- Empiricism Values Accountabilities Events Artifacts Done
People + Teams
- 20% of exam
- Self-Managing Teams Facilitation Coaching Leadership Impediments
Products + Agility
- 20% of exam
- Product Goal Product Backlog Forecasting Stakeholders Value
Quick Facts
- Exam PSM I
- Credential Professional Scrum Master I
- Owner Scrum.org
- Questions 80
- Time 60 minutes
- Pass 85%
- Cost $200 USD
- Format MC, MA, TF
- Training Not required
- Validity Lifetime
Three Pillars FR
- Transparent inspection enables adaptation.
- Transparency Inspection Adaptation
PO vs Developers FR
Product Owner
- Owns product value
- Orders Product Backlog
- May cancel Sprint
Developers
- Create Increment
- Own Sprint Backlog
- Decide technical approach
- PO what; Developers how
Event Picker FR
- Need Sprint objective → Sprint Planning ( Create Sprint Goal )
- Choose Sprint work → Sprint Planning ( Developers select )
- Inspect daily progress → Daily Scrum ( Developers only )
- Adapt Sprint Backlog → Daily Scrum ( Protect goal )
- Inspect product outcome → Sprint Review ( Stakeholders collaborate )
- Adapt Product Backlog → Sprint Review ( PO accountable )
- Improve team process → Retrospective ( Last event )
- Goal becomes obsolete → Cancel Sprint ( PO only )
Empiricism FR
- Empiricism Knowledge from experience
- Lean thinking Reduce waste
- Transparency Visible common truth
- Inspection Check progress often
- Adaptation Adjust from learning
- Complex work Unknowns expected
- Scrum Lightweight framework
Scrum Values FR
- Committed focused people openly respect courage.
- Commitment Focus Openness Respect Courage
Review vs Retro FR
Sprint Review
- Inspect product
- Adapt Product Backlog
- Stakeholders attend
Retrospective
- Inspect team
- Improve effectiveness
- Scrum Team attends
- Product vs process
Values FR
- Commitment Support goals
- Focus Sprint work
- Openness Expose reality
- Respect Capable people
- Courage Right thing
- Trust Empiricism enabler
Artifact Commitments FR
- Product, Sprint, Increment need commitments.
- Product Goal Sprint Goal Definition of Done
Done vs Release FR
Done
- Meets DoD
- Usable Increment
- Quality gate
Release
- Business decision
- PO accountable
- May happen anytime
- Done enables release
Accountabilities FR
- Scrum Team One cohesive unit
- Product Owner Maximizes value
- Scrum Master Accountable for Scrum
- Developers Create Increment
- Stakeholders Outside Scrum Team
- Team size Ten or fewer
- Cross-functional All skills inside
- Self-managing Decide who/how/what
Planning Topics FR
- Plan why, what, then how.
- Why valuable What Done How deliver
Events FR
- Sprint One month max
- Planning Why/what/how
- Daily Scrum 15 minutes
- Sprint Review Inspect outcome
- Retrospective Improve effectiveness
- Planning box 8 hours max
- Review box 4 hours max
- Retro box 3 hours max
Artifacts + Commitments FR
- Product Backlog Emergent ordered list
- Product Goal Long-term objective
- Sprint Backlog Goal/items/plan
- Sprint Goal Single Sprint objective
- Increment Usable Done work
- Definition of Done Quality commitment
- Commitments Artifact transparency
- Undone work Returns to backlog
Facilitate vs Manage PE
Facilitate
- Guide conversation
- Preserve neutrality
- Enable decisions
Manage
- Assign tasks
- Direct people
- Control execution
- Enable, do not command
Scrum Master Picker PE
- Team lacks Scrum → Teach ( Guide basics )
- Team owns issue → Coach ( Build capability )
- Meeting needs structure → Facilitate ( Neutral stance )
- External blocker exists → Remove ( Impediment )
- Manager disrupts team → Coach management ( Servant leadership )
- PO orders poorly → Coach PO ( Value focus )
- Conflict escalates → Facilitate dialogue ( Clarify boundaries )
- ScrumBut appears → Expose impact ( Empirical change )
Scrum Master Service PE
- Coach team Scrum understanding
- Remove impediments Enable progress
- Facilitate events As requested
- Coach PO Effective backlog
- Serve organization Lead adoption
- Cause change Increase effectiveness
- Shield team Reduce disruptions
- Teach Scrum Clarify boundaries
Team Dynamics PE
- Facilitation Neutral process help
- Coaching Grow capability
- Mentoring Share experience
- Teaching Explain Scrum
- Conflict Facilitate clarity
- Safety Speak openly
- Impediment Blocks progress
- Management Supports environment
Product Goal vs Sprint Goal PR
Product Goal
- Long-term target
- Backlog commitment
- One at time
Sprint Goal
- Sprint objective
- Backlog commitment
- Scope can flex
- Target vs step
Product Picker PR
- Need long target → Product Goal ( Backlog commitment )
- Need short focus → Sprint Goal ( Sprint commitment )
- Need value order → Product Backlog ( PO accountable )
- Need delivery plan → Sprint Backlog ( Developers own )
- Need quality line → Definition of Done ( Increment commitment )
- Need market feedback → Sprint Review ( Adapt direction )
- Future is uncertain → Forecast ( Not commitment )
- Feature is risky → Prototype ( Validate value )
Product Ownership PR
- Product value PO accountability
- Ordering PO accountable
- Visibility Backlog transparent
- Refinement Ongoing detailing
- Product Goal Backlog commitment
- One product One backlog
- Release PO decision
- Stakeholders Feedback source
Output vs Outcome PR
Output
- Features delivered
- Work completed
- Activity measure
Outcome
- User behavior
- Value achieved
- Impact measure
- Value beats volume
Agile Product PR
- Forecast Evidence-based projection
- Velocity Optional measure
- MVP Learning slice
- Outcome Value result
- Output Delivered work
- Hypothesis Testable belief
- Feedback Adapt backlog
- Release plan Forecast, not promise
Common Traps
Role Count
- Three accountabilities ≠ No Development Team
Daily Scrum
- Developers inspect ≠ No status report
Sprint Scope
- Goal fixed ≠ Scope negotiable
Sprint Cancellation
- PO authority ≠ Not team vote
Definition of Done
- Required for Increment ≠ Not acceptance criteria
Backlog Ownership
- PO accountable ≠ Work may delegate
Forecasts
- Empirical projection ≠ Not fixed promise
Last Minute
- 1. 85% means 68 correct
- 2. Sprint max: one month
- 3. Daily Scrum: 15 minutes
- 4. Planning: why, what, how
- 5. Artifacts each have commitments
- 6. PO orders Product Backlog
- 7. Developers own Sprint Backlog
- 8. SM accountable for Scrum
- 9. Only PO cancels Sprint
- 10. Done work enters Increment
PSM I
- Practice Questions 200 questions Study Guide 39 topics Cheat Sheet 69 facts Flashcards 50 cards Shorts 1 short Videos 1 video Blogs 1 blog Free CE Podcast