Sprint Backlog

Definition of Sprint Backlog:

A sprint backlog is a list of Product Backlog Items (PBIs) that the team selects to complete during a Scrum sprint. These PBIs are typically user stories taken from the product backlog.

Backlog

Use of the Sprint Backlog:

During the sprint planning meeting, the team decides which PBIs or user stories to include in the next sprint, based on the estimated work effort and team capacity needed to complete each one. The team breaks the PBI’s or user stories down into tasks and assigns an estimate in work hours for completing each task.

Synonyms for Sprint Backlog:

Iteration Backlog

Benefits of the Sprint Backlog:

  • ensures that the highest-priority PBIs are completed first.
  • allows for longer term planning.
  • breaks down work into manageable components.
  • allows the team to determine the amount of PBIs they can accomplish during the sprint.
The Sprint Backlog explained by Sohrab Salimi

Product Owner Trainings

=> Become a Certified Scrum Product Owner

Scrum Master Trainings

=> Become a Certified ScrumMaster

Author

Sohrab Salimi

Scrum Academy GmbH

Sohrab is a long-standing Certified Scrum Trainer (CST) and CEO of the Scrum Academy GmbH based in Cologne. He is a trained medical doctor and worked for Bain & Company as a consultant and as a CIO at SE-Consulting, among others, before founding the Scrum Academy. As a consultant and trainer, he has been supporting companies from a wide range of industries for over a decade on topics related to agile transformation, innovation and organizational development.

Related articles

Lean-Agile Procurement

Lean Agile Procurement brings you one step closer to become an agile Organization. Learn what is important to be completely agile!

What can really happen when you build experiments as a corporate

Strategyzer Coach and Expert Paris Thomas talked at the agile100 about Organisational Innovation and why you must experiment as a company!

A new Framework to Create Clarity and Succeed

Find out, why most companies fail due to systemic problems and not because of their product. Nils Holger Pohl in Session at agile100