A collection of stories and tasks the Sprint team will work on at some point in the future. Either the Product Owner has not prioritized them or has assigned them lower priority. Teams or organizations may use the term “backlog” in one of the following four ways:

  • Stories or tasks that are likely to be considered in the next iteration’s planning game.
  • Stories or tasks that are definitely planned to be worked on in the next iteration (rather than just being available for consideration).
  • Stories or tasks that are assigned to the current iteration, but are not being worked on, yet. As the team has time, these will be worked on after the higher priority items are completed.
  • In a very fluid team, the planning game may assign more stories than can be done during the iteration. The backlog consists of stories and tasks that may slip into the next iteration.

Related Resources

Agile Requirements: User Stories, Backlogs, & Beyond [Agile Amped Podcast] Industry Favorites: Product Backlog Resources [Blog] Product Owner Anti-Patterns, Part 2: The Churning Backlog [Blog]