Dynamic Agility Conferences
Introduces the conference logic behind Dynamic Agility: decision capability, alignment formats and the operating rhythm around higher-level coordination.
Open deck in BoxValue Stream Conference Workshop
A minimalist working map for decision-capable conferences: from ART landscape and shared objectives to refinement cadence, PI Planning readiness and fast execution realignment.
Intro Material
Two source decks shape the workshop narrative: one introduces the Dynamic Agility conference logic, the other frames roadmapping as a living decision and refinement system.
Introduces the conference logic behind Dynamic Agility: decision capability, alignment formats and the operating rhythm around higher-level coordination.
Open deck in BoxFrames roadmaps as living artifacts: business intent, shared foundations, capacity, risks and execution signals become visible for real trade-off decisions.
Open deck in BoxInvite people because a decision needs them — not because the org chart looks complete.
A conference creates a draft. Tactical feedback makes it PI-Planning-ready.
Syncs are useful when they change decisions, artifacts or response speed.
Exercise 01
Create the evidence base for a Value Stream Conference: ARTs, objectives, shared work, capacity and the problems the conference must actually solve.
Identify the Agile Release Trains and adjacent units that need one shared coordination level.
Capture local and shared objectives, then identify which outcomes create real Value Stream coordination demand.
Identify shared standards, foundations, communities and roadmap inputs that need Value Stream-level coordination.
Make executing capacity, useful bucket classes, historical data sources and rough capacity splits visible.
Turn symptoms into a prioritized backlog of flow problems the Value Stream Conference must be able to discuss, decide on and remove.
Exercise 02
Design the invitation and preparation system by contribution source: portfolio, shared initiatives, ARTs, central functions, suppliers and facilitation.
Decide which portfolio people and inputs make the Value Stream Conference decision-capable.
Identify which stream-wide initiatives must be represented, what roadmaps they bring, and who prepares shared foundation inputs.
Decide which ARTs, Solution Trains, Solution Areas, Agile Teams and non-agile execution units must represent capacity, feasibility and constraints.
Identify central functions that must be represented, prepared or available so the Value Stream Conference can make real decisions.
Decide which suppliers, partners and external firms must contribute roadmaps, capacity, lead times, contracts, interfaces and decision rights.
Design the facilitation roles, readiness checks, runbook, rooms, boards and follow-up system that make the Value Stream Conference runnable.
Exercise 03
Turn the preparation package into a focused two-day conference agenda that creates a credible draft roadmap and a go-refine path.
Compose the opening that creates decision readiness without becoming a presentation festival.
Design the first divergence phase: structured problem-solving, open market or a hybrid.
Review the draft, resolve conflicts, update guardrails and prepare the second day.
Refine roadmap gaps and test operating-model hypotheses around value.
Close with a draft roadmap, confidence signals, risks, owners and the refinement handoff.
Exercise 04
Place higher-level conferences, syncs and feedback loops on the PI timeline so ART PI Planning can make real commitments.
Decide whether strategic decisions need a portfolio event or a smaller decision slot.
Define how portfolio intent becomes a value-stream draft roadmap.
Align transformation initiatives such as architecture, DevOps, AI, toolchain, operations and agile transformation.
Compare ART capacity, overloads, support options, maintenance synergies and fixed commitments.
Prepare cross-ART alignment and plan-ready inputs before ART PI Planning.
Define recurring update loops that harden draft roadmaps before PI Planning.
Check timing, decision rights, artifact flow, feedback loops and readiness for ART commitments.
Exercise 05
After PI Planning, design the sync system that keeps execution adaptive without duplicating the refinement cadence.
Decide when strategic surprises, funding changes or major risks need portfolio-level realignment.
Inspect end-to-end flow, blockers, shared initiatives and roadmap drift during execution.
Choose combined or role-specific syncs for cross-ART realignment.
Connect lower-level execution signals upward and decisions back down into ART and team work.
Separate what must be separate, then merge refinement and execution syncs where they share people, purpose and artifacts.
Dynamic Agility
This is not a meeting calendar forever. It is a realignment hypothesis that should be tested against decision quality, response time and roadmap reliability.
Workshop anfragen