Road Mapping Workshop

02 / Application

When to Use Road Mapping

Road mapping workshops are most valuable when an organization needs to surface delivery intent and align investment decisions across multiple teams or value streams. Use this workshop when existing planning artifacts are not connecting strategy to real execution, or when stakeholders lack a shared view of what is coming and why.

Prerequisites

Roles and Responsibilities

• Facilitator (RTE or Agile Coach)Guides the session flow, manages time, surfaces conflicts, and ensures outcomes are captured. Keeps discussion strategic rather than drifting into implementation detail.
• Product ManagementOwns the feature and epic backlog input, provides business value context, and is accountable for the roadmap content decisions made in the session.
• Business Owners and SponsorsRepresent strategic priorities and investment intent. Their presence ensures roadmap decisions are grounded in organizational strategy, not just delivery convenience.
• Architecture and Engineering LeadProvides technical feasibility input and surfaces dependencies or enabler work that must be sequenced before business features can land.
• Scrum Masters and Team LeadsInform capacity and velocity assumptions, and ensure team-level dependencies are represented in the roadmap sequencing decisions.

Not every role needs to be present for the full session. Business owners and sponsors can participate in the framing and prioritization portions and step away during detailed sequencing work.

Scheduling and Timing

• Run 4–8 weeks before PI Planning for maximum impact — far enough out to influence PI objectives, close enough that the context is current.
• Half-day sessions (3–4 hours) work well for programs with an existing backlog and clear strategic context. Full-day sessions are appropriate for new value streams or major strategic pivots.
• Schedule a 30-minute pre-session with product management to review backlog inputs and confirm the strategic context document is complete and shared with all participants.
• Plan a follow-up distribution within 48 hours so the roadmap is shared while context is fresh and stakeholders can begin acting on it.

04 / Facilitation

Facilitation Agenda

This agenda guides facilitators through a structured road mapping session. Time estimates reflect a half-day format — adjust durations for a full-day session when working with a new value stream or a major strategic reset. Keep the session outcome-focused: the goal is a shared, actionable roadmap artifact, not an exhaustive discussion of every feature.

Presenting the Road Mapping Process

1. Open and Frame the Session (15 min)

   • Welcome participants and review the session objectives and agenda.
   • Establish ground rules: stay strategic, timebox discussions, and treat all decisions as drafts subject to PI Planning refinement.
   • Share the strategic context — review the current strategic themes and OKRs together as a group before any backlog discussion begins.
2. Review the Current Backlog (20 min)

   • Walk through the prepared epic and feature backlog as a group — confirm everyone is working from the same list.
   • Flag any items that are missing, stale, or need further definition. Park them in a “needs definition” swim lane rather than blocking the session.
   • Review the known milestones, committed dates, and dependencies that will constrain sequencing.
3. Map Features to Strategic Themes (25 min)

   • Using sticky notes or digital cards, have product management place each feature under the strategic theme it most directly supports.
   • Facilitate a brief discussion for items where the strategic fit is unclear — if the group cannot connect a feature to a strategic theme in two minutes, move it to a “strategic alignment needed” column.
   • Highlight features that support multiple strategic themes; these often carry higher business value and should be weighted accordingly in sequencing.
4. Sequence the Roadmap (45 min)

   • Working from the theme-mapped features, begin placing items into PI swim lanes — current PI, next PI, and future horizon.
   • Use WSJF scores (Cost of Delay / Job Duration) to resolve sequencing conflicts where the group disagrees. Let the math start the conversation, then allow stakeholders to override with business context.
   • Mark enabler features and architectural work that must precede business features — these often need to move earlier in the sequence than their business value score alone would suggest.
   • Identify and visually map dependencies between features across teams or value streams. Any dependency that crosses a PI boundary is a risk to flag explicitly.
5. Validate Milestones and Commitments (20 min)

   • Overlay known committed milestones and regulatory deadlines onto the sequenced roadmap. Confirm that what has been sequenced in each PI can realistically land by any milestone it is tied to.
   • Identify any sequencing decisions that now look at risk given milestone constraints — surface these explicitly rather than leaving them as assumptions.
   • Get verbal confirmation from business owners that the milestone commitments still align to strategic priorities as sequenced.
6. Identify Risks and Open Items (15 min)

   • Walk the roadmap as a group and call out any items that still need definition, approval, or capacity confirmation before the roadmap can be considered a working draft.
   • Assign an owner to each open item and a target resolution date — before PI Planning if the item is needed to confirm PI objectives.
   • Capture risks using the ROAM format (Resolved, Owned, Accepted, Mitigated) for any risks surfaced during sequencing.
7. Confirm and Close (10 min)

   • Read back the roadmap as built: strategic themes, sequenced features by PI, milestone commitments, and open items with owners.
   • Get verbal alignment from all participants that the draft roadmap reflects the group’s shared intent.
   • Confirm the distribution plan and follow-up timeline: roadmap artifact within 48 hours, stakeholder communications within one week.

Common Anti-Patterns to Avoid

• Sequencing by team preference rather than strategic value — every placement decision should be traceable back to a strategic theme or OKR.
• Treating the roadmap as a commitment rather than a plan — a roadmap is a directional artifact that will be refined at each PI. Presenting it as a locked schedule sets false expectations.
• Skipping enabler and architectural features in the sequencing pass — technical debt and enabler work are real sequencing constraints and must appear on the roadmap alongside business features.
• Building the roadmap without business owners present — a roadmap built by product and engineering alone, without strategic validation, rarely survives its first stakeholder review.

06 / References

References and Resources

• Scaled Agile Framework (SAFe): Roadmap
• Scaled Agile Framework (SAFe): PI Planning
• Scaled Agile Framework (SAFe): Lean Portfolio Management