Scrum Product Backlog Prioritisation
A 59 Seconds Agile Training Video
Continue to Part 5 Below
Prioritizing the Product Backlog
A 59 Seconds Agile Article
This article provides an ‘Introduction to Prioritizing the Product Backlog’ and looks to discuss what the Product Backlog is. It provides an overview of who is involved in the process of Prioritizing the Product Backlog.
Prioritizing the Product Backlog: Product Requirements
The second aspect of features to consider when placing them in the product backlog is what kind of reward they offer, or what their value to the product is. One of the simplest ways to measure value is through finances. So you must consider how much value a feature will add to the product in comparison with how much investment the feature requires.
In your current traditional framework of development, valuable products may be left to be built last because no effort is made to understand how much value the feature adds, and what it is worth to the entire product.
In the prioritized product backlog, the return on investment is considered. If a feature doesn’t have a very high return on investment, the feature may be a nice-to-have feature that could be given a low priority.
Your company might already have a good idea of the return on investment of the product features, if the company uses benefits management. This might mean looking at the net present value, or focusing on the value of money right now rather than in the future, and the internal rate of return, or how long it will take to get the return on your investment.
Armed with these numbers, you’ll be able to figure out which features of the product will add the most value and you will be able to give these features a higher priority. Planning and prioritization are the keys to unlocking maximum value.
Continue Reading —> Next
Prioritizing the Product Backlog
A 59 Seconds Agile Video Animation
Continue Reading —> Next
User Stories Applied
A 59 Seconds Agile Book Review
User Stories Applied by Mike Cohn is one of our favourite books on Agile User Stories. The book starts with an overview into user stories, and details what a user story is and the different aspects of them. He then discusses how to go about writing a user story, and provides details of the INVEST criteria that can be used to determine if the story is meeting all of its objectives. Next Mike gives an in depth discussion of who user stories are written for and where to begin when gathering the details for them. The book then discusses acceptance testing user stories, including how to go about specifying these criteria and the responsibilities of the development team and customers during this process.
Continue Reading —> Next
Prioritizing the Product Backlog
A 59 Seconds Agile Infographic
Continue Reading —> Next
Agile Scrum Master Training Course
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum:
Continue Reading —> Next
