Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Scrum Alliance
Exam Format
Registration
Validity
Skills this practice test covers
- Apply transparency, inspection and adaptation to a team problem described in a scenario.
- Decide whose accountability a task falls under: the Product Owner's, the Scrum Master's or the Developers'.
- Plan a Sprint around why it is valuable, what can be Done and how the work will get Done.
- Match each artifact to its commitment: the Product Goal, the Sprint Goal and the Definition of Done.
- Handle incomplete work at the end of a Sprint without lowering quality.
- Coordinate several teams on one product with a shared Product Backlog and a common Definition of Done.
Explore related topics
CSM exam content
5 domains · 32 topics · 199 of 203 questions sorted by domain
Scrum Theory and Values29 questions
This domain explains why Scrum works: the team decides from what it can observe, not from a fixed plan. It also covers the five Scrum values and the ideas Scrum shares with the Agile Manifesto.
Skills tested
- Name the pillar of empiricism that is missing when progress is hidden from stakeholders.
- Connect each Scrum value, such as courage or openness, to a team behavior.
- Recognize when a value is compromised, for example when a team hides a problem.
- Explain why Scrum is a framework and not a methodology.
- Link Scrum to lean thinking and the Agile Manifesto.
Questions by topic
- Applying Scrum Values to Team Interactions11
- Understanding Empiricism6
- Diagnosing Issues with Empiricism11
- Handling Incomplete Work1
Scrum Team and Accountabilities64 questions
This domain sets out who is accountable for what. Candidates must tell apart the work of the Product Owner, the Developers and the Scrum Master, and treat the Scrum Team as one self-managing unit without sub-teams.
Skills tested
- Keep a Scrum Team small, cross-functional and free of sub-teams.
- Describe how the Product Owner maximizes value and orders the Product Backlog.
- Show how the Scrum Master serves the Product Owner, the Developers and the organization.
- Leave the Sprint Backlog and the daily plan to the Developers.
Questions by topic
- Scrum Master Service to the Organization2
- Scrum Team Size7
- Collective Accountability6
- Developer Self-Management8
- Cross-Functional Teams5
- Stakeholder Collaboration3
- Scrum Master Service to the Product Owner1
- Product Owner7
- Organizational Impediment Removal1
- Scrum Master24
Scrum Events46 questions
The Sprint is the container for every other event. Candidates must know what each event inspects and adapts, who takes part and how long it may last.
Skills tested
- Keep each Sprint at a fixed length and block changes that endanger the Sprint Goal.
- Facilitate Sprint Planning so it ends with a Sprint Goal and a plan for delivery.
- Keep the Daily Scrum to its 15-minute timebox and focused on progress toward the Sprint Goal.
- Use the Sprint Review to inspect the outcome with stakeholders and adapt the Product Backlog.
- Turn Sprint Retrospective findings into process and quality improvements.
Questions by topic
- Facilitating Sprint Planning8
- Daily Scrum Purpose5
- Event Timeboxes6
- The Sprint9
- Stakeholder Collaboration3
- Sprint Planning Topics7
- Sprint Retrospective7
- Handling Incomplete Work1
Scrum Artifacts and Commitments39 questions
Each artifact carries a commitment that keeps it transparent: the Product Goal for the Product Backlog, the Sprint Goal for the Sprint Backlog and the Definition of Done for the Increment. Questions test these pairs and what happens to work that is not Done.
Skills tested
- Keep the Product Backlog emergent and ordered as the single source of work.
- Refine Product Backlog items until they are small and clear enough for a Sprint.
- Use the Sprint Backlog as a real-time picture of the Developers' plan.
- Return work that does not meet the Definition of Done to the Product Backlog.
Questions by topic
- Product Goal8
- Product Backlog Characteristics7
- Definition of Done8
- Sprint Backlog6
- Handling Incomplete Work5
- Sprint Goal5
Scaling and Implementing Scrum21 questions
This domain looks beyond one team. Candidates plan how an organization adopts Scrum step by step, and how several teams build one product together.
Skills tested
- Plan an incremental Scrum adoption and remove organizational impediments.
- Coordinate teams that share a Product Backlog through a Scrum of Scrums.
- Agree on one Definition of Done so that every team's work integrates into one Increment.
- Manage dependencies between teams before they block integration.
Questions by topic
- Multiple Team Coordination11
- Scaling the Definition of Done8
- Scrum Master Service to the Organization1
- Cross-Functional Teams1
Requirements
- Required: a 16-hour CSM course taught by a Certified Scrum Trainer (CST).
- Required: the test must be taken within a set period after the course.
- Recommended: a basic grasp of software development and some experience of teamwork.
- Recommended: familiarity with project management concepts.
About the CSM exam
CSM checks whether a new Scrum Master knows the Scrum framework well enough to guide a team by it. Scrum Alliance requires a 16-hour course with a Certified Scrum Trainer (CST) before the test. The test covers empiricism and the Scrum values, the three accountabilities, the five events, the artifacts with their commitments, and Scrum across many teams. Passing earns the Certified ScrumMaster certification, which stays valid for two years.
The Scrum events, the accountabilities and the artifacts get the most questions in the PlanetCert practice test. The explanations help most where two options both sound agile, such as a Scrum Master who assigns tasks and one who lets the Developers manage their own work. Study Mode suits the scenario questions on impediments and incomplete work. Flashcard Mode helps with the three commitments and the event timeboxes. Brainy AI Assistant can explain what may change during a Sprint, or how several teams share one Product Backlog.
How to earn the certification
- Earns
- Certified ScrumMaster (CSM)Foundational
The certification stays valid for two years and renews with Scrum Education Units (SEUs) and a renewal fee.
How to prepare for CSM
- 1
Read the Scrum Guide twice
Most CSM topics come from the Scrum Guide, where small words decide answers, such as who is accountable for ordering the Product Backlog. Read it once for the overall picture and once for the exact rules.
- 2
Bring real cases to the course
Ask the trainer about situations from real teams, such as a Product Owner who is rarely available or a Daily Scrum that turns into a status report. Many practice questions describe cases like these.
- 3
Pair each artifact with its commitment
Draw three rows: Product Backlog and Product Goal, Sprint Backlog and Sprint Goal, Increment and Definition of Done. Add who is accountable for each one and when the team inspects it.
- 4
Walk through one Sprint
Trace a Sprint from Sprint Planning to the Sprint Retrospective. For each event, state its purpose, who takes part and its timebox, then check each answer against the Scrum Guide.
- 5
Close with a timed run
Take the CSM practice test in Timed Mode after the course. For every miss, ask Brainy AI Assistant which accountability or rule the question turned on, then reread that part of the Scrum Guide.
Start a timed CSMrun
Who CSM is for
- People stepping into a Scrum Master role for the first time.
- Project managers and team leads whose teams are adopting Scrum.
- Product managers and developers who want to know how a Scrum Team works.
Typical job titles: Scrum Master · Agile coach · Project manager · Team lead · Product manager
CSM glossary
16 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Certified Scrum Trainer (CST)
- A trainer approved by Scrum Alliance to teach the course that every CSM candidate must complete.
- Cross-functional
- A team that has all the skills it needs to create a valuable, usable Increment each Sprint.
- Daily Scrum
- A short daily event in which the Developers inspect progress toward the Sprint Goal and adapt their plan.
- Definition of Done
- The formal description of the quality an Increment must meet. It is the commitment attached to the Increment.
- Five Scrum Values
- Commitment, focus, openness, respect and courage: the values a Scrum Team lives by so that empiricism can work.
- Increment
- A concrete stepping stone toward the Product Goal: usable work that adds to all prior Increments.
- Lean Thinking
- An approach that reduces waste and focuses on the essentials. Scrum is founded on it, together with empiricism.
- Organizational impediments
- Obstacles outside the team, such as policies or structures, that slow the team down and that the Scrum Master helps remove.
- Product Backlog refinement
- The ongoing work of breaking Product Backlog items into smaller, more precise items with more detail.
- Product Goal
- The long-term objective for the product. It is the commitment attached to the Product Backlog.
- Scrum Education Units (SEUs)
- Credits for learning activities. Scrum Alliance asks for them, together with a fee, to renew the certification.
- Scrum of Scrums
- A coordination meeting where people from several Scrum Teams discuss dependencies and integration.
- Self-managing
- A Scrum Team decides inside the team who does what, when and how, without direction from outside.
- Servant leadership
- The way a Scrum Master leads: by serving the team and the organization, for example through coaching and removing impediments.
- Sprint Goal
- The single objective for one Sprint, set in Sprint Planning. It is the commitment attached to the Sprint Backlog.
- Three Pillars of Empiricism
- Transparency, inspection and adaptation: the three ideas that let a Scrum Team learn from real results instead of a fixed plan.