A Kanban roadmap can be a great way to track your features across your discovery and delivery lifecycle. This roadmap organizes features by status. You can learn more about feature statuses in Productboard in this article.
In this article:
- How to create a Kanban roadmap
- When should I use a Kanban roadmap?
- Learn more about using Kanban roadmaps
How to create a Kanban roadmap
Create your roadmap
- Navigate to your Roadmap board.
- From the drop-down menu, select Create Roadmap.
- Select Kanban roadmap from the left menu.
- Click Choose roadmap.
- Click Add status.
- Select a status from the menu to create your first column.
Add or rearrange status columns
- Click [+] to add a new status column.
- Click ・・・ to add a status column to the left or the right.
- Click and hold a status to drag and drop the column.
Add features to a Kanban roadmap
There are three ways to add a feature to a Kanban roadmap:
- Click [+] in a status column to search for an existing feature. If the feature has another status, the feature status will change to match that of the column.
- Click [+] in a status column to create a new feature. The feature will automatically be assigned the status of the column.
- From the features board, click the status of a feature to select one of the statuses you're viewing on your roadmap.
Keep in mind that you can also perform step 3 by dragging and dropping a feature to another status when viewing the Features board by status:
How to organize your Kanban roadmap
- Click Settings to open up the configurations menu.
- Select Swimlanes to organize your roadmap horizontally.
- Toggle Effort to display story points on each feature card.
- Click on the People section and select which avatar you want to visualize on each feature card - Owner, Teams, or Custom Member field.
- Scale and Enterprise plans: Toggle Objectives to display any objectives associated with that feature.
- Toggle Show hidden cards to display feature and subfeature cards that have been manually hidden from contributors.
- Toggle Show subfeatures to display associated subfeature cards.
Organize by hierarchy
- Click on Settings in the top right corner to access additional organization options.
- Select Hierarchy to group feature ideas by their relevant components or sub-components.
- Hover over a component and click the down-facing caret which appears in order to hide or expand its associated features.
Organize by objectives (available on Scale and Enterprise plans)
- Click on Settings in the top right corner to access additional organization options.
- Select Objectives to group feature ideas by their relevant objective.
- Toggle Priority to display how important this feature is towards the overarching objective.
- Toggle Team to display the team associated with the overarching objective.
- Click the down-facing caret on an objective to hide or expand its associated features.
- Drag and drop your objectives to adjust the order in which they're displayed.
How to share and export your Kanban roadmap
- After making any configuration changes, click Save roadmap. You will see confirmation once your roadmap changes have been saved, and the Save button will now read Share.
- Click Share to configure your roadmap sharing settings.
- Click Print to print your roadmap.
- Click Export to image to generate a PNG of your roadmap.
When should I use a Kanban roadmap?
Kanban roadmaps are good for:
- You're a team using working in a dual track agile approach.
- You're using a continuous release process without fixed releases or versions.
- Communicating at a high level with product leadership: are we blocked? are we moving ideas out of our backlog and into delivery?
- Communicating with teams already using a Kanban board to organize their work.
- Product teams with lots of granular statuses. Colorful icons do the trick when there are only a few possible statuses, but if you're trying to track >5 statuses, a Kanban view is easier to follow.
Kanban roadmaps might not be good for:
- Measuring progress against strict deadlines with specific milestones. Consider a Features Timeline roadmap instead.
- A huge features backlog that needs cleaning up. Try a simpler Now-next-later roadmap to render order out of chaos.
- Customer-facing teams, who will want more specific release timelines. Try a Releases timeline plan.
Comments
Article is closed for comments.