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.
Product Launch Lifecycle
Works best for:
Product Management, Planning
The Product Launch Lifecycle template guides product managers through the stages of launching new products. By outlining pre-launch, launch, and post-launch activities, this template ensures comprehensive product launch planning and execution. With sections for defining launch objectives, identifying target audiences, and tracking performance metrics, it facilitates coordinated efforts across marketing, sales, and product teams. This template serves as a roadmap for successful product launches, maximizing market impact and customer adoption.
Social Media Strategy Planning
Works best for:
Roadmap, Planning, Mapping
The Social Media Strategy Planning template provides a structured approach for developing and implementing social media strategies. By defining objectives, target audiences, and content plans, teams can maximize the impact of their social media efforts. This template fosters collaboration and alignment across teams, ensuring that social media initiatives are integrated with broader marketing goals and contribute to overall business objectives.
UML Sequence Registration Process Template
Works best for:
UML
The UML Sequence Registration Process Template helps visualize and document user registration processes. It enables the rapid creation of sequence diagrams, which are crucial for enhancing clarity and identifying potential issues early in the design phase. This template not only supports collaborative efforts through Miro's platform, facilitating real-time teamwork, but also ensures a comprehensive system design. Being part of a broader collection of UML diagram templates, it stands as a valuable asset for projects involving registration workflows, contributing to streamlined project execution and effective communication among team members.
Event Planning Template
Works best for:
Planning, Workshops
Whether you’re planning a product launch, fully remote conference, or milestone event, the Event Planning Template will act as a visual checklist and map for all the details you need to consider before the big day. The Event Planning Template is an adaptable way to make sure the creative and strategic vision of your event doesn’t get lost in the details. By mapping out different sections - from the marketing plan, to the agenda, to snacks and swag for guests — you and your team can focus on the details most important to your functions, and collaborate as needed when overlaps occur.
Buyer Persona Template
Works best for:
Marketing, Desk Research, User Experience
You have an ideal customer: The group (or few groups) of people who will buy and love your product or service. But to reach that ideal customer, your entire team or company has to align on who that is. Buyer personas give you a simple but creative way to get that done. These semi-fictional representations of your current and potential customers can help you shape your product offering, weed out the “bad apples,” and tailor your marketing strategies for serious success.
Agile Transition Plan Template
Works best for:
Agile Methodology, Agile Workflows
An Agile transformation roadmap can help you, your team, and your organization transition from rigid compliance-heavy methods to the more flexible Agile way of doing things incrementally. From requirements to integrations to security, you can map out your organization's moving parts as “swim lanes” that you can then update regularly. Use your roadmap as a way to tell the story of how you see your product growing over a period of time. Get buy-in without overselling and keep your roadmap simple, viable and measurable. By using an Agile transformation roadmap, you can avoid getting bogged down in details and instead invest in big-picture strategic thinking.