top of page

Scrum Primer - Sprint Backlog

This article is part of a series on Scrum Primer. See the first post on Sprints

Sprint Backlog lists prioritised items pulled out from the Product Backlog that meet a defined Sprint Goal. Therefore, you could think of it as a logical subset of the Product Backlog. The Development Team owns the Sprint Backlog and is created through a Sprint Planning event.

There are three must-haves for a Sprint Backlog;

Product Backlog Details
Product Backlog

Sprint Length

This can 2 weeks, 3 weeks or even 4 weeks. The length must be defined way ahead of the sprints. It's even better if it's made a standard across the organisation to ensure consistency among teams.

Sprint Goal

The goal for the Sprint is your guidance for picking a logical subset of Product Backlog items. What will your outcome (product increment) be at the end of the Sprint?

Clarify, Re-Clarify Product Backlog Items

The items selected from the Product Backlog must be crystal clear for the team - a clearly defined Story with an Acceptance Criteria.


Ensure alignment

Ensure there is a good discussion around the backlog items. The debate must happen until the whole team is aligned with the goal and everything they will do during the Sprint.

Populate the Scrum Board

Start breaking down the User Stories into tasks or To-Dos in the Scrum Board.

Assign all To-Dos

Don't have tasks un-assigned. If there is uncertainty at the start, it will linger throughout your Sprint.

16 views0 comments

Recent Posts

See All

Use Cases

[NOTE: These Use Cases explore hypothetical organisations] . Use Case 1: Digital Workforce Management for Plantation Workers Startup: AgriWork Solutions Problem Statement: Managing a large workforce a


bottom of page