← Back to The Checklist

The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).$^1$

The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum.

A Sprint Backlog is a subset of the Product Backlog and lists the work items to complete in one specific Sprint. The Sprint Backlog aims to identify items from the Product Backlog that the team will work on during the Sprint. This occurs during the Sprint Planning process. These items move from the Product Backlog into the Sprint Backlog and shouldn’t change once the Sprint begins.

Double Click to Enlarge

The exact frequency will vary based on how long your Sprints are, but you’ll likely be doing this every two weeks or once a month.

A clear Sprint Backlog prevents scope creep by clarifying exactly what your team will be doing—and not doing—during each sprint.$^2$

The Sprint Backlog is then broken down further into User Stories with their subsequent tasks to complete each one.

What’s Included?

Your backlog should document specific components like the name of your current sprint, the descriptions and user stories for each initiative, each task’s priority, relevant real-time changes, and scheduling details for sprint planning meetings or daily standups—to name a few.

Here are some standard details you’ll find within a Sprint Backlog; see the first image above if you’re a visual learner (like me):

User Story

A user story is a software feature (or perhaps a specific feature of any non-software product) written from the end-user’s perspective. It’s an important piece to include to understand each feature’s effect on the end-user.

Task Info

• Task name: While obvious enough, keep your backlog organized by starting each task with a clear, action-oriented name. Ensure each task title begins with a verb—for example, “Design new mobile component for the web app” is more descriptive than “New mobile component.” This will help stakeholders quickly understand the backlog (and prevent unnecessary questions) and deliverables that each team member is working on.
• Task description: Along with an actionable name, include a brief description of each task. This creates clarity around tasks, so stakeholders are aware of upcoming steps.
• Task prioritization: Since there are several tasks in a given project, it’s crucial to prioritize your most important objectives. This ensures you meet deadlines and your sprint stays on track.

Metrics

• Sprint burndown chart: A burndown chart is a graph that represents the work left to do versus the time it takes to complete it. Your team will use these charts to estimate how long each iteration will take.
• Daily time allocation: To track your time estimates against the actual time on your burndown chart, you need to track daily time allocations. Analyze how long each task takes in minutes or hours. Total up your weekly time allocations for each task to complete your burndown chart at the end of the week.

While each sprint backlog will differ slightly, these are all essential details to include when starting your backlog.

$^1$The 2020 Scrum Guide

$^2$Asana