Value Streams and Processes for Project Management
This domain tests how project work contributes to value streams and where it sits in the ITIL service value chain. You must distinguish a value stream from a process and trace a project from mandate to benefit.
Value stream versus process
A value stream is the end-to-end series of steps that creates value for a consumer; a process is a repeatable set of activities inside a practice. The project management practice contributes to value streams such as 'concept to live service' or 'opportunity to portfolio decision'; it is not itself the value stream.
Position in the service value chain
- Plan: strategy, portfolio decisions, mandates, business case approval.
- Engage: stakeholders, requirements, communication.
- Obtain/build: creating or acquiring the products.
- Design and transition: readiness, acceptance, release planning.
- Deliver and support: handover and early-life support.
- Improve: lessons, benefit reviews, corrective action.
Internal process flow
Initiation → planning → execution → monitoring and control → closure, with gates authorizing progression. The flow is iterative: feedback from a gate or from execution returns to planning, and monitoring and control runs continuously.
Worked example
For a new HR service, plan authorizes the project and funds it, engage captures requirements from HR and staff representatives, obtain/build builds the service, design and transition confirms support readiness and acceptance, deliver and support goes live, and improve captures lessons. A gate sits between each transition, and the post-implementation review feeds the next iteration.
Traps
Equating a value stream with a process; drawing a single linear waterfall and ignoring feedback loops; omitting engage; forgetting that project management also appears in improvement-driven value streams, not only in build work.