Scrum Product Backlog Template (with Priority Overview)
Scrum Product Backlog
A Product Backlog is a list of top-level requirements that are usually associated with a single Project or Product.
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 or Epic.
A product backlog will contain a range of requirements:
- Themes- very top-level requirements or objectives e.g. A new website
- Epics – very large user stories e.g. A new website section
- User Stories – an Independent, Negotiable, Valuable, Estimatable, Small, Testable (“INVEST”) piece of functionality
As products rise to the top of the product backlog i.e. become higher priority, the Product Manager will work with the team to break Themes and Epics into User Stories.
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.
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.
The primary objective of the Product Manager is to deliver value. 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. In a product development environment i.e. ongoing development, the value needs to be packed into each sprint.
This Product Backlog template provides the following tools:
- Assign stories to sprints (release plan)
- Calculate the number of releases required to deliver your backlog based on your velocity
- Calculates how many sprints you can afford to deliver based on your project budget
- Plots your user stories on a chart based on Effort vs. Value
Subscribe to the to be notified when I upload new Articles, Videos, Templates and Tips!
I actually was able in my SDLC processes to marry the Waterfall with Scrum and Agile and it is working ...
I experienced that using story points based on complexity has brought the team disagreement in assigning points. We still ...
Hi, in addition to your article, you can view this list as well on my website in a more clear ...
Good article, and I STRONGLY ENCOURAGE everyone to read Andy Bruce's earlier response. Andy has nailed the often missed point ...
You have completely demonstrated the whole scheme of software development within the above diagram on such a fine way. Truly ...
Where can I get this template please? Contrary to the Sprint Backlog Template, there is no Download button…
Thank you!
Well spotted! Fixed.
Thank you very much!
Those templates are pretty well done!
Great template, thats perfect!
Jef
[...] Product Backlog at Agile101.net (link) [...]
Thanks!
Gr8 template.
Hi,
Great template. Quick question
I am not sure if I am reading the graph right, the data set for the graph selects both story points and value points as x axis on one row and for another row, story points and value points are put on y axis..in short my graph doesn’t seem to show the stories in right quadrant. Am I doing something wrong?