From Roadmap to User Story
A guide to aligning priorities and breaking down work across multi-team products
less than a minute
Aligning priorities across multi-team products can be challenging. This guide outlines how to effectively break down work from program-level roadmaps to team-level user stories.
Program Roadmap
Key Point
Establishing and understanding goals and priorities is crucial for an effective work breakdown process.
Program Roadmap
- Stakeholders and leadership teams must define high-level initiatives and their priorities
- Work can then be dispersed among product teams
- Leadership teams can be composed of a core group of product owners
Product Roadmap
The program roadmap should break down into the product roadmap, which includes the prioritized list of epics for each product.
Product Vision
The leadership team should define:
- Product vision
- Roadmap
- Dependencies for each product
Team Backlog
The team backlog should comprise the prioritized epics from the product roadmap.
Feature Backlog
Effective Work Breakdown
The core group needed to effectively break down high-level requirements includes:
- Product owners
- Tech leads
- Project managers
Product teams should use processes effective for Work Decomposition to break down epics into:
- Smaller epics
- Stories
- Tasks