Are there technical differences between a Product and a Release Backlog (scrum template)?
I understand the difference between a product and release backlog, but am curious -- why there are two difference Plan Types for them? In the following example the Product Backlog uses EBand_Backlog and the Release Backlog
points to EBand_R1 or EBand_R2. This just seems to be a difference in scope selection.
What does using type of Product Backlog buy me or using Release Backlog?
EBand_Backlog
EBand_R1
EB_R1_Sprint1
EB_R1_Sprint2
EBand_R2
Accepted answer
Technical I know following differences:
- predefined plan views
- in the Advanced Release Burndown report, you need to select an Iteration where a plan of the type "Release Backlog" exists. And it is not allowed to have a second Iteration selected for this report, where another plan of type "Release Backlog" exists.
This is a problem in my setup, where I have a seperate Iteration within the Release, parallel to the sprints to hold the "Release Backlog". e.g.
- predefined plan views
- in the Advanced Release Burndown report, you need to select an Iteration where a plan of the type "Release Backlog" exists. And it is not allowed to have a second Iteration selected for this report, where another plan of type "Release Backlog" exists.
This is a problem in my setup, where I have a seperate Iteration within the Release, parallel to the sprints to hold the "Release Backlog". e.g.
Product BacklogIf you want to use the Advanced Release Burndown for this Situation, the Release backlog plans cannot be of type "Release Backlog".
Release 1.0
Rel1.0_Backlog
Rel1.0_Sprint01
Rel1.0_Sprint02
Release 2.0
Rel2.0_Backlog
Rel2.0_Sprint01
Rel2.0_Sprint02