The ITIL Product and Service Lifecycle

Every product and service an organization runs, from a brand-new idea through to a system about to be retired, is managed through the same eight activities. That single set is the ITIL Product and Service Lifecycle: the whole-life model of how one common set of activities applies to every product and service. The eight are discover, design, acquire, build, transition, operate, deliver, and support. Digital products and digital services are treated as two views of the same technology-based solution, so they share this one lifecycle and are managed together as an ecosystem rather than in separate silos. Hold that as your model: one set of eight activities, revisited across a whole life, not a pipeline run once. The trap the exam sets is that these are the identical eight activities the Version 5 value chain uses, so a stem will offer the value chain, a value stream, or the continual improvement model as if it were the lifecycle. Keep the lens straight: the lifecycle is the whole-life view of the eight activities, while the value chain is the operating model that arranges those same eight into value streams to meet demand.

Read the two subtopics in order and the second builds on the first. Introduction to the Product and Service Lifecycle is the map: it names the eight activities, establishes that they are not sequential nor linear but iterative, so an organization moves backwards and forwards between them and different versions of one product can sit in several activities at once, and it separates the lifecycle from the value chain, a value stream, the continual improvement model, and the five sequential ITIL v3 stages it replaces. Purpose and Scope of the Lifecycle Activities then gives each activity its job, held in three groups by what each does to a product or service: four that bring it into being (discover, design, acquire, build), one that moves it into live use (transition), and three that keep it valuable once live (operate, deliver, support). Reach for the first subtopic to recognise the model and name the eight; reach for the second to match a described situation to the single activity that owns it.

These questions reward one instinct: fix the boundary between neighbouring activities, and default to the Version 5 eight-activity model. Ask what the situation does to the product or service. While it is being brought into being, discover understands the need and design specifies the solution, while acquire obtains the components and build assembles and tests them. Crossing into live use is transition, the one-time deployment and final quality gate, not build, which only makes a change ready, and not deliver, which is ongoing. Once the service is live, operate keeps it running, deliver routes its value to users, and support handles issues and requests rather than deploying anything. When an answer offers ITIL v3's five stages, or an ITIL 4 six-activity service value chain, as the lifecycle activities, it is describing a superseded model, so choose the eight-activity Version 5 answer.