8 Different Ways to Organize Your Backlog
Often we don’t question our product backlogs, they’re a list of stuff we hope, might and would like to do, but do they always have to be represented as a list?
The 8 Different Ways to Organize Your Backlog
1. User Story Map
Backlog as a User Story MapUser Story Maps are a great way to quickly build out your backlog for the first time, it’s also a powerful tool for release planning.
For more mature products I’ve often split my user story map by customer archetype, JTBD, objectives and even problem spaces, depending on what makes the most sense.
2. Idea Funnel Backlog
Idea Funnel Backlog feeding into a Kanban board.
Literally a funnel! A great way to visualise your backlog and to actually physically restrict the number of product backlog items that are at the “top” (well “right”) of the backlog.
This form of backlog is great to help with prioritisation and focus whilst also keeping things fluid without too much overhead or formal structure.
3. Opportunity Backlog
Splitting your backlog into two — Opportunity backlog for discovery and Development for delivery.
All the ideas, problem spaces, and opportunities are thrown in here, if validated as a good idea they graduate to the delivery backlog.
And eventually the learning will lead to more opportunities and thus making its way back into the Opportunity backlog and that’s the circle of Product Development!
4. Classes of Work Backlog
Divide your backlog into multiple smaller backlogs based on different classes of work.
What often happens is that in order to keep track of everything product managers go labeling-crazy. When you think about it what they are actually doing is dividing their backlog into multiple smaller backlogs based on different classes of work.
One simple thing to do is to literally separate them. Most tools will allow you to achieve this using different views and filters whilst keeping the integrity of a single view for things like your sprints.
5. Tree Backlog
Tree backlogs are great for complex products with many different feature sets.
Technology Trees are great for complex products with many different types of features. Representing your backlog in this manner is a great way to visually show how different features inter-relate and how certain functionality can start out simple and incrementally be enhanced.
6. Impact Map Backlog
Impact maps are great for ideating many alternative paths towards a particular outcome.
Impact mapping works in a similar way to the Tree Backlog in the sense that it branches out. However, unlike the Tree each stage in the branch is not another backlog item rather it represents a stage in the impact map moving from the WHY > WHO > WHAT > HOW.
Representing your backlog this way is great for keeping everything outcome orientated. However impact mapping backlogs aren’t great at representing other classes of work such as technical debt, bug fixes, etc.
7. Circle Backlog
Circle backlogs are perfect for creating ‘slices’ to categorise your work whilst still maintaining a holistic view in one place.
There’s just something about breaking the mould — or perhaps it has to do with the lack of corners — that brings the creativity out in people.
You can even get creative and have different slice sizes, a great way to physically restrict WIP!And much like the Funnel Backlog they also can act as a roadmap + backlog in one.
8. Conversion Funnel Backlog
Conversion Funnel backlogs are great for early and growth stage products with clear conversions.
It brings two important pieces of information together, the quantitative data around drop-offs/potential pain-points in your funnel but also the backlog items/opportunity areas.
If there is a clear drop off at a particular point then everything within that section of the backlog is now your top priority. You get laser-focus, and you keep focusing on that section of the backlog until the numbers improve or if you get another compelling reason to focus on something else.
This template was created by Ant Murphy.
Get started with this template right now.
Kanban Pizza Game
Works best for:
Agile, Kanban
The Kanban Pizza Game is an interactive way for teams to learn and apply Kanban principles. By simulating a pizza delivery process, teams experience how to visualize work, limit work in progress, and optimize flow. Through rounds of iteration and reflection, participants gain insights into continuous improvement and lean thinking, fostering collaboration and driving efficiency. Get ready to slice through inefficiencies and deliver value faster with the Kanban Pizza Game!
Venn Diagram for Research
Works best for:
Venn Diagram
The Venn Diagram for Research template is a powerful tool for analyzing relationships and intersections in research data. Use it to compare different variables, identify overlaps, and draw insights from complex datasets. This template is ideal for researchers, analysts, and academics looking to visualize their findings and communicate results effectively. It's perfect for scientific studies, market research, and any field that requires detailed data comparison.
Product Monetization Canvas
Works best for:
Product Management, Planning
The Product Monetization Canvas template assists product managers in developing effective monetization strategies. By mapping out revenue streams, pricing models, and value propositions, this template helps align product features with revenue generation opportunities. With sections for analyzing market demand and competitive pricing, it enables teams to optimize monetization strategies and maximize profitability. This template serves as a strategic guide for identifying and capitalizing on revenue opportunities throughout the product lifecycle.
ERD Healthcare Management System Template
Works best for:
ERD
The ERD Healthcare Management System Template streamlines the process of creating and managing entity-relationship diagrams for healthcare management systems. This template helps users visualize the complex relationships between different entities such as patients, healthcare providers, medical records, and billing information. It offers a flexible and customizable framework that can be adapted to fit the specific needs of any healthcare management system, ensuring clarity and efficiency in system design and database structure.
Incident Management Process Flowchart Template
The Incident Management Process Flowchart Template in Miro is designed to streamline and clarify the process of managing incidents within an organization. This template serves as a visual guide that outlines the steps involved in incident management, from the initial declaration to the final review. It is a living document, continuously evolving based on feedback and lessons learned from past incidents, ensuring that the process remains up-to-date with best practices. By defining incidents as disruptions requiring a coordinated response to restore service levels, the template emphasizes the importance of a structured, organized, and timely approach. It covers various phases such as Incident Declaration, Assessment, Response, Communication, and Review, providing a clear framework for teams to follow.
Agile Board Template
Works best for:
Agile Methodology, Meetings, Agile Workflows
Part of the popular Agile framework, an Agile Board is a visual display that allows you to sync on tasks throughout a production cycle. The Agile Board is typically used in the context of Agile development methods like Kanban and Scrum, but anyone can adopt the tool. Used by software developers and project managers, the Agile Board helps manage workload in a flexible, transparent and iterative way. The Agile template provides an easy way to get started with a premade layout of sticky notes customizable for your tasks and team.