Complementary Frameworks
No framework works alone
ITIL v5 focuses on digital product and service management. Organizations must combine it with complementary frameworks addressing different concerns like project management, software development, and enterprise architecture.
Official ITIL v5 guidance: ITIL + PRINCE2 + DevOps
The official book identifies three frameworks with complementary roles:
| Framework | Primary Concern | Covers |
|---|---|---|
| ITIL v5 | Product and service management (ongoing operations) | Managing digital products and services throughout lifecycle |
| PRINCE2 | Project management (temporary endeavours) | Delivering discrete projects that create or change products and services |
| DevOps | Engineering culture and practices (velocity and collaboration) | Building, deploying, and operating software rapidly and reliably |
How they fit together
ITIL manages the ongoing lifecycle. PRINCE2 manages the projects that create changes within that lifecycle. DevOps provides the engineering practices that make both faster and more reliable.
Where they overlap and complement
Activities flow through all three frameworks at different stages -- from strategy and discovery through design, build, transition, operation, support, and continual improvement. Each framework contributes specific expertise at different points.
Extended integrations
ITIL + Agile / SAFe
Agile methodologies and Scaled Agile Framework complement ITIL in organizations using iterative delivery:
- Sprint planning aligns with product backlog concepts
- Increment delivery moves through ITIL's Transition activity
- PI (Program Increment) planning maps to value stream mapping
- Retrospectives implement ITIL's Continual Improvement practice
- Definition of Done includes operational readiness criteria
ITIL + COBIT
COBIT (Control Objectives for Information and Related Technology) addresses governance where ITIL addresses management practices:
| Dimension | ITIL v5 | COBIT 2019 |
|---|---|---|
| Focus | Management practices (how to do the work) | Governance objectives (what must be achieved) |
| Scope | Digital product and service management | Enterprise governance of information and technology |
| Audience | IT practitioners and managers | Board, audit committee, CIO |
| Compliance | Supports ISO 20000, ISO 27001 | Supports SOX, regulatory governance |
Integration pattern: Use COBIT to define governance objectives and ITIL to define how to achieve them through management practices.
ITIL + TOGAF
TOGAF (The Open Group Architecture Framework) provides enterprise architecture methodology that complements ITIL:
- Architecture vision feeds into ITIL's Discover activity
- Business architecture defines processes that ITIL services support
- Technology architecture defines infrastructure ITIL operates
- Architecture change management aligns with Change Enablement
- Architecture repository feeds into Service Configuration Management
- Architecture governance complements ITIL governance patterns
ITIL + Lean / Six Sigma
Lean and Six Sigma complement ITIL's continual improvement capability:
| Concept | Source | ITIL v5 Application |
|---|---|---|
| Value stream mapping | Lean | Core ITIL v5 concept: map work flow from demand to value delivery |
| Waste elimination (Muda) | Lean | Apply to ITIL processes to eliminate handoffs, waiting, over-processing |
| DMAIC | Six Sigma | Structured improvement for ordered-context problems with measurable defects |
| Kaizen | Lean | Aligns with ITIL's Continual Improvement principle and model |
| Kanban | Lean | Visual management of workflow; applicable to incident, change, request queues |
Choosing the right combination
| Organization Type | Recommended Framework Combination |
|---|---|
| Enterprise IT | ITIL + COBIT + PRINCE2 + TOGAF |
| Digital product company | ITIL + Agile/SAFe + DevOps |
| Regulated industry | ITIL + COBIT + ISO standards |
| Managed service provider | ITIL + DevOps + Lean |
| Government/public sector | ITIL + PRINCE2 + COBIT |
| Startup/scale-up | ITIL (selective) + DevOps + Agile |
Anti-patterns in framework integration
| Anti-pattern | Problem | Solution |
|---|---|---|
| "Framework collecting" | Adopting every framework simultaneously creates complexity and confusion | Choose the minimum set needed for your context |
| "Siloed frameworks" | ITIL, Agile, and DevOps teams operate independently | Create integrated practices drawing from all frameworks |
| "Framework wars" | Teams argue about which framework is "right" | Frameworks are complementary tools, not competing religions |
| "Certification-driven adoption" | Choosing a framework because staff already have certificates | Choose based on organizational need, then invest in training |
Related pages
- DevOps & SRE Integration (detailed DevOps integration)
- Decision Framework (adoption approach decisions)
- ISO Alignment (ISO 20000 and 27001 integration)
- Operating Model Design (team topology for multi-framework environments)
Last updated on April 2, 2026
ITIL® is a registered trademark of PeopleCert. © 2026 ITIL v5 Compass