PRIORITISING THE PRODUCT BACKLOG FOR TESTERS
The Product Backlog is a list that tells the team what need to be done within the project. It breaks down the Product Vision into manageable increments called Product Backlog Items (PBIs), and each PBI would briefly describe what needs to be done. User story formats are commonly used by Agile teams to describe requirements from the point of view of the user.
Even though everything in the Product Backlog has a purpose, all of them are not necessarily or immediately essential. In order for the project to have a better chance at getting a return on investment (ROI), they need to give their users positive experiences at the earliest opportunity possible, especially if the product is new and just breaking into the market. This is why it’s important for the team to prioritise the Product Backlog: to deliver the highest-value features to the users first.
Because part of Agile development involves continuous delivery, ensuring quality in the product is all the more important and puts testers in the forefront. And for testers to be great, they need to be able to help prioritise work effectively as well. Which are the features should be tested first? Which are the urgent bugs that should be addressed in the next deployment? This article will describe some factors in prioritising the Product Backlog as well as some techniques that can be used in prioritisation.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: