Show all posts
4 years ago

3D Backlog Management

Managing or prioritizing backlog, re-prioritizing work in progress — these activities make up the most of product owner's work. That's not a breaking news, obviously. Product Owners have lots of things to consider as they:

1. keep some work in the backlog (as unsorted as a heap of wooden logs)

2. sign off some work to go into production

3. re-prioritize work that is already in progress.

At times, the boundaries between a pure production flow (Work In Progress, as in Kanban) and backlog are quite blurred. Some items might stall, as it turns out that they need to be re-prioritized and/or returned back to the "heap of logs". You might wonder, as a product owner, or a project manager, when is it OK to go with the 2D map which plots work against In Progress states (like in the classical Kanban board), or when you need a 3D concept map to balance your decisions against multiple priorities? Are there any workarounds you can use for a 2D map to make it work as 3D, when there are more things to consider than merely putting work through the production flow?

Some of you might be familiar with the concept of story maps vs. process maps, but I'm using a bit different perspective. A part of it is covered by the story map concept of "walking skeleton", but what I'm trying to highlight is the speed and convenience with the 1-2-3 product owner actions.

Here's a 2D Kanban board,  where Planned is some prioritized, "ready to go to In Progress" work:

open planned articles board


You might need to introduce yet another buffer for the sorted out Planned state. That's when you most probably add the Open state:

Backlog ->  Open ->  Planned -> Work In Progress -> Done

The Open and Planned states are not the sequential production states. The Planned state is a product of of applying some other 3d dimension. Some set of business or any other priorities.  As a product owner,  you need to sift the work through many deciding criteria, bouncing it between Open and Planned as often as needed. That's what we call "grooming the backlog".

If you operate within this 2D environment, on a physical or electronic Kanban board, you might use tags, or colors for the cards, or add more non-production states which are essentially priorities (as Open - Planned states).

Now take a look at this visual. It's a little bit different from what is considered a story map concept, as  I'm using another set of coordinates, where X-axis is work, Y-axis is progress, the X-Y plane is any work in progress AND Z-axis is any other 3d dimension, or lens, through which you filter the backlog or work in progress. The red lines in the Z-plane against the X-Y plane represent those various influences, or filtering criteria.

3D backlog environment
If you're using some tool to switch and rotate the criteria on the Z-axis fast, you're much better off grooming your backlog, prioritizing work, and tracking work in progress. I've mentioned some workarounds, such as using tags, introducing the states that are not actually "production" but rather "prioritizing" states, colors for cards. Another traditional technique is prioritizing work in lists, not on a board. But all those practices are quite limiting. They don't provide enough versatility.

Z-axis are essentially swimlanes, if you look closer, and flexibility with swimlanes is a huge thing. If 2D workarounds are limiting, or your current backlog management tools do not give you enough freedom with swimlanes, we have an unbelievably flexible 3D backlog management experience in store for you, coming soon in a newer version of our tool. It will work exactly as on the visual above: rapidly switchable Z-axis influences (swimlanes) that highlight certain backlog items and work in progress.

work by teams screen

Stay tuned.

  • Andreas

    Well elaborated article!
    While i was reading it i wondered whether adding story mapping functionality to TargetProcess could be a new, useful feature.


  • indigo777

    Andreas: If I understood you correctly, you’re wondering if story mapping functionality will appear in Targetprocess in the future? If that’s your question, then the answer is “yes”. Stay tuned 🙂 Actually, the screen at the bottom of the post shows a little but of it. The story mapping that TP will have, will be more than classical story mapping, and that’s exactly what my post is about.

Get started for free

How many people would be using Targetprocess?
  • Myself
  • 2–20
  • 21–100
  • 101–1000
  • 1000+
By clicking Continue you agree to our Terms of service and Privacy policy