A product backlog lists and prioritizes the task-level details required to execute on the strategic plan set forth in the roadmap. The backlog should communicate what’s next on the development team’s to-do list as they execute on the roadmap’s big-picture vision. Typical items in a product backlog include user stories, bug fixes, and other tasks.
The backlog is a translation of how your team will deliver the vision outlined on an agile product roadmap. In many ways, it is a giant to-do list for your development team.
What does the product backlog contain?
What belongs in your product backlog? This is a difficult question because the contents of the backlog vary greatly from team to team. In general, the backlog functions as a list of all projects and initiatives related to a product. If an initiative is not included on the backlog, it will most likely not get done. This means it is home to a variety of different items including (but not limited to):
- New features
- Infrastructure updates
- Changes to existing functionalities
- Bug fixes
- Technical debt and refactoring
In most cases, backlog items are broken down into user stories. However, not all backlogs talk in user stories. Every team has their own way of structuring the contents in their backlog.
Who owns the product backlog?
While the entire cross-functional agile team works together on the backlog, the product owner owns it. In most cases, the product owner (or product manager) holds responsibility for organizing and maintaining the product backlog. However, it’s generally advised to allow various members of the cross-functional team to contribute items to the product backlog.
It’s worth noting here that depending on a team’s approach to agile, there may be multiple backlogs with different purposes and owners. In the Scrum methodology, for example, a sprint backlog owned by the delivery team.
How is the product backlog managed?
Managing the product backlog comes with several different responsibilities and tactics. As the product roadmap is updated often, it needs to be closely connected to the product backlog. So, the backlog needs to be prioritized (and re-prioritized) often to reflect changes and new findings.
Additionally, care should be taken to keep the backlog organized and easy-to-navigate. Agile best practices suggest striving for a “DEEP product backlog,” where the items slated for near term have the most detail, and the level of detail decreases with priority.
In addition, most agile teams participate in backlog grooming sessions to refine and order backlog items. During these sessions, the team works together to prepare a few sprints worth of user stories ahead of time. Backlog grooming sessions ensure that the user stories at the top of the backlog contain sufficient detail for the delivery team to understand them.
What is the difference between a product backlog and product roadmap?
The product backlog is not to be confused with a product roadmap. Both of these living documents serve distinct purposes for agile teams. While the backlog lists tactical details of development, the roadmap focuses on the broader product strategy. For a more in-depth comparison, read our overview of the product roadmap vs. product backlog.