The Scrum events give a team its rhythm, and the artifacts give those events something to inspect. Scrum has three artifacts, the Product Backlog, the Sprint Backlog, and the Increment. Each one represents work or value and is designed to make key information as transparent as possible, so that everyone inspecting it has the same basis for adaptation.
Each artifact also carries a commitment that adds focus and gives progress something to be measured against. The Product Backlog has the Product Goal, the Sprint Backlog has the Sprint Goal, and the Increment has the Definition of Done. These commitments exist to reinforce empiricism and the Scrum values for the Scrum Team and its stakeholders.
You'll start with an overview of the artifacts and commitments. Then you'll look at the Product Backlog as the single, ordered source of work for the Scrum Team, the Sprint Backlog as the Developers' plan for the Sprint, and the Increment as the usable, verified result that meets the Definition of Done.
With the artifacts clear, you'll be ready for the next module, Backlog Management & User Stories, where you learn how to keep the Product Backlog healthy and write items the team can act on.
An overview of the three Scrum artifacts and their commitments as the Scrum Guide describes them: the Product Goal, the Sprint Goal, and the Definition of Done.
The Product Backlog as defined in the 2020 Scrum Guide: an emergent, ordered list of what is needed to improve the product, and how refinement prepares items for Sprint Planning.
The Sprint Backlog as described in the 2020 Scrum Guide: the Sprint Goal, the selected Product Backlog items, and the Developers' plan for delivering the Increment.
The Increment as defined in the 2020 Scrum Guide: a usable stepping stone toward the Product Goal that meets the Definition of Done.