1C · Identify initiatives
Which stream-wide initiatives exist or are needed?
Exercise 2B
Value Stream Initiative Contributions
Identify which stream-wide initiatives must be represented, what roadmaps they bring, and who prepares the shared foundation inputs before the Value Stream Conference.
Chapter 2 · Getting able to decide
Where Exercise 2B fits.
Exercise 2 turns the evidence base from Exercise 1 into a contribution-based invite and preparation system. Exercise 2B focuses on the shared foundations that must be represented before the Value Stream Conference can make credible decisions.
1E · Flow problem backlog
Which flow problems must the conference solve?
2A · Portfolio inputs
Which strategic intent, funding and guardrails are needed?
2B · Initiative inputs
Which foundation roadmaps, communities and owners are needed?
2C · Tactical inputs
Which ART, team and department capacity makes the draft realistic?
Exercise output
A Value Stream Initiative contribution map: initiative, community status, roadmap status, responsible invitee, preparation network and readiness gaps.
Core concept
What is a Value Stream Initiative?
A Value Stream Initiative is a shared foundation that must be harmonized across the stream so the stream can deliver value reliably. It creates or maintains a shared capability, standard, platform, evidence chain, operating model or technical direction.
Not just another feature
It is work that creates or maintains a shared capability, standard, platform, evidence chain, operating model or technical direction.
Not automatically a CoP
A Community of Practice can own the initiative, but a preparation network may be enough when no formal CoP exists.
Not the roadmap yet
Exercise 2B identifies who brings or creates the initiative roadmap. The roadmap itself is prepared after the exercise.
Typical examples
Architecture, platform, DevOps, infrastructure, cyber, compliance, toolchain, AI/data, transformation, release and operations.
Why this matters
Stream-wide initiatives are often the invisible coordination load.
Many flow problems are not solved by one ART working harder. They need shared standards, shared foundations and shared ownership.
They shape feasibility
Business objectives become realistic only if architecture, platform, compliance, DevOps, data and supplier foundations keep up.
They create hidden dependencies
A roadmap without shared foundations often becomes an optimistic list of objectives with late surprises.
They need owners
If nobody owns the stream-wide standard, nobody can prepare the trade-off decision for the conference.
They need representation
Not every expert should attend, but every relevant initiative needs a person who can speak for its roadmap and constraints.
They need a decision gap
Each selected initiative should bring the decision gap that the conference room can actually close.
Readiness logic
Four states for each Value Stream Initiative.
Decide whether the initiative is already ready for the conference or needs preparation first. For every initiative marked A, B or C, name who prepares the roadmap, who represents it in the conference and which decision gap the conference should close.
A · CoP exists on Value Stream level
Use the CoP. Ask it to prepare or update the roadmap and name the conference representative.
B · Only local CoPs exist
Connect the local CoPs across ARTs, departments and suppliers. Create one shared stream view.
C · No CoP, but initiative is needed
Create a temporary preparation network and name a roadmap owner or initiative owner.
D · No initiative needed now
Do not create ceremony. Park it as not relevant for this conference and revisit later if needed.
Participation model
Invitees are not the whole preparation network.
A Value Stream Conference has limited room. Many experts prepare the input; fewer people represent it in the conference.
Conference invitee
Represents the initiative, explains the roadmap, can make or escalate decisions, and updates the artifact during the conference.
Preparation network
Architects, engineers, SMEs, lead developers, supplier experts, compliance people and local CoP members build the roadmap before the event.
Keep the room small enough
Do not invite every architect, tester or domain expert. Invite people who can represent prepared input and pull in standby expertise when needed.
Keep preparation broad enough
The representative must not invent the roadmap alone. The roadmap should be the voice of the people who understand the initiative.
Roadmap input stack
Each initiative should bring a minimum viable roadmap.
The Value Stream Conference integrates roadmaps. It should not become the first place where the roadmap is invented.
Portfolio inputs
Objectives, epics and guardrails.
Value Stream Initiative roadmaps
Architecture, DevOps, cyber, AI, platform and other shared foundations.
Tactical inputs
Capacity, constraints and risks.
Draft VS Roadmap
Aligned direction that can be refined after the conference.
Decision gaps
Trade-offs, sequencing, capacity, ownership or escalation needs.
| Element | Question it answers | Good-enough input for the conference |
|---|---|---|
| Scope | Which part of the Value Stream is affected? | Affected ARTs, departments, suppliers, teams or functions. |
| Direction | What standard or capability are we building? | Target state, main milestones and known constraints. |
| Decision gap | What must the room decide? | Trade-off, sequencing, capacity, ownership or escalation need. |
| Owner | Who can update the roadmap? | Named representative and preparation network. |
Snippet cards
Pick the initiatives that affect flow, standards or shared foundations.
Selection rule: choose initiatives because they affect one of your top flow problems or business objectives — not because the list looks complete.
Core initiatives
- Architecture
- Platform / Product Platform
- DevOps / CI-CD
- Infrastructure / Cloud
- Cybersecurity
- Compliance / Safety
- Toolchain / ALM
- AI / Data
- Release / Operations
Additional candidates
- UX / Customer Journey
- Observability / Telemetry
- Quality System
- Data Governance
- Supplier Integration
- Systems Engineering
- Risk Management
- Training / Enablement
People and ownership
- Value Stream CoP Lead
- Initiative Owner
- Roadmap Owner
- Domain / Function Lead
- ART / Solution Train Reps
- Local CoP Representatives
- Supplier / Partner Expert
- Standby Expert
Preparation artifacts
- Initiative Roadmap
- Standards / Guardrails
- Decision Gap List
- Dependency Map
- Evidence / Compliance Chain
- Service Model
- Adoption Plan
- Readiness Checklist
Checklist · Step 1
Which Value Stream Initiatives do we have or need?
Use this as a fast multiple-choice inventory. Need means the initiative should exist or be harmonized for this Value Stream. Unsure becomes follow-up research before invitations are finalized.
| Initiative | Have | Need | No | Unsure | Notes / scope |
|---|---|---|---|---|---|
| Architecture / target architecture | □ | □ | □ | □ | |
| Platform / shared product platform | □ | □ | □ | □ | |
| DevOps / CI-CD | □ | □ | □ | □ | |
| Infrastructure / cloud / environments | □ | □ | □ | □ | |
| Cybersecurity | □ | □ | □ | □ | |
| Compliance / safety | □ | □ | □ | □ | |
| Toolchain / ALM / traceability | □ | □ | □ | □ | |
| AI / data / analytics | □ | □ | □ | □ | |
| Transformation / org design | □ | □ | □ | □ | |
| Release / operations / support | □ | □ | □ | □ | |
| Own initiative | □ | □ | □ | □ |
Checklist · Step 2
Do we have a community or preparation network?
For every initiative marked Have, Need or Unsure, check how it is currently organized. Use existing CoPs when they exist; otherwise create the smallest preparation network able to build a shared roadmap input.
| Initiative | VS CoP exists | Local CoPs only | No CoP · prep group needed | No formal group needed | Owner known? |
|---|---|---|---|---|---|
| Architecture | □ | □ | □ | □ | □ |
| Platform | □ | □ | □ | □ | □ |
| DevOps / Infrastructure | □ | □ | □ | □ | □ |
| Cybersecurity | □ | □ | □ | □ | □ |
| Compliance / Safety | □ | □ | □ | □ | □ |
| Toolchain / ALM | □ | □ | □ | □ | □ |
| AI / Data | □ | □ | □ | □ | □ |
| Transformation / Org Design | □ | □ | □ | □ | □ |
| Release / Operations | □ | □ | □ | □ | □ |
| Own initiative | □ | □ | □ | □ | □ |
Checklist · Step 3
Does the initiative have a roadmap good enough for the conference?
The roadmap does not need to be perfect. It must be good enough to support trade-off decisions. If there is no roadmap, create a preparation backlog item — not a conference agenda item yet.
| Initiative | Ready | Draft | Missing | Update needed | Decision gap / missing input |
|---|---|---|---|---|---|
| Architecture / platform | ○ | ○ | ○ | ○ | |
| DevOps / infrastructure | ○ | ○ | ○ | ○ | |
| Cyber / compliance / safety | ○ | ○ | ○ | ○ | |
| Toolchain / ALM | ○ | ○ | ○ | ○ | |
| AI / data | ○ | ○ | ○ | ○ | |
| Transformation / org design | ○ | ○ | ○ | ○ | |
| Release / operations | ○ | ○ | ○ | ○ | |
| Quality / test / V&V | ○ | ○ | ○ | ○ | |
| Supplier integration | ○ | ○ | ○ | ○ | |
| Own initiative | ○ | ○ | ○ | ○ |
Checklist · Step 4
Who attends, who prepares, who stays on standby?
Use participation modes to avoid inviting everyone while still keeping the decision loop short. Core invitees represent roadmaps and decisions; preparation-only people shape the input; standby people shorten the loop.
| Initiative | Core invitee | Block only | Standby | Prep only | Named role / person |
|---|---|---|---|---|---|
| Architecture | □ | □ | □ | □ | |
| Platform | □ | □ | □ | □ | |
| DevOps / Infrastructure | □ | □ | □ | □ | |
| Cybersecurity | □ | □ | □ | □ | |
| Compliance / Safety | □ | □ | □ | □ | |
| Toolchain / ALM | □ | □ | □ | □ | |
| AI / Data | □ | □ | □ | □ | |
| Transformation / Org Design | □ | □ | □ | □ | |
| Release / Operations | □ | □ | □ | □ | |
| Own initiative | □ | □ | □ | □ |
Exercise 2B Canvas
Value Stream Initiative contribution board.
Capture every initiative that needs to be represented or prepared for the Value Stream Conference. The output is a set of initiatives that must be represented in the conference package — plus the exact preparation gaps that need follow-up.
| Initiative | Affected units | Community status | Roadmap status | Invitee / owner | Decision gap |
|---|---|---|---|---|---|
| Architecture / Platform | |||||
| DevOps / Infrastructure | |||||
| Cybersecurity | |||||
| Compliance / Safety | |||||
| Toolchain / ALM | |||||
| AI / Data | |||||
| Transformation / Org Design | |||||
| Own initiative |
Exercise 2B Canvas
Roadmap preparation network canvas.
Use this when the roadmap does not yet exist or only exists inside local communities. The core question: who must help build the roadmap, even if they will not attend the conference?
| Initiative | Preparation network | Roadmap owner | Artifacts to prepare | Due / trigger | Risk if missing |
|---|---|---|---|---|---|
| Architecture | local CoPs · architects · lead devs | roadmap · standards · interfaces | late architecture decisions | ||
| DevOps | DevOps · infra · quality · release | pipeline roadmap · gates | integration and deployment delays | ||
| Cyber / Compliance | security · compliance · safety · suppliers | evidence chain · risk view | audit / safety surprises | ||
| AI / Data | data · AI · legal · platform · ART reps | data platform · governance | blocked AI adoption | ||
| Transformation | LACE · org design · coaches · HR | operating model changes | local change conflicts | ||
| Own |
Exercise 2B Canvas
Initiative readiness backlog.
Turn missing CoPs, missing roadmaps and unclear owners into concrete preparation work. If the initiative is relevant but not ready, create a preparation item rather than pretending the conference can decide it.
| Readiness gap | Initiative | Owner | Next action | Needed before | Status |
|---|---|---|---|---|---|
| No roadmap | draft minimum viable roadmap | Missing / Draft / Ready | |||
| No representative | name invitee or block owner | Missing / Draft / Ready | |||
| Local CoPs not connected | create prep network | Missing / Draft / Ready | |||
| Decision gap unclear | write decision question | Missing / Draft / Ready | |||
| Affected scope unclear | map ARTs / functions / suppliers | Missing / Draft / Ready | |||
| Standby path missing | reserve expert decision window | Missing / Draft / Ready | |||
| Own gap | Missing / Draft / Ready |
Example walkthrough
Architecture initiative: from local expertise to conference input.
Use the same pattern for platform, cyber, DevOps, compliance, AI/data or any other Value Stream Initiative.
Local architecture CoPs
ART A · ART B · supplier · department
Prep network
Connect people and align assumptions
Architecture roadmap
Target state · standards · gaps
Conference rep
Decision gaps · live updates
What the conference decides
Sequencing, standards and trade-offs
Fast version
15-minute invite-and-prep hypothesis.
Use this when the group has little time and only needs a first invite-and-prep hypothesis.
Pick initiatives
Use the checklist. Mark Have / Need / No / Unsure.
Check community status
VS CoP, local CoPs, no CoP, prep group or not relevant.
Check roadmap readiness
Ready, draft, missing or update needed.
Select invitee mode
Core, block only, standby, prep only.
Record readiness gaps
Owner, roadmap, scope, decision gap, standby path.
Skip rule
If a roadmap or CoP question cannot be answered quickly, park it as a readiness gap and assign a follow-up owner.
Debrief 2B
Are the Value Stream Initiatives conference-ready?
Close the exercise by checking whether every selected initiative can contribute a decision-ready input.
Relevance
Which initiatives are truly needed for the current top flow problems and objectives?
Community
Do we have a Value Stream CoP, only local CoPs, or no community yet?
Roadmap
Does a roadmap exist, or must we create a minimum viable roadmap first?
People
Who represents the initiative, and who prepares the input beforehand?
Decision gap
What exactly should the conference be able to decide or clarify?
Readiness
Which gaps must be closed before invitations and pre-briefs go out?
Handoff
From Value Stream Initiatives to Tactical Units.
Exercise 2B makes shared foundations visible. Exercise 2C checks what the execution units can realistically absorb: capacity, constraints and tactical contribution to the selected initiatives.