Study guide
7.1 CSM Test Format & Scoring
Certified ScrumMaster CSM
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Agile Foundations, Scrum Theory & Empirical Process Control
1.1 Agile Manifesto & Lean Thinking 1.2 Empirical Process Control 1.3 Complex Adaptive Systems & Cynefin Framework 1.4 Scrum Framework Overview & Core Rules 1.5 Iterative & Incremental Delivery 1.6 Partial Scrum Adoption & Its Consequences
2 Chapter 2: The Five Scrum Values & Cultural Mindset
2.1 Commitment & Focus 2.2 Openness & Respect 2.3 Courage & Ethical Leadership
3 Chapter 3: Scrum Team Accountabilities & Dynamics
3.1 Developers Accountability & Self-Management 3.2 Product Owner Accountability & Business Value 3.3 Scrum Master Accountability & Servant Leadership 3.4 Team Characteristics, Size & Cross-Functionality 3.5 How the Scrum Team Interacts Across a Sprint 3.6 Why Scrum Has No Project Manager
4 Chapter 4: The Five Scrum Events & Timeboxing
4.1 The Sprint Container & Goal Preservation 4.2 Sprint Planning Event 4.3 Daily Scrum Event & Micro-Planning 4.4 The Sprint Review 4.5 The Sprint Retrospective 4.6 Effects of Skipping the Sprint Retrospective 4.7 Choosing a Suitable Sprint Length 4.8 Inspect & Adapt at Every Scrum Event
5 Chapter 5: Scrum Artifacts, Commitments & Definition of Done
5.1 Product Backlog & Product Goal 5.2 Sprint Backlog & Sprint Goal 5.3 Increment & Definition of Done 5.4 Multi-Team DoD & Technical Debt Management 5.5 Product Backlog Refinement 5.6 Product Backlog Item Attributes & Ordering 5.7 Creating & Evolving the Definition of Done
6 Chapter 6: Scrum Master Core Competencies, Servant Leadership & Coaching
6.1 Facilitation & Professional Coaching Techniques 6.2 Removing Impediments & Root Cause Analysis 6.3 Servant Leadership & Organizational Change 6.4 Agile Metrics, Velocity Traps & Scaling Basics 6.5 Development Practices That Protect the Increment 6.6 Serving the Product Owner 6.7 Organizational Design Change from Adopting Scrum
7 Chapter 7: The CSM Test — Format, Logistics & Official Blueprint
7.1 CSM Test Format & Scoring 7.2 Course Prerequisite, Attempts & Renewal 7.3 The Official Learning Objectives Blueprint
7.1 CSM Test Format & Scoring
Key Takeaways Explain This Topic AI
The CSM test contains 50 multiple-choice questions and must be completed within 60 minutes.
The passing score is at least 74%, which Scrum Alliance states as 37 correct answers out of 50.
The test is taken online and is not proctored — there is no testing centre and no webcam supervision.
You cannot pause the test, but questions can be bookmarked and returned to within the 60-minute limit.
The test is available in 13 languages, and candidates needing more than 60 minutes must request an accommodation from Scrum Alliance support in advance.
Last updated: August 2026
Quick Answer: 50 multiple-choice questions, 60 minutes, pass at 74% — 37 correct out of 50. Taken online, not proctored , after you complete the required course. You cannot pause it, but you can bookmark questions and return to them inside the hour.
These are Scrum Alliance's own published figures. Unlike many certification bodies, Scrum Alliance states the passing threshold plainly rather than using a scaled score, which makes preparation targets unusually concrete: you can miss 13 questions and still pass.
The Published Facts
- Attribute Value
- Number of questions 50 multiple-choice
- Time limit 60 minutes
- Passing score At least 74% — 37 of 50 correct
- Questions you may miss 13
- Delivery Online, through the Scrum Alliance website
- Proctoring Not proctored ; no in-person testing centre
- Pausing Not possible once started
- Bookmarking Yes — flag questions and return within the time limit
- Basis of questions The CSM Learning Objectives and the Scrum Guide
Languages 13, including English, Spanish (Castilian), Latin American Spanish, Portuguese, French, Italian, German, Japanese, Simplified Chinese, Danish, Czech, Polish, and Russian
- Extra time Available by accommodation request to Scrum Alliance support
- What 50 Questions in 60 Minutes Actually Means
The arithmetic is comfortable: 72 seconds per question on average. In practice you will answer most Scrum Guide recall questions in 20–30 seconds, which banks time for the longer scenario items.
A workable pacing plan:
First pass (about 35 minutes). Answer everything you know immediately. Bookmark anything that needs thought rather than sitting on it.
Second pass (about 20 minutes). Work the bookmarked items with the time you have banked.
Final sweep (about 5 minutes). Confirm no question is unanswered. There is no penalty for a wrong answer, so never leave a blank.
How the Questions Are Built
Scrum Alliance states the test is based on the CSM Learning Objectives and the Scrum Guide. Two practical consequences:
The Scrum Guide is the authority for anything it covers. Where a trainer's practice differs from the Guide, the Guide's position is the safer answer.
Anything not in the Scrum Guide but present in the Learning Objectives is fair game — facilitation techniques, coaching stances, impediment handling, technical debt, and organizational change all appear in the CSM Learning Objectives without appearing in the Scrum Guide.
Question styles you should expect:
Style Example Shape How to Approach It
Direct recall "What is the maximum timebox for the Sprint Retrospective?" Know the numbers cold; these are free marks
Accountability "Who is responsible for sizing Product Backlog items?" Map to the three accountabilities; beware options that add a fourth
Scenario / best action A stakeholder does X — what should the Scrum Master do? Prefer coaching and transparency over deciding for people
- Negative framing "Which of the following is NOT…" Slow down; these produce most careless errors
- Reading the Distractors
Incorrect options on this test are patterned, and recognizing the patterns is worth several marks:
Restores a hierarchy. Any option where the Scrum Master assigns work, or a manager directs Developers, contradicts self-management.
Breaks a timebox. Extending a Sprint or an event to finish work is essentially always wrong.
Lowers quality. Relaxing the Definition of Done to hit a date is always wrong.
Uses retired terminology. "Development Team," "3 to 9 members," "commitment to complete all items," "grooming," and "roles" instead of "accountabilities" all signal pre-2020 material.
Makes the Scrum Master a decision-maker. The Scrum Master leads by teaching, coaching, and facilitating — not by adjudicating.
Is absolute where Scrum is not. Options containing "never," "always," or "must under all circumstances" deserve extra scrutiny, though occasionally they are correct — only the Product Owner may cancel a Sprint, for instance.
Exam-Day Practicalities
Because the test is unproctored and browser-based, the failure modes are logistical rather than procedural: an unstable connection, a browser extension interfering with the test page, or starting the test with 40 minutes free rather than a clear hour. None of these are exotic, and all are avoidable — use a wired or reliable connection, close other applications, and start only when you have the full hour uninterrupted.
Real-World Preparation Strategy
The most reliable preparation is unglamorous: read the 2020 Scrum Guide end to end at least twice. It is roughly 13 pages, and a large share of the 50 questions can be answered directly from it. Read it once early to build structure, then again close to your test date to sharpen the exact wording — particularly the timeboxes, the accountability lists, and the three artifact commitments.
After that, work through the CSM Learning Objectives themselves and check that you can produce a real answer to each one, because the objectives are what the test is built from. Sections 7.2 and 7.3 of this guide cover the logistics around the test and the full objective list.