Design the Path from Higher-Level Alignment to PI Planning Readiness
Place conferences, final syncs, and recurring refinement loops on the PI timeline so portfolio intent, value-stream roadmaps, solution-train inputs, and ART capacity assumptions become plan-ready before PI Planning.
- Source
- Slides 62–85
- Fast path
- 7 × 5 minutes
- Input
- Decision-capable conference package
- Output
- Refinement cadence hypothesis
- Next step
- Execution Cadence
Understanding Refinement Cadence
Higher-level events create plan-ready inputs—not ART commitments
Refinement Cadence designs the route from strategic and value-stream alignment toward PI Planning. Conferences create draft roadmaps, guardrails, decision logs, and handoff packages. Recurring syncs harden these drafts with feedback from ARTs, Solution Areas, shared initiatives, central functions, suppliers, and the people who will refine the work.
Start with the ART PI Planning date and work backwards. Every conference, sync, and final check should make that planning event easier, faster, and more decision-capable.
Portfolio, Value Stream, transformation, ART capacity, Solution Train, and final readiness decisions need named locations.
Roadmaps, guardrails, decision logs, risk boards, and contribution forecasts must become more trustworthy over time.
ARTs, Solution Areas, teams, suppliers, shared foundations, and central functions challenge the draft before commitment.
A sync belongs on the cadence only when it can change a decision, update an artifact, or validate a material assumption before PI Planning.
Running the Exercise
Eight moves from conference package to cadence hypothesis
Use the deck’s snippet cards as a menu. Duplicate, rename, or remove cards where the value stream reality demands it.
-
1
Approximately 3–5 minutes
Place the PI Planning Anchor and Work Backwards
Start with the target PI Planning event. Mark the IP iteration or final readiness window, then place conferences early enough that ARTs, Solution Trains, and Solution Areas can refine before commitments are made.
AnchorWhen does PI Planning happen? Use the real ART PI Planning date, not an ideal calendar placeholder.
ReadinessWhat must be true before then? Objectives, guardrails, dependencies, risks, capacity, and major constraints are visible.
SpacingHow much refinement time remains? Check that conferences do not consume the very time needed for validation and refinement.
Conference Refinement PI Planning Readiness -
2
Exercise 4A · Portfolio Level
Design the Portfolio Conference Hypothesis
Decide whether portfolio-level alignment is needed, when it happens, how long it takes, who must attend, and whether a final portfolio sync is useful before PI Planning.
NoneExisting mechanisms are enough Use when strategy and guardrails are already clear.
Early ConferenceSet strategy and guardrails One to two days early in the PI for priorities, epics, and investment boundaries.
Final SyncVerify PI guardrails Half to one day near IP sprint for last portfolio-level decisions.
Portfolio Conference Canvas Option Timing Duration Decision need Output / hypothesis No conference — — strategy already clear guardrail risk? Early conference Sprint 1 1–2 days priorities + epics strategic frame Mid-PI review Sprint 3 0.5–1 day course correction adjusted guardrails Final sync IP 0.5–1 day last decisions PI guardrails Decision test: if no portfolio decision changes a downstream roadmap, do not add a portfolio conference just because the template offers one.
-
3
Exercise 4B · Value Stream Level
Design the Value Stream Conference Hypothesis
Decide how the value stream turns portfolio intent into a draft roadmap and a refinement path. Place the event so there is enough downstream refinement time before PI Planning.
No Value Stream Conference Use only if another layer already creates stream-wide clarity without local optimization risk.
Early Value Stream Conference One to two days in Sprint 2-ish to create the draft Value Stream Roadmap.
Two Half-Days Use when overnight reflection or leadership review improves decision quality.
Final Value Stream Sync IP-sprint hardening point before downstream PI Planning.
Recurring Value Stream Syncs Roadmap update and decision cadence between the conference and final sync.
Downstream Handoff Package Define what Solution Trains, ARTs, and shared foundations receive after the conference.
Timing test After the Value Stream Conference, is there still enough time to refine with trains, ARTs, suppliers, and shared foundations before PI Planning? -
4
Exercise 4C · Transformation Conference
Decide Whether Transformation Initiatives Need Their Own Alignment Event
Use this only when architecture, infrastructure, toolchain, AI/data, operations, agile transformation, or platform initiatives must be co-developed before value-stream trade-offs begin.
ArchitectureTarget state and interfaces Technical runway, decomposition guardrails, and architecture constraints.
DevOpsDelivery system Pipeline, automation, quality gates, release, and deployment model.
AI / DataShared intelligence layer Data platform, AI governance, use cases, analytics, and automation.
ITIL / OperationsRun and support Service model, incident flow, operations handoff, and KTLO implications.
Agile transformationOperating model Roles, learning system, collaboration expectations, and change capacity.
Toolchain / ALMTraceability and workflow Shared tooling, workflow standards, evidence chain, and data flow.
Design test: do transformation initiatives strengthen each other—or silently create incompatible operating models?
-
5
Exercise 4D · ART Conference
Decide Whether ART Representatives Need Capacity Alignment Before the Roadmap Hardens
Use an ART Conference or capacity exchange sync when ARTs can rebalance maintenance, KTLO, enablers, specialist bottlenecks, or cross-ART support before higher-level choices become constraints.
Capacity bucketsCompare work mix New, enabler, maintenance, KTLO, compliance, innovation, and buffer.
Support swapShift or unblock work Where can one ART support another or absorb a temporary bottleneck?
SpecialistsFind narrow capacity Architects, cyber, test, safety, supplier, or platform experts.
Handoff packageMake capacity explicit Unresolved conflicts, support agreements, fixed commitments, and risks.
Capacity test After this ART alignment, are overloads, support options, fixed commitments, and risk buffers visible enough for roadmap decisions? -
6
Exercise 4E · Solution Train Level
Design the Solution Train Conference Hypothesis
Use this when several ARTs need one shared solution direction before ART PI Planning. The conference creates plan-ready inputs; ART PI Plannings create ART commitments.
ST ConferenceCross-ART roadmap One to two days around PI middle to align ARTs, shared enablers, and milestones.
Final ST SyncPI-readiness check Half to one day in the IP sprint for final decisions and plan-ready inputs.
ST SyncsRecurring update loop Weekly or once per iteration, depending on change rate and decision latency.
Input PackART PI Planning input Objectives, guardrails, dependencies, risks, roadmap constraints, and confidence.
Design question: which cross-ART dependencies must be aligned before teams can responsibly commit in their ART PI Planning?
-
7
Exercise 4F · Refinement Structure
Design the Refinement and Sync Cadence
After each conference, decide how the draft roadmap will be hardened. Choose syncs by purpose, frequency, participants, artifact, and decision type—not by meeting habit.
Refinement / Sync Cadence Canvas Sync / refinement Frequency Who is in? Artifact updated Decision type Portfolio Sync weekly / sprint / ad hoc LPM + BOs portfolio roadmap strategic guardrails Value Stream Sync weekly / sprint VS owner + stream leads VS roadmap stream decisions Solution Train Sync weekly / sprint STE/RTE/PM/Architects ST roadmap cross-ART decisions ART / SA refinement as needed affected people ART / SA boards local feasibility Final Sync chain IP sprint decision core final inputs readiness Decision backlog Prepare decisions so syncs are not information theater.
Roadmap owner Every sync needs someone able to update the relevant artifact.
SME standby Use standby experts when a full-time seat would create meeting load.
-
8
Exercise 4G · Integrated Cadence
Check the End-to-End Path to PI Planning
The whole cadence is useful only if ARTs can enter PI Planning with clear objectives, guardrails, dependencies, risks, and real capacity assumptions.
Timing Enough time between portfolio, value stream, solution-train, ART refinement, final sync, and PI Planning?
Decision rights Are the people with authority in the right events or available through fast standby paths?
Artifact flow Does every event update a roadmap, backlog, risk log, dependency view, or guardrail?
Feedback flow Do ARTs, Solution Areas, and teams validate hypotheses before commitment?
Inspect & adapt How will the organization learn whether this cadence improved decision quality after one PI?
Closing statement:This is our cadence hypothesis. We will test it with the people affected, run it once, and adapt it based on feedback, decision quality, and roadmap reliability.
Example Pattern
A 12-week cadence: conferences early, final syncs near IP, PI Planning as the commitment point
The deck repeatedly uses a 12-week PI model with major conferences in the first half of the PI, recurring syncs through refinement, and condensed final syncs in the IP sprint.
Start with the ART PI Planning anchor and place upstream events only when they improve readiness.
Do not schedule conferences so late that downstream units have no time to validate or refine.
If nothing can change and no artifact is updated, the sync is likely information theater.
Facilitation
Design a cadence hypothesis—not a meeting calendar forever
Ask which decision, artifact, feedback loop, or readiness risk each event improves. Remove the rest.
Move upstream, reduce scope, or create a smaller decision slot. Conferences that starve refinement defeat their purpose.
Use final syncs for material readiness checks, not for redoing the whole conference.
Reassert the guardrail: higher-level events create inputs; ARTs make commitments in PI Planning.
Require a decision backlog, artifact owner, and explicit update path for each recurring sync.
Write it as an experiment with review criteria: decision speed, roadmap reliability, meeting load, and downstream usefulness.
Ready to Move On?
The refinement cadence is useful when it clarifies decisions, feedback loops, and artifact updates
- PI Planning is placed as the commitment anchor.
- Portfolio, Value Stream, transformation, ART, and Solution Train events are selected only where they improve readiness.
- Each event has timing, duration, participants, inputs, outputs, and a hypothesis to test.
- Final syncs have a narrow readiness purpose.
- Recurring syncs have frequency, participants, artifact owner, and decision type.
- ARTs, Solution Areas, teams, and suppliers have time to validate before commitments.
- Roadmaps, risk logs, dependency views, guardrails, and decision logs are updated after events.
- The cadence hypothesis has inspect-and-adapt criteria after one PI.
Source Foundation
This page distills slides 62–85 of 05 Value_Stream_Conference.pptx. The public research links support the PI timebox, Solution Train coordination across ARTs and suppliers, and flow-based refinement discipline.