ITIL and other frameworks

The exam likes to offer a choice: ITIL or DevOps, ITIL or PRINCE2. In this domain that either/or framing is the trap, because the answer is almost always that the two work together. The mental model that dodges it is simple: ITIL is the constant that runs and continually improves a live product or service, and each partner framework does a different job that ITIL leaves open, so the useful question is never which one wins but what does each one own and where do the two meet. DevOps, a culture and set of practices that unites software development ('Dev') with IT operations ('Ops'), brings speed; PRINCE2 (PRojects IN Controlled Environments), a structured project management method, brings governed delivery of a temporary change. ITIL Version 5 is deliberately designed to work alongside frameworks and methods like these rather than replace them, letting an organization combine each one's strengths (ITIL Version 5 Foundation: What's New guide).

Two subtopics take the domain in order, one partner framework each. ITIL and DevOps covers the fast, collaborative delivery culture: DevOps relies on continuous integration and continuous delivery or deployment (CI/CD) and automation, and it meets ITIL inside the eight-activity ITIL Product and Service Lifecycle (discover, design, acquire, build, transition, operate, deliver, support, used iteratively rather than in a fixed order), where DevOps accelerates the build, transition and deliver activities while ITIL keeps the flow governed, and both share continual improvement (ITIL Product and Service Lifecycle model). ITIL and PRINCE2 covers governed change: a project is a temporary, time-bound effort that delivers a defined change, PRINCE2 governs that project through defined stages, defined roles and continued business justification, and once the project delivers, ITIL operates, supports and improves the result as an ongoing service. Reach for the first subtopic when a stem is about speed, CI/CD, automation or Dev-and-Ops collaboration; reach for the second when it is about projects, why project management matters, or delivering a defined change into live operation.

One instinct wins most questions here: prefer the option where ITIL and the other framework combine, and be wary of any answer where one replaces or rules out the other. The same instinct sorts the roles. When the need is a temporary, controlled effort to deliver a defined change, the project framework (PRINCE2) fits; when the need is to run, support and continually improve a product or service over time, ITIL fits; and when the need is a fast, automated flow of delivery, DevOps fits inside ITIL's governance. So when several options look workable, pick the one that keeps the frameworks complementary and matches each framework to the job it owns.