5A · Portfolio execution syncs
When do priority, funding, risks or assumptions need portfolio-level realignment?
Exercise 5
Design the Execution Cadence
After PI Planning, design the sync system that keeps execution adaptive — without confusing it with next-PI refinement or creating unnecessary meeting load.
Exercise 5 overview
Five execution cadence decisions.
Exercise 5 starts after PI Planning. It asks how portfolio, value stream, solution train, ART and Solution Area syncs keep the system responsive during execution.
5B · Value Stream syncs
How often does the value stream inspect flow, blockers and roadmap drift?
5C · Solution Train syncs
Which cross-ART decisions need one combined sync versus focused role/topic syncs?
5D · ART / Solution Area syncs
How do ART Syncs, Solution Area Syncs and team events connect upward?
5E · Merge logic
Which syncs are refinement-only, execution-only or useful for both?
Two-PI view
Refinement and execution happen in every PI.
Use the two-PI view as a thinking aid: current-PI execution signals and next-PI refinement run in parallel. Then merge both logics where purpose, participants and artifacts fit together.
Next-PI refinement
Conferences, final syncs and roadmap hardening.
Current-PI execution
Fast realignment from execution signals.
Dual-purpose sync
One event updates current execution and next-PI refinement.
Boards and roadmaps
The artifact must change during or right after the sync.
Room or standby
If nobody can decide, the sync is only information exchange.
5A · Portfolio Level
Portfolio execution syncs.
Decide how portfolio-level decisions stay connected to execution signals during the PI.
Design question
Which execution signals are important enough to trigger portfolio-level realignment without pulling the portfolio into every delivery detail?
| Option | Cadence | Purpose | Participants | Artifact |
|---|---|---|---|---|
| No sync | — | stable portfolio frame | — | no update |
| Portfolio Sync | 1× sprint | priority / funding deltas | LPM + BOs | portfolio board |
| Mid-PI Review | S3 / S4 | strategic course correction | exec + VS leads | guardrails |
| Initiative Sync | weekly? | critical epic / initiative | epic owner + SMEs | initiative roadmap |
| Risk / Compliance Sync | triggered | regulatory or risk event | risk + legal + BO | risk log |
Strategic Surprise
Market, regulation or executive priority changes during the PI.
Investment Guardrail Change
Budget, staffing, supplier cost or funding assumptions change materially.
Cross-Value-Stream Trade-off
A disruption requires priority or capacity movement across Value Streams.
Standby-Only Pattern
Reserve decision makers; call them in only when an issue needs them.
5B · Value Stream Level
Value Stream execution syncs.
Decide how the end-to-end value stream inspects flow, blockers and roadmap drift during execution.
Design question
Which end-to-end flow problems cannot be solved by one Solution Train or ART alone?
| Option | Cadence | Purpose | Participants | Artifact |
|---|---|---|---|---|
| VS Sync | weekly / sprint | value-flow realignment | VS owner + ST leads | VS roadmap |
| Flow Blocker Sync | triggered | cross-train blocker | affected roles | blocker board |
| Shared Initiative Sync | weekly? | architecture / DevOps / AI | CoP + train reps | initiative map |
| Customer / Market Sync | mid-PI | business learning | BOs + PMs | objective delta |
| Final VS Exec Review | IP | learning for next PI | VS leads + ARTs | retro inputs |
Value Flow Interruption
End-to-end flow is blocked across several trains, domains or suppliers.
Capacity Rebalancing
Unplanned KTLO, incidents or compliance work shifts capacity.
Dependency Cascade
A delay in one area changes sequencing across the Value Stream.
Decision Backlog Triage
Turn execution signals into decisions, owners and roadmap updates.
5C · Solution Train Level
Solution Train execution syncs.
Decide how multiple ARTs realign during execution and which focused syncs are worth the overhead.
Design question
Which cross-ART decisions need fast realignment at Solution Train level?
| Option | Cadence | Purpose | Participants | Artifact |
|---|---|---|---|---|
| Combined ST Sync | weekly / sprint | cross-ART decisions | ST leads + ART reps | solution roadmap |
| RTE / STE Sync | weekly | flow + impediments | RTEs / STE | impediment board |
| PM / PO Sync | weekly | scope / objective trade-offs | PMs + POs | feature board |
| Architect Sync | weekly? | technical direction | architects + SMEs | arch runway |
| Problem-Space Sync | triggered | urgent issue solving | affected people | decision log |
Cross-ART Blocker
One ART’s issue blocks another ART’s committed objective.
Integration Event at Risk
System demo, milestone or integration window is endangered.
Architecture Change
Interface, technical runway or system design changes during execution.
Update Planning Board
Make immediate changes to board, owners, risks and decision backlog.
5D · ART / Solution Area Level
ART and Solution Area execution syncs.
Design the lower-level syncs that feed execution signals upward and receive decisions back down.
Design question
How do we create fast realignment close to the work while avoiding a meeting lattice that eats execution capacity?
| Option | Cadence | Purpose | Participants | Artifact |
|---|---|---|---|---|
| ART Sync | weekly / sprint | ART realignment | RTE + PM + SA reps | ART board |
| PO / PM Sync | weekly | scope + objectives | POs + PM | feature backlog |
| Architect Sync | weekly? | technical integration | system arch + teams | arch board |
| Solution Area Sync | weekly / ad hoc | local dependency solving | SA teams / reps | SA board |
| System Demo + Sync | sprint | evidence + decisions | ART / stakeholders | demo outcomes |
Merge Refinement + Execution
Use one ART Sync if future work and current issues fit together.
Separate Execution Sync
Use when current commitments need fast decisions.
Solution Area Sync
Affected teams inspect the problem and validate options close to the work.
Change-Rate Trigger
Cadence follows volatility: daily, weekly, per sprint or on demand.
5E · Merge Logic
Refinement and execution run in the same PI.
Separate what must be separate, then merge what can share the same people, artifacts and decision rhythm.
| Sync | R | E | BOTH | Merge / separate because | Artifact owner |
|---|---|---|---|---|---|
| Portfolio Sync | □ | □ | □ | ||
| Value Stream Sync | □ | □ | □ | ||
| Solution Train Sync | □ | □ | □ | ||
| ART Sync | □ | □ | □ | ||
| Architecture Sync | □ | □ | □ | ||
| Community Sync | □ | □ | □ | ||
| Own sync | □ | □ | □ |
Aha question
Which syncs are accidentally duplicated because refinement and execution were designed separately?
Roadmap view
What feeds the shared Value Stream Roadmap?
Prepared artifacts and execution signals become layers in the shared roadmap and help make trade-offs explicit.
Business Objective / Epic Roadmaps
Portfolio intent, outcomes and milestones.
Shared Initiative Roadmaps
Architecture, DevOps, cyber, compliance, platform and AI.
ART / Solution Train Roadmaps
Capacity, KTLO, constraints and local commitments.
Execution Signals
Blockers, risks, demos, customer feedback and capacity drift.
Problem / Risk Backlog
Flow problems, trade-offs, risks and decision needs.
Sync Decision Log
What changed, who decided and which artifact was updated.
Debrief 5A–5E
Does the execution cadence create fast realignment?
The cadence is useful only if it lets the right people make the right decisions while keeping artifacts trustworthy.
Response time
Which changes must be handled within a day, week, sprint or PI?
Decision power
Who must attend versus who can be on standby and pulled in?
Artifact truth
Which board or roadmap changes during or right after the sync?
Merge quality
Which syncs combine refinement and execution without losing focus?
Meeting load
Where does the cadence create avoidable overhead?
Inspect & adapt
When do we review whether the cadence actually worked?
Output
An execution realignment hypothesis for the next PI.
This is not a meeting calendar forever. It is a realignment hypothesis tested against change rate, decision speed and roadmap reliability.