Scrum Artifacts Explained: Product Backlog, Sprint Backlog and Increment

Scrum artifacts represent important work or value within Scrum. They provide transparency so the Scrum Team and stakeholders can understand what is happening and make better decisions.

Scrum has three main artifacts: Product Backlog, Sprint Backlog and Increment.

1. Product Backlog

The Product Backlog is an ordered list of what is needed to improve the product.

It is the single source of work undertaken by the Scrum Team. The Product Owner is accountable for effective Product Backlog management.

Commitment: Product Goal

The Product Goal describes a future state of the product that the Scrum Team is working toward.

2. Sprint Backlog

The Sprint Backlog contains the work selected for the Sprint, together with the Sprint Goal and the Developers' plan for delivering the Increment.

It is a plan created and adapted by the Developers during the Sprint.

Commitment: Sprint Goal

The Sprint Goal is the single objective for the Sprint. It provides flexibility while giving the team a shared purpose.

3. Increment

An Increment is a concrete stepping stone toward the Product Goal.

Multiple Increments can be created during a Sprint. An Increment must meet the Definition of Done to be considered part of the product.

Commitment: Definition of Done

The Definition of Done is a formal description of the quality state required for work to be considered complete.

Scrum Artifacts at a Glance

Artifact
Commitment
Product Backlog
Product Goal
Sprint Backlog
Sprint Goal
Increment
Definition of Done

How They Connect

The Product Backlog contains the work needed to improve the product.

During Sprint Planning, Developers select Product Backlog items and create a plan for achieving the Sprint Goal.

During the Sprint, the Developers work toward the Sprint Goal and create an Increment that meets the Definition of Done.

Product Backlog ↓ Sprint Backlog ↓ Increment

Why Are Artifacts Important?

Scrum relies on transparency. If the state of the work or product is unclear, decisions can be based on incorrect information.

Scrum artifacts help everyone inspect the same information and make appropriate adaptations.

Easy way to remember:

Product Backlog → What is needed
Sprint Backlog → What we are working on
Increment → What we have created

What Comes Next?

We will now examine each artifact separately, starting with the Product Backlog.