ITIL 5 Foundation · Domain 7 of 7

ITIL 5 Foundation Domain 7: ITIL and other frameworks

The smallest category, shared with ITIL and AI: why ITIL is used alongside DevOps and PRINCE2, and how each framework covers a different part of managing products and services across their lifecycle.

Exam weight estimate
2.5%
Official syllabus topics estimate
2
Estimated questions estimate
~1 of 40
Suggested study time estimate
1–2 hrs

About 11 min read Reviewed October 2026

Overview

This category explains how ITIL fits with two other widely used approaches. The DevOps topic asks you to explain how ITIL and DevOps can be used together and how they complement each other in lifecycle management. The PRINCE2 topic asks you to explain why project management matters to product and service management and how ITIL and PRINCE2 complement each other across the lifecycle.

ITIL 4 Foundation did not test other frameworks. Version 5 adds this category because PeopleCert now positions ITIL, PRINCE2 and DevOps-style practice as parts of one landscape. The core message is complementarity rather than competition: DevOps speeds the flow of change from build through deployment with automation and shared ownership, PRINCE2 governs time-bound projects that create or change products and services, and ITIL manages the whole lifecycle and the value system around them. Version 5's value chain terms, such as continuous deployment and site reliability engineering, give the vocabulary for this discussion.

How it's tested

Expect a single explain-level question with four statements about how ITIL relates to DevOps or PRINCE2. The correct statement describes the frameworks as complementary and places each one's strength correctly within the lifecycle; the wrong ones exaggerate overlap or replacement.

  • Complement or replace?

    Statements claim one framework replaces another, and you choose the one describing combined use.

  • Where does each fit?

    You match DevOps, PRINCE2 or ITIL to the part of the lifecycle where its guidance is strongest.

  • Why project management?

    Options explain why project management matters, and you pick the one about controlled delivery of change to products and services.

Reasoning it through

A stem asks which statement best describes ITIL and PRINCE2 used together. An option saying PRINCE2 manages live services after go-live sounds thorough but is wrong: PRINCE2 governs a temporary project. The correct choice says PRINCE2 manages the project that creates or changes a product or service, while ITIL manages that product or service across its whole lifecycle, including operation and continual improvement.

Syllabus topics 2

Official syllabus topics from the PeopleCert outline, in outline order.

7.1 ITIL and DevOpsUsing ITIL and DevOps together and how they complement each other across the lifecycle.
What it means
DevOps is a culture and set of practices that brings development and operations together to deliver change quickly and reliably, using automation such as continuous integration, delivery and deployment. ITIL provides the broader management system: the value system, practices, governance and the full lifecycle from discover to support. Used together, DevOps speeds the flow of change while ITIL ensures it fits value, risk and service needs.
What to understand
DevOps is strongest in build, transition and operate, where automation and shared ownership shorten lead times. ITIL adds discover, design, deliver and support, plus practices such as change enablement, incident management and service level management that keep fast change safe and visible. Version 5 treats them as complementary: ITIL change enablement can authorise standard pipeline changes automatically rather than slowing DevOps teams down.
How it shows up
A statement question on how DevOps and ITIL work together across the lifecycle.
Common confusion
Believing DevOps removes the need for change enablement; ITIL supports automated, low-risk change authorisation.
7.2 ITIL and PRINCE2Why project management matters, and how ITIL and PRINCE2 complement each other across the lifecycle.
What it means
Project management matters because many changes to products and services are large, uncertain and time-bound, so they need controlled planning, governance and justification. PRINCE2 provides that control for the project that creates or changes a product or service.
What to understand
PRINCE2 governs a temporary organization delivering specific outputs under a business case, then hands them over. ITIL manages the product or service before, during and after the project: discovering the need, transitioning the outputs into live use, operating, delivering and supporting them, and improving them continually. Together they cover both the one-off change and the ongoing lifecycle, which is why Version 5 calls them complementary.
How it shows up
A statement asking which describes the relationship between the frameworks, or why project management is needed.
Common confusion
Thinking PRINCE2 continues after handover to run the live service; that is ITIL's domain.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • DevOps

    A culture and practice set joining development and operations for fast, reliable change.

    Remember
    Relies heavily on automation pipelines.
    Tested as
    Statement questions on combined use.
    Trap
    Treating it as a replacement for service management.
  • Complementary use

    Each framework covers a different need; together they cover the lifecycle.

    Remember
    The right answer rarely says replace.
    Tested as
    Most likely correct theme in this category.
    Trap
    Picking an option that ranks one framework above the other.
  • DevOps strengths

    Build, transition and operate through automation and shared ownership.

    Remember
    Continuous integration and deployment are DevOps techniques.
    Tested as
    Matching strengths to lifecycle activities.
    Trap
    Assigning discover or support as DevOps' main focus.
  • ITIL strengths

    The value system, practices, governance and the full lifecycle.

    Remember
    Covers what happens before and after delivery pipelines.
    Tested as
    Matching strengths to lifecycle areas.
    Trap
    Describing ITIL as only an operations framework.
  • Change enablement with DevOps

    Standard, low-risk pipeline changes can be pre-authorised.

    Remember
    Control and speed can coexist.
    Tested as
    Statements about change control in DevOps.
    Trap
    Choosing an option that removes change control.
  • PRINCE2

    A project management method for temporary organizations delivering products under a business case.

    Remember
    Ends at project closure and handover.
    Tested as
    Statement questions on combined use.
    Trap
    Assuming it manages live operations.
  • Why project management matters

    Large, uncertain, time-bound changes need controlled planning and justification.

    Remember
    Projects are one way change enters the lifecycle.
    Tested as
    Explain-level question on importance.
    Trap
    Choosing an option claiming every change needs a project.
  • Handover point

    Project outputs move into transition and live use under ITIL management.

    Remember
    The seam between PRINCE2 and ITIL.
    Tested as
    Scenario statements about who manages what after go-live.
    Trap
    Placing post-handover support inside the project.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Where each framework is strongest

ConceptMeaningKey differenceCommon trap
ITIL Value system and full product and service lifecycle Covers the whole life from discover to support Thinking it ignores fast delivery
DevOps Fast, automated flow of change Strongest in build, transition and operate Thinking it covers governance and value
PRINCE2 Controlled delivery of a time-bound project Ends at handover Thinking it manages live services

Typical overstatements to reject

ConceptMeaningKey differenceCommon trap
DevOps replaces ITIL Claims automation makes service management unnecessary Ignores value, governance and support Choosing it because DevOps sounds modern
PRINCE2 replaces ITIL Claims project control covers the whole lifecycle Ignores operation and continual improvement Choosing it because both use governance language
ITIL replaces both Claims ITIL already contains project and DevOps methods Ignores their specialised guidance Choosing it out of loyalty to the exam topic

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Replacement claim

    What candidates pick
    DevOps makes ITIL unnecessary for modern teams.
    Why it looks right
    Many articles frame them as rivals.
    Why it's wrong
    Version 5 presents them as complementary; DevOps speeds change, ITIL manages value, risk and the full lifecycle.

    Clue to watch for Options with replace, no longer needed or instead of.

  2. No change control

    What candidates pick
    DevOps teams skip change enablement entirely.
    Why it looks right
    Pipelines deploy automatically.
    Why it's wrong
    Change enablement still applies; low-risk standard changes can be pre-authorised so automation and control coexist.

    Clue to watch for The stem mentions automated deployment and risk together.

  3. PRINCE2 runs the service

    What candidates pick
    PRINCE2 continues to manage the service after go-live.
    Why it looks right
    The project built it, so it seems natural to keep running it.
    Why it's wrong
    A PRINCE2 project is temporary and closes at handover; ITIL then manages operation, delivery, support and improvement.

    Clue to watch for Words such as after go-live, ongoing or live service.

  4. Every change is a project

    What candidates pick
    All changes to services should be run as PRINCE2 projects.
    Why it looks right
    Project control sounds safe.
    Why it's wrong
    Many changes are small and handled within normal practices; projects suit large, uncertain, time-bound change.

    Clue to watch for The stem describes a routine or minor change.

  5. ITIL is operations only

    What candidates pick
    ITIL covers just the operate and support part of the lifecycle.
    Why it looks right
    ITIL's history centres on service operation.
    Why it's wrong
    Version 5 covers the whole lifecycle from discover to support within the value system.

    Clue to watch for Statements limiting ITIL's scope.

Answer framework

Use this filter on the single other-frameworks question you are likely to see.

  1. Identify which framework pairing the stem is about, ITIL with DevOps or ITIL with PRINCE2, and recall each one's core purpose.
  2. Strike any option that says one framework replaces, removes or makes another unnecessary, since Version 5 stresses complementary use.
  3. Place each framework in the lifecycle: DevOps strongest in build, transition and operate; PRINCE2 within a time-bound project ending at handover; ITIL across the whole lifecycle.
  4. Check that the remaining option keeps governance and control in place, for example change enablement alongside automation.
  5. Choose the statement that describes combined use with each framework doing what it does best, rather than one claiming a single framework does everything.

Practice question

An organization uses PRINCE2 to run a twelve-month project that replaces its customer billing platform. Which statement best describes how ITIL relates to this project?

Choose one answer

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

Treat this as a one-hour topic. Draw the eight lifecycle activities in a line and shade where each framework is strongest: DevOps over build, transition and operate; a PRINCE2 project as a bar that starts after discover and ends at handover; and ITIL as a band covering everything. That one picture answers most questions in this category.

Then write two sentences for each pairing that explain why they complement each other, using concrete examples such as pre-authorised pipeline changes or a project handing a new platform to service teams. Read a few practice statements and practise rejecting overstatements quickly; words like replace, eliminate and only are reliable warning signs.

If you already hold a PRINCE2 or DevOps certification, focus on the Version 5 framing rather than your existing knowledge, because the exam tests ITIL's view of the relationship. Leave this category until after the larger ones are secure, then revisit it briefly in your final review.

FAQ

How much of the exam is ITIL and other frameworks?

ITIL and other frameworks carries 2.5% of the Version 5 exam, so expect about one of 40 questions. PeopleCert publishes the weighting; the count is an editorial estimate.

Which frameworks are covered?

Only DevOps and PRINCE2. The syllabus has one topic for each and asks you to explain how they work with ITIL and complement it across the lifecycle.

Do I need to know PRINCE2 principles or processes?

No. You need to understand why project management matters and how a project relates to the ITIL lifecycle, not the PRINCE2 method itself.

Does DevOps conflict with ITIL change enablement?

Version 5 treats them as compatible. Change enablement can pre-authorise low-risk, automated changes so DevOps teams keep their speed while risk stays controlled.

Was this in ITIL 4 Foundation?

No. Comparing ITIL with other frameworks is new to the Version 5 Foundation syllabus, reflecting PeopleCert's positioning of ITIL, PRINCE2 and DevOps together.

What is the most common wrong answer?

Statements claiming one framework replaces another. The syllabus language is about combined and complementary use, so replacement claims are usually distractors.

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 7 knowledge

Check that you can place DevOps and PRINCE2 correctly in the lifecycle and reject statements that one framework replaces another.

Keep going