Agile/Scrum blog

Onderwerp: Product Backlog

Implementing the Product Backlog. A practical overview on how to setup an effective Product Backlog

Ron Eringa Door: Ron Eringa,  10-04-2014
Onderwerp: Product Backlog  

Scrum Guide:
“The Product Backlog lists all features, functions, Requirements, enhancements, and fixes that constitute the changes to be made to the product in future Releases. Product Backlog Items have the attributes of a description, order, estimate, and value.”

One of the most important artifacts in Scrum is the Product Backlog. The Product Backlog is owned by the Product Owner and should be the single source for any changes that you make to your product.

The Scrum Guide tells us WHAT a Scrum Team should do with the Product Backlog to guarantee that we are continuously focusing on building the highest value features each Sprint. What the Scrum Guide doesn’t tell us is HOW to implement this Backlog and how it is used on a day to day basis. This is actually a good thing, since we don’t want to be too prescriptive towards our community, do we?