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