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.
IT Project Timeline
Works best for:
Timeline, Planning
The IT Project Time Line template is essential for managing IT projects efficiently. It allows you to visualize project milestones, deadlines, and key tasks in a clear, chronological format. Track progress, allocate resources, and ensure timely delivery of your IT projects. Ideal for project managers and IT teams aiming to stay organized and meet critical deadlines.
Mandala Chart Template
Works best for:
Planning, Brainstorming, Goal setting
The Mandala Chart Template helps you visualize the relationships between a central theme and its sub-themes. One of the key benefits is how it fosters a holistic understanding of any topic. This perspective ensures every detail is noticed, making it an invaluable asset for those aiming for comprehensive insight and thorough planning or a better understanding of their goals.
Monthly Planner Template
Works best for:
Operations, Strategic Planning, Project Planning
To knock out every task and accomplish every goal for the month, it helps to take a big picture, 10,000 foot view of things—meaning a 30-day view. That’s why a monthly calendar can come in so handy, especially on bigger projects. Use our template to create a visual representation that helps you track and space out every deadline and to-do, both for individuals and full teams. You’ll even be able to customize it your way, with images, video, and sticky notes.
Fishbone Diagram for Quality Control
Works best for:
Fishbone diagram
Maintaining high standards of quality is vital in any industry. The Fishbone Diagram for Quality Control template helps you identify and analyze the root causes of quality issues. Use it to categorize potential causes into areas such as materials, methods, manpower, and machinery. This structured approach ensures a thorough examination of all possible factors affecting quality, leading to more effective solutions and continuous improvement.
Cross Functional (Swimlane) Chart
Works best for:
Flowcharts, Mapping, Diagrams
The Cross Functional (Swimlane) Chart template offers a visual tool for mapping out processes or workflows with multiple stakeholders or functional areas. It provides swimlanes for organizing tasks and responsibilities by department or role. This template enables teams to visualize process flows, identify handoffs, and improve coordination and collaboration across functions. By promoting transparency and accountability, the Cross Functional (Swimlane) Chart empowers organizations to streamline workflows and drive cross-functional alignment effectively.
Lean Project Charter
Works best for:
Agile
The Lean Project Charter template provides a streamlined approach to defining project objectives, scope, and success criteria. It emphasizes clarity, brevity, and alignment with Lean principles, enabling teams to kickstart projects with focus and purpose. This template empowers teams to set clear goals, establish shared understanding, and align stakeholders, driving efficiency and effectiveness in project delivery. By promoting transparency and accountability, the Lean Project Charter sets the foundation for successful project execution and continuous improvement.