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.
Process Map Template
Works best for:
Agile Methodology, Product Management, Mapping
Process mapping allows you to assess, document, and strategize around any plan or approach your team has put in place. It’s a useful tool for eliminating or preventing blockers. Organized by stages, a process map enables your team to divide up a process or system and record deliverables and action items at each stage of the process. By breaking down the objectives, activities and deliverables at any stage of a project, you can gain insight into whether you are on track or effectively working through a problem.
Wardley Mapping Canvas Template
Works best for:
Leadership, Strategic Planning, Mapping
A Wardley Map represents the landscape in which a business operates. It's made up of a value chain (the activities required to fulfill user needs) graphed against the evolution of individual activities over time. You place components with value on the y-axis and commodity on the x-axis. Use a Wardley Map to understand shared assumptions about your environment and discover what strategic options are available. Easily communicate your understanding of the landscape to your team, new hires, and stakeholders.
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.
Communications Plan Template
Works best for:
Marketing, Project Management, Project Planning
You saw the opportunity. You developed the product. Now comes an important step: Find your audience and speak to them in a way that’s clear, memorable, and inspiring. You need a communications plan—a strategy for controlling your narrative at every stage of your business—and this template will help you create a good one. No need to build a new strategy every time you have something to communicate. Here, you can simplify the process, streamline your messaging, and empower you to communicate in ways that grow with your business.
Backlog Refinement with Jira Template
Works best for:
Agile, Backlog Refinement
The Backlog Refinement with Jira template in Miro improves collaboration among team members. It provides a visual and interactive space for teams to review, prioritize, and clarify upcoming work items together in real time. This collaborative approach ensures alignment on priorities and details, leading to a more organized and efficient workflow. The seamless integration with Jira automatically syncs all changes, reducing the need for manual updates and keeping both platforms up-to-date.
Hiring Process Timeline
Works best for:
Timeline, Planning
Simplify your hiring process with the Hiring Process Timeline template. This tool helps you map out each step of your recruitment process, from job posting to onboarding. Visualize deadlines, track candidate progress, and ensure a smooth and efficient hiring experience. Perfect for HR teams looking to streamline and enhance their recruitment strategy.