A–Z definitions of key terms, each pointing to its home topic. Format (spec §13):

**Term** — plain-English definition. *[Wikipedia](url)* (optional) — See Topic N.N — Title.

Entries are added by each topic's author in the same commit as the topic. The reference-editor reconciles this file after each part.

A

Agile Manifesto — The 2001 statement of four values and twelve principles for software development, read here as a call for continuous stakeholder involvement, improvement, and delivery. — See Topic 2.1 — Agile Manifesto and Principles.

AI agent — An AI system that takes actions through tools, not only answers, and so needs scope, least privilege, approval gates, an audit trail, and a kill switch. — See Topic 5.5 — Agentic AI and Human Oversight.

AI governance — The owners, rules, risk assessment, testing, and records that keep AI use accountable. — See Topic 5.6 — AI Governance, Risk, and Compliance.

AIOps — The use of machine learning on operations data to reduce alert noise, find anomalies, and suggest causes. — See Topic 5.2 — AIOps.

Alarm fatigue — Desensitization to alerts that are too many or too often false, so that real ones are missed. — See Topic 3.10 — Monitoring and Event Management.

Alert — A notification that an event needs human attention now. — See Topic 3.10 — Monitoring and Event Management.

Asset — Something of value an organization owns or controls, including hardware, software, cloud services, and data. — See Topic 4.1 — Asset Management.

Audit trail — A record of what happened, by whom, and when, kept where it cannot be altered by those it concerns. — See Topic 8.1 — Governance, Risk, and Compliance.

Automation — Using technology to perform tasks with reduced human involvement. — See Topic 6.1 — Automation Strategy.

Availability — The ability of a service to perform its agreed function when required. — See Topic 3.11 — Availability, Capacity, and Performance.

B

Backlog — An ordered list of work or improvement ideas, each with an owner and status. — See Topic 3.15 — Continual Improvement.

Business continuity — Keeping critical functions running, or resuming them quickly, during and after a serious disruption. — See Topic 3.12 — Service Continuity Management.

Business impact analysis — A study of what happens to the organization if a service is unavailable for a given time. — See Topic 3.12 — Service Continuity Management.

C

Capacity — The maximum throughput a service can deliver. — See Topic 3.11 — Availability, Capacity, and Performance.

Change enablement — The ITIL 4 practice of making changes to services safely and quickly by assessing risk and assigning authority by risk. — See Topic 3.4 — Change Enablement.

Change failure rate — The share of changes that cause incidents or need remediation, one of the four delivery measures reported by DORA. — See Topic 2.2 — Continuous Delivery.

Chaos engineering — Deliberately introducing failures under control to find weaknesses before real incidents do. — See Topic 3.12 — Service Continuity Management.

CMDB — A configuration management database: a repository of configuration items, their attributes, and their relationships. — See Topic 4.4 — Configuration Management.

Configuration item — Any component that needs to be managed in order to deliver a service. — See Topic 4.4 — Configuration Management.

Continual improvement — The recurring cycle of choosing a small change, trying it, checking the result, and keeping or reversing it. — See Topic 3.15 — Continual Improvement.

Continuous delivery — Keeping software always releasable and shipping small changes to live services often through automated build, test, and deploy. — See Topic 2.2 — Continuous Delivery.

D

Data governance — Managing data as an asset with owners, definitions, quality checks, and rules for access and retention. — See Topic 7.2 — Data Foundations and Governance.

Data lineage — A record of where data came from and what happened to it on the way to a report or model. — See Topic 7.2 — Data Foundations and Governance.

DevOps — A set of cultural habits, practices, and tools that bring development and operations together to change live services quickly and run them reliably. — See Topic 2.5 — DevOps.

DORA metrics — Four delivery measures from the DORA research program: deployment frequency, lead time for changes, change failure rate, and time to restore service. Use them as questions, not scores. — See Topic 2.2 — Continuous Delivery.

E

Enterprise service management — Applying service management practices and tools beyond IT to functions such as HR, facilities, and legal. — See Topic 1.9 — Enterprise Service Management.

Error budget — The permitted amount of unreliability implied by a service level objective, spent on change and risk. — See Topic 2.6 — Site Reliability Engineering.

Event — A change of state that has significance for the management of a service. — See Topic 3.10 — Monitoring and Event Management.

Experience level agreement (XLA) — An agreement that sets targets for how users experience a service, alongside technical targets. — See Topic 3.7 — Service Level Management.

F

Feature flag — A switch that turns a feature on or off at run time without a new deployment; also called a feature toggle. — See Topic 3.5 — Release and Deployment Management.

FinOps — A practice that brings financial accountability to cloud spending by putting engineering, finance, and product owners in the same conversation. — See Topic 4.5 — Financial Management and FinOps.

Flow — How smoothly work moves from request to done. — See Topic 2.3 — Flow and Kanban.

Four dimensions — The ITIL 4 view that every service needs organizations and people, information and technology, partners and suppliers, and value streams and processes. — See Topic 1.6 — Four Dimensions of Service Management.

G

Generative AI — AI systems that produce new content, such as text and code, from prompts. — See Topic 5.4 — Generative AI for Incidents, Knowledge, and Changes.

GitOps — An approach in which a repository is the single source of truth for desired state and an automated agent keeps live systems matching it. — See Topic 6.3 — Infrastructure as Code and GitOps.

Goodhart's law — When a measure becomes a target, it ceases to be a good measure. — See Topic 7.3 — Measurement and Reporting.

Guardrail — A boundary built into tools that keeps work safe without stopping it, in contrast to a gate that waits for approval. — See Topic 8.1 — Governance, Risk, and Compliance.

H

Hallucination — An AI output that is fluent but unsupported or false. — See Topic 5.1 — AI in Service Management.

Human in the loop — A person who reviews or approves an AI output or action before it takes effect. — See Topic 5.5 — Agentic AI and Human Oversight.

I

Incident — An unplanned interruption to a service or reduction in its quality. — See Topic 3.2 — Incident Management.

Infrastructure as code — Defining infrastructure in reviewed text files that tools apply. — See Topic 6.3 — Infrastructure as Code and GitOps.

ISO/IEC 20000 — An international standard for service management systems, against which an organization can be audited and certified. — See Topic 1.8 — Service Management Frameworks and Standards.

ITIL — Guidance for IT service management, owned by PeopleCert, with practices, a value model, and a certification scheme for people. — See Topic 1.2 — ITIL.

ITIL 5 — ITIL (Version 5), the version that PeopleCert introduced in 2026, described by its owner as digital product and service management, including the impact of AI and emerging technologies. — See Topic 1.3 — ITIL 5.

K

Kaizen — Change for the better: continuous improvement by small changes made by the people who do the work. — See Topic 2.4 — Lean and Kaizen.

Kanban — A method for visualizing work, limiting work in progress, and managing flow. — See Topic 2.3 — Flow and Kanban.

Knowledge-Centered Service (KCS) — A method for capturing and improving knowledge as a by-product of solving problems. — See Topic 3.9 — Knowledge Management.

Known error — A problem that has been analyzed but not resolved, usually with a documented workaround. — See Topic 3.3 — Problem Management.

L

Lead time — The elapsed time from request to delivery as the customer experiences it. — See Topic 7.6 — Process and Value Stream Analytics.

Lean — A way of thinking about work that removes waste and focuses on the value the customer receives. — See Topic 2.4 — Lean and Kaizen.

M

Maturity model — A table of stages, here Initiate, Develop, Standardize, Manage, and Orchestrate, used as a self-assessment aid. — See Topic 1.8 — Service Management Frameworks and Standards.

O

Observability — The ability to ask new questions of a running system and get answers from the data it emits. — See Topic 7.4 — Observability and Telemetry.

Operational level agreement (OLA) — An agreement between internal teams that supports a service level agreement. — See Topic 3.7 — Service Level Management.

Orchestration — Coordinating many automated tasks across tools into one process. — See Topic 6.2 — Workflow Automation and Orchestration.

P

Peer review — Review of a change by another competent person before it is made. — See Topic 3.4 — Change Enablement.

Postmortem — A written review after a significant incident that looks at the system and tracks actions. — See Topic 3.3 — Problem Management.

Practice — A set of organizational resources designed for performing work or accomplishing an objective, as ITIL 4 uses the word. — See Topic 1.4 — The Service Value System.

Problem — A cause, or potential cause, of one or more incidents. — See Topic 3.3 — Problem Management.

Product owner — The person accountable for maximizing the value of a product and managing its backlog. — See Topic 2.8 — Product and Service Ownership.

Prompt — The text and material given to an AI model to get a response. — See Topic 5.7 — AI Skills and Prompts.

Prompt injection — Hostile instructions hidden in content that an AI model reads, trying to change its behavior. — See Topic 5.5 — Agentic AI and Human Oversight.

R

Recovery point objective (RPO) — The maximum acceptable amount of data loss, measured in time. — See Topic 3.12 — Service Continuity Management.

Recovery time objective (RTO) — The target maximum time to restore a service after a disruption. — See Topic 3.12 — Service Continuity Management.

Release — Making a service, feature, or version available for use, which may happen separately from deployment. — See Topic 3.5 — Release and Deployment Management.

Retrospective — A regular meeting in which a team looks back at how it worked and chooses what to change. — See Topic 3.15 — Continual Improvement.

Risk register — A record of risks with owners, assessments, treatments, and status. — See Topic 8.1 — Governance, Risk, and Compliance.

Root cause analysis — A family of methods for finding the underlying causes of a problem. — See Topic 3.3 — Problem Management.

Runbook — A documented procedure for a specific, recurring operational task or situation. — See Topic 3.9 — Knowledge Management.

S

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. — See Topic 1.1 — Service Management.

Service catalog — A maintained, user-facing description of what a provider offers (ITIL: service catalogue), with a technical view behind it. — See Topic 3.8 — Service Catalog Management.

Service desk — The single point of contact between a service provider and its users. — See Topic 3.1 — Service Desk.

Service level agreement (SLA) — A documented agreement between a provider and a customer on the services and the expected level of service. — See Topic 3.7 — Service Level Management.

Service level indicator (SLI) — A measure of some aspect of a service as users experience it. — See Topic 2.6 — Site Reliability Engineering.

Service level objective (SLO) — A target for a service level indicator over a period. — See Topic 2.6 — Site Reliability Engineering.

Service request — A request that initiates a service action agreed as a normal part of service delivery. — See Topic 3.6 — Service Request Management.

Service value chain — The ITIL 4 operating model of six activities that every value stream passes through in its own order. — See Topic 1.7 — The Service Value Chain.

Service value system (SVS) — The ITIL 4 model of how opportunity and demand become value through governance, a value chain, practices, guiding principles, and continual improvement. — See Topic 1.4 — The Service Value System.

Shadow IT — Technology bought and used without the knowledge of the IT function. — See Topic 4.1 — Asset Management.

Shift left — Moving checks and resolution earlier, toward the user or the start of the lifecycle. — See Topic 3.1 — Service Desk.

Site reliability engineering (SRE) — An engineering discipline that treats operations as a software problem, with SLOs, error budgets, and toil limits. — See Topic 2.6 — Site Reliability Engineering.

Software bill of materials (SBOM) — A list of the components in a piece of software, with versions and licenses. — See Topic 4.2 — Software Asset Management.

T

Telemetry — Data that systems emit about themselves, mainly metrics, logs, and traces. — See Topic 7.4 — Observability and Telemetry.

Toil — Manual, repetitive, automatable work that grows with the service and adds no lasting value. — See Topic 2.6 — Site Reliability Engineering.

V

Value stream — The series of steps an organization undertakes to create and deliver a product or service to consumers. — See Topic 1.7 — The Service Value Chain.

W

Work in progress (WIP) — The number of items started but not finished. — See Topic 2.3 — Flow and Kanban.