Certified ScrumMaster (CSM) — Exam Survival Guide

Window: Early-career Scrum / agile leads | Format: 50 online MCQs, 60 minutes, pass mark 37/50 (74%)

Must-do topics

CSM = “Do you actually understand Scrum enough to protect it from being turned back into waterfall?”

Scrum roles

Scrum Master: servant leader, coach, blocker-remover, protector of Scrum.

Product Owner: outcome and value, backlog ordering.

Developers/Team: cross-functional, self-managing, accountable for increments.

Events with real purpose

Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.

Time-boxes, what “done” looks like each time.

Artifacts + commitments

Product Backlog (Product Goal), Sprint Backlog (Sprint Goal), Increment (Definition of Done).

Scrum values

Focus, Openness, Respect, Courage, Commitment — often hidden inside people questions.

Top traps (avoid)

Treating Scrum Master as “project manager with a new badge.”

Turning Daily Scrum into a status meeting for the SM instead of a planning huddle for the team.

Letting managers dictate Sprint scope mid-Sprint instead of using proper change handling.

Underplaying impediments (“we’ll just try harder”) instead of escalating/removing blockers.

Time split

50 Q, 60 minutes → ~1.2 minutes per question.

Target:

First pass in ~35–40 minutes, last 20+ minutes to revisit marked items.

Last-48h checklist

Two short passes over the Scrum Guide, looking for:

“Where have we cut corners in real life?” → those are exam traps.

2–3 sets of 20–30 practice questions, focusing on:

What the SM should do when: scope creep hits, PO is absent, team is over-committing, stakeholder wants daily reports.

Quick frames

On every question:

Is this about process, people, or product?

Is the suggested action protecting Scrum or quietly breaking it?

What would a servant leader do instead of a command-and-control manager?

Default safe answers often look like:

Facilitate a conversation with the right people.

Coach PO or stakeholders on Scrum values and events.

Help the team self-organise instead of assigning tasks.

Speed tactics

If a “solution” involves: adding extra meetings, heavy documentation, or command-style control, it’s usually wrong.

If there’s a choice between “ask the team” vs “decide for them,” Scrum usually prefers ask the team.

When in doubt, pick the option that:

Makes work transparent, keeps inspect-and-adapt alive, and respects roles.

Day-of mini-plan

Read 3–4 Daily-Scrum / Sprint-change scenarios before starting.

During test:

Don’t overthink; CSM is concept-heavy, not trick-heavy.

Attitude:

“My job is to guard focus and flow, not micromanage story points.”