CSM — Scrum Alliance Certified ScrumMaster Study Plan
A practical 7-day, 14-day, 30-day, and 60/90-day study plan for the Scrum Alliance Certified ScrumMaster CSM exam.
Orientation
This independent study plan is for candidates preparing for the Scrum Alliance Certified ScrumMaster (CSM) exam, exam code CSM, from Scrum Alliance.
The CSM exam is not best approached as a memorization-only test. You need to understand Scrum vocabulary, accountabilities, events, artifacts, commitments, empiricism, Scrum values, and the ScrumMaster’s role in real team situations. Your study time should move quickly from reading into scenario judgment: “What should the ScrumMaster do next?” “Who is accountable?” “What makes this event effective?” “Which response preserves transparency, inspection, and adaptation?”
Use this page to choose a schedule, organize daily practice, review missed questions, and decide when you are ready to test.
Which Plan Should You Use?
| Your situation | Recommended plan | Daily time target | Main goal |
|---|---|---|---|
| Exam is in 7 days and you have already taken training or reviewed Scrum basics | 7-day final review | 60–120 minutes | Close gaps, practice scenarios, avoid overloading |
| Exam is in 2 weeks | 14-day focused plan | 60–90 minutes | Build fluency and correct misunderstandings |
| You are starting with a month | 30-day balanced plan | 45–75 minutes | Learn, practice, review, and stabilize |
| You are new to Scrum or want a low-stress path | 60/90-day full preparation path | 25–45 minutes | Build durable understanding with spaced review |
If you have not yet completed any Scrum Alliance eligibility or course steps required for your CSM attempt, verify your current requirements directly in your Scrum Alliance account or candidate instructions. Use this plan for exam preparation and review rhythm.
What to Study for CSM
Organize your study around Scrum reasoning, not just definitions.
| Area | What to know | Practice focus |
|---|---|---|
| Scrum theory | Empiricism, transparency, inspection, adaptation | Identify when a situation lacks transparency or feedback |
| Scrum values | Commitment, focus, openness, respect, courage | Choose responses that reinforce team behavior |
| Scrum Team | ScrumMaster, Product Owner, Developers | Distinguish accountability from collaboration |
| Scrum events | Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective | Know purpose, participants, outputs, and common anti-patterns |
| Scrum artifacts | Product Backlog, Sprint Backlog, Increment | Understand visibility, ownership, and use |
| Commitments | Product Goal, Sprint Goal, Definition of Done | Match each commitment to its artifact |
| ScrumMaster service | Coaching, facilitation, impediment removal, servant leadership | Decide what the ScrumMaster should do and should not take over |
| Product work | Backlog refinement, stakeholder feedback, value delivery | Separate Product Owner decisions from team self-management |
| Agile mindset | Incremental delivery, adaptation, collaboration | Recognize command-and-control traps |
| Change and impediments | Organizational blockers, stakeholder pressure, team dysfunction | Pick actions that help the team improve without bypassing Scrum roles |
Your Daily Practice Rhythm
Use the same rhythm most days. It keeps prep active and prevents passive reading from consuming the schedule.
| Step | Time | Action |
|---|---|---|
| 1. Warm-up recall | 5–10 min | Write key Scrum terms from memory: roles, events, artifacts, commitments, values |
| 2. Focused review | 20–30 min | Study one topic deeply; use the Scrum Guide and your course notes |
| 3. Practice questions | 20–40 min | Answer mixed and topic-specific questions without looking up answers |
| 4. Missed-question review | 15–30 min | Explain why the correct answer is correct and why your choice was attractive |
| 5. Scenario summary | 5 min | Write one rule you will apply on exam day |
For short schedules, increase practice time. For longer schedules, keep the daily session shorter but more consistent.
Baseline Diagnostic: Start Here
Before choosing detailed study topics, run a diagnostic.
| Step | How to do it | What to record |
|---|---|---|
| Take an untimed diagnostic set | Use a mixed set of CSM-style questions | Score, uncertain questions, slow topics |
| Mark every guess | Do not count lucky guesses as mastered | “Correct but guessed” is still a review item |
| Categorize misses | Assign each miss to a topic | Role, event, artifact, value, scenario judgment, wording |
| Identify top 3 gaps | Pick the highest-impact weak areas | These drive your next 3 study sessions |
| Retake only after review | Do not immediately repeat the same questions | Avoid memorizing answer patterns |
7-Day Final Review Plan
Use this plan if your CSM exam is within a week and you already have a basic understanding of Scrum.
7-Day Schedule
| Day | Focus | Study actions | Practice actions |
|---|---|---|---|
| 7 days out | Diagnostic and gap map | Review Scrum framework at a high level | Take a mixed diagnostic set; create a miss log |
| 6 days out | Accountabilities | Review ScrumMaster, Product Owner, Developers | Practice role-based questions and accountability scenarios |
| 5 days out | Events | Review purpose of each Scrum event | Practice event anti-pattern questions |
| 4 days out | Artifacts and commitments | Review Product Backlog, Sprint Backlog, Increment, Product Goal, Sprint Goal, Definition of Done | Practice artifact/commitment matching and scenario questions |
| 3 days out | ScrumMaster scenarios | Review coaching, facilitation, impediment handling, self-management | Practice “what should the ScrumMaster do next?” questions |
| 2 days out | Timed mock and explanation review | Take one timed mixed mock | Review every miss and every guess |
| 1 day out | Light final review | Review notes, values, definitions, and recurring mistakes | Do a short confidence set only; stop heavy study early |
7-Day Priorities
| If you are weak in… | Spend extra time on… | Avoid… |
|---|---|---|
| Scrum vocabulary | Events, artifacts, commitments, accountabilities | Jumping straight into full mocks only |
| Scenario questions | ScrumMaster stance, self-management, Product Owner boundaries | Memorizing answer letters |
| Event questions | Purpose of each event and who uses it | Treating events as status meetings |
| Artifact questions | Transparency and commitments | Thinking artifacts are just documents |
| Values and mindset | Behavior-based examples | Treating values as slogans only |
Final 48 Hours
Stop adding new sources in the final 48 hours. Use only:
- Your missed-question log
- Scrum Guide notes
- Course notes or instructor materials
- One short confidence practice set
- A final list of “rules I keep missing”
Do not take multiple full mocks the day before the exam unless you are calm and using them only for review. Fatigue can create false doubt.
14-Day Focused Plan
Use this plan if you have two weeks and can study most days. The goal is to build understanding in week one and test readiness in week two.
Week 1: Build the Framework
| Day | Focus | Actions |
|---|---|---|
| 1 | Baseline diagnostic | Take a mixed set, mark guesses, build your miss log |
| 2 | Scrum theory and values | Review empiricism, Scrum values, why Scrum uses frequent inspection |
| 3 | Scrum Team accountabilities | Compare ScrumMaster, Product Owner, and Developers; write boundary examples |
| 4 | Scrum events part 1 | Study Sprint, Sprint Planning, Daily Scrum |
| 5 | Scrum events part 2 | Study Sprint Review and Sprint Retrospective |
| 6 | Artifacts and commitments | Map artifacts to commitments and transparency purpose |
| 7 | Mixed review | Practice mixed questions; update top gaps |
Week 2: Scenario Judgment and Timed Practice
| Day | Focus | Actions |
|---|---|---|
| 8 | ScrumMaster service | Practice facilitation, coaching, impediment, and conflict scenarios |
| 9 | Product and stakeholder situations | Review Product Owner accountability, stakeholder feedback, value and ordering |
| 10 | Team self-management | Practice questions on Developers’ ownership, Daily Scrum use, Sprint Backlog adaptation |
| 11 | Timed mock 1 | Take a timed mixed mock; review explanations deeply |
| 12 | Targeted repair | Study only the top 3 miss categories from the mock |
| 13 | Timed mock 2 or half mock | Take another timed set if needed; otherwise do targeted practice |
| 14 | Final review | Review miss log, definitions, values, event purposes; stop heavy study early |
14-Day Success Rule
By the end of day 10, you should be spending more time on scenario decisions than on basic definitions. If you are still unsure about roles, events, or artifacts, pause full mocks and repair those foundations first.
30-Day Balanced Plan
Use this path if you want enough time for repeated exposure, missed-question review, and timed practice without cramming.
30-Day Overview
| Phase | Days | Goal | Output |
|---|---|---|---|
| Foundation | 1–7 | Learn the Scrum framework accurately | Topic notes and first miss log |
| Application | 8–16 | Apply Scrum to team and stakeholder scenarios | Scenario examples and corrected assumptions |
| Integration | 17–24 | Mix topics and build timing | Timed sets and refined review notes |
| Final readiness | 25–30 | Confirm exam readiness and reduce mistakes | Final miss log and exam-day checklist |
Days 1–7: Foundation
| Day | Study focus | Practice |
|---|---|---|
| 1 | Diagnostic and study setup | Mixed diagnostic; create topic tracker |
| 2 | Scrum theory and values | Short topic set on empiricism and values |
| 3 | Scrum Team | Role/accountability questions |
| 4 | Sprint and Sprint Planning | Event purpose questions |
| 5 | Daily Scrum, Sprint Review, Retrospective | Event scenario questions |
| 6 | Artifacts and commitments | Matching and scenario questions |
| 7 | Foundation review | Mixed set; update weak areas |
Days 8–16: Application
| Day | Study focus | Practice |
|---|---|---|
| 8 | ScrumMaster as coach | “What should the ScrumMaster do?” questions |
| 9 | Facilitation and impediments | Conflict, blocker, and meeting scenarios |
| 10 | Product Owner and value | Backlog, ordering, stakeholder feedback questions |
| 11 | Developers and self-management | Sprint Backlog and Daily Scrum scenarios |
| 12 | Definition of Done and Increment | Quality, completion, transparency scenarios |
| 13 | Sprint Goal and adaptation | Mid-Sprint change and focus questions |
| 14 | Stakeholder pressure | Protecting Scrum while staying collaborative |
| 15 | Mixed scenario set | Timed or semi-timed set |
| 16 | Review day | Rewrite rules from your miss log |
Days 17–24: Integration and Timing
| Day | Focus | Actions |
|---|---|---|
| 17 | Timed set 1 | Take a timed mixed set; review all misses |
| 18 | Repair topic 1 | Study your weakest topic; do targeted questions |
| 19 | Repair topic 2 | Study second weakest topic; do targeted questions |
| 20 | Timed set 2 | Practice under time; track rushed misses |
| 21 | Events and artifacts review | Rebuild the framework from memory |
| 22 | ScrumMaster scenario review | Practice coaching/facilitation choices |
| 23 | Timed mock | Take a longer timed mock or two timed sections |
| 24 | Deep review | Review explanations; update final weak list |
Days 25–30: Final Readiness
| Day | Focus | Actions |
|---|---|---|
| 25 | Final weak area repair | Study only recurring misses |
| 26 | Mixed confidence set | Timed but not exhausting |
| 27 | Scrum Guide pass | Re-read key sections and compare to miss log |
| 28 | Final mock or half mock | Use if it will inform review; do not chase volume |
| 29 | Light final review | Definitions, values, events, artifacts, commitments |
| 30 | Exam readiness | Review checklist; rest; stop heavy study early |
60/90-Day Full Preparation Path
Use this path if you are new to Scrum, have a busy schedule, or want to build durable understanding before testing. The 60-day version compresses the checkpoints; the 90-day version adds more spacing and review.
60/90-Day Structure
| Phase | 60-day timing | 90-day timing | Goal |
|---|---|---|---|
| Orientation and basics | Days 1–10 | Days 1–14 | Understand the Scrum framework and exam expectations |
| Framework mastery | Days 11–25 | Days 15–35 | Learn accountabilities, events, artifacts, commitments |
| ScrumMaster application | Days 26–40 | Days 36–60 | Practice real ScrumMaster decisions |
| Mixed practice | Days 41–52 | Days 61–78 | Build accuracy and timing |
| Final readiness | Days 53–60 | Days 79–90 | Confirm readiness and reduce final errors |
Phase 1: Orientation and Basics
| Weekly target | Actions |
|---|---|
| Understand what Scrum is for | Review empiricism, incremental delivery, and why Scrum uses short feedback loops |
| Build a study system | Create a miss log, topic tracker, and “uncertain but correct” list |
| Learn core terms | Memorize roles/accountabilities, events, artifacts, commitments, and values |
| Take a light diagnostic | Use the result to guide study, not to judge readiness |
Phase 2: Framework Mastery
| Topic | Study actions | Practice actions |
|---|---|---|
| Scrum Team | Write what each accountability owns and does not own | Role boundary questions |
| Events | Create a one-page event map: purpose, participants, timing concept, outcome | Event anti-pattern questions |
| Artifacts | Explain how each artifact supports transparency | Artifact scenario questions |
| Commitments | Match Product Goal, Sprint Goal, and Definition of Done to their artifacts | Commitment matching questions |
| Values | Write one behavioral example for each value | Values-in-scenario questions |
Phase 3: ScrumMaster Application
Focus on judgment, not just recall.
| Scenario type | What to practice |
|---|---|
| Team waits for the ScrumMaster to assign work | Reinforce self-management; do not become a task manager |
| Stakeholder pressures the team mid-Sprint | Use Product Owner boundaries, Sprint Goal, and transparency |
| Daily Scrum becomes a status report | Refocus on Developers inspecting progress toward the Sprint Goal |
| Retrospective produces no improvement | Facilitate useful inspection and adaptation |
| Product Backlog is unclear | Support collaboration while respecting Product Owner accountability |
| Definition of Done is ignored | Emphasize transparency, quality, and usable Increment |
Phase 4: Mixed Practice
| Week type | Actions |
|---|---|
| Mixed-topic week | Alternate timed mixed sets with targeted repair |
| Scenario week | Practice ScrumMaster, stakeholder, team, and event scenarios |
| Explanation week | Spend more time reviewing explanations than answering new questions |
| Timing week | Use timed sets to reduce hesitation and second-guessing |
Phase 5: Final Readiness
In the last 7–10 days of a long plan, switch to the 7-day final review schedule. Do not keep adding new study resources. Your main job is to stabilize what you know and eliminate repeated errors.
Missed-Question Review Method
Most CSM improvement comes from reviewing missed questions correctly. Do not only read the correct answer.
Miss Log Template
| Field | What to write |
|---|---|
| Question topic | Role, event, artifact, commitment, value, ScrumMaster scenario, stakeholder scenario |
| Why I missed it | Misread, guessed, confused roles, ignored Scrum value, chose command-and-control answer |
| Correct principle | The Scrum rule or mindset that decides the question |
| Trap answer | Why my chosen answer looked appealing |
| New rule | A short statement to apply next time |
| Retest date | When you will revisit the topic |
Example Review Notes
| Miss pattern | Better review question |
|---|---|
| “I confused ScrumMaster and Product Owner.” | Who is accountable for value and Product Backlog decisions? Who coaches and facilitates Scrum? |
| “I treated Daily Scrum as a report to the ScrumMaster.” | Who is the Daily Scrum for, and what is being inspected? |
| “I picked the answer where the ScrumMaster solves it directly.” | Should the ScrumMaster solve it, facilitate, coach, or remove an organizational impediment? |
| “I ignored the Sprint Goal.” | Which option best protects focus while allowing adaptation? |
| “I chose the most detailed process.” | Is the option consistent with Scrum, or is it adding unnecessary command-and-control behavior? |
What to Practice Next
Use your latest practice results to decide your next session.
| If your recent practice shows… | Practice next | Study action |
|---|---|---|
| Many definition misses | Core framework review | Rebuild roles, events, artifacts, and commitments from memory |
| Role confusion | Accountability scenarios | Compare ScrumMaster, Product Owner, Developers |
| Event confusion | Event purpose questions | Write one sentence for why each event exists |
| Scenario hesitation | Mixed ScrumMaster judgment sets | Identify the principle behind each correct answer |
| Rushed errors | Timed short sets | Slow down on keywords: accountable, responsible, should, best |
| Correct but guessed | Explanation review | Treat as a miss until you can explain it |
| Repeated same-topic misses | Stop mixed practice temporarily | Do a focused repair session before more mocks |
Timed Mock Exam Strategy
Timed practice is useful, but only after you know the framework well enough to learn from mistakes.
| Preparation stage | Use timed mocks? | Best use |
|---|---|---|
| First few study days | Not yet, except diagnostic | Find gaps without worrying about timing |
| Middle of plan | Yes, short timed sets | Build pacing and topic mixing |
| Final third of plan | Yes, full or longer mixed mocks | Confirm readiness and review explanations |
| Last day | Usually no full mock | Use light confidence practice only |
How to Review a Timed Mock
- Mark all incorrect answers.
- Mark all correct answers you guessed.
- Sort misses by topic.
- Identify whether the issue was knowledge, wording, or judgment.
- Review the relevant Scrum principle before doing more questions.
- Write 5–10 final rules from the mock.
- Retest only the weak topics first, not the entire mock immediately.
CSM Scenario Judgment Checklist
When a question asks what the ScrumMaster should do, use this checklist.
| Question to ask | Why it matters |
|---|---|
| Does the answer preserve Scrum accountabilities? | The ScrumMaster should not take over Product Owner or Developers’ decisions |
| Does it support self-management? | Scrum teams should not rely on command-and-control assignment |
| Does it improve transparency? | Hidden work, unclear Done, and vague goals weaken inspection |
| Does it enable inspection and adaptation? | Scrum events exist for feedback and adjustment |
| Does it respect the Sprint Goal? | Adaptation should not destroy focus |
| Does it coach rather than command? | The ScrumMaster teaches, facilitates, coaches, and removes impediments |
| Does it align with Scrum values? | Good answers often reinforce openness, courage, respect, focus, or commitment |
Final-Week Rules
Use these rules in the last week regardless of your plan length.
| Rule | Why |
|---|---|
| Stop collecting new resources 48 hours before the exam | New material can create confusion and reduce confidence |
| Review explanations more than new questions | Explanation review fixes reasoning errors |
| Keep a short final notes page | One page is easier to remember than scattered notes |
| Do not ignore guessed-correct answers | Lucky answers are hidden weaknesses |
| Practice scenario wording | Many mistakes come from choosing a plausible but non-Scrum response |
| Sleep and reduce study load the day before | Fatigue increases misreading and second-guessing |
Exam-Readiness Checks
You are likely ready to schedule or sit for the CSM exam when most of these are true.
| Readiness check | Yes/No |
|---|---|
| I can explain the purpose of each Scrum event without notes | |
| I can distinguish ScrumMaster, Product Owner, and Developers’ accountabilities | |
| I can match each artifact to its commitment | |
| I understand how Scrum values appear in behavior-based questions | |
| I can explain why the Daily Scrum is not a status meeting for the ScrumMaster | |
| I can identify command-and-control trap answers | |
| I review guessed-correct questions as carefully as missed questions | |
| My recent timed practice feels controlled, not rushed | |
| My repeated miss categories are shrinking | |
| I know what I will review in the final 24 hours |
Final 24-Hour Review List
Keep the final day simple.
| Time | Action |
|---|---|
| Morning or early day | Read your one-page framework summary |
| Midday | Review missed-question rules and recurring traps |
| Afternoon | Do a short, low-stress mixed set if it helps confidence |
| Evening | Stop heavy study; review only light notes |
| Before exam | Re-check instructions, identification, timing, and testing setup |
Practical Next Step
Choose the schedule that matches your remaining time, take a short diagnostic set, and build your miss log today. Then use each study session to do three things: review one Scrum topic, answer CSM-style practice questions, and write down the Scrum principle behind every miss or guess.