PRIORITIZING THE PRODUCT BACKLOG FOR TESTERS
There are different ways and techniques that can be used for prioritising the Product Backlog:
1. MoSCoW Prioritisation Scheme – This method simply categorises PBIs into the following buckets: Must have, Should have, Could Have, Won’t have. These categories are decreasing in order, starting with high-value user stories to those that are considered to have very low or no value at all. Categorising PBIs this way will make it easy for the Agile team to prioritise the set of user stories that should be delivered first – which fall under “Must have.”
2. Paired Comparison – This technique entails the Agile team to list all the PBIs, take one item, compare to each of the remaining PBIs, and do the same for all PBIs. Each time two PBIs are being compared, the team decides which of the two is more important. This way, the Product Backlog is more prioritised.
3. 100-Point Method – Developed by Dean Leffingwell and Don Widrig, this method prescribes the team to distribute 100 points to each customer during a voting session. Each participant would then allocate the points to PBIs that they think should be developed, putting more points or weight on those perceived to be more important. Once voting is done, points are totalled, and then PBIs are then arranged from those having the most points to the least.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: