The Practitioner exam assesses the ability to apply the Strategic Value Streams body of knowledge in realistic organisational situations. Where the Foundation exam tests knowledge and understanding, the Practitioner exam presents scenarios and requires candidates to diagnose structural problems, evaluate competing courses of action, and judge the reasoning behind assertions about value streams. It builds directly on the Foundation syllabus and covers the same 17 topics at a higher cognitive level.

Exam format

• 102 questions per sitting, drawn evenly across the 17 syllabus topics (6 questions per topic)
• A mix of single-answer multiple-choice and select-two multiple-response questions in every topic
• Select-two questions are scored all or nothing, both correct selections are required to earn the mark
• 90 minutes
• Pass mark 60%
• Questions are scenario-based and include assertion and reason items, assessing application, analysis and evaluation

Section A. The strategic problem

1. Competitive Advantage and Organisational Viscosity

Diagnosing why organisations with sound strategies and busy teams still lose ground to faster rivals.

• Diagnose organisational viscosity from scenario evidence such as tightened controls that slow delivery further
• Analyse cases where efficiency gains fail to produce advantage because performance is judged relative to alternatives
• Judge whether a scenario shows advantage being created, renewed or eroded
• Identify the structural factors that explain why organisations facing identical conditions respond at different speeds
• Evaluate assertion and reason pairs about viscosity, movement and strategic direction
• Assess the strategic risk in assuming historical dominance will persist

2. Why Organisations Need Value Streams

Analysing the structural failure modes of functional organisation in live situations.

• Diagnose the structural issue when strategy is widely understood yet daily work remains unchanged
• Predict the likely outcome when a bold vision is announced, but business units continue pursuing their own priorities
• Evaluate the consequences of planning decisions that consistently override strategic positioning choices
• Recognise scenarios that most clearly demonstrate the gap between strategy and work
• Assess which organisational conditions best support sustained value delivery in service of strategy
• Explain why value streams must be shaped by strategy rather than implemented uniformly

3. Value Streams as the Lowest Viscosity Structural Form

Applying flow thinking to utilisation, queues and structural redesign decisions.

• Analyse scenarios where full allocation coexists with long lead times and identify the systemic cause
• Recommend the structural redesign that most directly reduces delay in a given situation
• Evaluate why lean practices applied inside functional silos deliver limited results
• Judge leadership choices between maximising specialist utilisation and reducing lead time
• Interpret what a shift from utilisation dashboards to lead time and throughput dashboards signals
• Apply work in progress limits and prioritisation as responses to long waiting times

4. Strategy, Planning and Execution

Diagnosing structural causes when strategy fails to become delivered change.

• Diagnose the structural weakness when transformation programmes multiply while coordination costs rise and decision rights blur
• Analyse circular blame patterns across functions as evidence of fragmented decision rights
• Evaluate the risk when a new strategy is announced but funding, reporting lines and approvals remain unchanged
• Interpret situations where staff cannot connect their metrics to enterprise outcomes
• Assess why execution delays worsen despite undiminished employee effort
• Construct the structural argument for value streams when challenged that project teams already deliver change

Section B. Defining value streams

5. Value Stream Definition

Applying the defining characteristics to classify real structures correctly.

• Apply the defining characteristics to determine whether a given structure is a value stream
• Identify which defining element is absent in a scenario, such as outcome accountability behind a detailed process map
• Evaluate the consequences of renaming a programme as a value stream without changing funding or accountability
• Analyse what remains stable when products launch and retire within an enduring stream
• Determine the consequences when no structure retains accountability after an initiative closes
• Distinguish the responsibilities of streams, programmes and portfolios in scenarios where they interact

6. Value Streams in the Enterprise Context

Evaluating how value streams succeed or fail inside a wider enterprise system.

• Diagnose why value stream benefits fail to materialise when annual project funding cycles are retained
• Evaluate the consequences of granting stream autonomy without architectural guardrails
• Recommend adjustments when incentives such as utilisation rewards contradict flow objectives
• Analyse friction between streams and shared functions such as procurement or platform teams
• Challenge overreach claims, such as value streams replacing portfolio management or defining competitive positioning
• Interpret oscillation between silo behaviour and horizontal collaboration during integration

Section C. Making the transition

7. Moving from Projects to Value Streams

Analysing the forces that keep delivery project-shaped and judging transition choices.

• Diagnose the structural force at work when every improvement must be framed as a temporary initiative to secure funding
• Analyse the accumulating effects of team dissolution and knowledge dispersal at project closure
• Evaluate the risk of emphasising milestone closure over sustained capability health
• Judge which work legitimately remains temporary and which should be absorbed into stream capacity
• Assess the consequences of adding flow metrics while retaining legacy stage gates
• Interpret funding and recognition changes as signals of structural and cultural transition

8. From Agile Practices to Value Stream Thinking

Interpreting system-level evidence that team agility is not producing enterprise flow.

• Interpret scenarios where team cycle times fall but end-to-end lead time does not improve
• Diagnose the structural issue when dependent teams run on misaligned cadences
• Analyse the risks of many backlogs operating without an overarching connection to strategy
• Recommend coordination mechanisms when teams face repeated external interruption
• Correct the claim that iteration itself is the objective of agile transformation
• Assign the accountabilities of agile leads and value stream leaders correctly in scenario situations

Section D. Operating value streams

9. The Value Stream Operating Model

Diagnosing operating model gaps from the behaviour they produce.

• Diagnose the missing operating model component from symptoms such as joint prioritisation conflicts or constant minor escalation
• Evaluate the consequences of abolishing planning cadence in pursuit of agility
• Assess the governance questions raised by capacity envelope funding
• Apply explicit decision matrices to separate local from enterprise decisions
• Analyse the risks of escalation cultures dependent on personal influence and informal networks
• Judge the maturity of a stream from how it measures success over time

10. Roles, Responsibilities and Decision Rights

Applying the role model to conflicts, gaps and boundary violations.

• Assign accountability correctly when outcomes are missed despite milestones being met
• Evaluate decisions that bypass role boundaries, such as approving regulatory exposure without risk consultation
• Diagnose the accountability breakdown behind accumulating technical debt or unresolved dependency friction
• Judge situations where documented decision rights are ignored in favour of informal hierarchy
• Select the appropriate mechanism for resolving trade-offs between speed and structural integrity
• Interpret frequent routine escalation as evidence of ambiguous decision rights

11. Demand, Flow and Capacity Management

Diagnosing flow pathologies and choosing disciplined responses.

• Diagnose flow problems from evidence such as stable demand with volatile lead times or rising work in progress with slipping dates
• Recommend responses to constraint bottlenecks, focusing capacity at the constraint rather than expanding everywhere
• Evaluate the fragility created by removing all slack in pursuit of full utilisation
• Judge design choices for volatile or bursty demand, including buffers, flexible capacity and demand shaping
• Analyse the effect of increased variety on capacity and backlog behaviour
• Evaluate assertion and reason pairs on constraints, variability, slack and work in progress

12. Measuring Value and Performance

Interpreting conflicting signals and avoiding measurement traps under pressure.

• Interpret conflicting signals, such as rising revenue alongside growing queues and declining engagement
• Classify measures as outcome, flow or health and as leading or lagging within a given scenario
• Identify measurement traps in context, including proxy confusion, metric proliferation and reacting to noise
• Judge governance responses, distinguishing a one-week dip from a sustained systemic trend
• Evaluate deliberate short-term performance sacrifices, such as architectural refactoring
• Assess the governance effect of using measurement for blame rather than learning

Section E. Sustaining and adapting

13. Risk, Issues and Change in Value Streams

Applying risk and change discipline to long lived systems under pressure.

• Diagnose governance imbalance when trivial risks reach executives while material risks stay unresolved at team level
• Analyse slow accumulation patterns, including architectural deviations and repeatedly deferred remediation
• Apply escalation criteria and subsidiarity to decide where a change should be absorbed or escalated
• Evaluate what recurring recorded issues over many months indicate about the system
• Judge responses to incidents that address recovery speed but ignore structural root causes
• Assess scope drift when gradual additions expand a stream beyond its strategic boundary without review

14. Funding Value Streams and Interventions

Evaluating how funding models shape behaviour and applying financial guardrails.

• Analyse the behavioural effects of quarterly business case funding on team continuity and knowledge
• Diagnose the pattern created when routine evolutionary work requires repeated initiative approval
• Evaluate the risks of outcome based funding when external volatility masks internal performance
• Apply guardrail and envelope logic to judge when reallocation needs approval and when it does not
• Assess how strategic criticality and stream maturity should shape investment decisions
• Interpret executive financial summaries that balance baseline spend, intervention investment and risk exposure

15. Interventions Within Value Streams

Judging when, how and whether to intervene in an enduring stream.

• Judge whether scenario evidence justifies intervention, distinguishing sustained shifts from temporary fluctuations
• Evaluate anticipatory intervention against waiting for visible erosion
• Apply charter discipline, ensuring trigger, intent, scope, success criteria and an accountable lead are defined
• Maintain the accountability boundary; the value stream owner remains accountable throughout
• Judge pause and stop decisions under systemic overload or when expected benefits become unattainable
• Assess disciplined closure, integrating new practices into routine operation and rebalancing capacity

16. Large Cross Value Stream Interventions

Coordinating enterprise-scale change without abandoning stream accountability.

• Classify a proposed change as local or cross-stream by its systemic reach and impact on shared assets
• Apply dual layer ownership, an executive sponsor for enterprise intent, with stream owners integrating change
• Sequence interventions using architectural coupling and operational criticality
• Arbitrate resource disputes between streams on the basis of enterprise value
• Evaluate the danger of coordination layers persisting after change is embedded
• Judge recalibration decisions when conditions shift mid-intervention

17. Enterprise Architecture and Organisational Constraints

Calibrating constraints so decentralised speed remains safe.

• Evaluate autonomy decisions such as replacing a shared platform with a local build, weighing speed against systemic integrity
• Diagnose the architectural discipline that was missing when inconsistent data definitions require costly reconciliation
• Calibrate constraints to risk, tighter where failure propagates across streams, lighter where differentiation is sought
• Assess platform owner accountability for reliability, roadmaps and anticipating demand from multiple streams
• Distinguish enabling constraints from control mechanisms and diagnose when architecture has ossified into oversight
• Align architectural posture with strategic intent, adaptable foundations for experimentation, standardisation for regulatory robustness