Overview
This category introduces the ITIL Product and Service Lifecycle and the purpose of each of its eight activities: discover, design, acquire, build, transition, operate, deliver and support. The syllabus has two topics. The first asks you to list the activities, explain how value chain activities enable the lifecycle, and explain that the activities are neither sequential nor linear. The second asks for the purpose of each activity.
For ITIL 4 holders this is the biggest change in the Foundation content. ITIL 4 used a service value chain of six activities: plan, improve, engage, design and transition, obtain/build, and deliver and support. Version 5 separates design from transition, splits obtain/build into acquire and build, and divides deliver and support into operate, deliver and support. Planning and improvement are handled elsewhere in the value system, through governance and the continual improvement model, rather than as lifecycle activities.
How it's tested
Expect recall and understanding questions. Some ask which activity has a stated purpose, some list four activities and ask which is not part of the lifecycle, and some test the idea that activities are iterative and can be combined in different orders within value streams.
-
Purpose match
A short purpose statement is given and you choose the activity, often between close pairs like acquire and build or operate and deliver.
-
Not in the lifecycle
Four terms are listed and you spot the one that comes from the ITIL 4 value chain, such as engage or plan.
-
Sequence statements
Statements about the lifecycle are offered and you choose the true one: activities are iterative, not a fixed linear order.
A question asks which activity ensures components are obtained from internal or external sources ready for assembly. Build is tempting because it sounds like making things, but build is about creating, configuring and integrating components. Securing the components from a supplier or another team is acquire. Engage and obtain/build would also appear, but both are ITIL 4 value chain terms and not among the eight activities.
Syllabus topics 2
Official syllabus topics from the PeopleCert outline, in outline order.
3.1 Introduction to the ITIL Product and Service LifecycleThe eight lifecycle activities, how value chain activities enable the lifecycle, and its non-linear use.
- What it means
- The lifecycle describes everything that happens to a product and its services, from spotting an opportunity to supporting users in live use. Its eight activities are discover, design, acquire, build, transition, operate, deliver and support. The syllabus says value chain activities enable this lifecycle, and Version 5 material presents the same eight names as the activities of the ITIL value chain.
- What to understand
- Two ideas carry the marks. First, the activities are not a sequence: work can loop back from support to discover, run several activities in parallel, or repeat activities for each product version. Second, the lifecycle sits inside the value system, so planning, governance and improvement still happen; they simply are not lifecycle activities. Be able to describe how the Version 5 list relates to the six ITIL 4 value chain activities.
- How it shows up
- A true or false style statement about order, or recall of the eight names.
- Common confusion
- Believing transition must always follow build; activities can repeat or overlap depending on the value stream.
3.2 Purpose of lifecycle activitiesThe purpose of discover, design, acquire, build, transition, operate, deliver and support.
- What it means
- Discover explores opportunities, needs and desired outcomes. Design shapes how the product and services will work and how users will experience them. Acquire secures the resources and components needed, from inside or outside the organization. Build creates, configures, integrates and tests components. Transition moves new or changed products and services into controlled use.
- What to understand
- Operate keeps technology and components running so they are available, secure and performing. Deliver makes the product and services available to consumers with the intended experience. Support helps users with issues and requests and feeds what is learned back into earlier activities. The three closest pairs are acquire and build, transition and deliver, and operate and support, so practise separating them by the question each one answers.
- How it shows up
- A purpose statement is matched to one activity, usually choosing between two neighbours.
- Common confusion
- Mixing operate, which keeps technology running, with deliver, which is about consumers receiving the product and service.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Eight lifecycle activities
Discover, design, acquire, build, transition, operate, deliver, support.
- Remember
- Exactly eight; engage, plan and improve are not among them.
- Tested as
- List and odd-one-out questions.
- Trap
- Including engage from the ITIL 4 value chain.
-
Non-linear use
Activities can repeat, overlap and run in different orders.
- Remember
- The syllabus states they are not sequential or linear.
- Tested as
- True statement questions about how the lifecycle works.
- Trap
- Selecting a statement that the activities must be completed in order.
-
Discover
Exploring opportunities, needs and desired outcomes.
- Remember
- Comes before design but can be revisited at any time.
- Tested as
- Purpose statements about understanding demand or user needs.
- Trap
- Confusing it with engage from ITIL 4.
-
Acquire vs build
Acquire obtains components; build creates and integrates them.
- Remember
- ITIL 4 merged both into obtain/build.
- Tested as
- Close-pair purpose questions.
- Trap
- Choosing build when the stem says sourced from a supplier.
-
Transition
Moving new or changed products and services into controlled use.
- Remember
- Now separate from design.
- Tested as
- Purpose statements about controlled introduction to live use.
- Trap
- Treating it as part of design as in ITIL 4.
-
Operate
Keeping technology and components running and secure.
- Remember
- New in Version 5 as a named activity.
- Tested as
- Purpose statements about availability and technical management.
- Trap
- Merging it with deliver or support.
-
Deliver vs support
Deliver makes the solution available to consumers; support helps users and resolves their issues.
- Remember
- ITIL 4 grouped these as deliver and support.
- Tested as
- Purpose statements about user help versus consumer access.
- Trap
- Picking deliver for incident handling.
-
Value chain enables lifecycle
Value chain activities make the lifecycle happen in practice.
- Remember
- Version 5 materials use the same eight names for the value chain.
- Tested as
- Explain-level questions on the relationship between the models.
- Trap
- Assuming the ITIL 4 six-activity chain still applies.
-
Plan and improve in Version 5
Not lifecycle activities; covered by governance and the continual improvement model.
- Remember
- They still matter, just elsewhere in the value system.
- Tested as
- Odd-one-out questions often include them.
- Trap
- Concluding that Version 5 dropped planning altogether.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
ITIL 4 value chain vs Version 5 lifecycle
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Plan, improve | ITIL 4 value chain activities | Version 5 handles them through governance and continual improvement | Listing them as lifecycle activities |
| Engage | ITIL 4 activity for stakeholder interaction | Version 5 spreads it across discover, deliver and support | Expecting it in the list of eight |
| Design and transition | One ITIL 4 activity | Version 5 separates design and transition | Treating them as a single activity |
| Obtain/build | One ITIL 4 activity | Split into acquire and build | Using the merged ITIL 4 name |
| Deliver and support | One ITIL 4 activity | Split into operate, deliver and support | Forgetting operate exists |
Close activity pairs
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Acquire | Securing components and resources | About obtaining | Choosing it for configuration work |
| Build | Creating, configuring, integrating and testing | About making | Choosing it for supplier purchasing |
| Operate | Running technology reliably | Faces the technology | Choosing it for consumer access |
| Deliver | Making the solution available to consumers | Faces the consumer | Choosing it for keeping servers running |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Engage in the list
- What candidates pick
- Engage as one of the lifecycle activities.
- Why it looks right
- It was a core ITIL 4 value chain activity.
- Why it's wrong
- Engage is not among the eight; its concerns are spread across discover, deliver and support in Version 5.
Clue to watch for The stem names the Product and Service Lifecycle.
-
Linear lifecycle
- What candidates pick
- A statement that activities run from discover to support in order.
- Why it looks right
- The list is usually presented in that order.
- Why it's wrong
- The syllabus states explicitly that the activities are not sequential or linear and can be used iteratively.
Clue to watch for Words like must, always or only after.
-
Build for sourcing
- What candidates pick
- Build for obtaining components from a supplier.
- Why it looks right
- In ITIL 4 obtain and build were one activity.
- Why it's wrong
- Obtaining components is acquire; build creates, configures and integrates them.
Clue to watch for Verbs such as procure, source or obtain.
-
Deliver for running servers
- What candidates pick
- Deliver for keeping technology available and secure.
- Why it looks right
- Delivery sounds operational.
- Why it's wrong
- Keeping technology running is operate; deliver concerns making the solution available to consumers.
Clue to watch for Focus on infrastructure versus focus on consumers.
-
Design includes transition
- What candidates pick
- Design for moving a change into live use.
- Why it looks right
- ITIL 4 combined design and transition.
- Why it's wrong
- Version 5 lists transition separately as the activity that brings new or changed solutions into controlled use.
Clue to watch for Phrases such as go-live, controlled use or release into production.
Answer framework
Use this approach when a stem describes work and asks which lifecycle activity it belongs to.
- Strike any option that is not one of the eight Version 5 activities, such as engage, plan, improve or obtain/build.
- Identify the object of the work: needs and opportunities, a design, components, a working solution, live technology, consumers or users with issues.
- Map that object to the activity whose purpose matches it, checking the close pairs of acquire and build, operate and deliver, and deliver and support.
- If the stem is a statement about the lifecycle as a whole, prefer options saying activities are iterative and combined flexibly into value streams.
- When two activities still seem to fit, choose the one whose purpose names the result described rather than the one sharing an everyday word with the stem.
Practice question
Want more like this? The ITIL 5 Foundation practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start by memorising the eight activities with a mnemonic built from their first letters, then write a one-line purpose for each in your own words. Check those lines against the Version 5 book so the key verbs match: explore, shape, secure, create, move into use, run, make available and help.
If you studied ITIL 4, build the mapping table from the comparison above and say it aloud a few times. Knowing exactly where the old six activities went is the best defence against distractors that use ITIL 4 names. Then practise with close pairs: write three short scenarios each for acquire versus build, operate versus deliver, and deliver versus support, and label them.
Finally, link the lifecycle to value streams. Pick one product you know, such as a mobile app, and trace a new feature from discover to support, noting where activities repeat. This makes the non-linear point concrete and prepares you for the value stream category.
FAQ
What share of the exam is The ITIL Product and Service Lifecycle?
The ITIL Product and Service Lifecycle category is weighted at 10%, about four of 40 questions. PeopleCert publishes the percentage; the count is our planning estimate.
Is the lifecycle the same as the ITIL 4 service value chain?
No. ITIL 4 had six value chain activities. Version 5 uses eight lifecycle activities, splitting several ITIL 4 activities and moving planning and improvement to other parts of the value system.
Do I need to know the order of the activities?
Learn the usual order for recall, but remember the key exam point: the activities are not sequential and can be repeated or combined in any order a value stream needs.
Which activity is completely new?
Operate is the clearest addition. ITIL 4 grouped running technology inside deliver and support, while Version 5 names operate separately.
Where did engage go?
Version 5 does not list engage as a lifecycle activity. Interaction with stakeholders runs through discover, deliver and support, and through service relationship management.
Are lifecycle activities linked to practices?
Yes. Management practices contribute to lifecycle activities, and the value system category tests how practices support the value chain.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 3 knowledge
Check that you can state the purpose of all eight activities and avoid ITIL 4 distractors like engage and obtain/build under time pressure.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the ITIL 5 Foundation AI tutor Get any concept explained your way