Strategic Value Streams Foundation Exam Syllabus

The Foundation exam assesses knowledge and understanding of the Strategic Value Streams body of knowledge. Candidates are expected to define core concepts, explain why value streams matter to competitive advantage, and distinguish value streams from adjacent structures such as projects, programmes and portfolios.

Exam format

  • 68 single-answer multiple choice questions, drawn evenly from the 17 syllabus topics (4 questions per topic)
  • 60 minutes
  • Pass mark 60%
  • Questions assess recall and comprehension of the body of knowledge


Section A. The strategic problem

1. Competitive Advantage and Organisational Viscosity

Why advantage is relative and external, and how the internal property of viscosity determines whether an organisation can act on its strategy.

  • Define competitive advantage as relative performance judged by those making choices between alternatives
  • Explain why internal efficiency, market leadership or short term success do not guarantee advantage
  • Describe maintained competitive advantage and the forces that erode it, including knowledge diffusion and shortening response cycles
  • Define organisational viscosity as an internal organisational property that resists movement
  • Identify factors that increase viscosity, such as overlapping governance authority, and factors that reduce it
  • Explain why viscosity determines organisational speed and responsiveness


2. Why Organisations Need Value Streams

The structural problems of functional organisation that value streams exist to address.

  • Explain why customer value emerges from integration across functions rather than from any single function
  • Describe fragmented accountability and its effect on decision making
  • Explain the utilisation trap and the cost of local optimisation to end to end flow
  • Distinguish projects as temporary structures from value streams as enduring ones
  • Describe strategic drift and structural inertia
  • Explain how value streams create line of sight between daily work and enterprise value


3. Value Streams as the Lowest Viscosity Structural Form

How organising around flow rather than utilisation reduces structural resistance.

  • Explain the structural purpose of a value stream in delivering defined customer outcomes end to end
  • Distinguish flow efficiency from resource utilisation and describe what happens when utilisation is maximised
  • Recognise the lean origins of value stream thinking and the principle of defining value from the customer perspective
  • Describe how work in progress limits and smaller batch sizes improve speed and predictability
  • Identify flow based measures such as cycle time, lead time and throughput
  • Describe the end to end accountability held by a value stream leader


4. Strategy, Planning and Execution

What strategy is, how it differs from planning and execution, and why the gap between strategy and work is structural.

  • Describe strategy as explicit organisational choices, including decisions about what not to do
  • Distinguish strategy from planning and from execution
  • Explain strategic congestion and the consequences of failing to make explicit choices
  • Explain why the gap between strategy and work is a structural problem rather than a communication failure
  • Describe why value must be deliberately designed to flow rather than assumed
  • Explain why value streams must follow strategy rather than precede it


Section B. Defining value streams

5. Value Stream Definition

The defining characteristics of a value stream and how it differs from neighbouring concepts.

  • Define a value stream as perpetual, end to end, flow based and accountable for a defined value outcome
  • Explain what perpetual and end to end mean in practice
  • Distinguish a value stream from a project, a programme, a portfolio, and a product or service
  • Explain what distinguishes a value stream from a simple process diagram, including accountability, governance and performance measures
  • Describe why boundary clarity and a defined stakeholder group matter
  • Explain how strategy gives value streams direction and coherence


6. Value Streams in the Enterprise Context

How value streams sit within the wider enterprise alongside portfolios, shared services and governance.

  • Explain how value stream boundaries are defined by customer value outcomes rather than reporting lines
  • Describe clear ownership and its effect on flow and decision clarity
  • Explain how value streams relate to portfolio management as the structure through which prioritised work flows
  • Describe how shared services support multiple streams through defined service agreements
  • Explain what a value stream operating model clarifies, including governance, decision rights and funding logic
  • Describe how demand management balances flow and capacity


Section C. Making the transition

7. Moving from Projects to Value Streams

Why organisations default to project delivery and what rebalancing toward value streams involves.

  • Explain why funding and governance systems keep organisations anchored to projects
  • Describe the structural costs of project based delivery, including knowledge loss and fragmented accountability at closure
  • Identify categories of work that remain legitimately temporary, such as regulatory mandates with defined completion
  • Explain the risks of retaining legacy stage gates and unchanged funding logic during transition
  • Describe the strengths and limits of programme and product centric stepping stones
  • State the objective of rebalancing, making value streams the dominant form for ongoing delivery


8. From Agile Practices to Value Stream Thinking

Why team level agility alone does not produce enterprise flow.

  • Describe the focus and artifacts of team level agile practice
  • Explain the risk of local optimisation when teams operate without strategic alignment
  • Describe how value streams connect strategy to team backlogs
  • Explain why dependency visibility and cadence alignment matter across teams
  • Identify lead time from concept to impact as the system level measure
  • Distinguish the accountabilities of agile leads from those of value stream leaders


Section D. Operating value streams

9. The Value Stream Operating Model

The components that translate structural intent into disciplined practice.

  • Identify the five core components, structural definition, governance architecture, decision rights allocation, cadence design and funding logic
  • Describe governance as sustained stewardship of alignment and flow health rather than episodic approval
  • Explain how predefined escalation criteria preserve coherence
  • Describe cadence as the rhythm of planning, delivery and review
  • Explain why funding logic must recognise streams as perpetual vehicles for value delivery
  • Describe hybrid funding models used during transition


10. Roles, Responsibilities and Decision Rights

The human architecture of a value stream.

  • Describe the accountabilities of the Value Stream Owner, Flow Leader, Risk Lead and architectural stewardship roles
  • Explain why accountability is expressed in outcomes achieved rather than activity performed
  • Explain why decision rights align with accountability and sit at the lowest capable level
  • Describe when escalation is appropriate, when trade offs exceed a role mandate
  • Explain the purpose of RACI style accountability mapping
  • Recognise frequent routine escalation as a sign of ambiguous decision rights


11. Demand, Flow and Capacity Management

Regulating what enters the stream and keeping work moving.

  • Explain the purpose of demand management, ensuring only strategically aligned work enters the system
  • Distinguish operational demand from change demand
  • Describe structured intake and the decisions of acceptance, deferral and rejection
  • Describe capacity as more than headcount, including skills, systems, decision bandwidth and vendor dependencies
  • Explain how high utilisation produces queues and reduces adaptability
  • Describe the aim of balancing demand and capacity, equilibrium between stability and adaptation


12. Measuring Value and Performance

The measurement disciplines that keep strategic intent visible and actionable.

  • Distinguish outcome measures, flow measures and health measures and give examples of each
  • Distinguish leading from lagging indicators and explain how flow measures give early warning
  • Explain why outcome measures should be few in number
  • Identify measurement traps, including noise, metric proliferation, proxy confusion and short termism
  • Explain measurement as a learning and diagnostic mechanism within governance
  • Describe why measurement is only meaningful through the lens of strategic intent


Section E. Sustaining and adapting

13. Risk, Issues and Change in Value Streams

Managing uncertainty as a permanent condition of long lived systems.

  • Describe risk in a perpetual value stream as a structural condition rather than an episodic event
  • Distinguish a risk from an issue
  • Explain disciplined escalation criteria, including impact, likelihood, regulatory exposure and cross stream dependency
  • Describe the principle of subsidiarity in decisions about change
  • Explain the role of risk logs, issue registers and change registers in building systemic memory
  • State the principle that safety precedes speed when change affects compliance or integrity


14. Funding Value Streams and Interventions

Financial models that sustain continuity while enabling strategic redirection.

  • Explain why funding shapes what is prioritised and sustained
  • Describe capacity based, outcome based and portfolio aligned funding models
  • Explain financial guardrails and investment principles as boundaries for autonomy
  • Distinguish baseline stream funding from intervention funding
  • Describe how strategic criticality and stream maturity shape investment
  • Describe the shift of finance partners toward strategic advisory support


15. Interventions Within Value Streams

Time-bounded, outcome-oriented adjustments made inside an enduring stream.

  • Define an intervention and distinguish it from a traditional project
  • Identify triggers for intervention, including sustained misalignment and credible opportunity or threat
  • Describe structured sensing through dashboards and governance forums
  • Identify the elements of an intervention: charter, trigger, intent, scope, success criteria and accountable lead
  • Explain why accountability remains with the value stream owner throughout
  • Describe disciplined closure and the conditions for pausing or stopping an intervention


16. Large Cross Value Stream Interventions

Coordinating change that spans shared assets and multiple streams.

  • Describe what distinguishes cross stream interventions, systemic reach across shared assets and interfaces
  • Identify common drivers, including regulation, strategic repositioning, shared architectural transformation and capability harmonisation
  • Describe dual layer ownership, an executive sponsor for enterprise intent, with stream owners integrating change
  • Explain the roles of enterprise architects and portfolio-level oversight
  • Describe sequencing by architectural coupling and operational criticality
  • Explain why coordinating layers are time bound and why accountability reverts to the streams


17. Enterprise Architecture and Organisational Constraints

How enabling constraints make decentralised speed safe.

  • Explain how architecture determines what forms of autonomy are safe
  • Describe standards and guardrails as enabling constraints that operate through design rather than case-by-case approval
  • Describe shared platforms as the structural substrate for multiple streams and the responsibilities of platform owners
  • Explain how constraints are calibrated, tighter where failure propagates, and lighter where differentiation is sought
  • Describe why architectural decisions are co-created with value stream leadership
  • Explain how architecture translates strategy into structural capability