The IT Value Chain and the Four IT4IT Value Streams
Domain 2 tests the IT Value Chain and the scope of each IT4IT value stream. The IT Value Chain expresses the end-to-end work of IT as Plan, Build, Deliver, and Run, with S2P supporting Plan, R2D supporting Build, R2F supporting Deliver, and D2C supporting Run. The value chain is a model for organizing work around value, not a sequence that must finish before the next begins.
Core rules
- S2P: strategy, demand, investment, service portfolio, and roadmap; decides what should exist and why.
- R2D: requirements, design, build, test, release, and deployment; turns intent into a production service.
- R2F: catalog, request, approval, and fulfillment; gives consumers what they are entitled to.
- D2C: event, incident, problem, knowledge, and restoration; detects and corrects service degradation.
- Each stream has entry and exit criteria, stages, functional components, and data objects.
Worked example
An employee requests a standard laptop from the service catalog. This is R2F because the outcome is fulfillment of an entitled request. If the laptop fails, the event and incident are D2C. If the company decides to offer a new managed laptop tier, that is S2P, then R2D. The reasoning: classify by the value outcome and trigger, not by the team's name.
Traps
Do not put every service desk ticket in R2F; incidents and problems belong in D2C. Do not confuse release in R2D with deployment or fulfillment. Do not reduce S2P to budgeting. Do not treat R2F as only catalog publishing; fulfillment and request governance matter.