Plots your user stories on a chart based on Effort vs.Calculates how many sprints you can afford to deliver based on your project budget.Calculate the number of releases required to deliver your backlog based on your velocity.Assign stories to sprints (release plan).This Product Backlog template provides the following tools: ongoing development, the value needs to be packed into each sprint. In a product development environment i.e. At a project-level, this value needs to be front-loaded into the development schedule – a side-benefit of this might be a self-funding project scenario. The primary objective of the Product Manager is to deliver value. The Product Manager will then begin to define, prioritise and add additional User Stories to the backlog in preparation for the next sprint – this might include new requirements or changes emerging from the previous sprint. Once broken down into User Stories, the Team will provide delivery estimations and commit to delivering a number of these stories (in line with pre-defined priorities) in the following sprint. become higher priority, the Product Manager will work with the team to break Themes and Epics into User Stories.

User Stories – an Independent, Negotiable, Valuable, Estimatable, Small, Testable (“INVEST”) piece of functionalityĪs products rise to the top of the product backlog i.e.Epics – very top-level requirements or objectives e.g.With that said, there is no reason why you can not use a Product Backlog to store requirements associated with multiple projects and products. You would in this case want to add an extra column or two into your product backlog to allow you to filter by Product or a particular Theme/Epic.Ī product backlog will contain a range of requirements: A Product Backlog is a list of top-level requirements that are usually associated with a single Project or Product.

Agile product backlog template