SkarpChapter 7 of 10
Artifacts and Commitments: Product Backlog, Sprint Backlog, Increment
Look inside the three Scrum artifacts and their commitments, and discover why Product Goal, Sprint Goal, and Definition of Done are among the most heavily tested concepts on PSM I.
Big Picture: 3 Artifacts, 3 Commitments
Three Artifacts, Three Commitments
Scrum has three artifacts, each with a commitment: Product Backlog + Product Goal, Sprint Backlog + Sprint Goal, Increment + Definition of Done. These are central in the 2020 Scrum Guide and heavily tested on PSM I.
Why Commitments Matter
Commitments are not extra artifacts. They are part of the artifacts, making progress transparent and guiding inspection and adaptation. Think: direction, focus, and quality bar.
Mental Model
Product Backlog + Product Goal = long‑term direction. Sprint Backlog + Sprint Goal = current Sprint focus. Increment + Definition of Done = actual usable value and quality standard.
Product Backlog and Product Goal
Product Backlog Basics
The Product Backlog is a single, ordered list of all work for the product. It is emergent and never complete. The Product Owner is accountable for managing it effectively.
One Product, One Backlog
For each product there is exactly one Product Backlog, even if multiple Scrum Teams work on it. Items are ordered, not just loosely prioritized.
Product Goal Explained
The Product Goal is the long‑term objective for the product. It provides direction to the Product Backlog and is pursued over multiple Sprints.
Only One Product Goal at a Time
There is one Product Goal at a time per product. When it is achieved or abandoned, the Scrum Team defines a new Product Goal that orients future backlog items.
Transparency Through Product Goal
The Product Goal clarifies why backlog items exist. Stakeholders can see how current and upcoming work contributes to a longer‑term outcome.
Example: Product Backlog and Product Goal in Action
Product Goal Example
Product: university course registration system. Product Goal: Enable students to register and pay online with fewer than 2% failed transactions. This is pursued over multiple Sprints.
Backlog Items Under That Goal
Backlog might include: course search, registration cart, payment integration, failure tracking, better checkout error messages. All clearly relate to the Product Goal.
Handling New Requests
If the CEO asks for "print ID cards", the Product Owner checks if it supports the current Product Goal. If not, it might be deferred to a future Product Goal rather than disrupting current focus.
Exam Angle
In PSM I, prefer answers where the Product Owner respects the current Product Goal as the main direction and uses it to discuss priorities with stakeholders.
Sprint Backlog and Sprint Goal
What Is the Sprint Backlog?
The Sprint Backlog is the plan for the current Sprint, created by the Developers. It includes the Sprint Goal, selected Product Backlog items, and a plan for delivering the Increment.
Ownership and Updating
Developers own the Sprint Backlog. It is a highly visible, real‑time picture of work for the Sprint and is updated throughout the Sprint as the team learns more.
Sprint Goal: The Objective
The Sprint Goal is a single objective for the Sprint. It explains why this Sprint is valuable and provides a shared focus for the Scrum Team.
Focus and Flexibility
The team focuses on achieving the Sprint Goal. Scope can be negotiated with the Product Owner during the Sprint as long as the Sprint Goal remains achievable.
Transparency Through Sprint Goal
The Sprint Goal makes it clear why the current work matters now. Looking at the Sprint Backlog, stakeholders can see progress toward that objective.
Activity: Strong vs Weak Sprint Goals
Decide whether each Sprint Goal is strong (good) or weak (bad), and think about why.
- "Complete 15 Product Backlog items."
- "Enable students to search for courses by department and semester."
- "Work on performance improvements."
- "Reduce average course search time from 5s to under 2s for 80% of searches."
Reflect:
- Strong Sprint Goals express outcome or capability, not just a task list.
- They are coherent: the selected items clearly contribute to a single objective.
Suggested answers (peek after thinking):
- 1: Weak – just a count of items, no clear outcome.
- 2: Strong – clear capability delivered.
- 3: Weak – too vague; no clear definition of success.
- 4: Strong – measurable improvement, outcome‑oriented.
Exam hint:
- When options include a "Sprint Goal" that is only "complete all committed items", prefer answers that define value or outcome instead.
Increment and Definition of Done
What Is an Increment?
An Increment is a concrete step toward the Product Goal. It includes all completed Product Backlog items this Sprint plus the value of all previous Increments.
Usable and Potentially Releasable
Each Increment must be usable and meet the Definition of Done. Multiple Increments can be created in a Sprint, but only work meeting the DoD counts in the Increment.
Definition of Done (DoD)
The Definition of Done is a formal description of the state of the Increment when it meets required quality measures. It gives a shared understanding of what "done" means.
Assessing Completion
The DoD is used to decide when a Product Backlog item is complete. If an item does not meet the DoD by Sprint end, it is not part of the Increment and usually returns to the Product Backlog.
Ownership and Standards
The Scrum Team owns the DoD. If the organization has mandatory standards, they must be included as a minimum. If not, the Scrum Team creates a suitable DoD.
Definition of Done: Single Team vs Multiple Teams
Single Team DoD
One Scrum Team, no org standards: the team defines its DoD, e.g., code review, passing unit tests, integrated to main branch, deployed to staging, basic security checks.
Multiple Teams, One Product
Three Scrum Teams share one Product Backlog for the same product. They must share at least one common Definition of Done so their work can combine into a single Increment.
Exam Trap: Different DoDs
If each team wants its own weaker DoD, that breaks transparency. For one product, they need a common minimum DoD. Teams may add stricter criteria on top, but not below it.
Quiz 1: Ownership and Purpose
Check your understanding of artifact ownership and commitments.
Who is accountable for creating and communicating the Product Goal and managing the Product Backlog?
- The Product Owner
- The Scrum Master
- The Developers
- The stakeholders
Show Answer
Answer: A) The Product Owner
The Product Owner is accountable for effective Product Backlog management, which includes developing and communicating the Product Goal and ordering Product Backlog items.
Quiz 2: Definition of Done and Partially Done Work
Apply the Definition of Done concept to a common exam scenario.
At the end of the Sprint, two items do not meet the Definition of Done. What is the best action?
- Release the Increment including those items if the Product Owner agrees
- Include only the work that meets the Definition of Done in the Increment; return unfinished items to the Product Backlog
- Extend the Sprint so the team can finish the items
- Mark the items as done if they are at least 80% complete
Show Answer
Answer: B) Include only the work that meets the Definition of Done in the Increment; return unfinished items to the Product Backlog
Work that does not meet the Definition of Done is not part of the Increment. The Sprint is never extended. Unfinished items go back to the Product Backlog for future consideration.
Thought Exercise: Tracing Transparency
For each question, mentally trace which artifact and commitment give transparency.
- "Are we still moving toward the long‑term outcome we want for this product?"
- Think: Product Backlog / Product Goal.
- "What are we trying to achieve this Sprint, and how are we progressing?"
- Think: Sprint Backlog / Sprint Goal.
- "Is this feature really done, and can we safely release it?"
- Think: Increment / Definition of Done.
Now, connect to exam scenarios:
- If a question is about direction over many Sprints, it is probably testing Product Goal.
- If it is about focus in a single Sprint or changing scope, it is probably testing Sprint Goal and Sprint Backlog.
- If it is about quality, partially done work, or multiple teams, it is probably testing Definition of Done and Increment.
When you practice questions, pause and label: "This is mainly about: Product Goal / Sprint Goal / DoD". This helps you pick answers consistent with the Scrum Guide 2020.
Key Terms Review
Use these flashcards to reinforce the core artifact and commitment concepts.
- Product Backlog
- The single ordered list of all work known for the product. Emergent, living artifact, managed by the Product Owner.
- Product Goal
- The long‑term objective for the product. Provides direction to the Product Backlog; one active Product Goal per product at a time.
- Sprint Backlog
- The plan for the current Sprint, created by Developers. Includes the Sprint Goal, selected Product Backlog items, and a plan for delivering the Increment.
- Sprint Goal
- The single objective for the Sprint. Provides focus and flexibility; scope may change as long as the Sprint Goal remains achievable.
- Increment
- A concrete step toward the Product Goal. A usable piece of the product that meets the Definition of Done and includes all previous Increments.
- Definition of Done (DoD)
- Formal description of the state of the Increment when it meets required quality measures. Shared understanding of what "done" means.
- Artifact Commitment
- A specific element attached to an artifact (Product Goal, Sprint Goal, Definition of Done) that enhances transparency and focuses the Scrum Team.
Key Terms
- Increment
- A usable piece of the product that meets the Definition of Done and represents a concrete step toward the Product Goal, building on all previous Increments.
- Sprint Goal
- The single objective for the Sprint that explains why the Sprint is valuable and provides focus while allowing scope flexibility.
- Product Goal
- The long‑term objective for a product that provides direction to the Product Backlog; pursued over multiple Sprints.
- Sprint Backlog
- The plan for the current Sprint, created and owned by the Developers, including the Sprint Goal, selected Product Backlog items, and a plan for delivering the Increment.
- Product Backlog
- The ordered list of all work known for a product, managed by the Product Owner and continuously refined.
- Definition of Done
- A shared, formal description of the quality criteria that an Increment must meet to be considered complete and potentially releasable.
- Artifact Commitment
- A Scrum concept where each artifact has an associated commitment (Product Goal, Sprint Goal, Definition of Done) that increases transparency and guides inspection and adaptation.