Let’s be honest. Most organisations that have adopted SAFe, PRINCE2 and ITIL together didn’t do so as the result of a carefully considered enterprise architecture decision. They did so because a consultant recommended SAFe three years ago, PRINCE2 has been the project standard since before anyone can remember, and ITIL appeared somewhere around the time the service desk needed a framework to justify its headcount.
The result, in many organisations, is a framework soup. Agile Release Trains running PI Planning while PRINCE2 project managers are trying to get a Stage Gate signed off. RTEs wondering whether they need a Business Case or a Feature. Service managers trying to work out where the ART ends and the service desk begins.
If any of that sounds familiar, this blog is for you.
Three Frameworks, Three Jobs
The starting point is understanding that SAFe, PRINCE2 and ITIL are not competing answers to the same question. They are answers to three different questions entirely.
| Framework | The Question It Answers | Its Primary Focus |
| PRINCE2 7 | Are we doing the right projects in the right way? | Project governance, business justification, controlled delivery |
| SAFe 6 | How do we deliver software at scale with agility? | Agile delivery across teams, programmes and portfolios |
| ITIL 5 | How do we run and improve our services reliably? | Service management, operations, continual improvement |
The moment you understand this, the apparent conflict dissolves. PRINCE2 governs whether a digital transformation initiative should exist and whether it’s delivering value. SAFe governs how the software within that initiative gets built. ITIL governs what happens after the software goes live and becomes a service. These are sequential and complementary, not competing.
| The frameworks don’t conflict. The confusion comes from organisations that use them as if they do. |
What Goes Wrong When Nobody Joins the Dots
In the absence of deliberate integration, organisations typically fall into one of three traps.
The Governance Gap
SAFe is excellent at delivery governance: PI Objectives, Feature prioritisation, ART-level metrics. What it doesn’t provide is business-level justification. Who approved the investment? What’s the expected return? What are the strategic objectives this ART is serving? These are PRINCE2 questions, and if nobody is asking them, you can have a beautifully functioning ART delivering the wrong thing with admirable efficiency.
The Handover Cliff
The moment an ART releases a product increment into production, it tends to disappear from the ART’s radar and land, often with a thud, in the service management world. If there’s no ITIL-informed transition process, the operations team receives something they didn’t help design, don’t fully understand, and weren’t resourced to support. The result is incidents, escalations, and a service desk drowning in tickets that are really disguised design defects.
The Three-Framework Tax
The opposite problem: organisations so keen to do all three properly that they impose the full overhead of all three simultaneously on every initiative. Every feature needs a Business Case. Every sprint review doubles as a Change Advisory Board. Every ART Sync requires an ITIL Problem Management representative. The result is paralysis dressed up as governance.
What Good Looks Like
Organisations that integrate these frameworks well tend to do three things consistently.
- They define clear handover points, where PRINCE2 governance hands to SAFe delivery, and where SAFe delivery hands to ITIL operations. These transitions are explicit, not assumed.
- They right-size the overhead, not every initiative needs a full PRINCE2 Business Case. A proportionality principle, already embedded in PRINCE2 7, allows governance to match the scale and risk of the work.
- They train people across frameworks, the RTE who understands what a Stage Gate is, and the Project Manager who understands what a PI is, are worth their weight in gold in organisations running all three.
| You don’t need to choose between governance and agility. You need to decide who owns each, and where one ends and the other begins. |
The Question Worth Asking in Your Organisation
Before your next framework adoption, integration project, or PMO restructure, ask these three questions:
- When a new digital initiative is proposed, who is responsible for the business justification and investment decision, and which framework governs that process?
- When software is being built, who is responsible for delivery governance across teams, and which framework gives them the tools to do that?
- When software becomes a live service, who is responsible for its ongoing reliability, change management and improvement, and which framework governs that?
If you can answer all three clearly, and if the people in each role understand how their work connects to the others, you’re in better shape than most organisations running all three frameworks. If the answers are unclear or overlap significantly, you’ve found your integration problem.
The good news is that PRINCE2, SAFe and ITIL were not designed to conflict. With deliberate integration, they form a genuinely coherent operating model for digital delivery at scale. The subsequent blogs in this series go deeper, mapping specific roles, practices and ceremonies across the three frameworks for practitioners who need to work across them daily.
To find out more about PDCA Consulting’s expert consulting services or coaching either:
- Call +49 172 579 4719
- Complete the contact form
- Contact via LinkedIn
Next in this series: Part 2: You’ve Got an ART. Now Who’s Governing the Business Case? A guide for SAFe practitioners navigating PRINCE2 and ITIL.
About the author: This blog series is produced by a PRINCE2 7 Master and ITIL 5 Master practitioner working in the DACH region, specialising in governance, service management, and agile transformation.
