Certified ScrumMaster
Certified ScrumMaster Cheat Sheet
CSM Is Foundational — But Facilitation Judgment Traps Are Real
The CSM tests Scrum fundamentals and servant-leadership judgment. Getting comfortable with the basics isn't enough if you misread facilitation scenarios.
Check Your Readiness →
Among the harder certs
Avg: Approximately 70–75%
Pass: 750 / 1000
Most candidates understand Certified ScrumMaster concepts — and still fail. This exam tests how you apply knowledge under pressure.
Core Framework
CSM Core: Servant-Leadership in Practice
Scrum Alliance's CSM focuses on the Scrum Master as servant-leader. Scenarios test whether you enable team self-management or inadvertently revert to command-and-control. The exam is based on the 2020 Scrum Guide.
-
01
Coach
— Guide the team to Scrum principles, don't impose
-
02
Facilitate
— Create conditions for collaboration, not control
-
03
Remove Impediments
— Act on blockers, don't just log them
-
04
Protect the Team
— Shield from external interference during Sprints
-
05
Serve the Organization
— Help the broader organization adopt agility
Scenario Traps
Wrong instinct vs correct approach
A senior manager keeps interrupting the team during the Sprint
✕ Wrong instinct
Attend meetings with the manager to represent the team's interests
✓ Correct approach
Protect the team from external interference by addressing the issue with the manager directly and educating them on the Sprint model and its value
The team wants to skip the retrospective because the Sprint went well
✕ Wrong instinct
Allow it — retrospectives are only needed when there are problems
✓ Correct approach
Coach the team that retrospectives are most valuable when things go well — to identify what to amplify and capture practices worth repeating
The Product Owner is unavailable during the Sprint
✕ Wrong instinct
The Scrum Master makes product decisions in the PO's absence
✓ Correct approach
The Scrum Master escalates the PO's unavailability as an impediment and works to restore engagement — they never substitute for the PO role
Quick Rules
Know these cold
-
▸
Scrum Master protects the team — from external pressure and internal dysfunction
-
▸
Retrospectives are mandatory every Sprint — not optional when things go well
-
▸
The Sprint Goal gives flexibility; not every Sprint Backlog item must be completed
-
▸
Scrum Master never takes on Product Owner responsibilities
-
▸
Impediment removal — oach first, escalate only when the team is truly blocked
-
▸
Sprint planning is timeboxed to 8 hours for a 4-week Sprint
-
▸
The Increment must be usable at the end of every Sprint, regardless of release decision
Self Check
Can you answer these without checking your notes?
In this scenario: "A senior manager keeps interrupting the team during the Sprint" — what should you do first?
Protect the team from external interference by addressing the issue with the manager directly and educating them on the Sprint model and its value
In this scenario: "The team wants to skip the retrospective because the Sprint went well" — what should you do first?
Coach the team that retrospectives are most valuable when things go well — to identify what to amplify and capture practices worth repeating
In this scenario: "The Product Owner is unavailable during the Sprint" — what should you do first?
The Scrum Master escalates the PO's unavailability as an impediment and works to restore engagement — they never substitute for the PO role
Failure Patterns
Common Exam Mistakes — What candidates get wrong
Acting as a project manager in Scrum clothing
Assigning tasks, tracking individual progress, or representing the team in meetings are project manager behaviors. The Scrum Master facilitates, coaches, and removes barriers — not directs.
Solving impediments for the team instead of with the team
When teams face blockers, the Scrum Master's first move is to coach the team to resolve them. Escalating or solving directly is correct only when the team genuinely cannot resolve it themselves.
Letting the Product Owner manage the Sprint Backlog
The Sprint Backlog belongs to the Developers. The Product Owner has no authority to add work to the Sprint Backlog without Developer agreement.
Confusing the Sprint Goal with the Sprint Backlog
The Sprint Goal is a commitment that provides focus and flexibility. Developers can adapt the Sprint Backlog to meet the Sprint Goal — they are not obligated to complete every item if the Goal is met.
Treating retrospectives as complaint sessions
Retrospectives must produce actionable improvements. A CSM who facilitates a retro without concrete actions for the next Sprint has failed their primary responsibility in that event.
Even foundational certifications have judgment traps. Test your CSM readiness with scenario-based questions.