Product backlogues and how they optimise your Agile experience

Project management centred around static to do lists isn’t an efficient way to run a team. To do lists can easily become disordered and disorganised. This leads to poor prioritisation of work, which leads to poorly co-ordinated and unfocused teams. All of this saps the efficiency from your team and makes them less adaptable.

But there’s a way you can keep your team on task, up to speed and focused — a product backlogue.

This post will explain:

• What a product backlogue is
• The benefits of using an Agile backlogue
• How to create a backlogue
• Tips and best practices for managing a backlogue

What is a product backlogue?

A product backlogue is a prioritised list of project tasks that might be needed to deliver a product. Backlogues are used to organise teams around more than just software development today, so some have adopted terms like “project backlogue” or “Agile backlogue.”

A backlogue provides better alignment and guidance than a traditional to-do list because items are continually prioritised — reorganised, added or removed as needed. When team members are ready for more work, they can pull tasks from the product backlogue and always be working on the right task. Instead of working your way down your to-do list one item at a time, a backlogue allows you to work on what’s currently most important.

There is a difference between a product backlogue and a sprint backlogue. The product backlogue is the single source of all possible tasks. A sprint backlogue, as in Scrum, includes items taken from the product backlogue that will be addressed in the next Sprint.

Four types of product backlogue items

There are four types of items most commonly included in a product backlogue.

• New features add functionalities that users need. These improve the product to keep your existing customers happy and attract new ones. In Agile, new features are often expressed in “user stories.”
• Technical work (sometimes called ”technical debt”) keeps the product up to date and in good condition. These are maintenance tasks such as optimising poorly written code in the software or fixing an issue on the website.
• Bugs are problems found by the end-user. These defects got through quality control unnoticed but need attention. Unlike software teams, marketing teams don’t need to deal with technical bugs, but they may need to deal with problems like a lacklustre headline, broken images or a weak CTA.
• Learning (or “research”) makes sure the team knows how to implement a new feature. By setting aside time for team members to increase their technical knowledge, they can be confident dealing with new features or trying new ideas.

The main benefits of a backlogue

Maintaining a product backlogue is key for Agile project management. Here are some of the benefits of building and maintaining a product backlogue.

• Keep your to-do list up to date. Team members always know what they need to do next. Team leaders know which jobs are most important and can give them to the most suitable team member.
• Encourage discussion about priorities. Because the backlogue is constantly being monitored and updated, team members can contribute to the discussion about which items are critical and deserve to be higher up the list. The team can vote on what’s more important and decide how much work will likely be necessary.
• Increase efficiency. When everyone is working from the same list of prioritised work, the team can spend less time debating and second-guessing and more time building a better product.
• Improve flexibility. Teams can adapt and react to new needs and circumstances because they can reassess the items in the backlogue. As the team’s priorities change, the list can change.

How to create a product backlogue

The product owner is in charge of the backlogue. It’s their responsibility to create and maintain the list of backlogue items.

Prerequisites to creating a product backlogue — the two Rs

Before creating the backlogue, the team should know the general requirements of the project and already have a roadmap for developing it — these are the two Rs of Agile backlogues. The requirements are the function, services and features of the product. The roadmap is the high-level plan of action for the product.

With the two Rs clearly established, here’s how to create a project backlogue:

1. Collect items. Start by collecting the tasks, to dos and upcoming work you and your team have already identified. These could already be part of the team’s or individual members’ to do lists. Gather the tasks from all these different places into one source.
2. Clarify items. Make sure you and the team thoroughly understand each item. Find out why it was requested, what the specific requirements are and how it will add value. Remember to use the product roadmap to guide what is added to and what stays in the backlogue.
3. Prioritise items. Arrange the items in order of importance. There are several ways to do this. You could complete the most complex tasks first or you could prioritise based on urgency. Some teams prioritise based on the level of affect vs. effort. Others prioritise based on business value — the work’s effect on revenue or savings. The method you choose will depend on the type of project you’re working on.
4. Manage the backlogue. To make sure the priorities are up to date it’s important to actively manage the backlogue. This is called “backlogue refinement.” You’ll continually add items to the backlogue as new ideas or requests come in. You’ll also need to remove and modify items as needed.

All these steps happen during the backlogue creation and as an ongoing process during the project’s entire lifecycle.

Tips and best practices for managing a product backlogue

With new requests and items coming in all the time, it’s easy for the backlogue to get out of control, so it’s essential for the product owner to keep on top of it. Here are some best practices for ongoing backlogue refinement.

• Split up a large list of backlogue items. When the backlogue becomes too big, it gets difficult to find anything and progress is less visible. It’s important to keep the backlogue manageable. One way you can do this is by grouping your items into long-term and short-term tasks.
• Delete items. It’s a good idea to get rid of items in the backlogue that you’ll never do. If an item isn’t valuable enough to implement and it’s been on the backlogue for a while, it’s time to delete it. With new items being added all the time, the product owner needs to be proactive in keeping the backlogue focused.
• Share the backlogue. When backlogues are only internal documents, they become stagnant — which is the opposite of Agile. Everyone involved should have access to the backlogue, so share it with all stakeholders.
• Visualise the backlogue. You can also visualise the backlogue for your team. Teams will have a digital visualisation of the backlogue, but it can help to have an analogue one too. This could be as simple as post-it notes on the wall, but putting it on display close to where the team works keeps everyone engaged.
• Review and reprioritise. Agile is all about flexibility and responsiveness, so your backlogue should reflect shifting priorities. The items with the highest priority should always be at the top of the backlogue. However you do it, make sure to regularly review and reprioritise backlogue items.

Getting started with product backlogues

The product backlogue is an essential part of Agile project management — having a prioritised and refined list of tasks increases your team’s flexibility and efficiency. Team members know exactly what they need to do and when they need to do it.

To set up your product backlogue, start collecting and listing tasks that still need to get done. Consult your whole team to find out what they’re working on and what’s coming up next. And don’t worry about making mistakes — the beauty of the backlogue is that it can always be changed to adapt to current needs.

When you’re ready to get really Agile, Adobe Workfront can help. Resource management, configurable dashboards and native integrations help you plan, iterate and continually improve your work.

To see how Workfront makes Agile project management easy, watch this overview video or request a demo.