SkarpChapter 9 of 14
Key ITIL 4 Practices II: Change Enablement, Release, Deployment, and Configuration
Follow the lifecycle of change from idea to live environment, and see how ITIL 4 keeps risk under control while enabling rapid delivery.
From Idea to Live: The Change Lifecycle in ITIL 4
Key Practices in This Module
In ITIL 4, four practices support the journey from idea to live: change enablement, release management, deployment management, and service configuration management.
What the Exam Expects
At Foundation level you must state each practice's purpose, distinguish them in short scenarios, and recognize configuration items (CIs) versus IT assets.
The High-Level Lifecycle
Typical flow: 1) Idea or need, 2) Change enablement assesses and authorizes, 3) Release management plans the package, 4) Deployment management moves it, 5) Service configuration management records what changed.
ITIL 4 Style
ITIL 4 is non-prescriptive. It supports classic IT, agile, and DevOps. You adapt the practices to your organization rather than follow a rigid process template.
Change Enablement: Purpose and Types of Change
Purpose of Change Enablement
Change enablement maximizes successful changes by assessing risk, authorizing changes, and managing the change schedule. It balances speed, value, and risk.
What Change Enablement Does Not Do
It does not design or build solutions (projects do that) and it does not physically deploy changes (deployment management does). It provides visibility and authorization.
Standard, Normal, Emergency
Standard changes: low risk, pre-approved, repeatable. Normal changes: assessed and approved case by case. Emergency changes: fast-tracked for urgent issues like critical security fixes.
Change Enablement in Modern IT
In agile and DevOps teams, automated tests, pipelines, and peer reviews can form part of change enablement, but the exam cares about the principle: risk-based authorization.
Example: Change Enablement vs Project vs Release
The University Scenario
A university introduces online exam proctoring. Several practices are involved: project management, change enablement, release management, deployment management, and service configuration management.
Project vs Change Enablement
Project management runs the project: budget, scope, tasks. Change enablement evaluates risk, gets authorization, and schedules when the new proctoring capability will be switched on.
Release vs Deployment
Release management defines what goes out together: software, portal changes, guides, training. Deployment management moves these items into test, pilot, and production environments.
Role of Configuration Management
Service configuration management records which courses use proctoring, which servers or SaaS tenants are involved, and how the new service relates to the portal and identity systems.
Quick Check: Which Practice Is It?
Select the practice that best fits the scenario.
An IT team reviews a proposed change to enable multi-factor authentication for all staff. They assess security benefits, possible login issues, and agree on a go-live weekend that avoids exam periods. Which ITIL 4 practice is mainly described?
- Change enablement
- Release management
- Deployment management
- Service configuration management
Show Answer
Answer: A) Change enablement
**Change enablement** is about assessing risk and impact, authorizing the change, and scheduling it. Release management focuses on the contents of the release; deployment management on moving components; service configuration management on recording CIs and relationships.
Release Management vs Deployment Management
What Is Release Management?
Release management makes new and changed services available in a controlled way. It focuses on what is in a release and when it is made available to users.
What Is Deployment Management?
Deployment management moves new or changed components into environments. It focuses on how rollout happens, using methods like phased or blue‑green deployment.
Example: App Version 3.0
Release management defines that version 3.0 includes new login options and bug fixes and will go out at month end. Deployment management executes the rollout via pipelines and staged user groups.
Exam Pattern
Packaging and coordinating = release management. Installing or rolling out = deployment management. Approving and scheduling = change enablement.
Classify the Scenario: Release or Deployment?
Read each short scenario and decide whether it mainly describes release management or deployment management. Then check yourself with the answers.
- A product owner works with marketing and support to decide which bug fixes and features will be included in "Summer Release 2026" and when it will be visible to customers.
- An engineer configures the pipeline to roll out the new version only to 10% of users at first, then 50%, then 100%, monitoring error rates at each stage.
- A change calendar entry shows that on Friday night, version 5.2 of the CRM, the updated API, and new training materials will all be introduced together.
- A team decides to use blue-green deployment to minimize downtime when switching to a new web front-end.
Think first, then reveal the suggested answers below.
Suggested answers
- Release management (deciding content and timing of a release).
- Deployment management (configuring how the rollout is executed).
- Release management (coordinating multiple components as one release event).
- Deployment management (choosing a deployment method).
Service Configuration Management and Configuration Items (CIs)
Purpose of Service Configuration Management
Service configuration management provides accurate, reliable information about services and the configuration items (CIs) that support them, including their relationships.
What Is a Configuration Item?
A CI is any component that must be managed to deliver a service: servers, VMs, apps, databases, key documents, even roles in some implementations.
CMDB and Relationships
Configuration data is often stored in a CMDB or CMS, which records how services, applications, servers, and other CIs are linked and depend on each other.
Why It Matters
Accurate CI data helps assess change impact, resolve incidents faster, analyze problems, and satisfy audit or compliance requirements.
CIs vs IT Assets: Do Not Mix Them Up
Focus of IT Asset Management
IT asset management focuses on value, cost, lifecycle, and compliance of assets like hardware, licenses, and cloud subscriptions.
Focus of Configuration Management
Service configuration management focuses on how components are configured and how they relate to services, including dependencies and technical details.
Same Item, Two Views
A database server as an asset: cost, contract, license. The same server as a CI: which services depend on it, OS version, cluster membership.
Exam Clues
Keywords: license and cost → IT asset management. CIs, CMDB, dependencies, impact analysis → service configuration management.
Quiz: CI or Asset Management?
Decide which practice the scenario is testing.
An organization reviews how many database server licenses it is paying for, compares this with actual usage data, and cancels unused licenses to reduce cost. Which practice is this mainly about?
- Service configuration management
- IT asset management
- Change enablement
- Release management
Show Answer
Answer: B) IT asset management
This scenario is about **licenses, usage, and cost**, which are part of **IT asset management**, not service configuration management. Configuration management would focus on dependencies and technical relationships.
Key Term Review: Change and Configuration
Use these flashcards to reinforce the core terms from this module.
- Change enablement (purpose)
- To maximize the number of successful changes by ensuring risks are properly assessed, authorizing changes, and managing the change schedule.
- Standard change
- A low-risk, pre-authorized change that is well understood and follows a documented, repeatable procedure.
- Normal change
- A change that must be assessed and authorized individually because its risk and impact can vary.
- Emergency change
- A change that must be implemented as soon as possible, often to resolve a major incident or security issue, using streamlined assessment and authorization.
- Release management (purpose)
- To make new and changed services and features available for use in a controlled way, focusing on what is released and when.
- Deployment management (purpose)
- To move new or changed components to live or other environments, focusing on how the rollout is executed.
- Service configuration management (purpose)
- To ensure accurate and reliable information about the configuration of services and the CIs that support them is available when and where needed.
- Configuration item (CI)
- Any component that needs to be managed in order to deliver a service, such as hardware, software, data, documents, or sometimes roles.
- IT asset management (focus)
- Managing the value, cost, risks, and lifecycle of IT assets, including licenses and contracts, to maximize value and control cost.
Mini Exam Drill: Pick the Right Practice
For each statement, decide which practice is being tested: change enablement, release management, deployment management, or service configuration management. Then view the suggested answers.
- "Ensures that information about servers, applications, and their dependencies is accurate so that impact of a proposed change can be assessed."
- "Groups multiple approved changes into a single package that will be introduced together at the start of the new semester."
- "Uses automated pipelines to roll out updated code to production in small batches several times per day."
- "Reviews a high-risk change request, considers security and availability impacts, and either authorizes or rejects it."
Suggested answers
- Service configuration management (accurate CI and dependency information).
- Release management (packaging and timing of a release).
- Deployment management (how components are rolled out, using automation).
- Change enablement (risk assessment and authorization of a change request).
Key Terms
- Normal change
- A change that must be assessed and authorized individually because its risk and impact can vary.
- Standard change
- A low-risk, pre-authorized change that is well understood and follows a documented, repeatable procedure.
- Emergency change
- A change that must be implemented as soon as possible, often to resolve a major incident or security issue.
- Change enablement
- ITIL 4 practice that maximizes successful changes by assessing risk, authorizing changes, and managing the change schedule.
- Release management
- Practice that makes new and changed services and features available for use in a controlled way, focusing on what is released and when.
- IT asset management
- Practice that plans and manages the full lifecycle of IT assets to maximize value, control cost, and manage risks related to ownership and use.
- Deployment management
- Practice that moves new or changed components to live or other environments, focusing on how rollout happens.
- Configuration item (CI)
- Any component that needs to be managed in order to deliver a service, such as hardware, software, data, documents, or sometimes roles.
- Service configuration management
- Practice that ensures accurate and reliable information about the configuration of services and the configuration items (CIs) that support them is available.
- Configuration management database (CMDB)
- A database used to store configuration records throughout their lifecycle and their relationships.