Scrum Artifacts

In archaeology, the term “artifact” refers to an object that was made by a human. The Latin roots of the word artifact roughly translate to “Work of Art.” So, an artifact is something that we make, either a tool that solves a problem, or a work of art that inspires us. Scrum describes three primary artifacts: the Product Backlog, the Sprint Backlog, and the Product Increment.

Click the play buttons below to view the videos.


Scrum Artifacts (3:48)

In this module, you’ll see how the three Scrum Artifacts — the Product Backlog, the Sprint Backlog, and the product Increment — share the same goals: to maximize transparency, and promote a shared understanding of the work. Main takeaway: The Product Backlog and Sprint Backlog describe work to be "Done" that will add value, and the product Increment is the “Done” portion of the product completed during a Sprint.


Product Backlog (2:20)

This segment talks about the Product Backlog, which is the Scrum artifact that answers the question: “What is most important to build next?” Main takeaway: With the dynamic nature of product development, the Product Backlog is constantly being updated and refined.


Product Backlog Refinement (2:16)

In previous installments, we described the Product Backlog as a “constantly evolving artifact” that is never complete. This segment shows how Product Backlog Refinement is the work that is "Done" to constantly evolve the Product Backlog. Main takeaway: Product Backlog Refinement is an ongoing activity throughout the life of a Product Backlog.


Sprint Backlog (2:33)

Learn more about the Sprint Backlog by thinking of it this way: The Sprint Backlog can be thought of as having two components: the “What” of the Sprint and the “How” of the Sprint. It also contains the Development Team’s plan for how they will deliver the product Increment and realize the Sprint Goal. Main takeaway: The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.


The Increment and Definition of Done (01:58)

In the final module of the Artifact section, you’ll learn that an Increment is broadly defined as an increase or addition. In Scrum, the Development Team works to deliver a new Increment of the product every Sprint. In order to assess when work is complete on a Product Backlog item or an Increment, the Scrum Team creates a shared definition of "Done." Main takeaway: The definition of Done is what guides the Development Team and provides transparency about the level of quality that is considered sufficient to release an Increment.

Links to other eLearning Series Sections:

Ready for more?

© 2017 Peter Green. All rights reserved. Licensed to Scrum Alliance, Inc. with permission.