The Product Backlog

The Product Backlog is a prioritized, ordered list, sorted by business value and risk. it contains the work needed to accomplish the project. The Product Backlog often contains user stories but may also contain functional requirements, nonfunctional requirements, bugs and various issues. The Product Backlog is estimated in abstract units such as story points, which use a relative weighting model. The Product Backlog is owned and managed by the Product Owner. The definition of done heavily influences it as well. 

The release plan can be derived through calculations on the Product Backlog. Each Sprint, the team will have a number of stories it can output. This number becomes the teams velocity. Velocity is how much product backlog effort a team can handle in one sprint. This can be estimated by viewing previous sprints, assuming the team composition and sprint duration are kept constant. It can also be established on a sprint-by-sprint basis, using commitment-based planning. Once established, velocity can be used to plan projects and forecast release and product completion dates.

The Product Owner can estimate what stories will be complete, and when, by viewing the size of the story and fitting stories into Sprints based on the velocity the team is able to execute. The Product Backlog should follow Bill Wake's INVEST model (external link) where stories should be:

  • I - Independent
  • N - Negotiable
  • V - Valuable
  • E - Estimable
  • S - Small
  • T - Testable

Sample Product Backlog:

Productbacklog