Scrum Artifacts and Commitments: Backlogs, Goals, and the Increment
Introduction
The three Scrum artifacts show where the product is going, what the Developers plan to do this Sprint, and what usable work exists. Each has a commitment. The Product Goal guides the Product Backlog, the Sprint Goal focuses the Sprint Backlog, and the Definition of Done sets the quality standard for the Increment.
For PSM I, these artifacts belong to Understanding and Applying the Scrum Framework. You will connect each artifact to its commitment and apply the distinction when plans change, backlog items need refinement, or work is presented at the Sprint Review.
Learning objectives
- Define the Product Backlog and the Product Goal, and explain how they relate.
- Define the Sprint Backlog and the Sprint Goal, and explain how they are updated during the Sprint.
- Define the Increment and explain how it relates to the Definition of Done.
- Describe Product Backlog refinement: who does it, when, and why.
- Explain transparency and why a misleading artifact is a problem the Scrum Master must address.
1. Product Backlog and the Product Goal
The Product Backlog is the Scrum Team’s single ordered list of work to improve the product. As the team learns, it revises that list. An item is ready to be considered during Sprint Planning when the team can reasonably complete it to the Definition of Done within one Sprint. Refinement helps the team reach that level of understanding.
Important properties:
- Emergent: it changes as the team learns about the product, its users, and its environment.
- Ordered: the Product Owner is accountable for Product Backlog management, including ordering. The guide does not prescribe how to order; value, risk, dependencies and urgency are common inputs.
- Single: there is one Product Backlog for one product, even when several Scrum Teams work on it.
- Transparent: the people who use it to make decisions can see and understand it.
The Product Goal
The Product Goal is the team’s long-term objective and is part of the Product Backlog. It describes a desired future state that helps the team decide which work to pursue. The Scrum Team completes or abandons that objective before it takes on another. For practical ways to order work toward the goal, see Product Backlog management and product value.
Example: from vision to goal
A regional library network owns an app that lets members search the catalogue. Its Product Owner defines the Product Goal: "Within 12 months, 60% of eligible loans are renewed in the app without staff help." This goal says nothing about technology or features. It is measurable, long-term and gives the Scrum Team a target. The Product Backlog contains items such as "Show renewal button on the loan detail screen", "Notify members three days before due date", and "Block renewal if another member has reserved the book". Items unrelated to the goal (e.g., "new colour theme") are ordered lower or removed.
Product Backlog refinement
During refinement, the team makes items smaller or clearer as needed. Developers who will do the work size the items, while the Product Owner helps them understand tradeoffs. The team might refine a complicated change in several conversations and leave less urgent work at a higher level of detail.
The 2020 Scrum Guide treats refinement as an ongoing activity. Teams choose when and how to do it. A regular session, acceptance criteria, or an item sizing convention can be useful local practices.
Comparison: Product Backlog versus requirements document
| Aspect | Product Backlog | Traditional requirements document |
|---|---|---|
| Completeness | Never complete; evolves with learning | Intended to be complete before work starts |
| Order | Ordered by the Product Owner | Often unordered or ordered by a phase plan |
| Change | Welcome at any time | Managed through change control |
| Owner | Product Owner is accountable | Often a business analyst or committee |
| Granularity | Top items small and precise, lower items coarse | Uniformly detailed |
2. Sprint Backlog and the Sprint Goal
The Sprint Backlog holds the Sprint Goal, the selected Product Backlog items, and the Developers’ plan to deliver the Increment. The Developers update it when they learn something that affects the plan. It should be detailed enough to support inspection at the Daily Scrum.
The Sprint Goal
The team agrees on the Sprint Goal during Sprint Planning. The Developers commit to that objective and can adjust how they achieve it. When a change affects the selected scope, the Developers discuss it with the Product Owner and protect the Sprint Goal.
Example: a Sprint Goal that keeps flexibility
For the library app, the Sprint Goal for Sprint 4 is "Members can renew a loan from the loan detail screen." The Developers plan the renewal button, API call, error message, email confirmation, and a reservation check. On day 5 they learn that email confirmation depends on an unavailable service. They agree with the Product Owner to use an on-screen confirmation and return email confirmation to the Product Backlog. Members can still renew loans safely because the reservation check remains in scope.
Who changes the Sprint Backlog?
The Developers maintain their plan. When the selected scope needs to change, they negotiate it with the Product Owner and keep the Sprint Goal in view.
3. The Increment
An Increment is a usable result that advances the Product Goal. It builds on earlier Increments and must work with them. Work joins an Increment only when it meets the quality criteria. See how the Definition of Done works for a closer look at those criteria.
Increment and release timing
A Scrum Team can create multiple Increments in one Sprint and deliver a usable Increment before the Sprint Review. The Review gives stakeholders a chance to inspect the overall outcome. The Scrum Guide leaves release decision rights and operational approval processes to the organization.
Example: inspect a usable Increment
A library team adds online renewal in the first week of a Sprint. It tests renewals against the catalogue and checks that existing borrowing still works. The new version meets the Definition of Done and the team makes it available to one branch. The team records how many borrowers complete renewal without help. That early use gives the Product Owner evidence to discuss at the Review.
In the second week, the team adds a reminder in the app. The reminder triggers twice on some devices, so the updated version fails the agreed quality checks. The version that already meets the Definition of Done is still usable. The reminder stays outside the Increment until the defect is resolved and the combined work passes the checks. At the Review, the team can discuss the delay and its consequences while presenting the usable result.
Acceptance criteria and the Definition of Done answer different questions here. The renewal item’s criteria might require members to see a new due date. The Definition of Done might also require accessibility and regression checks across the app. Meeting the renewal criteria alone does not establish that the updated product meets the broader quality standard.
Comparison: three artifacts, three commitments
| Artifact | Commitment | Question it answers | Owner / main author |
|---|---|---|---|
| Product Backlog | Product Goal | Where is the product heading and what is needed? | Product Owner is accountable |
| Sprint Backlog | Sprint Goal | Why is this Sprint valuable and how will we do it? | Developers |
| Increment | Definition of Done | Which usable work meets the product’s quality standard? | Scrum Team, following any organizational minimum |
4. Transparency and the commitments
The commitments give readers a standard against which to inspect each artifact. An ordered list is easier to interpret when people can see what Product Goal it serves. The Sprint Goal helps Developers decide whether a change to the plan is appropriate. The Definition of Done makes it possible to compare a board’s status with what the product can actually do.
When two people interpret an artifact differently, the Scrum Master can help surface the difference. Ask the Product Owner and Developers to compare the list of priorities with the work they actually plan to undertake. If those priorities conflict, make the disagreement visible and work from one Product Backlog.
Example: a Product Backlog nobody trusts
A bank's Product Owner keeps two lists: the official Product Backlog and a private spreadsheet with "real" priorities for key executives. The Developers discover that urgent items appear in the Sprint without passing through the backlog. The Scrum Master coaches the Product Owner to merge the lists, explain ordering rationale in the Sprint Review, and invite the executives to inspect the single backlog. Transparency improves, and the number of surprise requests drops.
5. Worked example: is this item ready, and who decides?
Statement. The Product Backlog has two candidate items for the next Sprint:
- Item A: "As a member I can renew a loan." It has acceptance criteria, a rough size of 5, and its dependencies are known.
- Item B: "Improve performance." It has no criteria and no size, and it is at the top of the backlog because a director insisted.
The Developers say B is too vague. The director wants B in the Sprint anyway. The Scrum Master is asked what to do.
Reasoning, step by step.
- Is B ready for selection? To consider B for selection, clarify the expected outcome and whether the team can reach it within one Sprint at the agreed quality standard.
- Who orders the backlog? The Product Owner. The director may influence the Product Owner but cannot reorder the backlog directly.
- Who decides how much goes into the Sprint? The Developers, in discussion with the Product Owner.
- What does refinement offer? The Product Owner and the Developers can refine B into smaller, precise items (for example, "Reduce the 95th-percentile response time for catalogue searches from four seconds to one second under a specified load").
Solution. Ask the director which users and requests are affected. Refine the item into work the Developers can size. At Sprint Planning, consider selecting a piece if it supports the Sprint Goal and fits the team’s forecast.
Why the other choices are worse. Forcing B into the Sprint ignores the Developers' accountability for what they can forecast. Letting the Scrum Master reorder the backlog takes the Product Owner's accountability away. Postponing the performance topic indefinitely ignores a genuine stakeholder need. Writing a detailed specification for every future item wastes effort because the backlog is emergent.
6. Common pitfalls and exam tips
- The Product Owner is accountable for the Product Backlog, even when others help. "Accountable" does not mean "writes every item"; the Product Owner may delegate the work.
- Only one Product Backlog per product, no matter how many teams work on it.
- The Product Goal sits in the Product Backlog and is the long-term objective; the Sprint Goal sits in the Sprint Backlog and is the Sprint's objective. A frequent trap swaps them.
- The Sprint Backlog is changed by the Developers during the Sprint. It is not frozen after Sprint Planning.
- Burn-down charts help forecasting but do not replace empiricism: the guide says that they, and similar practices, are useful but do not replace the importance of empiricism. In complex environments, what will happen is unknown.
- No Increment without Definition of Done. Work that misses the Definition of Done cannot be released or presented at the Review and returns to the Product Backlog.
- Release timing. A Done Increment may be delivered before the Review. Use the organization’s release process.
- Refinement is not a formal event. The Scrum Team decides how it is done. Do not select an answer that says refinement "is a required meeting".
- Exam tip: read carefully who does what: the Product Owner orders, the Developers size, the Developers plan the Sprint Backlog, the Scrum Team creates the Increment.
7. Mini case study
Situation. A Scrum Team of eight builds a point-of-sale system. After Sprint 5 the following facts are known:
- The Product Backlog has 340 items. Even the first few items lack enough detail to judge what they would change. Two stakeholders keep separate lists they pass directly to individual Developers.
- Sprint Planning ends with a list of items but no Sprint Goal: the Product Owner says "all items are equally important".
- Items often remain "90% done" at the end of the Sprint. The Developers show them at the Review as "almost working".
- The Product Goal is "be the best POS in the market".
- The Scrum Master is asked to maintain the Sprint Backlog and update it every night.
Questions. (1) What is wrong with each artifact? (2) What should the Scrum Master do?
Commented solution.
- Product Backlog: it is neither ordered nor single, and detail is missing. The Product Owner should consolidate the lists, order them and explain why. Refinement should bring the top items to a level the team can select. The Product Owner may trim items that are no longer useful.
- Product Goal: "be the best POS in the market" is not a usable target. A better goal might be "Enable shops in both pilot regions to keep selling during an internet outage and reconcile sales when the connection returns." The team could use pilot adoption and reconciliation errors to judge progress. It must be something the Scrum Team can plan against and later fulfil or abandon.
- Sprint Goal: it is missing. Without a Sprint Goal, the Developers are likely to work on separate items and lose coherence. Sprint Planning should produce one.
- Increment: "90% done" work does not meet the Definition of Done, so it is not an Increment and should not be presented as one. The team should show only Done work and return the rest to the Product Backlog.
- Sprint Backlog: it belongs to the Developers. The Scrum Master should coach them to keep it up to date themselves, not do it for them.
Scrum Master actions. Facilitate a workshop on the three commitments, help the Product Owner with Product Backlog techniques, help the Scrum Team define a Definition of Done that respects any organizational standard and that Developers can apply consistently, and use Retrospectives to check whether transparency has improved.
Key terms
- Product Backlog: ordered, emergent list of what is needed to improve the product; the single source of work.
- Product Goal: long-term objective of the Scrum Team; commitment for the Product Backlog.
- Sprint Backlog: Sprint Goal, selected items and a plan for delivering them; owned by the Developers.
- Sprint Goal: single objective for the Sprint; commitment for the Sprint Backlog.
- Increment: usable stepping stone toward the Product Goal; must meet the Definition of Done.
- Definition of Done: formal description of the state of the Increment when it meets the quality measures; commitment for the Increment.
- Refinement: ongoing activity to break down and define Product Backlog items.
- Transparency: shared, honest view of the work and the product state.
Summary checklist
- The Product Backlog is a single, ordered, emergent list, and the Product Owner is accountable for it.
- The Product Goal belongs to the Product Backlog; the Scrum Team fulfils or abandons it before taking on another.
- Items that can be Done in a Sprint are ready for selection.
- Refinement is ongoing; the Developers size the items.
- The Sprint Backlog combines the Sprint Goal, selected items and a plan, and is updated throughout the Sprint by the Developers.
- The Sprint Goal stays fixed while scope may be renegotiated.
- An Increment is usable, additive, verified and meets the Definition of Done; multiple Increments can be created in a Sprint.
- The Sprint Review is never a gate to release.
- Each artifact has one commitment: Product Goal, Sprint Goal, Definition of Done.
Sources
- The Scrum Guide (November 2020), Ken Schwaber and Jeff Sutherland, CC BY-SA 4.0: https://scrumguides.org/scrum-guide.html (opens in a new tab)
- Scrum.org, Professional Scrum Master I assessment: https://www.scrum.org/assessments/professional-scrum-master-i-certification (opens in a new tab)
- Scrum.org, suggested reading for the Professional Scrum Master: https://www.scrum.org/resources/suggested-reading-professional-scrum-master (opens in a new tab)
