Back

Product Backlog Prioritisation for Scrum Masters – Part 2

Priority Factors

Dependencies refer to product backlog items that rely on other items in order to work properly. A user cannot assign medication to a patient without the ability to add and update patient information. In a point of sale system, users cannot view transaction history for the day if this history isn’t saved, to begin with. Therefore, the Scrum Team must plan these dependencies in advance.

Prioritization Tools

For particularly large projects, there can be numerous items in the product backlog. Deciding which items are more or less important than others is a difficult task for such projects. Fortunately, there are tools that the Scrum Team can use to aid the process of prioritization.

One of the most popular prioritization tools is the MoSCoW technique. This mnemonic gives a reminder of four categories that product backlog items can fall into. Every backlog item is either a “must have,” “should have,” “could have,” or “won’t have this time.”

Urgent items like security fixes or legal requests are “must have” features. If these items are not included in the next sprint, there could be serious consequences. “Should have” items are features or requests that stakeholders expect the software product to include. In the absence of “must have” items, “should have” are the features that stakeholders could most use. “Could have” items would be nice to have, but are not necessarily required. “Won’t have this time” are the bottom level of product backlog items. These items are considered less valuable than anything else in the product backlog. Other backlog items are more important and would offer greater benefit and value to the stakeholders.

Prioritization Tools

Another method of prioritizing the product backlog is called paired comparison. As the name implies, a paired comparison is the process of examining every item in the product backlog and comparing them to every other item individually. For each backlog item x, compared to each other backlog item y, is x or y more important? This gives the Product Owner a definite priority rank for each item in the product backlog. The problem with the paired comparison method is that it can be very time consuming and labor intensive.

A prioritization method that works better for involving stakeholders is the 100 point method. In this method, stakeholders are each given 100 points to assign to specific user stores based on which they think is most important. By totaling or averaging the points on each item, the Product Owner has a definite list of what the stakeholders find most valuable. The 100 point method can also be combined with other methods. However, with this method, stakeholders do get a more direct voice in what they want in the next sprint. The Scrum Master assists the Product Owner with these prioritization sessions and ensures that the scrum processes are being followed.

The Product Owner and Scrum Master clearly have an important job in prioritizing the product backlog. Despite the size of this responsibility, the Product Owner does have tools and methods to apply. By using these tools appropriately, the Product Owner can produce a product backlog that contains items ranked by their priority and allows the rest of the Scrum team to develop the product and features.

The ‘Agile Scrum Master Training Course With 59 Seconds Training‘ is now available for free. This free Scrum Master Certified Online Training Course provides an in-depth understanding of the Agile Scrum Master roles and responsibilities, where you find out what a Scrum Master does and how to do it. During this free course you will learn all of the tools needed to succeed as an Agile Scrum Master.

Thank you for choosing us to learn about the Agile Scrum Framework.

<– Continue Reading –>

Our Book Recommendations

We found these books great for finding out more information on Agile Scrum:

Our Book Recommendations

We found these books great for finding out more information on Agile Scrum:

Master of Agile – Agile Scrum Master With 59 Seconds Agile (Video Training Course)

Introductory Offer: Free Course

Master of Agile – Agile Scrum Master With 59 Seconds Agile (Video Training Course)

What is this course?

This ‘Master of Agile – Agile Scrum Master With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Master 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 Master

What will you learn?

You will gain an in-depth understanding of the Agile Scrum Master roles and responsibilities, and you will be able to

  • Fully understand the role of the Agile Scrum Master
  • 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:

  1. An Introduction to Agile Project Management (Scrum Master)
  2. Using the Agile Manifesto to Deliver Change (Scrum Master)
  3. The 12 Agile Principles (Scrum Master)
  4. The Agile Fundamentals (Scrum Master)
  5. Introduction to Scrum (Scrum Master)
  6. Scrum Projects (Scrum Master)
  7. Scrum Project Roles (Scrum Master)
  8. Scrum in Projects, Programs & Portfolios (Scrum Master)
  9. How to Manage an Agile Project (Scrum Master)
  10. Leadership Styles (Scrum Master)
  11. The Agile Project Life-cycle (Scrum Master)
Translate »