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

ADKAR — A change model of awareness, desire, knowledge, ability, and reinforcement developed by Jeff Hiatt for Prosci. Wikipedia — See Topic 5.8 — Organizational Change and Adoption.

Agile (agile software development) — An umbrella term for approaches to continuous software delivery that deliver in small steps and learn from feedback, based on the values and principles agreed in 2001. Wikipedia — See Topic 1.3 — Agile Software Development.

Agile learning — Applying agile project methods, especially Scrum, to learning: short cycles that alternate learning and doing, with a sponsor, a coach, and a team. Wikipedia — See Topic 1.10 — Agile Learning.

Agile management — Applying agile and lean ideas to team and project management, especially product development; an informal term, not a standard. Wikipedia — See Topic 1.9 — Agile Management.

Agile Manifesto — The 2001 statement of four value pairs, written by 17 practitioners at Snowbird, Utah. Wikipedia — See Topic 1.1 — Agile Manifesto.

Agile principles — The twelve principles behind the Agile Manifesto that spell out its values in daily work. — See Topic 1.2 — Agile Principles.

AIOps — Using AI, machine learning, and big data analytics to automate and improve IT operations; defined by Gartner in 2016. Wikipedia — See Topic 6.2 — AI in IT Service Management.

Alert — A notification for a human, delivered as a ticket, email, or page. — See Topic 3.10 — Monitoring and Event Management.

Asset tag — A unique identifier attached to or recorded for a device so that it can be tracked through its life cycle. — See Topic 4.3 — Hardware Asset Management.

Availability — The ability of a service to do what users need when they need it, often expressed as a percentage over a period. Wikipedia — See Topic 3.11 — Availability, Capacity, and Performance.

B

Baseline (configuration) — An agreed reference configuration; once baselined, changes go through formal control. Wikipedia — See Topic 4.4 — Configuration Management.

Blameless postmortem — A review that records an incident, its impact, causes, and actions without blaming individuals or teams. — See Topic 3.2 — Incident Management.

Business impact analysis (BIA) — A method of identifying and evaluating how disruptions affect operations and of setting recovery priorities. Wikipedia — See Topic 3.12 — Service Continuity Management.

C

Capacity planning — Determining the capacity an organization needs to meet changing demand; in IT, a synonym for capacity management. Wikipedia — See Topic 3.11 — Availability, Capacity, and Performance.

Change enablement — The ITIL 4 practice of making sure changes are assessed, authorized, and scheduled so that beneficial changes proceed safely. — See Topic 3.4 — Change Enablement.

Change fail rate — The share of deployments that need immediate intervention, such as a rollback or hotfix (DORA). — See Topic 3.4 — Change Enablement.

Change lead time — The time for a change to go from committed to version control to deployed in production (DORA). — See Topic 3.4 — Change Enablement.

Chargeback — Billing consumers, or moving cost to their budget, for the services they use. — See Topic 4.5 — IT Financial Management and FinOps.

COBIT — A framework from ISACA for IT governance and management that links business goals to IT goals. Wikipedia — See Topic 2.7 — ITSM Frameworks and Standards.

Collective code ownership — An Extreme Programming practice in which anyone on the team may change any part of the code. Wikipedia — See Topic 1.6 — Extreme Programming.

Community of practice — A group that shares a concern or passion for something and learns to do it better by interacting regularly. Wikipedia — See Topic 5.8 — Organizational Change and Adoption.

Configuration item (CI) — A component whose configuration is tracked, with attributes and relationships to other items. Wikipedia — See Topic 4.4 — Configuration Management.

Configuration management database (CMDB) — An ITIL term for a database storing configuration items and their relationships. Wikipedia — See Topic 4.4 — Configuration Management.

Continual improvement — An ongoing effort to improve products, services, or processes, in small steps or breakthroughs. Wikipedia — See Topic 3.15 — Continual Improvement.

Continuous delivery — The ability to release changes of all kinds on demand quickly, safely, and sustainably (DORA). Wikipedia — See Topic 3.5 — Release and Deployment Management.

Continuous integration (CI) — Merging work into a shared repository frequently, with an automatic build and test on each merge. Wikipedia — See Topic 1.6 — Extreme Programming.

Copyleft — A family of open-source licenses that require recipients to use the same license for at least some parts of what they distribute. Wikipedia — See Topic 4.2 — Software Asset Management.

Customer and user (ITSM) — A customer pays for or commissions a service; a user uses it. They may be different people with different needs. Wikipedia — See Topic 2.1 — IT Service Management.

Cycle time — In Kanban, the time from the start to the finish of a completed work item. Wikipedia — See Topic 1.5 — Kanban.

D

Daily Scrum — A 15-minute daily event in which the Developers inspect progress toward the Sprint Goal and plan the next day. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Data erasure — A method that overwrites every sector of a storage device so the data cannot be recovered; ordinary deletion removes only pointers. Wikipedia — See Topic 4.3 — Hardware Asset Management.

Defense in depth — Layering overlapping administrative, logical, and physical controls so that one failure is not enough. Wikipedia — See Topic 3.13 — Information Security Management.

Definition of Done — The quality standard that work must meet to count as part of a Scrum Increment. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Definition of Workflow (DoW) — In the Kanban Guide, the team's agreed description of its work items, workflow states, work in progress control, policies, and service level expectation. Wikipedia — See Topic 1.5 — Kanban.

Deployment frequency — How often deployments occur (DORA). — See Topic 3.4 — Change Enablement.

DevOps — The integration and automation of software development and IT operations, characterized by shared ownership, workflow automation, and rapid feedback. Wikipedia — See Topic 5.2 — DevOps.

Diffusion of innovations — Everett Rogers's theory of how new ideas spread, with five adopter categories and five attributes that affect the speed of adoption. Wikipedia — See Topic 5.8 — Organizational Change and Adoption.

Disciplined Agile (DA) — A toolkit of process goals and options, owned by the Project Management Institute since August 2019, that helps a team choose its way of working. Wikipedia — See Topic 1.8 — Scaling Agile.

Drift (configuration) — The difference between the intended (declared) state of a system and its actual (discovered) state. — See Topic 4.4 — Configuration Management.

E

Electronic waste (e-waste) — Discarded electrical or electronic devices, including items destined for reuse, resale, recycling, or disposal. Wikipedia — See Topic 4.3 — Hardware Asset Management.

Emergency change — A change that must be made urgently, for example to restore service, with expedited authorization. — See Topic 3.4 — Change Enablement.

Enterprise service management (ESM) — Applying ITSM tools and ideas to other business areas such as human resources or facilities. Wikipedia — See Topic 2.1 — IT Service Management.

Entitlement — What an organization is allowed to use under its contracts and licenses. — See Topic 4.2 — Software Asset Management.

Error budget — The rate at which a service level objective may be missed, used to guide release decisions. — See Topic 3.7 — Service Level Management.

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

Extreme Programming (XP) — An agile method that emphasizes engineering practices such as pair programming, test-driven development, and continuous integration. Wikipedia — See Topic 1.6 — Extreme Programming.

F

FinOps — An operational framework and cultural practice that maximizes the business value of technology through collaboration between engineering, finance, and business teams. — See Topic 4.5 — IT Financial Management and FinOps.

FitSM — A family of lightweight, freely licensed ITSM standards that grew out of the EU-funded FedSM project; organizations cannot be certified as conformant. Wikipedia — See Topic 2.7 — ITSM Frameworks and Standards.

Four dimensions of service management — ITIL 4's checklist of organizations and people; information and technology; partners and suppliers; and value streams and processes. — See Topic 2.5 — Four Dimensions of Service Management.

Four golden signals — Latency, traffic, errors, and saturation: the signals to watch for a user-facing system. — See Topic 3.10 — Monitoring and Event Management.

Futurespective — A forward-looking group exercise that imagines possible futures to inform current decisions; the counterpart of a retrospective. — See Topic 6.1 — Team Conversations.

G

Goodhart's law — The adage that when a measure becomes a target, it ceases to be a good measure. Wikipedia — See Topic 5.6 — Metrics and Measurement.

Governance, risk, and compliance (GRC) — A holistic approach to corporate governance, risk management, and regulatory compliance. Wikipedia — See Topic 5.7 — Governance, Risk, and Compliance.

Guardrail — A limit built into the path of work that keeps it on course without stopping it, such as an automated policy check. — See Topic 5.7 — Governance, Risk, and Compliance.

Guiding principles (ITIL) — Seven recommendations: focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; optimize and automate. — See Topic 2.4 — ITIL Guiding Principles.

H

Hallucination (AI) — An AI response that contains false or misleading information presented as fact. Wikipedia — See Topic 6.2 — AI in IT Service Management.

I

Incident — A disruption or potential disruption in service availability or quality. Wikipedia — See Topic 2.1 — IT Service Management.

Incident commander — The person who holds the high-level state of an incident and coordinates the response. — See Topic 3.2 — Incident Management.

Increment — In Scrum, a usable, verified step toward the Product Goal that adds to all earlier Increments. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Information security — Protecting information by mitigating information risks; its core goals are confidentiality, integrity, and availability. Wikipedia — See Topic 3.13 — Information Security Management.

Infrastructure as code (IaC) — Managing and provisioning resources through machine-readable definition files, often kept in version control. Wikipedia — See Topic 4.4 — Configuration Management.

ISO/IEC 20000 — An international standard for IT service management systems, against which an organization can be certified. Wikipedia — See Topic 2.7 — ITSM Frameworks and Standards.

ISO/IEC 27001 — The standard for information security management systems; organizations can be certified against it. Wikipedia — See Topic 3.13 — Information Security Management.

IT asset management (ITAM) — Business practices that join financial, contractual, and inventory functions to support life cycle management and IT decisions. Wikipedia — See Topic 4.1 — IT Asset Management.

IT service management (ITSM) — The activities an organization performs to design, build, deliver, operate, and control IT services offered to customers. Wikipedia — See Topic 2.1 — IT Service Management.

ITIL — A framework of practices for IT service management and IT asset management; certification is for individuals, not organizations. Wikipedia — See Topic 2.2 — ITIL.

J

K

Kaizen — Continuous, incremental improvement, traced to improvement teams at Toyota in 1936. Wikipedia — See Topic 1.7 — Lean Software Development.

Kanban — A strategy for optimizing the flow of value by visualizing the workflow, limiting work in progress, and improving the workflow. Wikipedia — See Topic 1.5 — Kanban.

Knowledge management — Processing knowledge to accomplish organizational goals: awareness, learning, collaboration, and innovation. Wikipedia — See Topic 3.9 — Knowledge Management.

Known error — A problem whose cause has been identified, usually with a workaround recorded. — See Topic 3.3 — Problem Management.

L

Large-Scale Scrum (LeSS) — A framework by Craig Larman and Bas Vodde that applies Scrum to many teams working on one product with one Product Owner and one Product Backlog. — See Topic 1.8 — Scaling Agile.

Lean coffee — An agenda-less, structured meeting in which participants build an agenda and vote on topics; created in Seattle in 2009 by Jim Benson and Jeremy Lightsmith. — See Topic 6.1 — Team Conversations.

Lean software development — An adaptation of lean manufacturing to software, stated as seven principles by Mary and Tom Poppendieck in 2003. Wikipedia — See Topic 1.7 — Lean Software Development.

Liftoff — The initial stage of an agile project in which a team aligns on vision, objectives, stakeholders, and an initial plan. — See Topic 6.1 — Team Conversations.

M

Muda (waste) — In lean, activity that adds no value for the customer; Shingo's seven wastes are inventory, overproduction, over-processing, transportation, motion, waiting, and defects. Wikipedia — See Topic 1.7 — Lean Software Development.

N

Net promoter score (NPS) — A measure based on one question about likelihood to recommend: percentage of promoters minus percentage of detractors. Wikipedia — See Topic 5.6 — Metrics and Measurement.

NIST AI Risk Management Framework — A voluntary framework, released 26 January 2023, for managing risks from AI to individuals, organizations, and society. — See Topic 6.2 — AI in IT Service Management.

Normal change — A change that needs assessment and authorization before it proceeds. — See Topic 3.4 — Change Enablement.

O

Objectives and key results (OKRs) — A goal-setting framework that pairs an objective with three to five measurable key results. Wikipedia — See Topic 5.6 — Metrics and Measurement.

Open-source software — Software whose source code is publicly available and may be used, studied, modified, and distributed under an open license. Wikipedia — See Topic 4.2 — Software Asset Management.

P

Pair programming — Two programmers working on one task at one workstation, one writing and one reviewing, swapping partners often. Wikipedia — See Topic 1.6 — Extreme Programming.

PDCA — Plan, do, check, act: an iterative method for controlling and continually improving processes and products. Wikipedia — See Topic 3.15 — Continual Improvement.

Permissive license — An open-source license that does not require derivative works to use the same license; examples are BSD, MIT, and Apache. Wikipedia — See Topic 4.2 — Software Asset Management.

PESTLE — A scan of political, economic, social, technological, legal, and environmental factors that affect all four dimensions. Wikipedia — See Topic 2.5 — Four Dimensions of Service Management.

Problem — The underlying cause, or suspected cause, of one or more incidents. — See Topic 3.3 — Problem Management.

Product Backlog — In Scrum, an ordered, evolving list of what the product needs; its commitment is the Product Goal. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Product Owner — In Scrum, the one person accountable for maximizing the value of the product and for ordering the Product Backlog. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Product owner (service owner) — The person accountable for the value of a product or service and for ordering its backlog. — See Topic 5.5 — Product and Service Ownership.

Prompt — The instruction and material given to an AI assistant for one task. Wikipedia — See Topic 6.3 — AI Skills and Prompts.

Pull system — A way of working in which new work starts only when there is capacity for it, produced by limiting work in progress. Wikipedia — See Topic 1.5 — Kanban.

Q

R

Recovery point objective (RPO) — The acceptable amount of data latency: how much data loss is tolerable. Wikipedia — See Topic 3.12 — Service Continuity Management.

Recovery time objective (RTO) — The acceptable time to restore a function after a disruption. Wikipedia — See Topic 3.12 — Service Continuity Management.

Refactoring — Improving the design of code without changing what it does. Wikipedia — See Topic 1.6 — Extreme Programming.

Request model — A repeatable pattern for a type of service request: information needed, approval, steps, and expected time. — See Topic 3.6 — Service Request Management.

Retrieval-augmented generation (RAG) — Letting a language model consult external sources before answering, to ground its output. Wikipedia — See Topic 6.2 — AI in IT Service Management.

Retrospective — A team meeting, often after a period of continuous software delivery, that looks at what went well, what could be improved, and how to apply the lessons. Wikipedia — See Topic 6.1 — Team Conversations.

Risk register — A record of identified risks with description, assessment, owner, treatment, and status. — See Topic 5.7 — Governance, Risk, and Compliance.

Root cause analysis (RCA) — A problem-solving method for finding the fundamental causes of faults; a factor is a root cause if removing it prevents the problem recurring. Wikipedia — See Topic 3.3 — Problem Management.

S

Scaled Agile Framework (SAFe) — A set of organization and workflow patterns for scaling lean and agile practices, published by Scaled Agile, Inc. Wikipedia — See Topic 1.8 — Scaling Agile.

Scrum — A lightweight framework of roles, events, and artifacts that helps people create value through adaptive solutions to complex problems. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Scrum Master — In Scrum, the accountability for establishing Scrum and helping the team and organization understand and apply it. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Scrum of scrums — A light coordination meeting in which representatives of several teams share progress and resolve dependencies. — See Topic 1.8 — Scaling Agile.

Scrumban — A mix of Scrum events and Kanban flow. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Service catalog — A curated collection of the services an organization offers, each with an owner, a description, and how to get help. Wikipedia — See Topic 3.8 — Service Catalog Management.

Service desk — The single point of contact between users or customers and the service provider, handling incidents and service requests. Wikipedia — See Topic 3.1 — Service Desk.

Service integration and management (SIAM) — An approach for managing several suppliers and integrating them into a single, business-facing service. Wikipedia — See Topic 3.14 — Supplier Management.

Service level agreement (SLA) — An agreement, typically a binding contract, between a provider and a customer that defines the service, its quality, and responsibilities. Wikipedia — See Topic 3.7 — Service Level Management.

Service level expectation (SLE) — In Kanban, a forecast of how long a work item should take to flow through the workflow, based on past cycle times; not an agreement. Wikipedia — See Topic 1.5 — Kanban.

Service level indicator (SLI) — A carefully defined quantitative measure of some aspect of the level of service provided. — See Topic 3.7 — Service Level Management.

Service level objective (SLO) — A target value or range for a service level measured by an SLI. Wikipedia — See Topic 3.7 — Service Level Management.

Service request — A routine request for something a service normally provides. Wikipedia — See Topic 2.1 — IT Service Management.

Service value chain — The operating model at the center of the ITIL 4 service value system: plan, improve, engage, design and transition, obtain/build, and deliver and support. — See Topic 2.6 — The Service Value Chain.

Service value system (SVS) — The ITIL 4 model of how guiding principles, governance, the service value chain, practices, and continual improvement turn demand and opportunity into value. — See Topic 2.3 — The ITIL Service Value System.

Showback — Showing consumers what they use and what it costs without billing them. — See Topic 4.5 — IT Financial Management and FinOps.

Site reliability engineering (SRE) — A discipline that applies software engineering to operations to improve the availability and performance of large services. Wikipedia — See Topic 5.3 — Site Reliability Engineering.

Skill (AI) — A reusable package of know-how for a kind of task: a directory with a SKILL.md file whose description says when to use it. — See Topic 6.3 — AI Skills and Prompts.

Software asset management (SAM) — A business practice for managing and optimizing the purchase, deployment, maintenance, use, and disposal of software. Wikipedia — See Topic 4.2 — Software Asset Management.

Software bill of materials (SBOM) — An inventory of the components used to build a software artifact, including open-source and proprietary parts. Wikipedia — See Topic 4.2 — Software Asset Management.

Software supply chain — The components, libraries, tools, and processes used to develop, build, and publish a software artifact. Wikipedia — See Topic 4.2 — Software Asset Management.

Sprint — In Scrum, a fixed timebox of one month or less in which all other events happen. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Sprint Goal — The single objective for a Scrum Sprint; the commitment of the Sprint Backlog. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Sprint Retrospective — The Scrum event in which the team inspects how it worked and plans improvements. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Sprint Review — The Scrum event in which the team shows the Increment to stakeholders and adjusts the Product Backlog. Wikipedia — See Topic 1.4 — Delivery Forecasting and Planning Metrics.

Standard change — A low-risk, well-understood change that follows a documented procedure and is pre-authorized. — See Topic 3.4 — Change Enablement.

Statement of Applicability — In ISO/IEC 27001, the document that justifies which Annex A controls an organization includes and excludes. Wikipedia — See Topic 3.13 — Information Security Management.

Supplier relationship management (SRM) — Systematic assessment of suppliers' strengths, performance, and capabilities, coordinating interactions across the relationship life cycle. Wikipedia — See Topic 3.14 — Supplier Management.

Sustainable pace — An Extreme Programming practice (also an agile principle) of avoiding regular overtime so that people stay effective over years. Wikipedia — See Topic 1.6 — Extreme Programming.

T

Tacit knowledge — Knowledge that is internalized and often not consciously known, so hard to write down. Wikipedia — See Topic 3.9 — Knowledge Management.

Technical debt — The future cost of rework caused by choosing a quick solution now instead of a better one. Wikipedia — See Topic 1.2 — Agile Principles.

Test-driven development (TDD) — Writing a failing test first, then just enough code to make it pass. Wikipedia — See Topic 1.6 — Extreme Programming.

The Three Ways — Gene Kim's three principles of DevOps: flow, feedback, and continual learning and experimentation. — See Topic 5.2 — DevOps.

Throughput — In Kanban, the number of work items finished in a period. Wikipedia — See Topic 1.5 — Kanban.

Toil — Operational work that is manual, repetitive, automatable, tactical, without enduring value, and growing linearly with the service (SRE usage). — See Topic 5.3 — Site Reliability Engineering.

U

Underpinning contract — In ITIL vocabulary, an agreement with an outside supplier that supports a service level agreement. — See Topic 3.14 — Supplier Management.

Unit cost — Cost divided by a business measure such as transactions, users, or services. — See Topic 4.5 — IT Financial Management and FinOps.

V

Value stream — A specific set of activities that create and deliver a particular service or product to customers; a path through the service value chain. — See Topic 5.4 — Value Stream Management; also Topic 2.6 — The Service Value Chain.

Value stream management — Managing the flow of work across all the teams in a value stream using shared measures, a named owner, and regular review. Wikipedia — See Topic 5.4 — Value Stream Management.

Value stream mapping — A technique that shows each step from request to delivered value with working time and waiting time, used to find waste. Wikipedia — See Topic 1.7 — Lean Software Development.

Value-stream mapping — A lean technique that maps current and future states of the steps taking a product or service to the customer, with time and volume at each stage. Wikipedia — See Topic 5.4 — Value Stream Management.

W

Waterfall model — A plan-driven approach that completes each phase of a project before the next begins. Wikipedia — See Topic 1.3 — Agile Software Development.

Work in progress (WIP) — The number of items started but not yet finished; limiting it creates a pull system. Wikipedia — See Topic 1.5 — Kanban.

Work item age — In Kanban, the time elapsed since an unfinished item started. Wikipedia — See Topic 1.5 — Kanban.

Work-in-process limit — A cap on how many items can be in a stage of a workflow at one time. — See Topic 5.4 — Value Stream Management.

Workaround — A way to reduce or avoid the impact of an incident or problem without removing its cause. — See Topic 3.3 — Problem Management.

Working agreement — A short set of rules a team writes for itself about how it will work together. — See Topic 6.1 — Team Conversations.

X

Y

Z