Receive weekly Agile & Scrum tips

close menu icon

Sprint Backlog

Table of contents

Definition of the Sprint Backlog

The Sprint Backlog is a plan made by and for the Developers in a Scrum Team. This backlog consists of three elements and is created during the Sprint Planning meeting. The three elements are:

  1. The tasks that the Developers plan to complete in the Sprint.
  2. The Sprint Goal.
  3. An actionable plan for delivering the Increment.

* The tasks are actually called Product Backlog items (PBIs).

For and by Developers

The Developers ultimately decide which items are included in the Sprint and how they will be worked on. This means they determine how the Sprint Goal is achieved. Developers therefore play an active role in planning and executing the work. Self-management is an essential part of Scrum and contributes significantly to job happiness.

Living document

The Sprint Backlog is also referred to as a living document: the Developers adjust it throughout the Sprint as more is learned and new insights are gained. Ultimately, it is an essential tool for getting the work done and achieving the Sprint Goal.

Transparency is crucial

Transparency is a crucial pillar in Scrum, as it is for the Sprint Backlog. All team members should be able to clearly see the content and progress of this backlog. This facilitates daily inspection (for example, during the Daily Scrum) and allows for adjustments when more is learned. The Scrum Team decides for themselves how they make the backlog transparent for the Sprint. For example, via software or a physical board with post-its.

Share this explanation with your network
Sluit je aan bij 1.000+ professionals

Ontvang tips, tools en tactieken uit de Agile en Scrum community wekelijks in je inbox

Join 1,000+ professionals

Receive free tips, tools and tactics from the Agile and Scrum community in your inbox.