Scrum has three artifacts: the Product Backlog, Sprint Backlog, and Increment. Each one has a commitment: the Product Goal, Sprint Goal, and Definition of Done. For the CSM exam, this is one of the highest-value study areas because many questions are really asking whether you understand transparency. The artifact makes work visible. The commitment makes the artifact meaningful.
Scrum Alliance still routes candidates through a 16-hour live CSM course, followed by a 50-question exam in 60 minutes that requires a 74% passing score. The official Scrum Guide explains how Scrum’s accountabilities, events, artifacts, and commitments work together. Memorizing names is not enough. You need to know why each pairing exists and what happens when a team weakens that connection.
Artifact-to-commitment map
| Artifact | Commitment | What the pairing protects |
|---|---|---|
| Product Backlog | Product Goal | Long-term value direction |
| Sprint Backlog | Sprint Goal | Focus and coherence during the Sprint |
| Increment | Definition of Done | Transparent quality at Sprint end |
Product Backlog and Product Goal
The Product Backlog is the ordered list of what is needed to improve the product. It is not a random request list, a project schedule, or a dumping ground for stakeholder wishes. The Product Owner is accountable for effective Product Backlog management, including ordering items and clearly communicating the Product Goal.
The Product Goal gives the Product Backlog a long-term objective. Without it, the backlog can become a disconnected set of requests. If a stakeholder demands a new feature, the Product Owner should consider whether it supports the current Product Goal before ordering it highly.
This is why the exam often rewards the answer that protects Product Owner accountability instead of the answer that gives the loudest stakeholder immediate control.
Sprint Backlog and Sprint Goal
The Sprint Backlog is more than a list of tasks. It includes the Sprint Goal, the selected Product Backlog items, and the Developers’ plan for delivering them. Developers own the Sprint Backlog because they are accountable for creating a usable Increment.
| Common question pattern | Better Scrum reasoning | Likely wrong answer |
|---|---|---|
| Who creates the Sprint Backlog? | Developers create it during Sprint Planning with the Scrum Team | The Product Owner assigns it |
| Can the Sprint Backlog change? | Yes, it can evolve as more is learned | It is frozen after Sprint Planning |
| What gives the Sprint coherence? | The Sprint Goal | A long list of individual tasks |
This article connects closely to Sprint Goal versus Sprint Backlog, because the exam often turns them into one combined concept check.
Increment and Definition of Done
An Increment is a concrete stepping stone toward the Product Goal. Work cannot be considered part of an Increment unless it meets the Definition of Done. For the CSM exam, the Definition of Done is often the quality boundary. It stops partial, unclear, or “almost finished” work from being treated as usable product progress.
That means a feature can be coded and still not be done. If the team’s Definition of Done includes testing, integration, accessibility checks, or documentation, then missing those items means the work is not yet part of the Increment. On the exam, answers that treat “coded” as “done” are usually traps.
Deep scenario: the unfinished feature
Imagine a Scrum Team selects five Product Backlog items for a two-week Sprint. By day nine, three are complete, one is partially built, and one is untouched. Stakeholders want the partially built feature shown during Sprint Review as if it were finished because it mostly works. The team’s Definition of Done includes automated test coverage and documentation, and those are not complete.
The stronger Scrum answer is to stay transparent. The completed work that meets the Definition of Done can be part of the Increment. The partial work should not be represented as done. During the Sprint Review, the team can still discuss what was learned, what remains, and how the Product Backlog may be adapted, but it should not blur quality boundaries just to sound more complete.
A quick way to tell whether a team is blurring artifacts
If a team cannot answer three separate questions clearly, it is probably blurring its artifacts: what creates value next, what Developers are doing right now, and what is genuinely done. That confusion shows up fast on the CSM exam because several wrong answers collapse those three questions into one generic backlog conversation.
A healthy Scrum Team can point to the Product Backlog for future value options, the Sprint Backlog for the current plan, and the Increment for usable completed work. Once those boundaries blur, quality and forecasting blur with them.
Why artifact questions are really transparency questions
Artifact questions matter because each artifact answers a different transparency question:
- Product Backlog: what might create value next?
- Sprint Backlog: what are we doing now, and how are Developers currently planning to do it?
- Increment: what is genuinely usable and done?
When candidates miss these questions, it is often because they focus on workflow convenience rather than on what Scrum is trying to make visible.
CSM-style practice questions
Who is accountable for ordering the Product Backlog?
The Product Owner is accountable for ordering the Product Backlog. Others may influence, advise, or provide technical input, but accountability stays with the Product Owner.
A team has coded a feature but it has not met the Definition of Done. Can it be part of the Increment?
No. Work must meet the Definition of Done to count as part of the Increment.
What commitment gives the Sprint Backlog focus?
The Sprint Goal gives the Sprint Backlog focus and coherence.
Scrum Artifacts FAQ
How many artifacts are in Scrum?
There are three Scrum artifacts in the Scrum Guide: the Product Backlog, Sprint Backlog, and Increment.
Why do commitments matter on the CSM exam?
They show whether you understand how Scrum turns containers of work into focused, transparent, quality-bound structures.
What is the easiest way to remember the Definition of Done?
Think of it as the quality filter that determines whether work can honestly be counted as part of a usable Increment.
Exam details verified against Scrum Alliance and the Scrum Guide on May 23, 2026. Policies and support pages can change, so verify the current CSM details before testing.
If you want a faster review tool for artifacts, commitments, and quality-boundary questions, the CSM PDF study guide includes a one-page mapping sheet and scenario explanations. If you want interactive practice, SimpuTech's CSM AI tutor can walk you through Product Backlog, Sprint Goal, and Definition of Done scenarios one question at a time.