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 |
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. Product BacklogIf you want to use the Advanced Release Burndown for this Situation, the Release backlog plans cannot be of type "Release Backlog". Virginia Brown selected this answer as the correct answer
|
One other answer
Product backlog -> Prioritized list of work of the entire product. E.g., feature 1, f2, f3, f4 Release backlog -> Subset of the product backlog that you are targetting for that release. E.g., f1,f2 Sprint backlog -> subset of Release backlog through a set of detailed tasks. E.g., f1 (task1, t2, t3)
|