Cheat Sheet - ITIL4 Foundation
Cheat Sheet - ITIL4 Foundation
Service – is defined as 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.”
Utility – is defined as 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.”
Warranty – is defined as the 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.”
Customer - is defined as a “person who defines the requirements for a service and takes responsibility
for the outcomes of service consumption.”
You will also be expected to remember the key concepts of creating value with services:
Organization - is defined as a “person or a group of people that has its own functions with
responsibilities, authorities and relationships to achieve its objectives.”
Outcome - is defined as “what the customer/user actually wants to achieve; a result enabled by one or
more outputs”
Think and work holistically - see the big picture e.g. on value
Information and technology - for IT Services, information management is the primary means of
delivering value
Partners and suppliers - differing levels of integration and formality across different sets of partners and
suppliers
Value streams and processes - Value Streams - steps to create and deliver products and services to
consumers. Processes - activities that transform inputs into outputs
Plan - "ensure a shared understanding of the vision, current status and improvement direction for all
four dimensions and all products and services across the organization"
Improve - "ensure continual improvement of products, services and practices across all value chain
activities and the four dimensions of service management."
Engage - "provide a good understanding of stakeholder needs, transparency, and continual engagement
and good relationships with all stakeholders."
Design & transition - "ensure that products and services continually meet stakeholder expectations for
quality, costs and time-to-market."
Obtain/build - "ensure that service components are available when and where they are needed, and
meet agreed specifications."
Deliver & support - "ensure that services are delivered and supported according to agreed specifications
and stakeholders’ expectations."
Service Value Streams are specific instances of the generic value chain
Service Value Streams are created to respond to particular situations, or to carry out a certain task
Service Value Streams therefore are specific combinations of activities and practices
You are required to understand the ‘purpose’ and key terms used in 8 of the ITIL practices, being.
Relationship management
Supplier management
Definition of IT Asset - any "valuable component that can contribute to delivery of an IT product or
service."
Definition of Event - “any change of state that has significance for the management of a service or other
configuration item (CI). Events are typically recognized through notifications created by an IT service, CI
or monitoring tool.”
Release management
Make new and changed services and features available for use
Definition of Configuration Item (CI) - a “component that needs to be managed in order to deliver an IT
service.”
Deployment management
The ITIL4 Foundation course syllabus says that you will be expected to understand the following 7 ITIL
Practices in detail
Continual improvement:
"align the organization’s practices and services with changing business needs through the ongoing
identification and improvement of services, service components, practices"
Take action
Change control
“maximize the number of successful IT changes by ensuring that risks have been properly assessed,
authorizing changes to proceed, and managing a change schedule.”
Definition of a Change - the “addition, modification, or removal of anything that could have a direct or
indirect effect on services.”
Assign appropriate Change Authorities to differing areas and the Change Types:
Standard
Normal
Emergency
Incident management
"minimize the negative impact of incidents by restoring normal service operation as quickly as possible.”
Problem management
"to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents,
and managing workarounds and known errors.”
Definition of a Known Error - a “problem that has been analysed and has not been resolved.”
"support the agreed quality of a service by handling all pre-defined, user-initiated service requests in an
effective and user-friendly manner.”
Definition of a Service Request - a “request from a user or user’s authorized representative that initiates
a service action that has been agreed as a normal part of service delivery.”
Well understood and predictable, they can be pre-defined as part of normal service
Service desk
"to capture demand for incident resolution and service requests. It should also be the entry point and
single point of contact for the service provider with all of its users.”
Empathy
Incident analysis
Incident prioritization
Effective communications
Emotional intelligence
"to set clear business-based targets for service performance, so that the delivery of a service can be
properly assessed, monitored and managed against these targets.”
“This practice involves the definition, documentation, and active management of service levels.”
SLAs:
Must relate to customers’ outcomes, not just operational metrics. A collection of relevant
metrics is usually required
The agreement must involve all stakeholders including partners, sponsors, users and customers
The central element of the SVS is the service value chain, an operating model which outlines the key
activities required to respond to demand and facilitate value realization through the creation and
management of products and services.