Your FREE ITIL 4 Foundation Flashcards 2026 – 250+ Cards

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.

A set of specialized organizational capabilities for enabling value for customers in the form of services.

The perceived benefits, usefulness, and importance of something. Value is subjective, co-created, and depends on the perspective of the stakeholder.

Value is no longer delivered one-way by a provider; it emerges from an active collaboration between providers and consumers (and other stakeholders).

A person or a group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives.

A role an organization takes when it provides services to consumers.

A generic role used to define the roles of customer, user, and sponsor — the organization that receives or uses services.

Customer: defines requirements and is responsible for outcomes. User: uses the service. Sponsor: authorizes the budget for service consumption.

A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.

A person who uses services.

A person who authorizes the budget for service consumption.

A result for a stakeholder enabled by one or more outputs. Outcomes are what the consumer wants; outputs are the deliverables.

A tangible or intangible deliverable of an activity. Outputs help achieve outcomes but are not the outcomes themselves.

An output is a deliverable (e.g., a report). An outcome is the result the stakeholder wants enabled by that output (e.g., a faster decision).

The amount of money spent on a specific activity or resource. Services can remove costs from a consumer or impose costs on a consumer.

A possible event that could cause harm or loss, or make it more difficult to achieve objectives. Services can remove or impose risks on a consumer.

The functionality offered by a product or service to meet a particular need — 'what the service does' (fitness for purpose).

Assurance that a product or service will meet agreed requirements — 'how the service performs' (fitness for use), covering availability, capacity, security, and continuity.

Utility = fit for purpose (what it does); warranty = fit for use (how well it performs). Both are required for a service to be valuable.

A description of one or more services designed to address the needs of a target consumer group, including goods, access to resources, and service actions.

Goods (supplied to the consumer), access to resources (granted under agreed conditions), and service actions (performed to address consumer needs).

A cooperation between a service provider and service consumer, including service provision, service consumption, and service relationship management.

Activities performed by an organization to provide services: managing resources, providing access, fulfilling agreed actions, and managing service performance.

Activities performed by an organization to consume services: using resources, performing actions, and receiving (acquiring) goods.

Joint activities performed by a provider and a consumer to ensure continual value co-creation based on agreed and available service offerings.

A provider takes on specified costs and risks on the consumer's behalf, letting the consumer focus on its desired outcomes.

Yes. A service can also impose new costs or risks on the consumer (e.g., training, downtime), which must be weighed against the value gained.

A configuration of an organization's resources designed to offer value for a consumer. Products are typically not consumed directly; service offerings are based on products.

A person or organization that has an interest in an activity, project, or organization — including customers, users, sponsors, employees, suppliers, and partners.

The idea that value is not delivered one-directionally but emerges through the active collaboration of providers, consumers, and other stakeholders in a service relationship.

Any financially valuable component that can contribute to the delivery of an IT product or service. (One of the 7 syllabus key terms.)

Any component that needs to be managed in order to deliver an IT service. (One of the 7 syllabus key terms.)

The addition, modification, or removal of anything that could have a direct or indirect effect on services. (One of the 7 syllabus key terms.)

An unplanned interruption to a service, or a reduction in the quality of a service. (One of the 7 syllabus key terms.)

A cause, or potential cause, of one or more incidents. (One of the 7 syllabus key terms.)

A problem that has been analyzed but has not been resolved. (One of the 7 syllabus key terms.)

Any change of state that has significance for the management of a service or other configuration item. (One of the 7 syllabus key terms.)

Costs removed from the consumer by the service (part of the value), and costs imposed on the consumer by the service (a trade-off against the value).

Risks removed from the consumer by the service (part of the value), and risks imposed on the consumer by the service.

Subjective — value depends on the perception and desired outcomes of the stakeholder, so the same output can represent different value to different consumers.

A service is only valuable (fit for use) when it has BOTH adequate utility (it does what's needed) AND adequate warranty (it performs reliably enough).

An action performed by a provider to address a consumer's need, performed according to an agreement with the consumer (part of a service offering).

Granting a consumer agreed access to resources such as networks, storage, or computing power under defined terms and conditions.

Items supplied to the consumer where ownership is transferred and the consumer takes responsibility for their future use.

Because a single person or organization can be customer, user, and sponsor at once, or these can be different parties — the generic role keeps the model flexible.

Provision = the provider's activities to supply a service (resources, access, actions, levels). Consumption = the consumer's activities to use it (using resources, requesting actions, receiving goods).

Another name for utility — the service does what is needed, supporting performance or removing a constraint for the consumer.

Another name for warranty — the service performs reliably enough, covering availability, capacity, security, and continuity.

No — the defining feature of a service is that the provider takes on specified costs and risks so the consumer can focus on its outcomes.

The customer — the role that defines requirements and takes responsibility for the outcomes of service consumption.

Organizations and people; Information and technology; Partners and suppliers; Value streams and processes.

All four must be considered for every service so it remains effective and balanced; ignoring a dimension can degrade or fail the service.

Covers structures, roles, responsibilities, culture, skills, and competencies needed to create and deliver value.

Covers the information, knowledge, and technologies (applications, databases, AI, cloud, etc.) used to manage and deliver services.

Covers an organization's relationships with other organizations involved in designing, developing, deploying, delivering, supporting, or improving services.

Covers how the various parts of the organization work together (the activities, workflows, controls, and procedures) to enable value creation.

A series of steps an organization undertakes to create and deliver products and services to a service consumer.

A set of interrelated activities that transform inputs into outputs; a process defines the sequence of actions and their dependencies.

Political, Economic, Social, Technological, Legal, and Environmental factors that constrain or influence how the four dimensions are addressed.

Political, Economic, Social, Technological, Legal, Environmental — the external factors affecting service management.

An organization's approach to partners and suppliers, ranging from insourcing to outsourcing to a service integration (SIAM) model.

An approach to managing multiple suppliers and integrating them to deliver a single, business-facing service.

The four dimensions apply to the entire service value system and to every component within it; each dimension is relevant to all SVS activities.

Service delivery becomes unbalanced and may fail — e.g., great technology with no skilled people, or a good process with an unmanaged supplier.

Organizations and people — it includes structures, roles, responsibilities, leadership, and the culture and competencies of staff.

Information and technology — the information and knowledge needed, plus the technologies (and their relationships) used to deliver and manage services.

Partners and suppliers — relationships with other organizations involved in designing, deploying, delivering, supporting, or improving services.

Value streams and processes — how the parts of the organization work together in a coordinated way to enable value through products and services.

Yes — they are interconnected and overlapping; each must be considered together for any service, alongside the external PESTLE factors.

Often remembered as O-I-P-V: Organizations & people, Information & technology, Partners & suppliers, Value streams & processes.

Outside — PESTLE factors are external; the organization cannot fully control them and must respond to them across all four dimensions.

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.

Everything the organization does should map, directly or indirectly, to value for stakeholders. Know who is being served and what their desired outcomes are.

Do not start from scratch; assess and reuse what already exists (services, processes, people, tools). Measure the current state with objective data.

Organize work into smaller, manageable sections that can be executed and completed in a timely manner; use feedback before, during, and after each iteration.

Working together across boundaries produces better buy-in, relevance, and success. Making work visible reduces the cost of poor information and builds trust.

No service, practice, process, or component stands alone. Take an integrated, end-to-end view; outcomes suffer when parts are managed in isolation.

Use the minimum number of steps needed to accomplish an objective. Eliminate anything that does not add value; design for outcomes.

Optimize work before automating it; do not automate a flawed process. Use technology to do what it can, freeing people for complex decision-making.

A recommendation that guides an organization in all circumstances, regardless of changes in goals, strategies, type of work, or management structure.

Yes — they are universal and enduring. They apply to virtually any initiative and to all relationships with stakeholders.

Start where you are — assess and reuse existing services, processes, and tools rather than building from scratch.

Progress iteratively with feedback — small iterations with feedback before, during, and after each step.

Optimize and automate — optimize the process first; automating an inefficient process just makes it fail faster.

Think and work holistically — services and their parts work together as a system, not in silos.

Keep it simple and practical — use the fewest steps necessary and remove anything that does not contribute to value.

Organizations should not use just one or two; consider the relevance of each principle and how they apply together to a given situation.

Seven — focus on value, start where you are, progress iteratively with feedback, collaborate and promote visibility, think and work holistically, keep it simple and practical, and optimize and automate.

Focus on value — every activity should map, directly or indirectly, to value for a stakeholder.

First understand and agree the context and objectives, then optimize the work (make it effective and useful), and only then automate — never automate a poor process.

Buy-in, relevance to objectives, and the likelihood of long-term success; reducing hidden work lowers the cost of poor information and improves trust.

Smaller iterations are easier to manage, deliver value sooner, allow feedback to keep work relevant, and reduce the risk of large-scale failure.

Start where you are — observe and measure the current state directly, because much of what already exists can often be reused and built upon.

Value, Start, Iterate, Collaborate, Holistic, Simple, Automate — focus on value; start where you are; progress iteratively; collaborate & promote visibility; think holistically; keep it simple; optimize & automate.

Start where you are — assess the current state objectively and reuse existing services, processes, people, and tools where possible.

A model showing how all the components and activities of an organization work together to facilitate value creation through IT-enabled services.

Guiding principles, governance, the service value chain, practices, and continual improvement.

Input: opportunity and demand. Output: value. The SVS converts demand and opportunity into value.

Opportunity represents options to add value for stakeholders or improve the organization; demand is the need or desire for products and services.

The means by which an organization is directed and controlled — evaluating, directing, and monitoring activities and performance.

A recurring organizational activity performed at all levels to ensure performance continually meets stakeholder expectations; it surrounds the whole SVS.

An operating model within the SVS — a set of six interconnected activities an organization performs to create value through products and services.

Plan; Improve; Engage; Design and transition; Obtain/build; Deliver and support.

Ensures a shared understanding of the vision, current status, and improvement direction for all four dimensions and all products and services.

Ensures continual improvement of products, services, and practices across all value-chain activities and the four dimensions.

Provides a good understanding of stakeholder needs, transparency, and continual engagement with all stakeholders.

Ensures products and services continually meet stakeholder expectations for quality, costs, and time to market.

Ensures service components are available when and where they are needed and meet agreed specifications.

Ensures services are delivered and supported according to agreed specifications and stakeholders' expectations.

No. The six activities combine in many different sequences to form value streams; their order depends on the work being done.

A specific combination of value-chain activities and practices designed for a particular scenario, converting demand into value.

Each value-chain activity draws on a different combination of the 34 ITIL practices to perform its work; practices are sets of resources for doing work.

A set of organizational resources designed for performing work or accomplishing an objective. ITIL 4 defines 34 management practices.

The four dimensions are relevant to and apply across all six service value chain activities.

Its flexible structure (principles, governance, value chain, practices, improvement) lets organizations respond to changing demand and opportunities in many ways.

The guiding principles and continual improvement apply across the entire service value system and every component within it.

The service value chain — the central operating model of the SVS — using practices and the guiding principles, under governance.

To evaluate, direct, and monitor the organization's activities, ensuring they align with policies, objectives, and stakeholder needs.

Practices are SVS components — sets of resources that the service value chain activities draw on to perform work.

No. The six activities are flexible and combine in different sequences to form value streams suited to particular scenarios.

A specific sequence of service value chain activities and the practices they use, designed to convert demand or opportunity into value.

Engage — it ensures understanding of stakeholder needs, transparency, and continual relationships with all stakeholders.

Obtain/build — it ensures service components are available where and when needed and meet agreed specifications.

Deliver and support — it ensures services are delivered and supported to agreed specifications and stakeholder expectations.

Guiding principles, governance, the service value chain, practices, and continual improvement — together converting opportunity/demand into value.

There is no fixed first/last — but Plan sets direction and Improve runs continuously; Engage often starts demand and Deliver & support runs the live service.

They guide decision-making throughout the SVS and apply to every component and activity within it.

34 practices, grouped into three categories: general management (14), service management (17), and technical management (3).

General management practices (14), service management practices (17), and technical management practices (3).

Aligns the organization's practices and services with changing business needs through ongoing improvement of products, services, and practices. One of the 7 deep-dive practices.

A 7-step approach: What is the vision? Where are we now? Where do we want to be? How do we get there? Take action; Did we get there? How do we keep the momentum going?

A database or structured document used to track and manage improvement ideas from identification through to action.

Everyone. Continual improvement is everyone's responsibility, though a dedicated team may coordinate and embed it.

Protects the information needed by the organization to conduct its business — confidentiality, integrity, and availability (CIA), plus authentication and non-repudiation.

Establishes and nurtures links between the organization and its stakeholders at strategic and tactical levels.

Ensures the organization's suppliers and their performance are managed appropriately to support seamless, quality products and services.

To get value for money from suppliers, create closer relationships, and manage risk through the supplier lifecycle (evaluation, contracting, performance, renewal).

Supports decision-making by ensuring the organization's financial resources and investments are used effectively (budgeting, accounting, charging).

Ensures the organization has the right people with the right skills and knowledge, in the right roles, to support its objectives.

Provides an understanding of all the different elements that make up an organization and how they interrelate (business, service, information, technology, environment architectures).

Ensures that all of an organization's projects are successfully delivered, balancing scope, schedule, cost, quality, resources, and risk.

Ensures the organization understands and effectively handles risk; risk is essential to but must be balanced against value.

Ensures the organization has the right mix of programs, projects, products, and services to execute its strategy within funding and resource constraints.

Maintains and improves the effective, efficient, and convenient use of information and knowledge across the organization.

Supports good decision-making and continual improvement by decreasing uncertainty through the collection of relevant data and its assessment.

Ensures that changes in an organization are smoothly and successfully implemented, and that lasting benefits are achieved by managing the human aspects of change.

Formulates the goals of an organization and adopts the courses of action and allocation of resources necessary to achieve them.

Service desk is a service management practice (capturing demand for incidents/requests); information security is a general management practice (protecting information).

(1) What is the vision? (2) Where are we now? (3) Where do we want to be? (4) How do we get there? (5) Take action; (6) Did we get there? (7) How do we keep the momentum going?

Confidentiality, Integrity, Availability — the core objectives of information security management (often extended with authentication and non-repudiation).

To protect the information the organization needs to conduct its business — its confidentiality, integrity, and availability.

To establish and nurture the links between the organization and its stakeholders at strategic and tactical levels.

To ensure suppliers and their performance are managed appropriately to support the seamless provision of quality products and services.

Information security management, relationship management, and supplier management (the three general management practices examined at purpose level on Foundation).

Because improvement opportunities arise everywhere; a small central team coordinates and embeds the practice, but all staff are expected to contribute.

A practice is a set of organizational resources (people, info, tools, value streams) for doing work; a process is a set of activities transforming inputs to outputs — practices may include processes.

To provide an understanding of all the different elements that make up an organization and how they interrelate.

To maintain and improve the effective, efficient, and convenient use of information and knowledge across the organization.

To support good decision-making and continual improvement by decreasing uncertainty through the collection and assessment of relevant data.

To ensure changes in an organization are smoothly and successfully implemented, and lasting benefits achieved by managing the people side of change.

To ensure the organization has the right mix of programs, projects, products, and services to execute its strategy within funding and resource constraints.

To ensure all of an organization's projects are successfully delivered.

To ensure the organization understands and effectively handles risk.

To support strategies and plans for service management by ensuring financial resources and investments are used effectively.

To formulate the goals of the organization and adopt the courses of action and allocation of resources necessary to achieve those goals.

To ensure the organization has the right people with the appropriate skills and knowledge in the correct roles.

Automation locks in a process; if the process is wasteful, automating it just produces poor results faster and at scale.

A tool — the CIR is a database/structured document used to capture and track improvement ideas; it is not a step of the improvement model.

Captures demand for incident resolution and service requests; it is the single, central point of contact between the provider and its users. One of the 7 deep-dive practices.

Provides a clear path for users to report issues, ask questions, and make requests; it has a major impact on user experience and satisfaction.

Increasingly, no — it needs strong empathy, communication, and incident-triage skills; the practical/emotional intelligence matters as much as technical knowledge.

Minimizes the negative impact of incidents by restoring normal service operation as quickly as possible. One of the 7 deep-dive practices.

An unplanned interruption to a service, or reduction in the quality of a service.

By impact and urgency, often using a priority matrix; the highest-impact, most-urgent incidents are resolved first, frequently via target resolution times.

An incident with significant business impact requiring a coordinated, often separate, resolution procedure and faster timescales.

Reduces the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors. One of the 7 deep-dive practices.

A cause, or potential cause, of one or more incidents.

A problem that has been analyzed but not resolved. Documenting known errors and workarounds speeds future incident resolution.

A solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available.

Problem identification, problem control (analysis, documenting known errors/workarounds), and error control (managing known errors and possible permanent fixes).

An incident is the interruption itself; a problem is the underlying cause of one or more incidents.

Supports the agreed quality of a service by handling all predefined, user-initiated service requests effectively and user-friendly. One of the 7 deep-dive practices.

A request from a user (or their authorized representative) that initiates a service action which has been agreed as a normal part of service delivery.

A service request is a normal, predefined, planned part of service delivery; an incident is an unplanned interruption or quality reduction.

Requests are predefined and repeatable, so they should be standardized and automated to the greatest degree possible for speed and consistency.

Maximizes the number of successful service and product changes by ensuring risks are properly assessed, changes are authorized, and the schedule is managed. One of the 7 deep-dive practices.

The addition, modification, or removal of anything that could have a direct or indirect effect on services.

Standard changes (low-risk, pre-authorized), normal changes (assessed/authorized via a change schedule), and emergency changes (must be implemented as soon as possible).

A low-risk, pre-authorized change that is well understood and fully documented and can be implemented without additional authorization.

A change that must be scheduled, assessed, and authorized following a standard process; ranges from minor to major.

A change that must be implemented as soon as possible (e.g., to resolve an incident or apply a security patch); assessment may be expedited.

The person or group that authorizes a change. ITIL 4 de-emphasizes a single change advisory board (CAB) in favor of appropriate, often decentralized, change authorities.

Sets clear, business-based targets for service performance so that delivery can be properly assessed, monitored, and managed against them. One of the 7 deep-dive practices.

A documented agreement between a service provider and a customer that identifies both the services required and the expected level of service.

It relates to a defined service, reflects an agreement (engagement and discussion), is simply written and easy to understand, and uses outcome-based metrics.

When SLA metrics look green on the outside but the customer experience is red inside — a sign metrics don't reflect real outcomes.

Provides a single source of consistent information on all services and service offerings, available to the relevant audience.

Ensures accurate and reliable information about the configuration of services, and the CIs that support them, is available when and where needed.

Any component that needs to be managed in order to deliver an IT service.

A database used to store configuration records (CIs) and their relationships throughout their lifecycle.

Effective handling of predefined requests improves user satisfaction and frees specialized resources to focus on complex incidents and problems.

Ensures that services deliver agreed levels of availability to meet the needs of customers and users.

Ensures that services achieve agreed and expected performance, cost-effectively satisfying current and future demand.

Ensures that the availability and performance of a service are maintained at a sufficient level in case of a disaster (business continuity / disaster recovery).

Systematically observes services and CIs, records and reports selected changes of state (events), and identifies and prioritizes those that require action.

Any change of state that has significance for the management of a service or other configuration item.

Makes new and changed services and features available for use. A release can be planned, scheduled, and controlled.

A version of a service or other configuration item, or a collection of configuration items, that is made available for use.

Ensures that new or changed products and services meet defined requirements for both utility and warranty.

Designs products and services that are fit for purpose, fit for use, and that can be delivered by the organization and its ecosystem.

Analyzes a business or some element of it, defines its needs, and recommends solutions that deliver value to stakeholders.

Continual improvement, Change enablement, Incident management, Problem management, Service request management, Service desk, and Service level management.

Release management makes features available for use; deployment management moves new/changed components into live (or other) environments.

To plan and manage the full lifecycle of all IT assets, helping maximize value, control costs, manage risks, and support decision-making about reuse and disposal.

To systematically observe services and CIs, and record and report selected changes of state identified as events.

Informational events (no action needed), warning events (something approaching a threshold), and exception events (a breach requiring action).

To make new and changed services and features available for use.

To ensure that accurate and reliable information about the configuration of services, and the CIs that support them, is available when and where it is needed.

Change enablement, incident management, problem management, service request management, service desk, and service level management (plus continual improvement, a general practice).

To maximize the number of successful service and product changes by ensuring risks are assessed, changes authorized, and the change schedule managed.

To minimize the negative impact of incidents by restoring normal service operation as quickly as possible.

To reduce the likelihood and impact of incidents by identifying actual and potential causes and managing workarounds and known errors.

To support the agreed quality of a service by handling all predefined, user-initiated service requests effectively and in a user-friendly manner.

To capture demand for incident resolution and service requests; it is the entry point and single point of contact for users.

To set clear, business-based targets for service performance so delivery can be properly assessed, monitored, and managed against them.

Through standardized, often automated, models or known-error records, freeing skilled staff to focus on complex or high-impact incidents.

A collaborative technique where multiple stakeholders work together on an incident until it's clear who is best placed to continue, then the rest disengage.

To ensure that services deliver agreed levels of availability to meet the needs of customers and users.

To ensure services achieve agreed and expected performance, satisfying current and future demand cost-effectively.

To ensure availability and performance are maintained at sufficient levels in case of a disaster, supporting overall business continuity.

To provide a single source of consistent information on all services and service offerings, available to the relevant audience.

To design products and services that are fit for purpose, fit for use, and that can be delivered by the organization and its ecosystem.

To analyze a business or element of it, define associated needs, and recommend solutions that enable the organization to add value to stakeholders.

To ensure new or changed products and services meet defined requirements for utility and warranty.

A measurable commitment within an SLA, ideally outcome-based and tied to the user experience, against which performance is judged.

A single technical metric (e.g., uptime) can look healthy while user experience is poor — the 'watermelon' effect. Use a balanced set of outcome-based metrics.

It de-emphasizes a single, heavyweight CAB in favor of appropriate, often decentralized change authorities suited to the change type and risk.

Standard = low-risk, pre-authorized, repeatable. Normal = scheduled, assessed, and authorized via a process. Emergency = must be done ASAP, with expedited assessment.

A user (or authorized representative) requesting something predefined and agreed as a normal part of service delivery — not an interruption.

So they can be reused to restore service quickly for future incidents caused by the same problem, even before a permanent fix exists.

Identification = finding/logging problems. Problem control = analysis and documenting known errors/workarounds. Error control = managing known errors and assessing permanent fixes.

The service desk — the central channel through which users report incidents, ask questions, and make service requests.

No — it also captures demand, coordinates with other practices, communicates with users, and shapes the user experience and perception of the provider.

Engagement and agreement with the customer, a defined service, simple clear language, and metrics that reflect the actual customer/user experience.

Monitoring observes states continuously; event management then filters and prioritizes the significant changes of state (events) that require a response.

A major incident has significant business impact and uses a separate, coordinated, faster procedure; a normal incident follows the standard incident process.

Incident management restores service fast (often via workarounds); problem management investigates underlying causes to prevent recurrence — they work closely together.

Because requests are predefined and repeatable, standardization and automation improve speed, consistency, and user satisfaction while freeing specialist staff.

Deployment management; Infrastructure and platform management; Software development and management.

Moves new or changed hardware, software, documentation, processes, or any other component to live (or other) environments.

Phased deployment, continuous delivery, big bang deployment, and pull deployment — chosen based on risk, speed, and environment.

Oversees the infrastructure and platforms used by an organization, enabling the monitoring of technology solutions including cloud.

Ensures applications meet stakeholder needs in terms of functionality, reliability, maintainability, compliance, and auditability.

Deployment management moves components into an environment; release management controls when functionality is made available to users. They often work together.

Deployments are usually authorized through change enablement; deployment management performs the technical move once the change is approved.

It lets organizations deploy code to production without exposing the feature to users (e.g., feature flags), supporting modern continuous-delivery practices.

Deployment management — the technical management practice examined at purpose level on Foundation.

Releasing to part of the production environment or user base at a time, then expanding in stages to control risk.

Deploying the new or changed component to all targets at once; higher risk but sometimes necessary.

Making new/changed software available in a controlled repository, and letting users or devices download (pull) it when ready.

An automated approach where changes are deployed frequently and reliably through an integrated pipeline.

To oversee the infrastructure and platforms used by an organization, enabling monitoring of technology solutions, including those of external and cloud services.

To ensure applications meet internal and external stakeholder needs for functionality, reliability, maintainability, compliance, and auditability.

They are distinct: deployment moves components into an environment; release controls when functionality becomes available to users. Modern practice deliberately decouples them.

Phased deployment — rolling out to part of the environment or user base first, then expanding once it proves stable.