Maintaining the Product Roadmap
Maintaining the Product Roadmap involves the ongoing process of updating the product’s roadmap based on the progress, insights, and changing priorities of individual Stream Teams within the Product.
Goal
The goal is to ensure the product roadmap reflects the current state of product development and enables transparent communication of the product direction to stakeholders.
Context
The Stream Teams decide on the features to build to achieve their objectives. This means that, rather than having a centralised roadmap that dictates what each stream should work on, the product roadmap is a reflection of the work that the Stream Teams are doing. It is a bottom up document rather than a top down one.
The Product Team then needs to track the progress of the different features because they are ultimately accountable for the Product success and therefore need to ensure that the Stream Teams are working on the right things.
Inputs
| Artifact | Description |
|---|---|
| Stream Team Kanban Boards | The boards from each Stream Team, showing current work items across all stages from discovery to delivery. |
Outputs
| Artifact | Description | Benefits |
|---|---|---|
| Product Roadmap | A document or visual representation that outlines the planned initiatives, features, and milestones based on the latest inputs from Stream Teams. | Ensures alignment across teams, aids in strategic planning, and communicates the product direction to stakeholders. |
Anti-patterns
- Creating a Static Roadmap: Failing to update the roadmap based on changing priorities and insights from Stream Teams.
- Overemphasis on Features: Focusing solely on features rather than strategic objectives and outcomes.