Scrum Artifacts Explained: Product Backlog, Sprint Backlog & Increment
Direct answer: Scrum has three artifacts — the Product Backlog, Sprint Backlog, and Increment. Each represents work or value, maximizes transparency, and has a matching commitment (Product Goal, Sprint Goal, Definition of Done). That three-plus-three structure is a frequent PSM I trap.
If you only memorize “Product Backlog / Sprint Backlog / Increment,” you will still miss scenario questions that mix up owners, commitments, and who may change what during a Sprint. This page is written for the 2020 Scrum Guide and for exam-style thinking, not corporate “we call everything a backlog” slang.
Video: Scrum Artifacts Explained
What are Scrum artifacts?
In the Scrum Guide, artifacts represent work or value. They are designed so that everyone inspecting them has the same basis for adaptation. When an artifact is incomplete or opaque, empiricism breaks: the team cannot inspect reality, so they adapt guesses.
Artifacts are not optional documentation. They are the transparent record of product value (Increment), product opportunity (Product Backlog), and the Sprint plan (Sprint Backlog).
Artifact + commitment map (memorize this)
| Artifact | Commitment | Primary accountability | What transparency looks like |
|---|---|---|---|
| Product Backlog | Product Goal | Product Owner | An ordered, emergent list that is the single source of work undertaken by the Scrum Team |
| Sprint Backlog | Sprint Goal | Developers | Sprint Goal + selected Product Backlog items + actionable plan for delivering the Increment |
| Increment | Definition of Done | Scrum Team (quality bar shared) | A concrete stepping stone toward the Product Goal; must meet DoD to be an Increment |
PSM I loves this pairing. If a question mentions “commitment,” map it to the artifact before you pick an answer.
1. Product Backlog
The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work for the Scrum Team. The Product Owner is accountable for effective Product Backlog management — including ordering, clarity, and ensuring stakeholders understand items as needed.
- Emergent: it is never “done.” New understanding creates new items; completed work is removed or refined.
- Ordered: higher order means more important work first. Ordering is not the same as a fixed priority number set by a steering committee.
- Product Goal: the long-term objective for the Scrum Team. The Product Backlog exists to achieve it. Only one Product Goal at a time.
Exam traps: the Scrum Master does not own the Product Backlog; Developers may refine items but do not replace Product Owner accountability; stakeholders do not reorder the backlog in Sprint Planning by majority vote.
Deep dive: Product Backlog chapter.
2. Sprint Backlog
The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), and an actionable plan for delivering the Increment (how). It is a plan by and for the Developers. It is highly visible and updated throughout the Sprint as more is learned.
- Created during Sprint Planning.
- Inspected and adapted every day, especially in the Daily Scrum.
- The Sprint Goal may be renegotiated with the Product Owner if the plan becomes obsolete, but the Developers do not casually abandon the Sprint Goal without collaboration.
Exam traps: the Product Owner does not “assign” Sprint Backlog tasks; the Daily Scrum is not a status report to the Scrum Master; the Sprint Backlog is not frozen at Planning — it is expected to evolve within the Sprint Goal.
Deep dive: Sprint Backlog chapter.
3. Increment
An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring all Increments work together. For work to be part of an Increment, it must meet the Definition of Done.
- Multiple Increments may be created within a Sprint.
- The Increment must be usable — not “almost done pending a future hardening sprint.”
- The Definition of Done is a formal description of the state of the Increment when it meets quality measures required for the product.
Exam traps: “Done” is not individual preference; if multiple teams share a product, they must mutually define and comply with the same Definition of Done; releasing may happen multiple times per Sprint — release is a business decision, creating a Done Increment is not optional.
Deep dive: Increment chapter.
How the three artifacts work together
- The Product Owner orders the Product Backlog toward the Product Goal.
- In Sprint Planning, Developers select items and create a plan (Sprint Backlog) toward a Sprint Goal.
- During the Sprint, Developers turn selected items into a Done Increment.
- In the Sprint Review, stakeholders inspect the Increment and adapt the Product Backlog.
- In the Sprint Retrospective, the Scrum Team improves quality and effectiveness (often refining how DoD and transparency work).
If transparency is weak on any artifact, inspection becomes theater and adaptation becomes guesswork. That is the empiricism thread Scrum.org tests heavily.
PSM I exam traps about artifacts
| Trap wording | What the Guide actually implies |
|---|---|
| “Who prioritizes the Sprint Backlog?” | Developers own the Sprint Backlog plan. Product Owner owns Product Backlog ordering, not task assignment inside the Sprint. |
| “Can the Product Owner cancel unfinished Sprint work mid-Sprint alone?” | Focus on Sprint Goal collaboration. Changing the plan requires Developer + Product Owner collaboration when the Goal is at risk. |
| “Is documentation an Increment?” | An Increment must meet DoD and be a usable product step — not a pile of unfinished tasks or partial components that cannot create value. |
| “Are commitments optional?” | Each artifact has a commitment that reinforces empiricism and focus. Know all three: Product Goal, Sprint Goal, Definition of Done. |
Quick practice: think like the exam
- Question pattern: “Who is accountable for maximizing value?” → Product Owner / Product Backlog effectiveness, not the Scrum Master micromanaging items.
- Question pattern: “What is created in Sprint Planning?” → Sprint Goal + selected items + plan (Sprint Backlog), not a fixed contract signed by stakeholders.
- Question pattern: “When is work part of the Increment?” → When it meets the Definition of Done.
Want volume practice with explanations? Use the free adaptive PSM I practice test or a timed PSM I mock exam. For the full certification map, see the PSM I guide.