Joshua RenderProduct Owner| CognizantHarrisville, Ny, United States
Your general answer is no there is only one product backlog.
Your more complicated answer is, do you want there to be more than one? Reality does not always adhere to an Agile method like Scrum
In more scaled up Agile versions companies may choose to have individual teams specialize in different areas. This could create a product backlog for back-end server development and a product backlog for front-end UX development as examples.
Generally, for a single project, you really only want one core product backlog for all teams involved in the project to draw from. This prevents having to maintain multiple backlogs and accidentally having two teams work on the same stuff.
The product backlog is different than the Sprint (or iteration) backlog. The product backlog should contain "all" currently known items to be worked on. The iteration backlog would be just those items that need to be worked on during the given iteration. Saving Changes...
Yeah there is, there;s the product backlog you have for this company, and the product backlog you have for that company. They differ in the way they are populated with stories/items, the way they are prioritized, if they are also risk prioritized, their level of granularity, their size, who has access to edit (PO and Dev Team?), and the list goes on. Saving Changes...
Damian PereraMonitoring & Evaluation Specialist| ChrysalisMellawagedara, Western Province, Sri Lanka
Are these not considered as different types of product backlogs?
01. Release backlog
02. Prioritized product backlog
03. Risk-Adjusted backlog
...
1 reply by Sonali Malu
Jun 24, 2018 3:10 AM
Sonali Malu
...
No.
Saving Changes...
Joshua RenderProduct Owner| CognizantHarrisville, Ny, United States
Release backlog wouldn't be the product backlog.
The prioritized product backlog is what you would do to the product backlog - prioritize it (by value usually). Once you prioritize it, the higher up elements would be first in line to be chosen for the next iteration.
You can also adjust the backlog by risk. But it is still the product backlog, it is just adjusted to try and complete the riskiest items first.(ie prioritized or adjusted for risk reduction). Saving Changes...
Nope, they are different. And the risk-adjusted or prioritized backlog is the same backlog. There is only ONE product backlog in an Agile project :-) Saving Changes...
Actually, there is only 1 product backlog that Agile theory says.
However, few organizations end up in classifying the product backlog like feature backlog, quick enhancements backlog, technical debt backlog, etc. This classification is usually depending upon the release plan every organization has for the project. Saving Changes...
Just to clarify, the release backlog is a different name (not a different backlog) to the product backlog. It is in fact a subset of the product backlog, like the Sprint Backlog. The best way to not get confused is just to say there is one product backlog, and we use various other names to represent different versions/subsets of the same backlog. Saving Changes...
Justus NScrum Master| BCBSTXArlington, Tx, United States
In my experience, there's only one product backlog. Saving Changes...
RAJESH K LProject Manager, PMP| Bharat Electronics, Bengaluru, IndiaBengaluru, Karnataka, India
"There are painters who transform the sun into a yellow spot, but there are others who, with the help of their art and their intelligence, transform a yellow spot into the sun."
