SkarpChapter 18 of 19
ITIL and Other Frameworks: Agile, DevOps, Lean, and Beyond
Place ITIL 5 alongside Agile, DevOps, Lean, and related frameworks to see how they complement each other and how exam questions may reference them conceptually.
Big Picture: ITIL 5 Among Agile, DevOps, and Lean
Why This Module Matters
Modern IT teams rarely use ITIL alone. They mix ITIL, Agile, DevOps, and Lean. Your job for the exam is to understand how these pieces fit together, not to treat them as competing methods.
ITIL as the Service Lens
ITIL provides the service management lens: how all capabilities work together as a service value system to enable value for customers. Agile, DevOps, and Lean are key capability families inside that system.
Exam Focus
Foundation questions about Agile, DevOps, and Lean are conceptual. They ask whether ITIL conflicts with them, how they complement the service value chain, and how value streams and flow connect to ITIL.
Simple Mental Model
Keep it simple: ITIL = how we manage services. Agile/DevOps/Lean = how we build, deliver, and improve work inside those services. The exam rewards you for seeing them as complementary, not rivals.
ITIL 5 Recap: Service Value System and Value Chain
Service Value System (SVS)
The service value system shows how all components and activities work together to enable value. It includes principles, governance, the value chain, practices, and continual improvement.
Service Value Chain (SVC)
The service value chain is a set of interconnected activities: Plan, Improve, Engage, Design & Transition, Obtain/Build, Deliver & Support, all working together to enable value realization.
Where Other Frameworks Plug In
Agile, DevOps, and Lean shape how we perform value chain activities and design value streams. Scrum sprints, DevOps pipelines, and Lean flow improvements all live inside the SVS.
Exam Tip
When a question mentions Agile or DevOps, link it mentally to an SVS component or value chain activity. That helps you choose answers that show integration, not conflict.
ITIL and Agile/Scrum: Complementary, Not Competing
Different Scopes
Agile/Scrum guide how a team plans and delivers increments. ITIL guides how an organization manages services end-to-end. They operate at different levels, so they can fit together.
Shared Principles
ITIL principles like focus on value, progress iteratively with feedback, and collaborate and promote visibility align closely with Agile values and Scrum events like reviews and retrospectives.
How Scrum Fits the Value Chain
A Scrum backlog and sprints feed Plan, Design & Transition, and Obtain/Build. Sprint reviews and retrospectives contribute to continual improvement inside the service value system.
Exam Traps
Beware statements like "ITIL requires waterfall" or "Scrum replaces ITIL". ITIL does not define roles like Product Owner and does not forbid iterative delivery.
Example: Scrum Team Inside an ITIL-Governed Service
Scenario Overview
A university runs a Student Portal as part of a service offering. A Scrum team builds features, while a service desk and change enablement protect live service quality.
Scrum and the Value Chain
The Product Owner’s backlog supports Plan and Design & Transition. Two‑week sprints cover Obtain/Build, with design, coding, and testing inside each iteration.
ITIL Practices Around the Team
Lightweight change enablement is built into the Scrum workflow. Incident management and the service desk handle live issues. Sprint retrospectives and incident reviews support continual improvement.
Exam Mapping
The best exam answers will say that ITIL practices are integrated into Agile ways of working, balancing speed with protection of the live service.
ITIL and DevOps: From Silos to Continuous Flow
What DevOps Brings
DevOps breaks down dev/ops silos using CI/CD, Infrastructure as Code, automation, and shared responsibility for reliability, aiming for fast, safe delivery.
How DevOps Fits ITIL
DevOps strengthens Obtain/Build and Deliver & Support. ITIL practices like change enablement and incident management provide governance around automated pipelines.
Shared Principles
The ITIL principle optimize and automate fits DevOps perfectly. Both value automation, feedback, and learning, supporting continual improvement.
Exam Traps
Avoid options claiming DevOps removes change enablement or that ITIL forces manual approvals for every change. The correct view is integrated and risk-based.
Example: DevOps Pipeline Within ITIL Change Enablement
Retailer DevOps Scenario
An online retailer uses a CI/CD pipeline for its Order Management service. Code commits trigger tests and, if successful, automatic production deployments several times per day.
Change Enablement’s Role
Most deployments are treated as standard changes: low-risk and pre-authorized. Change enablement designs the pipeline, risk rules, and rollback plans, not each individual approval.
Other ITIL Practices
Release management handles planning and communication. Monitoring and event management plus incident management respond to failures and feed learning back into the pipeline.
Exam Mapping
Look for answers where ITIL adapts to support automation with risk-based policies and traceability, rather than blocking frequent deployments.
ITIL and Lean: Value, Waste, and Flow
Lean Basics
Lean focuses on value, waste, and flow. It aims to remove non‑value‑adding work and create smooth, predictable movement of work from start to finish.
Lean and ITIL Value Streams
ITIL builds value streams from service value chain activities. Lean value stream mapping helps visualize these end-to-end steps and spot waste and bottlenecks.
Example: Laptop Request
A "Request new laptop" value stream runs from user request (Engage) through approval and procurement (Plan, Obtain/Build) to configuration and delivery (Design & Transition, Deliver & Support).
Exam Angles
When questions mention long waits, many handoffs, or improving flow, think Lean and ITIL value streams, plus continual improvement of the service value system.
Thought Exercise: Mapping a Simple Value Stream
Use this short exercise to connect Lean value streams to the ITIL service value chain.
Scenario: A company offers a Password Reset service for employees. Currently:
- Users email the service desk when they forget their password.
- The service desk logs a ticket and sends it to a Level 2 team.
- Level 2 resets the password manually and emails the user.
- Users often wait 4–6 hours.
Your tasks:
- Identify the value stream steps (high level).
- Write down 4–6 steps from "user has a problem" to "user can log in again".
- Map each step to a value chain activity:
- Which step is mainly Engage?
- Which ones are Deliver & Support?
- Spot Lean waste:
- Where do you see waiting, unnecessary handoffs, or manual work that could be automated?
- Propose one improvement that uses ideas from another framework:
- For example, could you use DevOps automation or an Agile user story to create a self-service reset feature?
Write your answers in a notebook or notes app. Then compare to the hints below.
Hints (do not peek until you try):
- The initial user email and service desk logging are part of Engage.
- Manual Level 2 work and communication are Deliver & Support.
- Obvious wastes: waiting for Level 2, manual steps, email ping-pong.
- A likely improvement: automated self-service reset (Obtain/Build + Deliver & Support), reducing waste and improving flow.
Using ITIL with Other Governance and Management Frameworks
Other Frameworks Around ITIL
Organizations also use COBIT, ISO/IEC 20000, ISO/IEC 27001, and scaled Agile frameworks. ITIL is meant to coexist and integrate with these, not replace them.
How They Align
COBIT says what to govern; ITIL explains how in services. ISO standards set requirements; ITIL-aligned practices help meet them inside the service value system.
Security and Compliance
Security standards influence ITIL practices like information security management, access management, and change enablement, ensuring services meet regulatory expectations.
Exam View
Foundation questions expect you to see ITIL as compatible with other frameworks. Prefer answers that integrate ITIL into existing governance and compliance structures.
Quick Check: Agile and DevOps Alignment
Test your understanding of how ITIL aligns with Agile and DevOps.
A product team uses Scrum and a DevOps pipeline to deliver a digital service. Which statement best reflects ITIL 5’s view of this situation?
- ITIL cannot be applied because Scrum and DevOps replace formal service management practices.
- ITIL should require the team to stop using Scrum and adopt a single standardized waterfall process.
- ITIL practices such as change enablement and incident management can be integrated into the team’s Agile and DevOps ways of working.
- DevOps automation removes the need for ITIL practices such as monitoring and event management.
Show Answer
Answer: C) ITIL practices such as change enablement and incident management can be integrated into the team’s Agile and DevOps ways of working.
ITIL 5 is designed to work with Agile and DevOps. It does not require waterfall or replace team-level methods. The best answer states that ITIL practices (change enablement, incident management, etc.) are integrated into Agile and DevOps workflows to protect service quality while supporting fast, iterative delivery.
Quick Check: Lean and Value Streams
Check your understanding of Lean and value streams in ITIL.
A service has long waiting times due to multiple handoffs between teams. The organization wants to improve flow end-to-end. Which ITIL-aligned approach best reflects Lean thinking?
- Introduce additional approval steps to ensure every handoff is tracked.
- Perform value stream mapping across service value chain activities to identify and remove waste.
- Limit continual improvement to annual reviews so that changes do not disrupt current processes.
- Increase documentation requirements for each team to better describe their internal processes.
Show Answer
Answer: B) Perform value stream mapping across service value chain activities to identify and remove waste.
Lean focuses on value, waste, and flow. In ITIL, this is implemented through value streams built from service value chain activities. Value stream mapping to identify and remove waste is the most Lean-aligned option. Adding approvals, delaying improvement, or increasing documentation usually adds waste, not flow.
Flashcards: Key Relationships and Definitions
Use these cards to reinforce key ITIL relationships with Agile, DevOps, and Lean.
- 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.
- service value system (SVS)
- A model representing how all the components and activities of an organization work together as a system to enable value creation.
- service value chain (SVC)
- A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization.
- continual improvement
- A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.
- How does Agile relate to ITIL?
- Agile (and Scrum) guide how teams iteratively plan and deliver work. ITIL provides the broader service management context. They are complementary: Agile teams operate within ITIL’s service value system and value chain.
- How does DevOps relate to ITIL?
- DevOps automation and collaboration strengthen ITIL value chain activities like Obtain/Build and Deliver & Support. ITIL practices such as change enablement and incident management provide governance and structure around DevOps pipelines.
- How does Lean relate to ITIL?
- Lean’s focus on value, waste, and flow aligns with ITIL’s value streams and value chain. Lean tools like value stream mapping help improve flow and remove waste in ITIL-managed services.
- Exam trap: ITIL vs Agile
- It is incorrect to say ITIL requires waterfall or conflicts with Agile. ITIL 5 explicitly supports iterative, feedback-driven approaches and can be tailored to Agile teams.
- Exam trap: DevOps vs change enablement
- DevOps does not remove the need for change enablement. Instead, change enablement defines risk-based policies and controls that can be automated within DevOps pipelines.
- Using ITIL with other governance frameworks
- ITIL coexists with frameworks like COBIT and ISO standards. ITIL provides practices and a value system that can be aligned with higher-level governance and regulatory requirements.
Putting It All Together and Next Steps in Your Study Path
Integrated View
ITIL gives the service management backbone. Agile/Scrum shape team work, DevOps provides automation and collaboration, and Lean sharpens value, waste, and flow across value streams.
Exam Patterns
Avoid answers that set ITIL against Agile, DevOps, or Lean. Prefer options showing integration and adaptation of ITIL practices to modern, iterative, automated ways of working.
Using the Skarp Path
Next, use the diagnostic, mock exam, and gap guide in this course. They will surface and reinforce any weak spots in your understanding of how ITIL aligns with other frameworks.
Core Question to Master
Be ready to answer: How does ITIL work with Agile, DevOps, and Lean to enable value co-creation through services? That understanding will carry you through many Foundation questions.
Key Terms
- Lean
- A management philosophy focused on maximizing value, minimizing waste, and improving flow across end-to-end value streams.
- Agile
- A family of principles and methods for iterative, incremental delivery and fast feedback, emphasizing collaboration and responsiveness to change.
- Scrum
- A popular Agile framework with defined roles, events, and artifacts used to deliver product increments in short, time-boxed iterations called sprints.
- DevOps
- A cultural and technical movement that integrates development and operations to enable fast, reliable delivery through 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.
- value stream
- The end-to-end set of steps an organization uses to create and deliver value to a customer, often mapped to analyze flow and waste.
- value co-creation
- The joint activities performed by a service provider and a service consumer to create value.
- 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.