3A · Vision Statements
Which context inputs and speeches create decision readiness?
Exercise 3
Turn the decision-capable preparation package into a working Value Stream Conference agenda: five blocks, clear outputs, named owners and visible artifact updates.
Exercise 3 overview
The agenda is built block by block. The goal is not a polished conference program, but a runnable working design: selected snippets, rough timeboxes, owners, prepared inputs and expected artifact updates.
Which context inputs and speeches create decision readiness?
How structured or open should the first problem-solving phase be?
How do review, leadership decisions and Planning Adjustment work?
How do we refine the roadmap and organize around value?
How do we close with a draft roadmap and go-refine path?
Every block has an output, every output has an owner, and every unresolved decision has a next sync.
3A · Block 1
Compose the opening that creates decision readiness — not a presentation festival. Pick only the context the room needs before it can make cross-ART trade-offs without rehashing strategy.
| Snippet / speech | Why it matters | Owner | Timebox | Output |
|---|---|---|---|---|
| Market / Executive Context | shared pressure | executive / sponsor | 15–30 min | guardrails |
| Product / Solution Vision | value direction | product / solution lead | 20–30 min | outcomes |
| Architecture / Platform | technical runway | architecture / platform owner | 15–30 min | constraints |
| DevOps / Cyber / Compliance | shared foundations | CoP / function lead | 10–20 min | risks |
| Capacity / Problem Backlog | realism and focus | RTE / roadmap owner | 10–15 min | decision backlog |
| Own snippet | context-specific |
How did customer need, market pressure or competitive pressure change?
Priorities, investment guardrails, outcomes and non-negotiables.
Capabilities, customer value, milestones and product direction.
Target architecture, integration strategy and major enablers.
Evidence chain, safety, audit needs and regulatory commitments.
KTLO, fixed commitments, maintenance and bottlenecks.
3B · Block 2
Design the first divergence phase: structured slots, open market or a hybrid. Each breakout needs a roadmap output: decision, owner, risk, capacity assumption, escalation item or updated roadmap entry.
| Session / room | Problem or trade-off | Who must join | Output | Timebox |
|---|---|---|---|---|
| A | top flow problem | decision makers + experts | decision / roadmap entry | 30–45 min |
| B | supplier / legal / security evidence | affected roles | owner / risk / escalation | 30–45 min |
| C | capacity conflict / architecture trade-off | RTEs / architects / PMs | capacity assumption | 30–45 min |
| Open market | emergent topics | self-organized | captured cards | 30 min |
| Own session |
Top problems get named rooms, owners and a required output.
Participants self-organize around hidden or emergent topics.
Scope versus sequence versus capacity: what should move or stop?
Cross-ART evidence chain, auditability, safety and threat-model needs.
Which work is deferred, split or sequenced when ARTs are overloaded?
Which risks need leadership review or named owners?
3C · Block 3
Converge at the end of Day 1, resolve conflicts, update guardrails, and reopen Day 2 with better assumptions.
| Element | Purpose | Decision rights | Output |
|---|---|---|---|
| Draft Review | system picture | reviewers + roadmap owner | conflicts visible |
| Leadership Review | resolve / escalate | decision makers | guardrails |
| Planning Adjustment | new Day 2 basis | facilitators + leaders | focus backlog |
| Optional votes / ROAM | confidence + risk | room / subgroups | owned risks |
Review business, architecture, DevOps, compliance, capacity and risk layers.
Leadership resolves conflicts the breakouts could not decide.
Resolve, Own, Accept or Mitigate before Day 2 starts.
Vote by area, train, topic or the whole room.
Budget, priority, compliance, supplier or architecture constraints change.
Every unresolved decision gets an owner and next sync.
3D · Block 4
Sharpen the roadmap and test collaboration structures as hypotheses. Organizational design is inspected with the people affected — not finalized by the agenda designer.
| Theme | Roadmap question | Org hypothesis | Validation needed | Output |
|---|---|---|---|---|
| Roadmap refinement | timing, sequence, owners | roadmap owners + ARTs | updated entry | |
| Organize around value | where does value flow break? | new collaboration cut | affected people | operating model hypothesis |
| CoP / platform / sync | which foundation needs ownership? | community or sync pattern | CoP / domain leads | cadence / owner |
| Own theme |
Clarify timing, sequence, owners and unresolved dependencies.
Which collaboration structure would improve value flow?
Move, split, combine or strengthen Solution Areas as a hypothesis.
Architecture, DevOps, Cyber, AI, Compliance or Platform CoPs.
What syncs are decision events, not information meetings?
Who affected by the hypothesis must inspect and adapt it?
3E · Block 5
Close with a credible draft roadmap, risks, confidence and a go-refine path. The output is a draft for refinement — not a finished execution plan.
| Final element | Who participates | Artifact updated | Decision / signal |
|---|---|---|---|
| Final Review | room + roadmap owner | draft roadmap | conflicts visible |
| Business Owner Acceptance | BOs / sponsors | guardrails | accept / adjust |
| ROAM + Confidence | room / subgroups | risk log | confidence level |
| Retrospective | participants + facilitation | refinement backlog | next sync |
Walk through the draft roadmap and major unresolved conflicts.
Confirm whether the draft is directionally useful.
Resolve, Own, Accept, Mitigate — with real owners.
Every unresolved decision has an owner and next sync.
Improve the conference system, not only room logistics.
Define the path to Final Value Stream Sync before PI Planning.
Debrief 3A–3E
A good agenda makes the next decision easier in every block. It creates context, produces decisions and updates artifacts instead of filling time with speeches.
Do participants know enough to make cross-ART trade-offs?
Are sessions driven by real problems, not org-chart habit?
Are conflicts, guardrails and Day 2 topics explicit?
Does roadmap and operating model get refined as hypotheses?
Is the output a draft roadmap with owners, risks and go-refine path?
Output
The agenda is ready when every block has a purpose, a timebox, an owner, a prepared input and a visible artifact update.