ITIL is a collection of best practices for running IT services that people can count on every day. An IT service is anything technology does for users: a website, an app, email, a support desk.
Scrum helps you build software. ITIL helps you keep it running well once real people use it.
This guide explains the key ITIL ideas in plain words and what changed with ITIL Version 5 in 2026. Then which practices even a small team can borrow.
What is ITIL in simple words?
ITIL is a framework of best practices for IT service management, which means organising how technology is delivered and supported so it creates value for users.
The name originally meant Information Technology Infrastructure Library. It started in the late 1980s with the UK government, which wanted its IT services to run in a more consistent way. Today ITIL is owned by PeopleCert.
Think of a restaurant. Cooking a great dish once is not enough. The restaurant needs a way to:
- take orders
- handle a dish sent back
- fix the cause when the same dish keeps coming back
- test a new recipe before it goes on the menu
ITIL is that system, for technology.
Why does ITIL matter?
Because most IT pain doesn't come from building. It comes from running.
Picture a growing company. Support requests pile up in WhatsApp, bugs reach customers, and nobody is sure who is responsible for what.
Each problem gets fixed, then comes back next month.
ITIL does not answer this with strict rules. It gives tested habits: one clear way to report problems, clear ownership, and changes that are checked before they go live.
How does ITIL define value?
ITIL says a service creates value only when it has two qualities:
| Quality | The question it asks | In plain words |
|---|---|---|
| Utility | Does it solve the problem? | Fit for purpose |
| Warranty | Does it work reliably, when needed? | Fit for use |
An app with a great feature that crashes every evening has utility but no warranty. An app that never crashes but doesn't do what users need has warranty but no utility. Both fail.
What are the four dimensions of ITIL 4?
ITIL 4, released in 2019, says every service depends on four areas. Ignore one and the service suffers.
- Organisations and people. Are roles and responsibilities clear?
- Information and technology. Is the data and the technology reliable and secure?
- Partners and suppliers. Can the companies you depend on, like your hosting or courier, deliver?
- Value streams and processes. Do the steps of your work actually produce value?
What is the ITIL service value system?
The service value system is the overall model that shows how all parts of ITIL work together to create value. It has five parts:
- Guiding principles. Seven pieces of advice, like "focus on value", "start where you are" and "keep it simple and practical".
- Governance. How decisions are made and checked.
- Service value chain. Six activities: plan, improve, engage, design and transition, obtain or build, deliver and support.
- Practices. ITIL 4 describes 34 practices, organised ways of doing specific work, like incident management or the service desk.
- Continual improvement. You are never finished. You keep measuring and improving.
Which ITIL practices matter most for a small team?
You don't need all 34. Three practices give most of the value:
| Practice | What it is | Restaurant version |
|---|---|---|
| Incident management | Restoring a broken service as fast as possible | A dish is sent back: replace it now |
| Problem management | Finding and fixing the root cause of repeated incidents | Why does that dish keep coming back? |
| Change enablement | Checking changes before they go live, so they don't break things | Test the new recipe before it reaches the menu |
A fourth one, the service desk, ties them together: one place where users report issues and get answers. For a small business, that can be a shared inbox or a single WhatsApp number with a simple log.
If your support still lives in chats and spreadsheets, I explain where that breaks in when WhatsApp and Excel break your business.
What is ITIL Version 5?
In 2026, PeopleCert launched ITIL (Version 5). The Foundation exam went live on 12 February 2026 (ITSM Academy, 2026).
Version 5 widens the focus from IT services to digital products and services as a whole. It also adds attention to AI, with a separate course on AI governance (PeopleCert).
What it means for you:
- If you hold ITIL 4: PeopleCert describes Version 5 as backward compatible, and offers a short bridge course to upgrade.
- If you are learning: start with the ideas in this guide. Value, the four dimensions and the practices remain the foundation.
What is the difference between ITIL and Scrum?
| Scrum | ITIL | |
|---|---|---|
| Main job | Build a product | Run and support services |
| Rhythm | Sprints of one month or less | Ongoing, every day |
| Key question | What do we build next? | Is the service working for users? |
| Typical users | Product teams | IT operations and support teams |
They don't compete. Many teams use Scrum to build and ITIL practices to run what they built. I explain Scrum in what is Scrum.
Is ITIL useful in Algeria?
Yes, especially as more businesses move their work online. ITIL is an international framework, so its ideas show up wherever IT teams support many users.
For a small business, the lesson is simpler. When your shop runs on a website or an app, downtime is lost sales. A clear way to report problems, fix root causes and test changes protects your income.
It also helps you judge a developer. Ask how they handle incidents and changes once your app is live. I list the questions to ask in prototype vs production.
What mistakes do teams make with ITIL?
- Treating it as rules to follow word for word. ITIL 4 says "start where you are". Adapt it.
- Fixing incidents but never the problem. If the same issue returns, find the root cause.
- Changing things live without testing. A careless change can break what worked yesterday.
- Having no single place to report issues. Requests get lost in calls and chats.
- Getting certified but changing nothing. The value is in the habits, not the certificate.
What should you do this week?
- Today: choose one place where all problems with your website or app get reported.
- This week: start a simple log: date, issue, how it was fixed.
- At month end: look for issues that came back. Those are problems to fix at the root.
- Before every change: test it somewhere safe first, and know how to undo it.
- If you want the certificate: check the current ITIL (Version 5) Foundation on PeopleCert's site.