Overview
The Scrum category is the heart of the Certified ScrumMaster learning objectives, covering Scrum as defined in the 2020 Scrum Guide. It has two groups of objectives. The Scrum Team covers the responsibilities and accountabilities of the whole team, the Scrum Master, the Developers and the Product Owner, why the Product Owner is a single person rather than a committee, and how the Product Owner keeps authority over the Product Backlog while collaborating with others. Scrum events and activities covers inspecting and adapting at each event, performing Sprint Planning, the Sprint Review and the Sprint Retrospective, the effects of skipping the Retrospective, how the Developers conduct the Daily Scrum and why it differs from a status meeting, when a Sprint may be terminated early, and the advantages and creation of a strong definition of Done.
The CSM is based on the Scrum Guide, so this category rewards understanding Scrum exactly as defined, the accountabilities, the purpose of each event, and the role of the definition of Done, applied in realistic team situations.
How it's tested
CSM questions test the Scrum Guide and the Scrum Master's understanding of it, often as realistic scenarios. Answer from what Scrum defines and why, not from how teams commonly behave: when an option reflects a status-meeting Daily Scrum or a Scrum Master directing the team, it is usually wrong. Read for what Scrum prescribes and the reasoning behind it.
-
Accountability or event
A responsibility or event is described, and you identify the correct accountability, purpose or participants.
-
Why Scrum works this way
A rule or constraint is described, and you choose the reason Scrum prescribes it, such as why the Daily Scrum is the Developers' event.
-
Done and quality
A completeness or quality situation is described, and you apply the definition of Done and its advantages.
A manager wants the Developers to report individual progress to the Scrum Master each morning at the Daily Scrum. In Scrum, the Daily Scrum is held by and for the Developers to inspect progress toward the Sprint Goal and plan their day, not to report status. So the correct response explains the Daily Scrum's real purpose and that it serves the Developers, which is what the Scrum Guide prescribes.
Learning objective categories 6
Official learning objective categories from the Scrum Alliance outline, in outline order.
1.1 Describe the responsibilities and accountabilities of the Scrum Team and its membersThe Scrum Team, Scrum Master, Developers and Product Owner accountabilities.
- What it means
- This covers the responsibilities and accountabilities of the whole Scrum Team and of each member: the Developers who create the Increment, the Product Owner accountable for maximizing product value, and the Scrum Master accountable for the team's effectiveness and for establishing Scrum.
- What to understand
- The Scrum Team is one cohesive unit, typically ten or fewer, with no sub-teams, collectively accountable for a valuable Increment each Sprint. Each member has a distinct accountability: Developers do the work and decide how, the Product Owner owns value and the Product Backlog, and the Scrum Master is a servant leader, not a project manager. Knowing who is accountable for what is foundational.
- How it shows up
- CSM items often describe a team member's task from a course-style scenario and ask which Scrum Team accountability owns it.
- Common confusion
- Carrying over a traditional project manager role into the Scrum Master, or letting the Product Owner decide how the Developers build the work.
1.2 Explain why the Product Owner is a single person with authority over the Product BacklogOne Product Owner, authority over the backlog, collaboration with others.
- What it means
- This covers why the Product Owner is a single person and not a group or committee, and how the Product Owner maintains authority over the Product Backlog while working collaboratively with Developers and stakeholders.
- What to understand
- The Product Owner is one person so that decisions are clear and value is maximized without the delays and conflicting priorities a committee brings. The Product Owner owns the ordering and content of the Product Backlog, and although they collaborate with and gather input from Developers and stakeholders, the decision authority remains theirs and the organization respects it. Understanding this single-person authority is a frequent exam point.
- How it shows up
- A backlog-ownership situation is described, and you must apply the Product Owner's single-person authority.
- Common confusion
- Splitting the Product Owner role across a committee, or letting others override the Product Owner's backlog decisions.
1.3 Inspect and adapt to increase transparency at the Scrum eventsEmpiricism and the purpose of each event.
- What it means
- This covers identifying how a Scrum Team inspects and adapts to increase transparency at each of the Scrum events, applying the empirical pillars of transparency, inspection and adaptation across the Sprint and its events.
- What to understand
- Each Scrum event is a formal opportunity to inspect progress or artifacts and adapt accordingly, and all depend on transparency to be meaningful. Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective each inspect and adapt something specific. Understanding empiricism and how each event enacts it explains why the events exist.
- How it shows up
- An event situation is described, and you must identify how it provides inspection and adaptation.
- Common confusion
- Treating the events as routine meetings rather than deliberate inspection and adaptation points.
1.4 Perform Sprint Planning, the Sprint Review, and the Sprint RetrospectiveConducting the planning, review and retrospective events.
- What it means
- This covers performing Sprint Planning (planning the Sprint's work and goal), the Sprint Review (inspecting the Increment and adapting the Product Backlog with stakeholders), and the Sprint Retrospective (inspecting and improving how the team works), including the effects of skipping the Retrospective.
- What to understand
- Sprint Planning starts the Sprint by setting the Sprint Goal and selecting and planning work. The Sprint Review is a collaborative working session with stakeholders on the Increment and what to do next, not a one-way demo. The Retrospective improves the team's process, and skipping it loses continuous improvement. Knowing each event's purpose, timebox and participants is essential.
- How it shows up
- A planning, review or retrospective situation is described, and you must apply the correct event's purpose or conduct.
- Common confusion
- Treating the Sprint Review as a one-way demo, or skipping or devaluing the Retrospective.
1.5 Explain the Daily Scrum and how it differs from a status meetingThe Developers' daily event and its constraints.
- What it means
- This covers explaining how the Developers conduct the Daily Scrum and discussing at least three ways it differs from a status meeting and why its constraints exist to support the Developers.
- What to understand
- The Daily Scrum is a 15-minute event by and for the Developers to inspect progress toward the Sprint Goal and adapt the plan for the day. It is not a status report to the Scrum Master or a manager; its constraints, short timebox, Developer ownership, focus on the Sprint Goal, keep it a planning session that supports the Developers' self-management. This distinction is heavily tested.
- How it shows up
- A Daily Scrum situation is described, and you must explain its purpose or how it differs from a status meeting.
- Common confusion
- Treating the Daily Scrum as a status meeting where Developers report to the Scrum Master or a manager.
1.6 Explain Sprint termination and the definition of DoneWhen a Sprint may be terminated early, and the definition of Done.
- What it means
- This covers explaining the conditions under which a Sprint could be terminated prematurely, and the advantages of a strong definition of Done along with at least one way to create one.
- What to understand
- Only the Product Owner can cancel a Sprint, and typically only if the Sprint Goal becomes obsolete, which is rare. The definition of Done is the shared quality standard an Increment must meet to be releasable; a strong definition of Done creates transparency, ensures quality and reduces risk, and work that does not meet it is not part of the Increment. Understanding both is central to Scrum.
- How it shows up
- A Sprint-cancellation or quality situation is described, and you must apply Sprint termination or the definition of Done.
- Common confusion
- Thinking anyone can cancel a Sprint, or counting work that does not meet the definition of Done as complete.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Scrum Team
One cohesive team of 10 or fewer, no sub-teams.
- Remember
- Collectively accountable for the Increment.
- Tested as
- Accountability questions.
- Trap
- Adding hierarchies or sub-teams.
-
Scrum Master accountability
Team effectiveness and establishing Scrum.
- Remember
- A servant leader, not a project manager.
- Tested as
- Accountability questions.
- Trap
- Treating them as a project manager.
-
Product Owner is one person
A single person with backlog authority.
- Remember
- Not a committee; decisions respected.
- Tested as
- Role questions.
- Trap
- Splitting the role.
-
Developers self-manage
The Developers decide how to do the work.
- Remember
- They are not assigned tasks.
- Tested as
- Accountability questions.
- Trap
- Having the Scrum Master assign their work.
-
Empiricism at the events
Each event inspects and adapts.
- Remember
- Transparency enables inspection and adaptation.
- Tested as
- Event questions.
- Trap
- Treating events as routine meetings.
-
Sprint Review
Collaborative session on the Increment with stakeholders.
- Remember
- Not a one-way demo.
- Tested as
- Event questions.
- Trap
- Treating it as a demo.
-
Sprint Retrospective
Improving how the team works.
- Remember
- Skipping it loses improvement.
- Tested as
- Event questions.
- Trap
- Devaluing or skipping it.
-
Daily Scrum
The Developers' 15-minute daily plan.
- Remember
- Held by the Developers to plan their next day; any status reporting is a misuse.
- Tested as
- Heavily tested event questions.
- Trap
- Treating it as a status meeting.
-
Sprint cancellation
Only the Product Owner can cancel a Sprint.
- Remember
- Usually only if the Sprint Goal is obsolete.
- Tested as
- Sprint questions.
- Trap
- Thinking anyone can cancel it.
-
Definition of Done
The quality standard for the Increment.
- Remember
- Anything short of Done goes back to the Product Backlog.
- Tested as
- Quality questions.
- Trap
- Counting undone work.
-
Transparency
Making work and process visible.
- Remember
- It enables meaningful inspection.
- Tested as
- Empiricism questions.
- Trap
- Overlooking its necessity.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
The three accountabilities
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Developers | Create the Increment | Decide how to do the work | Being assigned work by the Scrum Master |
| Product Owner | Maximizes product value | Owns the Product Backlog, one person | Being a committee |
| Scrum Master | Team effectiveness, establishes Scrum | Servant leader | Acting as project manager |
Daily Scrum: Scrum vs. status meeting
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Daily Scrum | The Developers' daily inspection and replanning against the Sprint Goal | By and for the Developers, timeboxed | Confusing with a status meeting |
| Status meeting | Reporting progress to a manager | Not what Scrum prescribes | Choosing it as correct |
Sprint Review vs. demo
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Sprint Review | Collaborate on the Increment and adapt the backlog | Working session with stakeholders | Confusing with a demo |
| One-way demo | Show completed work only | Not the full purpose | Treating the Review as this |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Daily Scrum is a status meeting
- What candidates pick
- Describe the Daily Scrum as Developers reporting status to the Scrum Master or a manager.
- Why it looks right
- Many teams run it that way.
- Why it's wrong
- The Daily Scrum is by and for the Developers to inspect progress toward the Sprint Goal and plan the day, not a status report.
Clue to watch for The stem has the Developers updating a manager or the Scrum Master on their tasks.
-
Scrum Master assigns work
- What candidates pick
- Have the Scrum Master assign tasks to the Developers.
- Why it looks right
- It resembles project management.
- Why it's wrong
- The Developers self-manage and decide how to do the work; the Scrum Master serves rather than directs.
Clue to watch for An answer choice has the Scrum Master handing out tasks or deciding how work gets done.
-
Anyone can cancel a Sprint
- What candidates pick
- Let the Scrum Master or Developers cancel the Sprint.
- Why it looks right
- The team runs the Sprint.
- Why it's wrong
- Only the Product Owner has the authority to cancel a Sprint, typically only if the Sprint Goal becomes obsolete.
Clue to watch for Someone other than the Product Owner proposes cancelling the Sprint.
-
Product Owner is a committee
- What candidates pick
- Share the Product Owner role across several people.
- Why it looks right
- The product is large.
- Why it's wrong
- The Product Owner is one person so decisions are clear and value is maximized; it is not a committee.
Clue to watch for The scenario suggests splitting the Product Owner role.
-
Undone work counts
- What candidates pick
- Count nearly finished items toward the Increment shown at the Sprint Review.
- Why it looks right
- The work seems nearly finished.
- Why it's wrong
- Work that does not meet the definition of Done is not part of the Increment and is not complete.
Clue to watch for An item is described as almost finished, with testing or another Done criterion still outstanding.
-
Skip the Retrospective
- What candidates pick
- Skip the Sprint Retrospective to save time.
- Why it looks right
- It frees time for delivery.
- Why it's wrong
- The Retrospective drives continuous improvement; skipping it loses the team's regular chance to inspect and improve how it works.
Clue to watch for Time pressure is used to justify dropping the Retrospective.
Answer framework
For any Scrum-category scenario, use these steps to find the answer the CSM expects.
- Answer from the Scrum Guide and the reasoning behind it, not from how teams commonly behave.
- Assign responsibilities to the correct accountability, keeping the Scrum Master a servant leader, the Product Owner a single authority, and the Developers self-managing.
- Treat each event as a timeboxed inspection and adaptation point, and the Daily Scrum as the Developers planning their day, not a status report.
- Remember only the Product Owner can cancel a Sprint, typically only when the Sprint Goal is obsolete.
- Apply the definition of Done as the quality standard, counting only Done work as part of the Increment, and never skip the Retrospective.
Practice question
Want more like this? The CSM practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Study this category straight from the 2020 Scrum Guide, since the CSM is based on it, and focus on both what Scrum defines and why. The most important habit is to answer from the Scrum Guide, not from how teams often work, because many wrong options are realistic workplace deviations such as a status-meeting Daily Scrum.
Master the accountabilities, keeping the Scrum Master a servant leader distinct from a project manager, the Product Owner a single authority over the backlog, and the Developers self-managing. Learn each event's purpose, timebox and participants, especially the Daily Scrum as the Developers' event and the Sprint Review as a collaborative session. Learn who can cancel a Sprint and the value of a strong definition of Done.
Because the CSM follows a required two-day trainer-led course, use the course materials alongside the Scrum Guide, and practice applied scenario questions. Afterwards, move to Category 2, Scrum Master Core Competencies.
FAQ
What does the Scrum category cover on the CSM?
It is the core and largest category, covering Scrum as defined in the 2020 Scrum Guide: the Scrum Team and accountabilities, the events and activities, the Daily Scrum, Sprint termination, and the definition of Done.
Should I answer CSM questions from the Scrum Guide or from experience?
From the Scrum Guide. The CSM is based on it, and many incorrect options describe common workplace deviations. When an answer reflects what teams often do rather than what Scrum prescribes, it is usually wrong.
Why is the Daily Scrum not a status meeting?
The Daily Scrum is a 15-minute event by and for the Developers to inspect progress toward the Sprint Goal and plan their day. It is not a report to the Scrum Master or a manager; its constraints exist to support the Developers' self-management.
Why is the Product Owner a single person?
So that decisions about the product and the Product Backlog are clear and value is maximized without the delays and conflicting priorities of a committee. The Product Owner collaborates with others but keeps decision authority.
Who can cancel a Sprint?
Only the Product Owner has the authority to cancel a Sprint, and typically only when the Sprint Goal has become obsolete, which is uncommon. The Scrum Master and Developers cannot cancel it.
What is the value of a strong definition of Done?
It creates transparency about what complete means, ensures the Increment's quality, and reduces risk. Work that does not meet the definition of Done is not part of the Increment and is not considered complete.
How does the Scrum framework category connect to the rest of the CSM exam?
The framework here is the foundation; the Scrum Master core competencies and the service objectives both build on a precise understanding of the accountabilities, events and definition of Done established in this category.
Other Agile & Scrum certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 1 knowledge
You have covered the Scrum Team, events, the Daily Scrum, Sprint termination and the definition of Done. Test whether you can answer from the Scrum Guide, not common practice, under exam conditions.