Product Backlog Prioritisation
The Product Backlog is a living document; new requirements will be added throughout the life of the project and this action along with an evolving understanding of the solution being built and a changing business background will necessitate continual reappraisal and reprioritisation.
Product Backlog Refactoring
- Re-evaluate calculated priority of top 20% of Product Backlog every Sprint and reprioritise accordingly
- Granularise and estimate probable Product Backlog for next Sprint
- Teams should allocate 5% of their Sprint time for this activity, which should be compartmentalised to minimise disruption to the current Sprint.
- Never allow the Product Owner to go into the Sprint Planning meeting with an inadequate Product Backlog.
Backlog Prioritisation Technique
- Allocate 1,000 arbitrary units of value among the Product Backlog
- Sort by Value (relative Priority in Scrum for Team System)
- Allocate your planning time 60% to top 20% in value, 30% to next 20%, and 10% to remainder
- Create Calculated Priority from value/cost
- Re-sort on Calculated Priority
- Manually adjust positions of product backlog items to fine tune
