Scrum Artifacts
Artifacts and commitments
Scrum has three artifacts, each with a commitment that supports transparency. The Product Backlog is an emergent, ordered list of what may improve the product; its commitment is the Product Goal, a long-term objective. The Sprint Backlog contains the Sprint Goal, selected items, and a plan for delivering them; its commitment is the Sprint Goal. The Increment is the sum of completed work that meets the Definition of Done; its commitment is the Definition of Done.
Ordering and done
Ordering is not the same as priority labels; the Product Owner orders the backlog to maximize value. The Sprint Backlog is a forecast, not a contract. An Increment is additive and must be usable; work that does not meet the Definition of Done is not part of the Increment. The Definition of Done creates shared transparency and should not be weakened to declare work complete.
Traps
Common traps: treating the Product Backlog as fixed; calling the Sprint Backlog a commitment to every task; assuming an Increment must be released every Sprint; treating the Definition of Done as optional; and allowing different interpretations of done within one Scrum Team. Another trap is confusing the Product Goal with the Sprint Goal.
Worked example
A team finishes coding but has not tested an item against the Definition of Done. Do not count it in the Increment. Return it to the Product Backlog for future ordering. Rule of thumb: artifact plus commitment equals transparency. If stakeholders cannot inspect the artifact against its commitment, fix the artifact or commitment before adding more reporting.