Scrum defines three formal artifacts: the Product Backlog, the Sprint Backlog and the Increment. Each exists to make a different aspect of work transparent so that a Scrum Team and its stakeholders can inspect evidence and adapt. The 2020 Scrum Guide, which remains the current official guide, also associates each artifact with a commitment: Product Goal, Sprint Goal and Definition of Done. Confusing those commitments with separate artifacts creates an inaccurate picture of the framework.
The Product Backlog makes future product work visible
The Product Backlog is an emergent, ordered list of what is needed to improve a product. It is not a one-time contract that becomes fixed after planning. The Product Owner is accountable for effective Product Backlog management and may work with others to refine it. As the team learns more from users, technical constraints or results, the contents and ordering can change.
The related commitment is the Product Goal. It describes a future state of the product that gives the team a longer-term objective. For example, a team improving an account-recovery service might aim to let users recover access securely without relying on manual support intervention. Items supporting that outcome can evolve as security and user research reveal new constraints.
The Sprint Backlog is the Developers’ plan for this Sprint
The Sprint Backlog contains the Sprint Goal, the Product Backlog items selected for the Sprint and an actionable plan for delivering the Increment. It is a plan by and for the Developers, updated as more is learned. It is not a frozen task assignment imposed by a manager at the start of the Sprint.
Its commitment is the Sprint Goal, which states why the Sprint matters. In the account-recovery example, the Sprint Goal might focus on proving that a new recovery workflow works safely for a defined group of users. If the team discovers a design defect, the plan may change while preserving focus on that outcome. A change in a technical task is not automatically a failure of Scrum.
The Increment is usable product value, not merely work completed
An Increment is a concrete step toward the Product Goal. It must be usable and meet the Definition of Done. Multiple increments may be created in a Sprint, and the Sprint Review is not a gate that must be passed before an Increment can be delivered. A team should not label unfinished integration work as Done merely because development tasks have been checked off.
The Definition of Done is the related commitment. It provides a shared understanding of the quality requirements an Increment must meet. For the recovery workflow, the team might require passing automated tests, accessible interaction, reviewed security controls and verified error handling before describing the work as complete. Those are illustrative examples of a team-owned standard, not requirements universal to every Scrum Team.
The three commitments answer different questions in an account-recovery example. The Product Goal identifies the desired long-term product outcome; the Sprint Goal explains why the team is investing this Sprint in a smaller, coherent step; and the Definition of Done sets the quality bar for any Increment claimed as usable. A successfully demonstrated interface can still fail the Definition of Done if required security review or recovery testing is incomplete. In that case the team has learned something, but it should not present unfinished work as a Done Increment.
Ownership also differs. The Product Owner is accountable for effective Product Backlog management, while Developers create and adapt the Sprint Backlog and are accountable for meeting the Definition of Done. These responsibilities do not mean that every backlog item must be a task personally assigned by a manager or that the Sprint Goal can be rewritten silently whenever work gets difficult. The official Scrum Guide is the authority for the artifact and commitment definitions; boards, status charts and local templates are optional techniques used to make the work visible.
Burndown charts and acceptance criteria are useful but different
A burndown chart, board or release forecast can help a team visualize work. Acceptance criteria can clarify what a particular item should do. These may be valuable practices, but they are not additional formal Scrum artifacts in the Scrum Guide. Treating every chart, meeting note or status report as an artifact makes the framework look larger and more prescriptive than it is.
Transparency matters more than decorative reporting. If a backlog item is ambiguous, a Sprint Goal is missing or supposedly Done work cannot be used, the team lacks the information necessary for sound adaptation. More dashboards will not repair those underlying problems.
Use artifacts together to inspect an outcome
During Sprint Planning, the team considers its Product Goal and selects an achievable Sprint Goal with the work and plan needed to pursue it. During the Sprint, the Developers revise the Sprint Backlog as they learn. The Increment provides concrete evidence of what is usable. Feedback from stakeholders can lead to changes in the Product Backlog and the next adaptation.
For Scrum teams, burndown charts, acceptance criteria and dashboard tools may support inspection, but they do not replace the Product Backlog, Sprint Backlog or Increment as the framework’s three formal artifacts. Teams should distinguish optional practices from the commitments and accountabilities defined in the current Scrum Guide.