4A · Portfolio Conference
Do we need none, one or several portfolio-level alignment events?
Exercise 4
Design the Refinement Cadence
Place portfolio, value stream, transformation, ART and solution-train events on the PI timeline so the draft roadmap becomes PI-Planning-ready without pretending that higher-level conferences create ART commitments.
Exercise 4 overview
The path toward PI Planning.
Exercise 4 designs a refinement cadence hypothesis: conference positions, final syncs, recurring update loops and readiness checks before PI Planning.
4B · Value Stream Conference
How does portfolio intent become a value-stream roadmap?
4C · Transformation Conference
Which transformation initiatives must align before value-stream trade-offs?
4D · ART Conference
Where can ART representatives rebalance capacity before roadmaps harden?
4E · Solution Train Conference
Which cross-ART dependencies must be aligned before ART PI Planning?
4F · Refinement Sync Cadence
Which recurring syncs harden the draft roadmaps?
4G · PI Planning Readiness
Does the cadence create readiness for ART commitments?
Timeline model
Start with PI Planning and work backwards.
The 12-week example places major conferences early in the PI and condensed final syncs in the IP sprint before PI Planning.
Portfolio / Transformation
Strategic frame and transformation inputs.
Value Stream Conference
Draft value stream roadmap and decision backlog.
Solution Train Conference
Cross-ART roadmap and plan-ready inputs.
Sync cadence
Feedback loops, roadmap updates and decision backlog review.
Final Sync chain
Final portfolio, VS and ST hardening before PI Planning.
Commitments
ARTs create ART-level commitments.
4A · Portfolio Level
Portfolio Conference hypothesis.
Decide whether the portfolio needs a conference, when it happens, and whether a final portfolio sync is useful.
Design question
Which strategic decisions must be clarified before Value Streams and Solution Trains can refine without ambiguity?
| Event / option | Timing | Duration | Inputs / participants | Output / hypothesis |
|---|---|---|---|---|
| No Portfolio Conference | — | — | strategy already clear | guardrail risk? |
| Early Portfolio Conference | S1 | 1–2 days | priorities + epics | strategic frame |
| Mid-PI Review | S3? | 0.5–1 day | course correction | adjusted guardrails |
| Final Portfolio Sync | IP | 0.5–1 day | last decisions | PI guardrails |
| Multiple events | early + IP | context-specific | high uncertainty | test pattern |
No Portfolio Conference
Existing portfolio mechanisms are enough; risk: strategic ambiguity remains hidden.
Early Portfolio Conference
Set strategy, priorities and guardrails early in the PI.
Portfolio Guardrails
Funding, budget, capacity bands or timing constraints are clarified.
Final Portfolio Sync
Verify final portfolio guardrails before PI Planning.
4B · Value Stream Level
Value Stream Conference hypothesis.
Decide how the Value Stream turns portfolio intent into a draft roadmap and refinement path.
Design question
Where must end-to-end value, shared initiatives and tactical capacity be harmonized before ART commitments?
| Event / option | Timing | Duration | Inputs / participants | Output / hypothesis |
|---|---|---|---|---|
| No VS event | — | — | portfolio + train input | risk of local optimization |
| VS Conference | S2? | 1–2 days | objectives + capacity | draft VS roadmap |
| Recurring VS Syncs | S2–S5 | short | feedback + updates | decisions |
| Final VS Sync | IP | 0.5–1 day | validated roadmap | PI-ready stream frame |
| Own VS pattern | context-specific | context-specific | context-specific | hypothesis |
Early Value Stream Conference
Creates a draft Value Stream Roadmap early enough for refinement.
Value Stream Roadmap Review
Overlay objectives, shared initiatives, capacity and problem measures.
Domain / CoP Sessions
Architecture, DevOps, Cyber, Compliance, AI/Data and Platform alignment.
Downstream Handoff Package
What should Solution Trains or ARTs receive after the conference?
4C · Transformation Conference
Transformation Conference hypothesis.
Decide whether transformation initiatives need their own alignment before the Value Stream Conference.
Design question
Where must architecture, infrastructure, toolchain and agile transformation be co-developed before value-stream trade-offs?
| Event / option | Timing | Duration | Inputs / participants | Output / hypothesis |
|---|---|---|---|---|
| No transformation event | — | — | initiative inputs | risk of conflicting signals |
| Transformation Conference | before VS | 0.5–2 days | initiative roadmaps | aligned transformation frame |
| Transformation Syncs | S1–S5 | short | updates + conflicts | guardrails |
| Final Transformation Sync | before VS / IP | 0.5 day | validated inputs | VS-ready constraints |
| Own pattern | context-specific | context-specific | context-specific | hypothesis |
Architecture Transformation
Target architecture, technical runway, interfaces and decomposition guardrails.
DevOps Transformation
Pipeline, automation, quality gates, release and deployment model.
AI / Data Transformation
Data platform, AI enablement, governance and analytics.
Conway Alignment
Co-evolve technical architecture, tooling and collaboration structure.
4D · ART Conference
ART Conference hypothesis.
Decide whether ART representatives should align capacity and cross-ART support before higher-level roadmaps harden.
Design question
Where can ART representatives rebalance capacity before the Value Stream Roadmap becomes a constraint?
| Event / option | Timing | Duration | Inputs / participants | Output / hypothesis |
|---|---|---|---|---|
| No ART Conference | — | — | local capacity input | risk of unrealistic roadmap |
| ART Conference | before VS/ST | 0.5–1 day | ART roadmaps + buckets | capacity alignment hypothesis |
| Capacity Exchange Sync | S2–S5 | short | flex + overload signals | support / shift decisions |
| Final ART Sync | IP | 0.5 day | validated capacity view | PI-ready ART input |
| Own pattern | context-specific | context-specific | context-specific | hypothesis |
ART Capacity Review
Compare New, Enabler, Maintenance, KTLO, Compliance and Buffer buckets.
Cross-ART Support Swap
Where can one ART absorb, unblock or support work from another ART?
Maintenance Synergy
Combine lifecycle, defects or technical-debt work across ARTs.
Handoff Package
Capacity view, unresolved conflicts, support agreements and risks.
4E · Solution Train Level
Solution Train Conference hypothesis.
Decide whether multiple ARTs need their own cross-ART alignment event before ART PI Planning.
Design question
Which cross-ART dependencies must be aligned before teams can responsibly commit in ART PI Planning?
| Event / option | Timing | Duration | Inputs / participants | Output / hypothesis |
|---|---|---|---|---|
| None | — | — | ARTs coordinate directly | PI input risk? |
| Solution Train Conference | S3? | 1–2 days | ART reps + ST roles | cross-ART roadmap |
| Solution Train Syncs | S3–S5 | short | decision reps | roadmap updates |
| Final ST Sync | IP | 0.5–1 day | decision core | PI-ready input |
| Own pattern | context-specific | context-specific | context-specific | test case |
Cross-ART Roadmap Alignment
Show where ARTs, shared enablers and milestones fit together.
Architecture / Integration Sync
System architecture, interfaces, test and integration alignment.
ART Capacity Reconciliation
Compare ART capacity buckets with cross-ART demands.
ART PI Planning Input Pack
Objectives, guardrails, dependencies, risks and roadmap constraints.
4F · Refinement Structure
Design the refinement and sync cadence.
After each conference, define how the draft roadmap is hardened before PI Planning: frequency, participants, artifact owner and decision type.
| Sync / refinement | Frequency | Who is in? | Artifact updated | Decision type |
|---|---|---|---|---|
| Portfolio Sync | weekly / once per sprint / ad hoc | LPM + BOs + sponsors | portfolio roadmap | strategic guardrails |
| Value Stream Sync | weekly / sprint | VS leads + ST / ART reps | VS roadmap | stream decisions |
| Solution Train Sync | weekly / sprint | ST leads + ART reps | ST roadmap | cross-ART decisions |
| ART / SA refinement | as needed | RTE + PM + teams | ART / SA boards | local feasibility |
| Final Sync chain | IP Sprint | decision core | final inputs | readiness |
4G · PI Planning Readiness
Check the path to PI Planning.
The cadence is useful only if it makes ART PI Planning easier, faster and more decision-capable.
Timing
Enough time between portfolio, value stream, solution train and PI Planning?
Decision rights
Are people with authority in the right events?
Artifact flow
Does every event update a roadmap, backlog, risk log or guardrail?
Feedback flow
Do ARTs and Solution Areas validate hypotheses before commitment?
Inspect & adapt
How will we learn whether the cadence worked after one PI?
Commitment anchor
Does PI Planning still create the ART commitments?
Output
A refinement cadence hypothesis with decision locations and artifact flow.
Close with a testable statement: this is not the meeting calendar forever; it is a cadence hypothesis to inspect after one PI.