The Product Backlog is the single place where work needed for the product is organized. Classically, the product backlog is a prioritized list. But does it have to be? The most important thing is prioritization, right? In this episode, product engineers Oliver Winter and Dominique Winter talk about other alternatives when it comes to good organization of the product backlog.
Advertisement
User story map, funnel backlog and more
Alternatives can be found quickly. Some methods are quite well known, like the user story map. The product backlog is organized in two dimensions. But other methods such as Classes of Work can also provide a helpful overview. The work is divided into different types and prioritized separately. And then there are alternatives from other areas such as the funnel backlog, where you focus on what work is currently necessary in which funnel areas. There are also impact maps, activity node network plans and a few more.
In the end, the alternative forms of organization all have their advantages and disadvantages. When working as product owners, product managers and product leaders, people have to weigh up which type is more suitable than others. Sometimes identifying dependencies can be more important, sometimes the absolute serialization of work. In the end, it often depends on the collaboration with your own stakeholder community.
The current edition of the podcast is also available on the Produktwerker blog: “Organize Product Backlog”.
The organizers will judge on March 12th and 13th, 2024 in Cologne dpunkt.verlag and iX die Product Owner Days on site for the first time. In addition to over 20 lectures on agile product management, three workshops will take place the day before.
Workshops on March 11th:
(May)
To home page