SkarpChapter 19 of 20
ITIL and Other Frameworks: Positioning ITIL in the Modern Ecosystem
See how ITIL fits alongside agile, DevOps, and other frameworks so you can reason about integration questions instead of memorizing buzzwords.
Positioning ITIL in Today’s Framework Jungle
Why This Module Matters
Modern IT organizations rarely use ITIL alone. You also see agile, DevOps, Lean, COBIT, ISO standards, and more. The exam expects you to explain how ITIL fits with these, not to memorize every detail.
High-Level Positions
- ITIL: service management and value co-creation
- Agile: iterative, customer-focused product development
- DevOps: bridges development and operations
- Lean: eliminates waste and improves flow
- Governance/standards: rules, controls, and requirements
ITIL as Integrator
ITIL (Version 5) offers a flexible, value-focused service value system that gives a common language and end-to-end view. It is meant to work with agile, DevOps, and Lean, not replace them.
What You Will Be Able To Do
You will map ITIL to agile/DevOps/Lean, explain how ITIL supports governance and compliance, and reason about integration scenarios like those you will see on the ITIL Foundation (Version 5) exam.
Recap: ITIL’s Core Pieces You’ll Be Integrating
Service and Value Co-Creation
Service: enables outcomes customers want, without them managing specific costs and risks. Value co-creation: joint activities by provider and consumer to create value.
Service Value System
The SVS is how all organizational components and activities work together as a system to enable value creation: guiding principles, governance, value chain, practices, continual improvement.
Service Value Chain Activities
The six activities, in order: plan, improve, engage, design and transition, obtain/build, deliver and support. These form the backbone where other frameworks plug in.
Continual Improvement
Continual improvement is a recurring activity at all levels to keep performance meeting stakeholders’ expectations. Agile and DevOps often strengthen this in practice.
ITIL and Agile: Mindset, Cadence, and Where They Meet
What Agile Focuses On
Agile delivers value in small, frequent increments. It uses short cycles, close customer collaboration, and the ability to respond quickly to change as you learn.
ITIL Is Not a Project Method
ITIL (Version 5) does not replace Scrum or Kanban. It gives service management structure around agile teams, especially once their products become live services.
Guiding Principles vs Agile Values
ITIL’s focus on value, progress iteratively with feedback, and collaborate and promote visibility align directly with agile’s customer focus, sprints, retros, and transparent boards.
Where Agile Fits in the Value Chain
Agile teams mainly contribute to design and transition and obtain/build, while also influencing engage and deliver and support through close work with customers and operations.
Example: Agile Product Team Inside an ITIL Service Value System
Scenario Overview
A university runs a Student Portal service. A Scrum team builds features, while the IT department uses ITIL (Version 5) to manage the service end-to-end.
Plan and Engage
Plan aligns the portal roadmap with university strategy. Engage workshops with students and staff feed needs into the Scrum product backlog.
Build and Change
Design and transition plus obtain/build happen through two-week sprints. Changes use ITIL change enablement: lightweight for low risk, formal for high risk.
Support and Improve
Deliver and support uses ITIL incident and problem management. Sprint retrospectives feed a continual improvement register reviewed by the service manager.
ITIL and DevOps: Flow, Feedback, and Reliability
What DevOps Brings
DevOps blends development and operations to deliver software faster and more reliably using CI/CD, automation, and shared responsibility for reliability.
DevOps in the Value Chain
DevOps shows up in obtain/build (pipelines, testing), design and transition (deployments), deliver and support (on-call, monitoring), and improve (metrics and learning).
Modern Change Enablement
ITIL change enablement classifies changes: standard (pre-approved), normal (risk-assessed), emergency (fast-tracked). This supports automated DevOps flows instead of blocking them.
Combined Benefits
DevOps provides speed and automation; ITIL provides governance and alignment with business value. The exam expects you to integrate them, not choose one.
ITIL and Lean: Waste, Flow, and Value Streams
Lean in a Nutshell
Lean defines value from the customer’s view, maps value streams, removes waste, creates flow and pull, and pursues perfection through continuous improvement.
Lean and ITIL Value Streams
The ITIL service value chain is a high-level value stream. The exam domain on value stream identification, mapping, and management strongly echoes Lean value stream mapping.
Principles That Align
ITIL’s keep it simple and practical and optimize and automate support Lean’s focus on reducing waste and improving flow across the service value system.
Using Both Together
Lean tools diagnose waste and bottlenecks; ITIL structures services, roles, and measurement. Combined, they guide improvements in the improve activity of the value chain.
ITIL and Governance/Standards: COBIT, ISO, and Compliance
Governance and Standards
Organizations must satisfy governance and compliance frameworks such as COBIT, ISO/IEC 20000, ISO/IEC 27001, and data protection laws like GDPR.
How ITIL Helps
ITIL (Version 5) provides practical service management practices and the service value system that support compliance with these standards and frameworks.
Governance in the SVS
In the ITIL service value system, governance sets policies, direction, and oversight. Practices and the value chain apply those policies in daily work.
Exam Perspective
When you see regulatory or audit scenarios, look for answers that use ITIL practices to meet requirements and emphasize governance within the SVS.
Thought Exercise: Mapping Practices Across Frameworks
Use this exercise to mentally connect ITIL (Version 5) with agile, DevOps, and Lean.
Task 1: Map an ITIL practice to another framework
Pick one ITIL practice from this list:
- Change enablement
- Incident management
- Problem management
- Service level management
For your chosen practice, answer in your own notes:
- Which service value chain activities does it mainly support (plan, improve, engage, design and transition, obtain/build, deliver and support)?
- How could agile help this practice? (Think: sprints, backlogs, retrospectives.)
- How could DevOps help this practice? (Think: automation, CI/CD, monitoring.)
- How could Lean help this practice? (Think: reducing waste, improving flow.)
Example to guide you (do not memorize, just understand):
- Practice: Incident management.
- Value chain: mainly deliver and support, plus engage and improve.
- Agile: use a simple Kanban board for incidents, daily standups for coordination.
- DevOps: automated alerts, on-call rotations, post-incident reviews.
- Lean: remove unnecessary handoffs, reduce waiting time for users.
Task 2: Spot integration opportunities in your experience
Think about any group projects, part-time jobs, or internships you have had:
- Did you see work tracked on a board or in sprints? (Agile.)
- Did you see automated testing or deployments? (DevOps.)
- Did you see efforts to simplify steps or remove delays? (Lean.)
Now imagine those activities as part of a service that needs to be planned, supported, and improved. Where would ITIL concepts like service value chain, service offering, and continual improvement help bring structure?
Quiz 1: ITIL with Agile and DevOps
Check your understanding of how ITIL integrates with agile and DevOps.
A company uses Scrum for development and has introduced a DevOps pipeline for frequent releases. Management worries this conflicts with ITIL (Version 5). What is the BEST ITIL-aligned response?
- Stop using Scrum and DevOps because ITIL requires formal processes and infrequent changes.
- Keep Scrum and DevOps, but adapt ITIL practices like change enablement and incident management to support automated, low-risk deployments.
- Ignore ITIL where Scrum is used, because agile teams should not be constrained by service management practices.
- Use ITIL only for major projects and leave day-to-day operations entirely to DevOps teams.
Show Answer
Answer: B) Keep Scrum and DevOps, but adapt ITIL practices like change enablement and incident management to support automated, low-risk deployments.
ITIL (Version 5) is designed to integrate with agile and DevOps. The best answer is to keep Scrum and DevOps while **adapting** ITIL practices such as change enablement (e.g., standard changes for low-risk deployments) and incident management to support frequent, automated releases. The other options wrongly treat ITIL and agile/DevOps as mutually exclusive.
Quiz 2: ITIL, Lean, and Governance
Test how well you can position ITIL with Lean and governance frameworks.
An organization is using Lean value stream mapping to reduce waste in its incident resolution process. It also wants to align with ISO/IEC 20000. How does ITIL (Version 5) MOST effectively support this situation?
- By replacing Lean with the service value chain, since Lean and ITIL cannot be used together.
- By providing detailed service management practices (like incident management and continual improvement) that can implement Lean improvements and support ISO/IEC 20000 requirements.
- By focusing only on governance and leaving process design entirely to Lean consultants.
- By enforcing a fixed set of processes that must not be altered by Lean changes.
Show Answer
Answer: B) By providing detailed service management practices (like incident management and continual improvement) that can implement Lean improvements and support ISO/IEC 20000 requirements.
ITIL (Version 5) works well with Lean and standards. Lean helps identify waste and improve flow; ITIL provides structured practices such as incident management and continual improvement that can implement those improvements and align with ISO/IEC 20000. ITIL does not replace Lean, nor does it forbid process changes.
Flashcards: Positioning ITIL with Other Frameworks
Flip these cards to reinforce key relationships between ITIL (Version 5) and other frameworks.
- How does ITIL (Version 5) relate to agile methods like Scrum?
- ITIL provides the service management structure and common language around services, while Scrum manages how a team plans and delivers work in iterations. They are complementary: agile teams often operate within ITIL’s service value chain activities such as design and transition and obtain/build.
- How does DevOps typically appear within the ITIL service value chain?
- DevOps practices support obtain/build (CI/CD, automated testing), design and transition (automated deployments), deliver and support (monitoring, on-call), and improve (post-incident learning and metrics). ITIL change enablement is adapted to support frequent, automated deployments.
- What is the main contribution of Lean thinking in an ITIL context?
- Lean contributes tools and principles to define value, map value streams, remove waste, and improve flow. In ITIL, this strengthens value stream identification, mapping, and management and supports the improve activity and guiding principles like keep it simple and practical.
- How does ITIL support governance frameworks like COBIT?
- COBIT defines what governance outcomes are needed for enterprise IT. ITIL provides detailed service management practices and the service value system that help achieve those outcomes in day-to-day service planning, delivery, and improvement.
- How does ITIL help organizations align with standards like ISO/IEC 20000?
- ITIL offers practical guidance for service management processes (incident, change, configuration, etc.) that ISO/IEC 20000 expects. Organizations can design their service management system using ITIL practices and show auditors how these meet standard requirements.
- In exam scenarios, what is the usual relationship between ITIL and other frameworks?
- The exam typically presents ITIL as a flexible, value-focused framework that integrates with agile, DevOps, Lean, and governance standards. The preferred answers emphasize combining and tailoring frameworks, not choosing one and rejecting the others.
Bringing It Together: ITIL as Your Integration Layer
ITIL as Integration Layer
ITIL (Version 5) sits over agile, DevOps, Lean, and governance frameworks as a flexible service management and value system that ties them into coherent services.
Exam Patterns to Watch
Look for answers that integrate ITIL with other frameworks, adapt practices for speed or automation, apply Lean to improve flow, and use ITIL to meet governance and compliance needs.
Your Next Practice Moves
Use Skarp’s diagnostic, mock exam, gap guide, and spaced review to practice spotting integration-friendly answers in realistic exam-style scenarios.
Key Terms
- Lean
- A set of principles and practices focused on defining value from the customer’s perspective, mapping value streams, eliminating waste, and improving flow.
- COBIT
- A governance framework for enterprise IT that defines objectives and practices for controlling and managing information and technology.
- agile
- A family of methods and a mindset emphasizing iterative delivery, customer collaboration, and responsiveness to change, often implemented using frameworks like Scrum or Kanban.
- DevOps
- A cultural and technical movement that integrates development and operations to deliver software faster and more reliably using automation, collaboration, and shared responsibility.
- service
- A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.
- governance
- The means by which an organization is directed and controlled, including defining policies, decision-making structures, and oversight mechanisms.
- ISO/IEC 20000
- An international standard specifying requirements for an organization to establish, implement, maintain, and continually improve a service management system.
- value co-creation
- The joint activities performed by a service provider and a service consumer to create value.
- service management
- A set of specialized organizational capabilities for enabling value for customers in the form of services.
- service value chain
- A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization.
- service value system
- A model representing how all the components and activities of an organization work together as a system to enable value creation.
- continual improvement
- A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.