The minute someone believes they can predict the future and provide a detailed estimate, on the individual work item level, a lot of damage is done. If we plan that something will start on a given date and finish on a given date, we start fooling everyone, including ourselves.
If you ever have to foresee the future, the Portfolio Kanban concept can be employed so that you deliver a flexible, lean, Kanban roadmap, that will actually help.
Challenges with Traditional Roadmap Implementations
The real problem with traditional roadmaps is that they are deterministic, often communicating fixed dates and scope, while they should be probabilistic, communicating that there is X percent probability to deliver certain scope by a given date.
Have you ever seen a product roadmap with milestones set on a given date? How often do you see any probability attached to this date? Right, hardly ever. This is a real challenge for many companies because project and program managers work with fixed dates.
However, when you talk about the future and you are in the knowledge work business, nobody knows how long things will take. Therefore, you must never ever communicate fixed dates and milestones, unless you are 100% certain that you can do it.
If you are required to communicate fixed dates, just because nobody would ever consider your bid for the project, then do what you have to do in order to win it. This will most likely require that you commit to delivering a certain amount of work for a certain period of time.
Good or bad, that’s how the world works today and that’s normal. However, the fact that you commit to a fixed date doesn’t require that you execute your project in a waterfall manner. You can still have a flexible roadmap within the specified boundaries.
What’s the way out? Portfolio Kanban and a Kanban Roadmap.
Before digging into the depths of the Portfolio Kanban application for Kanban Roadmap implementations, let’s scratch the topic of Upstream Kanban otherwise known as Customer Kanban.
Upstream Kanban / Customer Kanban
As Patrick Steyaert explains in the article “Customer Kanban – from customer push to customer pull”, Upstream Kanban (Customer Kanban) is:
Upstream Kanban visualizes the demand in terms of options that are explored to define and select the work items that will be committed.
Everything else aside, thinking in terms of options is critical to getting to a better understanding of how a Kanban Roadmap works. All non-started projects are options visualized as Kanban cards on the “Requested” area of your Kanban board. Even if a given project is committed, unless it’s been started, it’s still an option that you can choose to execute or not.
Treating non-started work as options is, in fact, deferring the commitment to the latest responsible moment. This is one of the Lean Software Development principles that Tom and Mary Poppendieck discuss in one of their popular books. This principle holds true not just for software development, but for any knowledge work.
If you defer the commitment, then you can choose to descope certain piece of work, should the circumstances require it. If you operate based on a predefined master plan, then you lose this flexibility. Even if you don’t need this flexibility, it may be useful, because you will learn new things as the project progresses. You can use this new knowledge to postpone some of the features and expedite others. Therefore, the ability to reorganize your plan in a quick and unobtrusive manner can lead to great economic benefits.
Portfolio Kanban and a Kanban Roadmap
If you are not familiar with the term Portfolio Kanban, please go through this article before you continue reading further: What is Portfolio Kanban?. To realize a Kanban roadmap, first, you need to have a Portfolio Kanban board. This board will usually hold MMFs (Minimal Marketable Feature) or Projects. The MMFs or Projects will be broken down into User Stories or simply put – tasks.
With the Kanban board in place, you need to focus on the leftmost part of the board – the Requested area (the one with the grey line at the top). The Requested area contains items that have not been started yet (options). Based on your project scope and timeline, you can add an unlimited number of columns to the Requested area, which, in this scenario, represents a reversed timeline.
Take a look at this sample image:
As shown above, the rightmost column in the Requested area is the closest one to the present moment (This Month). The farther you go to the left, the more you go into the future – “Next 3 Months”, “Unplanned”. Naturally, the items that you put in these columns should get planned for the corresponding period.
For example, all the items that are in the “This Month” column should be expected to finish before the end of the month. All work items in the “Next Three Months” should be expected to finish in the next three months, etc.
When it comes to priority, the higher an item is within the column, the higher its priority is. If you want to re-prioritize, just drag and drop the item to its new position.
The names of the columns can vary as per your convenience, as long as they indicate a reversed timeline. In the example above, we used months, but in your case, it could be days, weeks, months, quarters or even years. The horizontal lanes can be used for different teams, products or whatever else makes sense in your context.
As simple as it may be, this is what a simple Portfolio Kanban Roadmap looks like.
What are the Benefits of a Portfolio Kanban Roadmap?
- It is Visual – The visual nature of the Kanban roadmap allows you to easily grasp a lot of information. For example, if some of the MMFs is blocked, due to a problem in some of the teams, you will immediately see this on our roadmap in real time. The Kanban roadmap is an excellent information radiator because everyone can see it and instantly answer themselves the question “When is X going to be done?” without the need of status reporting.
- Easy to Re-prioritize – As mentioned above, changing the priority is as simple as dragging and dropping the card to a new position. This is how you make sure that the teams will only work on the most important items first.
- Easy to Change Due Dates – What should you do if due dates change? Well, instead of updating a three-year plan, all you need to do is change the column of some of the items. Of course, this activity requires careful analysis around capacity and throughput, but we have something to help you there as well: Portfolio Kanban – How To Forecast on the Portfolio Level.
- Supports Flow on the Global Level – Probably the most important piece is that your Kanban roadmap is not a static powerpoint presentation that nobody looks at. On the contrary – it is a living entity that constantly broadcasts information and enables flow across the organization. With this approach to roadmapping, you won’t just say when things will get done, but you’ll be able to actively monitor if they are on track and what is still left to be done.
What are the Disadvantages of a Portfolio Kanban Roadmap?
The only real disadvantage to the Kanban roadmapping approach is the lack of fixed dates. Technically speaking, you could label a column with a certain date and treat it as a milestone, but this is more or less violating the flow-based approach described above.
This concept represents a different paradigm and needs changes in perspective to get started and get used to. However, once you’ve managed your first project this way, you are not likely to look back at the old ways.