Product Backlog - International Scrum Institute

In the simplest definition the Scrum Product Backlog is simply a list of
all things that needs to be done within the project. It replaces the
traditional requirements specification artifacts. These items can have a
technical nature or can be user-centric e.g. in the form of user
stories. The owner of the Scrum Product Backlog is the Scrum Product
Owner. The Scrum Master, the Scrum Team and other Stakeholders
contribute it to have a broad and complete To-Do list.


Working with a Scrum Product Backlog does not mean that the Scrum
Team is not allowed to create and use other artifacts. Examples for
additional artifacts could be a summary of the various user roles,
workflow descriptions, user interface guidelines, storyboards, or user
interface prototypes. However, these artifacts do not replace the Scrum
Product Backlog but complement and detail its content.


The Scrum Product Owner uses the Scrum Product Backlog during the
Sprint Planning Meeting to describe the top entries to the team. The
Scrum Team then determines which items they can complete during the
coming sprint.


Each Scrum Product Backlog has certain properties that differentiate it from a simple to-do list:


  • an entry in the Scrum Product Backlog always add value for the customer
  • the entries in the Scrum Product Backlog are prioritized and ordered accordingly
  • the level of detail depends on the position of the entry within the Scrum Product Backlog
  • all entries are estimated
  • the Scrum Product Backlog is a living document
  • there are no action-items or low-level tasks in the Scrum Product Backlog






The Scrum Product Backlog - International Scrum Institute

Comments

Popular posts from this blog

IKIGAI as a tool for inclusive communities

Kindness Week: transforming our community one kind act at a time!

Quality Management Systems