Product Backlog Prioritisation For Product Owners

Prioritizing the work of any project is an important and difficult task. Every project has limitations that have to be balanced, generally, these are time, quality, and cost, where you can only control at most two of these variables. With unlimited time and expectations for perfect quality, you can ensure the project cost will skyrocket. If you have a very specific budget and timeline, then you are going to have to sacrifice quality or features. When working in the agile method, it’s up to the product owner to make the tough choices and prioritize the work to make sure that the team is working towards the product vision each sprint. The product owner and Scrum Master then work together to align the team and prepare for the next sprint.

Prioritization is important because it means putting a thoughtful approach to scheduling work. Using the product vision as the guide, the product owner looks through the work to be done and creates a plan depending on which work should be executed next. Using this plan the product owner can then align with the Scrum Master and the team to fully develop the next sprint. Along the way, the product owner will also meet with stakeholders to make sure they are informed about the team’s progress and work to realign in cases where there are new issues or new initiatives that are influencing the product. This alignment with stakeholders will mean the product owner can forge ahead and the team will feel confident they are creating a product that will be successful.

Ways to Prioritize Work

So now you have all the work laid out, it should be easy to prioritize what needs to happen next, right? This can actually be quite challenging. The first way to consider prioritizing work is to start by looking at your “epics”. Your epics are your largest user stories that usually encapsulates a set of user stories.

59 Seconds Agile - Prioritising the Product Backlog

59 Seconds Agile – Prioritising the Product Backlog

For example an epic could be “As a user I want to be able to create an account so that I can track my work in the system”, this then gets broken down into user stories that could include “As a user I want the ability to login using my email”, “As a user I want to be able to log in using a Google account authentication”, “As a user I want the ability to edit my profile picture”, and so one. All of these stories are still related to the idea of a user account though. In any project, you may have many of these epics that define a large chunk of work for one of your features. The best place to start is prioritizing these key feature sets and then work through the user stories in each of those in discrete features. This can also be a great way for the product owner to give focus to the sprint so that by the end the team has a fully functioning feature set to demonstrate.

MoSCoW Method

Another method for prioritizing work is one where stakeholders and the product owner must look at the work and determine if each user story is a Must Have, Should Have, Could Have, or Won’t Have, this is usually shortened to the MoSCoW method. This forces stakeholders to consider, given the constraints of the project, what features are critical to product success and what can be postponed for the time being. The wonderful thing about agile development is that nothing is set in stone and maybe there is a Could Have a feature that gets changed to a Must Have because the market changed or it was discovered it would be easy to implement and have a high impact for the customer. This type of prioritizing works best when the number of stakeholders is smaller and consultation with them is easy and consistent.

Kano Model

A more customer-centric way of looking at feature prioritization is by using the Kano Model. This model really puts the customer’s needs at the forefront of the discussion. This model considers the customer’s satisfaction with a product versus its functionality and this is normally done through user surveys or questionnaires.

Prev <— Continue Reading —> Next

Our Favourite Agile Books

Read Our Reviews

Learn More about the Scrum Product Owner

The History of Agile For Product Owners

Agile project delivery principles evolved because industry leaders recognized that the linear nature of waterfall delivery created long windows of time between gathering requirements and delivering working software…

Read More

What is Agile to the Product Owners?

While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products…

Read More

Why Use Agile as a Product Owners?

When determining if a move to Agile is right, a PESTLE can be used to simplify what factors should be considered. While Agile is sometimes thought of as a software development project management method, it isn’t just for these types of technology-centric companies…

Read More

59 Seconds Agile - Scrum Product Owner Training Course

59 Seconds Agile – Scrum Product Owner Training Course

The Agile Manifesto For Product Owners

Agile is a quick, simple, lightweight and effective way of managing projects. In traditional project management models…

Read More

The Agile Principles For Product Owners

When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to…

Read More

The Agile Fundamentals For Product Owners

Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience…

Read More

The Declaration of Interdependence For Product Owners

The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and…

Read More

The Agile Frameworks For Product Owners

There are many different Agile frameworks – all of them share the same philosophy and are built around the Agile Manifesto and Principles. But they vastly differ in their approaches, values, and structure. …

Read More

The Scrum Framework For Product Owners

The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum…

Read More

The Scrum Roles For Product Owners

Scrum is a useful tool for the creation, maintenance, plan, and execution of diverse products and services. The tool consists of…

Read More

59 Seconds Agile – Scrum Product Owner Training Course

59 Seconds Agile – Scrum Product Owner Training Course

The Scrum Team Size For Product Owners

The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum …

Read More

The Agile Project Vision For Product Owners

At the heart of any great product is a great vision. It describes the primary goal or goals of a product and creates a focus that…

Read More

Forming the Scrum Team For Product Owners

Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is…

Read More

Developing Epics For Product Owners

The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single…

Read More

The Agile Product Backlog For Product Owners

A Product Backlog is an organized collection of the existing User Stories (aka Wants and Needs) for an explicit business endeavor. Think of a shopping catalog of User Stories, ordered by urgency, that can be perused and selected from to determine what will be worked on during the current…

Read More

Release Planning For Product Owners

Although flexibility and adaptability are part and parcel of an agile methodology, this does not mean that no planning is required when…

Read More

Creating User Stories For Product Owners

User Stories are an integral part of the agile development process. They are an important agile technique that is used to frame…

Read More

Estimating User Stories For Product Owners

One of the principles of self-managing teams in Agile Scrum is working collaboratively with the Product Owner to effectively deliver…

Read More

Creating Tasks For Product Owners

According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a…

Read More

Estimating Agile Tasks For Product Owners

In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to…

Read More

Creating the Sprint Backlog For Product Owners

The Sprint Backlog is defined as a group of user stories that are grouped together during the Sprint Planning Meeting.  This…

Read More

Creating the Deliverables For Product Owners

Agile Scrum provides the framework for delivery of the vision of an organization. Execution of the vision includes processes, ceremonies and project deliverables that are also known as artifacts…

Read More

The Daily Stand-Up For Product Owners

The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the…

Read More

Product Backlog Prioritisation For Product Owners

The product backlog is a key element of Agile software development. It facilitates a development environment that creates valuable features and products for stakeholders…

Read More

The Sprint Review Meeting For Product Owners

The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able …

Read More

Demonstrating and Validating the Sprint For Product Owners

As organizations migrate to Agile principles, there may be questions about how the organization can prove that there is value…

Read More

The Sprint Retrospective For Product Owners

A very simple step by step guide to help you choose the appropriate product development methodology from…

Read More

Releasing the Product For Product Owners

One of the most important milestones any project will ever have is finally releasing their product and putting it out there. It’s the…

Read More

Regression Testing For Product Owners

In companies using agile development, it is common to introduce changes in a product incrementally. Along with the new changes, unexpected issues may arise, testing whether the existing functionality is broken or not becomes very important…

Read More

Scrum Master

Find out more about the Agile and the Developer Role

Read More

Product Owners

Find out more about the Agile and the Product Owner Role

Read More

Developers

Find out more about the Agile and the Developer Role

Read More

More Articles

Read More

  Chicken Appreciation Society

Share
Translate »