Scrum Artifacts and Commitments
What you must know
Each artifact represents work or value and carries a commitment that reinforces transparency and focus.
- Product Backlog → Product Goal. The backlog is an emergent, ordered list of what is needed to improve the product; it is the single source of work. The Product Goal describes a future state of the product and gives the team a long-term target.
- Sprint Backlog → Sprint Goal. The Sprint Backlog is composed of the Sprint Goal (why), the selected items (what), and the plan (how). The Sprint Goal is the single objective for the Sprint and provides coherence and flexibility.
- Increment → Definition of Done. An Increment is a concrete, usable step toward the Product Goal. The Definition of Done is the formal description of quality; if an item does not meet it, it cannot be released or presented at the Review and returns to the backlog.
The Product Backlog is refined continuously; the Sprint Backlog is updated throughout the Sprint as more is learned. Commitments are not fixed promises of scope - they create transparency about intent. Multiple teams on one product share one Product Backlog, one Product Owner, and one Product Goal.
Traps
- "The Sprint Goal is a list of backlog items" - it is one objective, and items are chosen to serve it.
- "The Definition of Done is set by the Scrum Master" - the team creates it; the organization may set a minimum standard.
- "An Increment must be released each Sprint" - it must be usable, not necessarily released.
- Confusing the Product Goal (long-term, product-level) with the Sprint Goal (one Sprint).
Rule of thumb
Pair each artifact with its commitment: Backlog→Product Goal, Sprint Backlog→Sprint Goal, Increment→Definition of Done. For quality questions, ask whether the work meets the Definition of Done before it can count.
Worked example: A developer finishes a feature but it lacks automated tests required by the Definition of Done. It is not part of the Increment; it returns to the Product Backlog for further work.