Scrum Artifacts

Definition

Scrum Artifacts are core elements of the Scrum framework that provide transparency about work and progress. They help Scrum Teams and stakeholders make informed decisions based on the same information.

Context

Scrum Artifacts are designed to maximize transparency, so everyone involved can inspect the current state of the product and adapt plans as needed. This supports empiricism, one of the foundations of Scrum, and strengthens alignment between the Scrum Team and stakeholders.

Description

The Scrum framework defines three main artifacts:

• The Product Backlog is a transparent, ordered list of all work needed to improve the product.

• The Sprint Backlog contains the Sprint Goal, which describes the outcome or impact the team aims to achieve, the Product Backlog Items selected for the Sprint, and the plan for delivering them.

• The Product Increment is the sum of all completed work that meets the Definition of Done.

Each Scrum Artifact has a commitment that enhances transparency and focus:

• Product Backlog → Product Goal

• Sprint Backlog → Sprint Goal

• Increment → Definition of Done

The Product Backlog and Sprint Backlog represent work that has not yet been completed. The Increment represents the working product created so far. These artifacts ensure that all Scrum Team members and stakeholders share the same understanding of the product and progress.

Example

Imagine a Scrum Team building a new mobile banking app.

• The Product Backlog lists all features, improvements, and fixes planned for the app.

• The Sprint Backlog shows the current Sprint Goal (e.g., "Enable secure user login"), the selected Product Backlog Items to achieve it, and the plan for delivering them in the Sprint.

• The Increment at the end of the Sprint is the working version of the app with the new login feature integrated and tested.

Common Misunderstandings

A common misconception is that the artifacts are just documents or reports. In reality, they are living elements that evolve as the product and the Scrum Team’s understanding evolve. Another misunderstanding is that the artifacts only exist for the Scrum Team. In fact, they are equally important for stakeholders to understand progress and priorities. A common misunderstanding is that a Definition of Ready is another artifact in Scrum. If you are keen to learn more about the Definition of Ready, click here.

Want to Learn More?

Read the Product Backlog article to see how this artifact captures all planned work. Explore the Sprint Backlog article to understand how teams plan each Sprint and set their Sprint Goal. Both articles feature additional videos to dive deeper.