CSM Cheat Sheet

Use this for last‑mile review. Pair it with the Syllabus for coverage and Practice for speed.

Scrum in 30 seconds (the “why”)

Scrum is a lightweight framework for solving complex problems by enabling:

• Transparency: everyone can see the reality.
• Inspection: we check progress frequently.
• Adaptation: we change direction quickly based on what we learn.

Most “best answer” questions reward choices that increase transparency, shorten feedback loops, and preserve team ownership.

Accountabilities (roles) — what each owns

Fast eliminations

• “Manager assigns tasks to developers” → usually wrong (team self-manages).
• “Scrum Master decides scope” → usually wrong (PO owns ordering/value; team owns how).
• “PO dictates how the work is done” → usually wrong (developers decide how).

Events — purpose, timeboxes, outputs

Common traps

• Daily Scrum is for developers (not a status meeting for management).
• Review is about product + value, Retro is about process + teamwork.

Artifacts + commitments (what “Done” means)

DoD vs Acceptance Criteria (don’t mix these up)

• Acceptance criteria: per‑item “what must be true for this story/backlog item to be acceptable.”
• DoD: shared quality bar for the Increment (testing, security, docs, performance, etc.).

If quality issues repeat, the answer is often: tighten DoD / fix the system, not “work harder.”

Product Backlog refinement (high-yield)

Refinement is ongoing and typically includes:

• breaking down items
• adding detail
• estimation / sizing
• keeping ordering aligned to value and risk

If the backlog is “too big / too vague,” the fix is: refine and order, not “start a Sprint with unclear work.”

Fast role-and-decision pickers

Scenario pickers (“best answer” rules)

When requirements are unclear

1. Clarify the Product Goal / outcome.
2. Collaborate with stakeholders to make assumptions explicit.
3. Slice work smaller and validate with feedback (Review).

When the team is missing the Sprint Goal

• Re-plan inside the Sprint (developers).
• Make work visible; negotiate scope with PO if needed.
• Avoid “extend the Sprint” (Sprints have fixed length).

When someone wants to add work mid‑Sprint

• New work goes to the Product Backlog.
• PO can negotiate with developers: swap scope only if it doesn’t endanger Sprint Goal.

When there’s conflict / blame

• Increase transparency; focus on process.
• Use Retro to agree on one improvement action with an owner and a measurable outcome.

When management wants status theatre

• Prefer transparent artifacts, Sprint Review evidence, and direct stakeholder conversation.
• Avoid turning Daily Scrum into a reporting meeting for outsiders.

Quick glossary (high-yield terms)

• Empiricism: decisions based on what is observed.
• Self-management: the team chooses how to accomplish the work.
• Increment: a step toward the Product Goal that meets the DoD.

Ready to validate speed? Use the CSM practice handoff or go straight to the CSM practice preview on MasteryExamPrep.