ITIL Foundation 4e by Axelos

From CNM Wiki
Revision as of 18:07, 27 December 2020 by Gary (talk | contribs)
Jump to: navigation, search

ITIL Foundation 4e by Axelos (hereinafter, the Publication) is the 4th edition of the ITIL® Foundation copyrighted by AXELOS Limited and published in 2019. The Publication provides the scope for the ITIL 4 Foundation certification. 


o The purpose of the ITIL 4 Foundation publication is to introduce readers to the management of the modern IT-enabled services, provide them with an understanding of the common language and key concepts and show them how they can improve their work and the work of their organization with ITIL 4 guidance
● The Need for Service Management
o Technology is advancing faster today than ever before. Developments such as cloud computing, infrastructure as a service, machine learning, and blockchain, have opened fresh opportunities for value creation, and led to IT becoming an important business driver and source of competitive advantage.
▪ Every organization is a service organization
▪ Almost all services today are IT enabled
▪ Service management is defined as a set of specialized organizational capabilities for enabling value to customers in the form of services.

Key concepts

Service Management

Main wikipage: Service management

Four Dimensions

Main wikipage: Four dimensions of service management

Value System

Main wikipage: Service value system

Guiding Principles

Main wikipage: ITIL guiding principles

Value Chain

Main wikipage: ITIL service value chain

Practices

Main wikipage: ITIL practices
  • Acceptance criteria. A list of minimum requirements that a service or service component must meet for it to be acceptable to key stakeholders.
  • Agile. An umbrella term for a collection of frameworks and techniques that together enable teams and individuals to work in a way that is typified by collaboration, prioritization, iterative and incremental delivery, and timeboxing. There are several specific methods (or frameworks) that are classed as Agile, such as Scrum, Lean, and Kanban.
  • Architecture management practice. The practice of providing an understanding of all the different elements that make up an organization and how those elements relate to one another.
  • Asset register. A database or list of assets, capturing key attributes such as ownership and financial value.
  • Availability. The ability of an IT service or other configuration item to perform its agreed function when required.
  • Availability management practice. The practice of ensuring that services deliver agreed levels of availability to meet the needs of customers and users.
  • Baseline. A report or metric that serves as a starting point against which progress or change can be assessed.
  • Best practice. A way of working that has been proven to be successful by multiple organizations.
  • Big data. The use of very large volumes of structured and unstructured data from a variety of sources to gain new insights.
  • Business analysis practice. The practice of analysing a business or some element of a business, defining its needs and recommending solutions to address these needs and/or solve a business problem, and create value for stakeholders.
  • Business case. A justification for expenditure of organizational resources, providing information about costs, benefits, options, risks, and issues.
  • Business impact analysis (BIA). A key activity in the practice of service continuity management that identifies vital business functions and their dependencies.
  • Business relationship manager (BRM). A role responsible for maintaining good relationships with one or more customers.
  • Call. An interaction (e.g. a telephone call) with the service desk. A call could result in an incident or a service request being logged.
  • Call/contact centre. An organization or business unit that handles large numbers of incoming and outgoing calls and other interactions.
  • Capability. The ability of an organization, person, process, application, configuration item, or IT service to carry out an activity.
  • Capacity and performance management practice. The practice of ensuring that services achieve agreed and expected performance levels, satisfying current and future demand in a cost-effective way.
  • Capacity planning. The activity of creating a plan that manages resources to meet demand for services.
  • Change. The addition, modification, or removal of anything that could have a direct or indirect effect on services.
  • Change authority. A person or group responsible for authorizing a change.
  • Change control practice. The practice of ensuring that risks are properly assessed, authorizing changes to proceed and managing a change schedule in order to maximize the number of successful service and product changes.
  • Change model. A repeatable approach to the management of a particular type of change.
  • Change schedule. A calendar that shows planned and historical changes.
  • Charging. The activity that assigns a price for services.
  • Cloud computing. A model for enabling on-demand network access to a shared pool of configurable computing resources that can be rapidly provided with minimal management effort or provider interaction.
  • Compliance. The act of ensuring that a standard or set of guidelines is followed, or that proper, consistent accounting or other practices are being employed.
  • Confidentiality. A security objective that ensures information is not made available or disclosed to unauthorized entities.
  • Configuration. An arrangement of configuration items (CIs) or other resources that work together to deliver a product or service. Can also be used to describe the parameter settings for one or more CIs.
  • Configuration item (CI). Any component that needs to be managed in order to deliver an IT service.
  • Configuration management database (CMDB). A database used to store configuration records throughout their lifecycle. The CMDB also maintains the relationships between configuration records.
  • Configuration management system (CMS). A set of tools, data, and information that is used to support service configuration management.
  • Configuration record. A record containing the details of a configuration item (CI). Each configuration record documents the lifecycle of a single CI. Configuration records are stored in a configuration management database.
  • Continual improvement practice. The practice of aligning an organization's practices and services with changing business needs through the ongoing identification and improvement of all elements involved in the effective management of products and services.
  • Continuous deployment. An integrated set of practices and tools used to deploy software changes into the production environment. These software changes have already passed pre-defined automated tests.
  • Continuous integration/continuous delivery. An integrated set of practices and tools used to merge developers' code, build and test the resulting software, and package it so that it is ready for deployment.
  • Control. The means of managing a risk, ensuring that a business objective is achieved, or that a process is followed.
  • Cost. The amount of money spent on a specific activity or resource.
  • Cost centre. A business unit or project to which costs are assigned.
  • Critical success factor (CSF). A necessary precondition for the achievement of intended results.
  • Culture. A set of values that is shared by a group of people, including expectations about how people should behave, ideas, beliefs, and practices.
  • Customer. A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.
  • Customer experience (CX). The sum of functional and emotional interactions with a service and service provider as perceived by a service consumer.
  • Dashboard. A real-time graphical representation of data.
  • Deliver and support. The value chain activity that ensures services are delivered and supported according to agreed specifications and stakeholders' expectations.
  • Demand. Input to the service value system based on opportunities and needs from internal and external stakeholders.
  • Deployment. The movement of any service component into any environment.
  • Deployment management practice. The practice of moving new or changed hardware, software, documentation, processes, or any other service component to live environments.
  • Design and transition. The value chain activity that ensures products and services continually meet stakeholder expectations for quality, costs, and time to market.
  • Design thinking. A practical and human-centred approach used by product and service designers to solve complex problems and find practical and creative solutions that meet the needs of an organization and its customers.
  • Development environment. An environment used to create or modify IT services or applications.
  • DevOps. An organizational culture that aims to improve the flow of value to customers. DevOps focuses on culture, automation, Lean, measurement, and sharing (CALMS).
  • Digital transformation. The evolution of traditional business models to meet the needs of highly empowered customers, with technology playing an enabling role.
  • Disaster. A sudden unplanned event that causes great damage or serious loss to an organization. A disaster results in an organization failing to provide critical business functions for some predetermined minimum period of time.
  • Disaster recovery plans. A set of clearly defined plans related to how an organization will recover from a disaster as well as return to a pre-disaster condition, considering the four dimensions of service management.
  • Driver. Something that influences strategy, objectives, or requirements.
  • Effectiveness. A measure of whether the objectives of a practice, service or activity have been achieved.
  • Efficiency. A measure of whether the right amount of resources have been used by a practice, service, or activity.
  • Emergency change. A change that must be introduced as soon as possible.
  • Engage. The value chain activity that provides a good understanding of stakeholder needs, transparency, continual engagement, and good relationships with all stakeholders.
  • Environment. A subset of the IT infrastructure that is used for a particular purpose, for example a live environment or test environment. Can also mean the external conditions that influence or affect something.
  • Error. A flaw or vulnerability that may cause incidents.
  • Error control. Problem management activities used to manage known errors.
  • Escalation. The act of sharing awareness or transferring ownership of an issue or work item.
  • Event. Any change of state that has significance for the management of a service or other configuration item.
  • External customer. A customer who works for an organization other than the service provider.
  • Failure. A loss of ability to operate to specification, or to deliver the required output or outcome.
  • Four dimensions of service management. The four perspectives that are critical to the effective and efficient facilitation of value for customers and other stakeholders in the form of products and services.
  • Goods. Tangible resources that are transferred or available for transfer from a service provider to a service consumer, together with ownership and associated rights and responsibilities.
  • Governance. The means by which an organization is directed and controlled.
  • Identity. A unique name that is used to identify and grant system access rights to a user, person, or role.
  • Improve. The value chain activity that ensures continual improvement of products, services, and practices across all value chain activities and the four dimensions of service management.
  • Incident. An unplanned interruption to a service or reduction in the quality of a service.
  • Incident management. The practice of minimizing the negative impact of incidents by restoring normal service operation as quickly as possible.
  • Information and technology. One of the four dimensions of service management. It includes the information and knowledge used to deliver services, and the information and technologies used to manage all aspects of the service value system.
  • Information security management practice. The practice of protecting an organization by understanding and managing risks to the confidentiality, integrity, and availability of information.
  • Information security policy. The policy that governs an organization's approach to information security management.
  • Infrastructure and platform management practice. The practice of overseeing the infrastructure and platforms used by an organization. This enables the monitoring of technology solutions available, including solutions from third parties.
  • Integrity. A security objective that ensures information is only modified by authorized personnel and activities.
  • Feedback loop. A technique whereby the outputs of one part of a system are used as inputs to the same part of the system.
  • Internal customer. A customer who works for the same organization as the service provider.
  • Internet of Things. The interconnection of devices via the internet that were not traditionally thought of as IT assets, but now include embedded computing capability and network connectivity.
  • IT asset. Any financially valuable component that can contribute to the delivery of an IT product or service.
  • IT asset management practice. The practice of planning and managing the full lifecycle of all IT assets.
  • IT infrastructure. All of the hardware, software, networks, and facilities that are required to develop, test, deliver, monitor, manage, and support IT services.
  • IT service. A service based on the use of information technology.
  • ITIL. Best-practice guidance for IT service management.
  • ITIL guiding principles. Recommendations that can guide an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure.
  • ITIL service value chain. An operating model for service providers that covers all the key activities required to effectively manage products and services.
  • Kanban. A method for visualizing work, identifying potential blockages and resource conflicts, and managing work in progress.
  • Key performance indicator (KPI). An important metric used to evaluate the success in meeting an objective.
  • Knowledge management practice. The practice of maintaining and improving the effective, efficient, and convenient use of information and knowledge across an organization.
  • Known error. A problem that has been analysed but has not been resolved.
  • Lean. An approach that focuses on improving workflows by maximizing value through the elimination of waste.
  • Lifecycle. The full set of stages, transitions, and associated statuses in the life of a service, product, practice, or other entity.
  • Live. Refers to a service or other configuration item operating in the live environment.
  • Live environment. A controlled environment used in the delivery of IT services to service consumers.
  • Maintainability. The ease with which a service or other entity can be repaired or modified.
  • Major incident. An incident with significant business impact, requiring an immediate coordinated resolution.
  • Management system. Interrelated or interacting elements that establish policy and objectives and enable the achievement of those objectives.
  • Maturity. A measure of the reliability, efficiency and effectiveness of an organization, practice, or process.
  • Mean time between failures (MTBF). A metric of how frequently a service or other configuration item fails.
  • Mean time to restore service (MTRS). A metric of how quickly a service is restored after a failure.
  • Measurement and reporting. The practice of supporting good decision-making and continual improvement by decreasing levels of uncertainty.
  • Metric. A measurement or calculation that is monitored or reported for management and improvement.
  • Minimum viable product (MVP). A product with just enough features to satisfy early customers, and to provide feedback for future product development.
  • Mission statement. A short but complete description of the overall purpose and intentions of an organization. It states what is to be achieved, but not how this should be done.
  • Model. A representation of a system, practice, process, service, or other entity that is used to understand and predict its behaviour and relationships.
  • Modelling. The activity of creating, maintaining, and utilizing models.
  • Monitoring. Repeated observation of a system, practice, process, service, or other entity to detect events and to ensure that the current status is known.
  • Monitoring and event management practice. The practice of systematically observing services and service components, and recording and reporting selected changes of state identified as events.
  • Obtain/build. The value chain activity that ensures service components are available when and where they are needed, and that they meet agreed specifications.
  • Operation. The routine running and management of an activity, product, service, or other configuration item.
  • Operational technology. The hardware and software solutions that detect or cause changes in physical processes through direct monitoring and/or control of physical devices such as valves, pumps, etc.
  • Organization. A person or a group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives.
  • Organizational change management practice. The practice of ensuring that changes in an organization are smoothly and successfully implemented and that lasting benefits are achieved by managing the human aspects of the changes.
  • Organizational resilience. The ability of an organization to anticipate, prepare for, respond to, and adapt to unplanned external influences.
  • Organizational velocity. The speed, effectiveness, and efficiency with which an organization operates. Organizational velocity influences time to market, quality, safety, costs, and risks.
  • Organizations and people. One of the four dimensions of service management. It ensures that the way an organization is structured and managed, as well as its roles, responsibilities, and systems of authority and communication, is well defined and supports its overall strategy and operating model.
  • Outcome. A result for a stakeholder enabled by one or more outputs.
  • Output. A tangible or intangible deliverable of an activity.
  • Outsourcing. The process of having external suppliers provide products and services that were previously provided internally.
  • Partners and suppliers. One of the four dimensions of service management. It encompasses the relationships an organization has with other organizations that are involved in the design, development, deployment, delivery, support, and/or continual improvement of services.
  • Partnership. A relationship between two organizations that involves working closely together to achieve common goals and objectives.
  • Performance. A measure of what is achieved or delivered by a system, person, team, practice, or service.
  • Pilot. A test implementation of a service with a limited scope in a live environment.
  • Plan. The value chain activity that ensures a shared understanding of the vision, current status, and improvement direction for all four dimensions and all products and services across an organization.
  • Policy. Formally documented management expectations and intentions, used to direct decisions and activities.
  • Portfolio management practice. The practice of ensuring that an organization has the right mix of programmes, projects, products, and services to execute its strategy within its funding and resource constraints.
  • Post-implementation review (PIR). A review after the implementation of a change, to evaluate success and identify opportunities for improvement.
  • Practice. A set of organizational resources designed for performing work or accomplishing an objective.
  • Problem. A cause, or potential cause, of one or more incidents.
  • Problem management practice. The practice of reducing the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors.
  • Procedure. A documented way to carry out an activity or a process.
  • Process. A set of interrelated or interacting activities that transform inputs into outputs. A process takes one or more defined inputs and turns them into defined outputs. Processes define the sequence of actions and their dependencies.
  • Product. A configuration of an organization's resources designed to offer value for a consumer.
  • Production environment. See live environment.
  • Programme. A set of related projects and activities, and an organization structure created to direct and oversee them.
  • Project. A temporary structure that is created for the purpose of delivering one or more outputs (or products) according to an agreed business case.
  • Project management practice. The practice of ensuring that all an organization's projects are successfully delivered.
  • Quick win. An improvement that is expected to provide a return on investment in a short period of time with relatively small cost and effort.
  • Record. A document stating results achieved and providing evidence of activities performed.
  • Recovery. The activity of returning a configuration item to normal operation after a failure.
  • Recovery point objective (RPO). The point to which information used by an activity must be restored to enable the activity to operate on resumption.
  • Recovery time objective (RTO). The maximum acceptable period of time following a service disruption that can elapse before the lack of business functionality severely impacts the organization.
  • Relationship management practice. The practice of establishing and nurturing links between an organization and its stakeholders at strategic and tactical levels.
  • Release. A version of a service or other configuration item, or a collection of configuration items, that is made available for use.
  • Release management practice. The practice of making new and changed services and features available for use.
  • Reliability. The ability of a product, service, or other configuration item to perform its intended function for a specified period of time or number of cycles.
  • Request catalogue. A view of the service catalogue, providing details on service requests for existing and new services, which is made available for the user.
  • Request for change (RFC). A description of a proposed change used to initiate change control.
  • Resolution. The action of solving an incident or problem.
  • Resource. A person, or other entity, that is required for the execution of an activity or the achievement of an objective. Resources used by an organization may be owned by the organization or used according to an agreement with the resource owner.
  • Retire. The act of permanently withdrawing a product, service, or other configuration item from use.
  • Risk. A possible event that could cause harm or loss, or make it more difficult to achieve objectives. Can also be defined as uncertainty of outcome, and can be used in the context of measuring the probability of positive outcomes as well as negative outcomes.
  • Risk assessment. An activity to identify, analyse, and evaluate risks.
  • Risk management practice. The practice of ensuring that an organization understands and effectively handles risks.
  • 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.
  • Service action. Any action required to deliver a service output to a user. Service actions may be performed by a service provider resource, by service users, or jointly.
  • Service architecture. A view of all the services provided by an organization. It includes interactions between the services, and service models that describe the structure and dynamics of each service.
  • Service catalogue. Structured information about all the services and service offerings of a service provider, relevant for a specific target audience.
  • Service catalogue management practice. The practice of providing a single source of consistent information on all services and service offerings, and ensuring that it is available to the relevant audience.
  • Service configuration management practice. The practice of ensuring that accurate and reliable information about the configuration of services, and the configuration items that support them, is available when and where needed.
  • Service consumption. Activities performed by an organization to consume services. It includes the management of the consumer's resources needed to use the service, service actions performed by users, and the receiving (acquiring) of goods (if required).
  • Service continuity management practice. The practice of ensuring that service availability and performance are maintained at a sufficient level in case of a disaster.
  • Service design practice. The practice of designing products and services that are fit for purpose, fit for use, and that can be delivered by the organization and its ecosystem.
  • Service desk. The point of communication between the service provider and all its users.
  • Service desk practice. The practice of capturing demand for incident resolution and service requests.
  • Service financial management practice. The practice of supporting an organization's strategies and plans for service management by ensuring that the organization's financial resources and investments are being used effectively.
  • Service level. One or more metrics that define expected or achieved service quality.
  • Service level agreement (SLA). A documented agreement between a service provider and a customer that identifies both services required and the expected level of service.
  • Service level management practice. The practice of setting clear business-based targets for service performance so that the delivery of a service can be properly assessed, monitored, and managed against these targets.
  • Service management. A set of specialized organizational capabilities for enabling value for customers in the form of services.
  • Service offering. A formal description of one or more services, designed to address the needs of a target consumer group. A service offering may include goods, access to resources, and service actions.
  • Service owner. A role that is accountable for the delivery of a specific service.
  • Service portfolio. A complete set of products and services that are managed throughout their lifecycles by an organization.
  • Service provider. A role performed by an organization in a service relationship to provide services to consumers.
  • Service provision. Activities performed by an organization to provide services. It includes management of the provider's resources, configured to deliver the service; ensuring access to these resources for users; fulfilment of the agreed service actions; service level management; and continual improvement. It may also include the supply of goods.
  • Service relationship. A cooperation between a service provider and service consumer. Service relationships include service provision, service consumption, and service relationship management.
  • Service relationship management. Joint activities performed by a service provider and a service consumer to ensure continual value co-creation based on agreed and available service offerings.
  • Service request. A request from a user or a user's authorized representative that initiates a service action which has been agreed as a normal part of service delivery.
  • Service request management practice. The practice of supporting the agreed quality of a service by handling all predefined, user-initiated service requests in an effective and user-friendly manner.
  • Service validation and testing practice. The practice of ensuring that new or changed products and services meet defined requirements.
  • Service value system (SVS). A model representing how all the components and activities of an organization work together to facilitate value creation.
  • Software development and management practice. The practice of ensuring that applications meet stakeholder needs in terms of functionality, reliability, maintainability, compliance, and auditability.
  • Sourcing. The activity of planning and obtaining resources from a particular source type, which could be internal or external, centralized or distributed, and open or proprietary.
  • Specification. A documented description of the properties of a product, service, or other configuration item.
  • Sponsor. A person who authorizes budget for service consumption. Can also be used to describe an organization or individual that provides financial or other support for an initiative.
  • Stakeholder. A person or organization that has an interest or involvement in an organization, product, service, practice, or other entity.
  • Standard. A document, established by consensus and approved by a recognized body, that provides for common and repeated use, mandatory requirements, guidelines, or characteristics for its subject.
  • Standard change. A low-risk, pre-authorized change that is well understood and fully documented, and which can be implemented without needing additional authorization.
  • Status. A description of the specific states an entity can have at a given time.
  • Strategy management practice. The practice of formulating the goals of an organization and adopting the courses of action and allocation of resources necessary for achieving those goals.
  • Supplier. A stakeholder responsible for providing services that are used by an organization.
  • Supplier management practice. The practice of ensuring that an organization's suppliers and their performance levels are managed appropriately to support the provision of seamless quality products and services.
  • Support team. A team with the responsibility to maintain normal operations, address users' requests, and resolve incidents and problems related to specified products, services, or other configuration items.
  • System. A combination of interacting elements organized and maintained to achieve one or more stated purposes.
  • Systems thinking. A holistic approach to analysis that focuses on the way that a system's constituent parts work, interrelate, and interact over time, and within the context of other systems.
  • Technical debt. The total rework backlog accumulated by choosing workarounds instead of system solutions that would take longer.
  • Test environment. A controlled environment established to test products, services, and other configuration items.
  • Third party. A stakeholder external to an organization.
  • Throughput. A measure of the amount of work performed by a product, service, or other system over a given period of time.
  • Transaction. A unit of work consisting of an exchange between two or more participants or systems.
  • Use case. A technique using realistic practical scenarios to define functional requirements and to design tests.
  • User. A person who uses services.
  • Utility. The functionality offered by a product or service to meet a particular need. Utility can be summarized as ‘what the service does' and can be used to determine whether a service is ‘fit for purpose'. To have utility, a service must either support the performance of the consumer or remove constraints from the consumer. Many services do both.
  • Utility requirements. Functional requirements which have been defined by the customer and are unique to a specific product.
  • Validation. Confirmation that the system, product, service, or other entity meets the agreed specification.
  • Value. The perceived benefits, usefulness, and importance of something.
  • Value stream. A series of steps an organization undertakes to create and deliver products and services to consumers.
  • Value streams and processes. One of the four dimensions of service management. It defines the activities, workflows, controls, and procedures needed to achieve the agreed objectives.
  • Vision. A defined aspiration of what an organization would like to become in the future.
  • Warranty. Assurance that a product or service will meet agreed requirements. Warranty can be summarized as ‘how the service performs' and can be used to determine whether a service is ‘fit for use'. Warranty often relates to service levels aligned with the needs of service consumers. This may be based on a formal agreement, or it may be a marketing message or brand image. Warranty typically addresses such areas as the availability of the service, its capacity, levels of security, and continuity. A service may be said to provide acceptable assurance, or ‘warranty', if all defined and agreed conditions are met.
  • Warranty requirements. Typically non-functional requirements captured as inputs from key stakeholders and other practices.
  • Waterfall method. A development approach that is linear and sequential with distinct objectives for each phase of development.
  • Work instruction. A detailed description to be followed in order to perform an activity.
  • Workaround. A solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available. Some workarounds reduce the likelihood of incidents.
  • Workforce and talent management practice. The practice of ensuring that an organization has the right people with the appropriate skills and knowledge and in the correct roles to support its business objectives.
Retrieved from "https://pravka.bskol.com/w/index.php?title=ITIL_Foundation_4e_by_Axelos&oldid=68428"