6.1 ITIL Management Practices Overview

What Is an ITIL Practice?

Quick Answer: In ITIL 4, a practice is a set of organizational resources designed for performing work or accomplishing an objective. There are 34 practices divided into 14 general management practices, 17 service management practices, and 3 technical management practices. Practices contribute to one or more service value chain activities — they are not single-purpose processes.

In ITIL v3, the framework was built around 26 rigid processes locked into a service lifecycle. ITIL 4 replaced that model with practices. The shift matters for the exam: a practice is broader than a process. Where a process is just a defined sequence of activities, a practice bundles together everything an organization needs to do the work — people, tools, information, partners, and the processes themselves.

A practice is therefore not what you do but the whole capability to do it. Every practice draws on all four dimensions of service management (organizations and people; information and technology; partners and suppliers; value streams and processes), so a practice can never be reduced to a flowchart alone.

Why ITIL 4 chose 'practices' over 'processes'

The rename is more than cosmetic. In ITIL v3, an organization that adopted a process tended to follow its prescribed steps rigidly. ITIL 4 acknowledges that real work needs flexibility: the same practice can be applied lightly for a small team or comprehensively for a large enterprise. Each practice in ITIL 4 includes a purpose, the practice success factors that show whether it is achieving that purpose, key activities, and the information and organizational structures it relies on.

By describing the whole capability rather than a fixed sequence, ITIL 4 lets organizations adopt and adapt only the parts that add value — a direct application of the guiding principle keep it simple and practical.

The Three Categories of Practice

ITIL 4's 34 practices are grouped by where their roots lie. Knowing which category a practice belongs to is a common exam question.

Note the deliberate overlap: deployment management is counted among the technical management practices, while release management sits in the service management group. The exam likes to test whether you can place a named practice in the right category, so memorize the three technical ones (deployment; infrastructure & platform; software development & management) — they are the smallest and easiest group to lock down.

Practices and the Service Value Chain

The service value chain (SVC) has six activities: plan, improve, engage, design & transition, obtain/build, and deliver & support. A key ITIL 4 idea is that each practice can contribute to multiple value chain activities, and each activity can draw on multiple practices. There is no one-to-one mapping.

For example, change enablement contributes to design & transition, obtain/build, and deliver & support. Incident management contributes mainly to deliver & support, engage, design & transition, and improve. This is the opposite of ITIL v3's lifecycle, where a process belonged to exactly one stage. Practices are reusable building blocks an organization combines into value streams to deliver products and services.

The seven practices examined in detail

The Foundation exam tests 15 practices at a basic level (you must recall their purpose), but 7 of them are examined in detail — you must know both their purpose and how they work:

• Incident management
• Problem management
• Change enablement
• Service request management
• Service desk
• Service level management
• Continual improvement

The other eight tested at recall level include: information security management, relationship management, supplier management, IT asset management, monitoring & event management, release management, service configuration management, and deployment management. Knowing exactly which practices are detail versus recall helps you budget study time, since the seven detail practices generate a disproportionate share of exam questions.

Practices and value streams

Where a value stream is a series of steps an organization takes to create and deliver value, practices are the resources those steps draw on. A single incident, for instance, might flow through a value stream that uses the service desk practice to log it, incident management to coordinate restoration, problem management if a root cause is suspected, and change enablement to deploy a fix. The exam expects you to see practices as the toolbox and value streams as the assembled workflow. Practices on their own do not create value — they must be combined and orchestrated.

This is why ITIL 4 stresses that focusing on individual practices in isolation is an anti-pattern; the service value system ties the practices, the value chain, the guiding principles, governance, and continual improvement into one whole.