Product Backlog Prioritisation for Developers – Part 2
Moscow prioritization
In MoSCoW method, the name stands for ‘M’ as MUST, ‘S’ as SHOULD, ‘C’ as COULD and ‘W’ as WON’T. These categories are ordered from highest to lowest priority. All the features in the backlog are grouped under these categories. ‘MUST’ features are those that are critical to the product development. If not implemented, the release will fail. ‘SHOULD’ features are good to have them in the product but not as important as the first group. ‘COULD’ features could be included in the product but are not necessary. They are mostly small enhancement to the product not directly required by the customer. ‘WON’T’ features are low priority items that need to be revised in the next planning session and will not be included in the current release. As this method is based on the interpretation of the importance, it is a qualitative approach and more suited for small projects rather than large projects involving many customers.
Paired comparison prioritisation
In Paired-comparison method, a list of user stories is provided. Each user story is compared pairwise with the other user stories in the list. At each step, it is decided which one is more important in the pair. The more important item is scheduled ahead of the lower importance item. This pairwise comparison is done for all the user stories in the backlog.
100 point method prioritisation
In 100-points method, each stakeholder is given a budget of 100 points to distribute among the backlog items. Any stakeholder gives more points to an item which they think is more important. The stakeholders can give different points to a specific item. The final value of the item is calculated by summing up the points given by different stakeholders. Based on this metric, the items are ordered and the highest value ones are implemented first. It is called cumulative voting as well as the votes from different stakeholders are accumulated to find the final value of the item.
<– Continue Reading –>
Our Book Recommendations
We found these books great for finding out more information on Agile Scrum:
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
Introductory Offer: Free Course
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
What is this course?
This ‘Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Developer roles and responsibilities
You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’
This course is aimed at those with or without prior knowledge and experience of the Agile values and principles
During this course you will learn the tools needed to succeed as an Agile Scrum Developer
What will you learn?
You will gain an in-depth understanding of the Agile Scrum Developer roles and responsibilities, and you will be able to
- Fully understand the role of the Agile Scrum Developer
- Understand the roles involved in an Agile project
- Create an effective Product Backlog
- Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
- Identify the roles involves in the Scrum Team
What topics are covered within this course
You will cover the following topics during this course:
- An Introduction to Agile Project Management (Developer)
- The 12 Agile Principles (Developer)
- Introduction to Scrum (Developer)
- Scrum Project Roles (Developer)
- The Agile Project Life-cycle (Developer)
- Acceptance Criteria and the Prioritised Product Backlog (Developer)
- Initiating an Agile Project (Developer)
- Forming the Scrum Team (Developer)
- Epics and Personas (Developer)
- User Stories and Tasks (Developer)
- Implementation of Scrum (Developer)
- The Daily Scrum (Developer)
- The Product Backlog (Developer)
- Scrum Charts (Developer)
- Review and Retrospective (Developer)
- Validating a Sprint (Developer)
- Retrospective Sprint (Developer)
- Releasing the Product (Developer)
- The Communication Plan (Developer)
- Formal Business Sign-off (Developer)