The Agile Product Backlog for Scrum Masters

A Product Backlog is an organized collection of the existing User Stories (A.K.A. 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 project iteration. As a preliminary activity to an iteration a Sprint Planning Meeting will be held, to discuss and review the highest prioritized items; by the end of the meeting, there should be team consensus on which User Stories have made the cut and these become the Sprint Backlog.

Scrum Master versus the Product Owner Role

Reaching this objective is usually harder than it sounds; the team must work together to substantiate the acceptance criteria for each Story, that the amount of work effort can be estimated and that the measured volume of work can be adequately completed and tested in the amount of time that has been set aside to work within. In addition, all the above should be true without unfairly demanding more work from one player than another or by neglecting to account for work that, if not ready, could prevent other work from being completed. The person who renders all this possible is the Scrum Master who is relied on to facilitate and drive meetings; ensuring there are no obstacles preventing team members from attending or external interruptions vying for their attention. The Scrum Master is also key to providing clarity around roles and responsibilities of the team, making sure that strategic questions are asked and that tasks are assigned and accomplished within the proper guidelines.

Scrum Masters are expected to be process experts and it rests on them not to get involved in the decision making but instead act as a combination of coach and referee; guiding the team in self-organization or course correcting as needed. A typical Sprint Planning Meeting will not begin without the Scrum Master validating with the Product Owner that there is an updated Product Backlog and if they are confident that the top priorities and dependencies are known.  If the answer is not yes, it is of great consequence as these prioritized User Stories set the theme of the Sprint. Although there may be a small window of opportunity for last minute decisions around what will be included in a sprint; for example, there may be an item that fits the timeline better or that is essential functionality to test properly, ultimately the Backlog should already highlight the items with the highest importance at the top of the list.

59 Seconds Agile - The Agile Product Backlog

59 Seconds Agile – The Agile Product Backlog

How to Solicit Feedback about Priority

Prior to the Sprint Planning Meeting, the Product Owner solicits feedback on the prioritization. The Product Owner has the final say on the prioritization as they have an overall view of all requirements. The Product Owner, therefore, needs to have a good understanding of the business value of each requirement, and the associated costs that may be incurred. They must also understand the dependencies or risks that need to be managed, and the complexity of implementation efforts. The Scrum Master can assist with this process and suggest appropriate methods to do so. As a starting point, there are some common prioritization tools, two of the most common methods are the MoSCow and the 100-Point Method.

The first method known as MoSCoW, is an acronym for Must Have, Should Have, Could Have, Won’t Have.  These acronyms refer to whether the prioritized features will be the next product release. Because there is an expectation of delivery built into each category it is a slightly more sophisticated version of High, Medium, Low and other similar labeling categorizations. All items identified as Must Have’s are the highest priority requirements, or in other words, if any one of the Must Have’s is not completed and implemented successfully the project/product will not be ready for the release. Anything that can be considered out of scope or a goal for the future will be listed as Won’t Haves and everything else will be either a Should Have or a Could have.  The goal of this method is to obtain consensus from the team that the right priority has been assigned. If there are differences of opinion, it is a good opportunity to find out why; it may be that one member knows something of significance that has not yet been discussed with the rest of the group.

The second method, known as the 100-point method, gives equal voice to all participants by functioning like a panel of judges. Each member starts with a bucket of points and is asked to vote by dispersing the points across the requirements. The trick is that the total of their individual votes cannot be a greater amount than they were initially given thus encouraging a well thought out distribution of points.

Prev <— Continue Reading —> Next

Our Favourite Agile Books

Read Our Reviews

The History of Agile For Scrum Masters

Prior to the 1990’s software development was very slow, often taking years to complete development and release the product to market. The industry was following a very formal methodology for products and software development…

Read More

What is Agile to the Scrum Master?

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 Scrum Master?

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

The Agile Manifesto For Scrum Masters

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

Read More

The Agile Principles For Scrum Masters

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 Scrum Masters

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 Scrum Masters

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

Read More

The Agile Frameworks For Scrum Masters

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 Scrum Masters

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 Scrum Masters

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

Read More

The Scrum Team Size For Scrum Masters

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 Scrum Masters

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 Scrum Masters

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

Read More

Developing Epics For Scrum Masters

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 Scrum Masters

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 Scrum Masters

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 Scrum Masters

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 Scrum Masters

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 Scrum Masters

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

Read More

Estimating Agile Tasks For Scrum Masters

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 Scrum Masters

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 Scrum Masters

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 Scrum Masters

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 Scrum Masters

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 Scrum Masters

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 Scrum Masters

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 Scrum Masters

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

Read More

Releasing the Product For Scrum Masters

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 Scrum Masters

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

Product Owners

Find out more about the Agile and the Product Owner Role

Read More


Find out more about the Agile and the Developer Role

Read More

More Articles

Read More

Chicken Appreciation Society

Translate »