Академический Документы
Профессиональный Документы
Культура Документы
Rob Akershoek
White Paper
June 2020
Contents
1
Introduction 03
5 Conclusion 22
6
About the author 23
8
About AXELOS 25
This white paper explains how ITIL® 4 and the IT4IT™ standard
can unite to manage the new digital reality. The combination
of these two frameworks enables a more streamlined and “A digital management
automated delivery model: one which leverages Agile and DevOps
methodologies. system that can
There are several synergies between ITIL and the IT4IT standard.
holistically manage IT
Both approaches are vendor agnostic and outcome centric: they service and product
focus on creating value. Also, they both consider the value chain
holistically. lifecycles is integral to
However, there are some key differences. For example, ITIL’s
emphasis is on practices, culture, and behaviour, and IT4IT’s
success.”
emphasis is on information flows and automating IT activities.
Four significant themes and challenges that are shaping future IT operating models are:
zz Digital business IT is a strategic asset that can enable new business models, boost customer
satisfaction, and automate business processes. Organizations are transforming the way they engage with
customers, employees, and other parties by creating a connected digital ecosystem. Budgets are shifting
from IT departments to other departments, so IT managers have less control over how technology is
selected, implemented, and managed. IT departments must collaborate to co-create digital offerings that
optimize value streams and customer journeys.
zz Technology ecosystem New technologies provide opportunities and risks. These include migrating
legacy applications to the cloud and leveraging opportunities such as big data, artificial intelligence, and
the Internet of Things. New technologies must be managed efficiently and effectively.
zz Increasing demand IT must deliver faster and improve product quality while reducing costs and risks
and complying with regulations.
zz Transform IT delivery New delivery paradigms, such as DevOps, Agile, and CI/CD, are emerging. A
key theme is automating activities, including building, testing, deployment, and monitoring activities.
New deployment methods, such as infrastructure as code, are adopted across multiple vendors in the
ecosystem.
These initiatives will not deliver the expected benefits if they are not well planned. To succeed in an
increasingly complex and connected digital ecosystem, organizations need a different approach, as is
illustrated in Figure 1.2.
Most IT organizations are not equipped to handle these increasing demands. Without a more effective
digital management model for IT, organizations will not be able to respond to opportunities or threats
quickly, resulting in higher costs, longer lead times, and lost revenue.
Organizations need to adopt a new operating model: one where IT is integrated, streamlined, and
automated.
The key components of ITIL 4 are the service value system (SVS), shown in Figure 2.1; the four
dimensions of service management, shown in Figure 2.2; and the service value chain, shown in Figure
2.3.
The SVS represents how the various components and activities of the organization work together to
facilitate value creation through IT-enabled services.
To ensure a holistic approach to service management, ITIL outlines four dimensions of service
management. These are:
zz Organizations and people An organization needs a culture that supports its objectives, as well as the
right level of capacity and competency among its workforce.
All four dimensions must be considered so that the service value chain remains balanced and effective.
The service value chain models a generic end-to-end value chain from demand to value. The service value
chain’s flexibility allows organizations to effectively and efficiently react to changes in demand.
zz providing the capabilities for managing IT, thereby enabling better, faster, cheaper, and less risky ways of
working across the entire value chain
zz providing guidance on integrating and automating IT Value Chains with a common service model
backbone
zz defining a common information model for IT management
zz supporting real-world use-cases driven by the digital economy, such as cloud sourcing, Agile, DevOps,
and service brokering
zz embracing existing process frameworks and methodologies, such as ITIL, COBIT, SAFe, SCRUM, and
ITIL and the IT4IT standard have a comparable focus on value chains. Where ITIL refers to the service
value chain, the IT4IT standard uses the IT Value Chain.
The operating model for the IT business function. It includes primary activities, which are concerned
with the production or delivery of products or services, and supporting activities, which make the
primary activities more efficient and effective.
The operating model for the IT business function. It includes primary activities, which are concerned with
the production or delivery of products or services, and supporting activities, which make the primary
activities more efficient and effective.
A series of steps that an organization uses to create and deliver products and services to a service
consumer. Value streams involve multiple value chain activities and are supported by multiple
practices.
A description of the key activities for a discrete area within the IT Value Chain where some unit of
net value is created or added to the service as it progresses through its lifecycle. Each value stream
encapsulates capabilities that are necessary to manage aspects of the service/product lifecycle.
The IT Value Chain has four value streams that outline how value can be added at every stage of the
product or service lifecycle. They are:
Functional component
A logical system that needs to be present in any IT organization to provide specific management
capabilities to support IT staff who are performing IT management activities. Functional components
manage specific IT management data and have defined inputs and outputs that are data objects.
The four value streams, shown in Figure 2.5, are vital for helping the IT function control the service model
as it advances through its lifecycle. Figure 2.6 shows how the four value streams interconnect.
Figure 2.6 highlights the IT4IT standard’s focus on the entire IT Value Chain, and it contains the most
important functional components within the IT function.
Implementing the IT4IT standard requires a careful selection of IT management tools that support the
identified interfaces and enable end-to-end workflows across the value streams.
Figure 2.7 highlights key data objects organized around the service
model backbone. They store data about every service across its
lifecycle and create and maintain the traceability of key information
“In both ITIL and and
IT4IT, the value decision-making across the entire value chain. Consistent links
between the data allow organizations to control the costs, risks, and
stream’s goal is to value associated with service management.
convert demand into A value stream is triggered by demand and ends in value; the value
value.” stream’s goal is to convert demand into value. These fundamental
rules are suggested by both ITIL and IT4IT. Despite the differences in
terminology, the two models can be effectively used together.
Figure 3.1 is an overview of how ITIL and IT4IT can be used to build an integrated IT operating model.
ITIL recommends work practices and ways of working, and IT4IT provides the information flows and
systems needed to automate end to-end workflows, enable flow, and provide transparency and traceability.
Figure 3.2 ITIL value chain activities and IT4IT value streams.
IT4IT value stream Engage value chain activity Example data objects
Strategy to portfolio Collaboration with stakeholders Business demands
about demand and opportunities
New ideas/improvement
Collaboration with vendors about opportunities
technology roadmaps and new
opportunities Feedback from the organization,
such as service reviews
Requirement to deploy Collaboration with vendors, New feature requests/
stakeholders, and users about requirements
new or modified requirements
and features Feedback from key users
Request to fulfil Collaboration with consumers Service requests, such as
about service requests from the requests to access an application
standard service catalogue or cloud resources
Brokering services across
multiple vendors
Detect to correct Collaboration with consumers to Incidents
report incidents, raise questions,
provide feedback, and so on Questions
Complaints
Feedback
Figure 3.3 Visualization of the primary mapping of ITIL practices to the IT4IT value streams
IT4IT value IT4IT functional Primary ITIL 4 practices Other ITIL 4 practices
stream component enabling this value stream supporting this value stream
Strategy to Enterprise Strategy management Continual improvement
portfolio architecture
Architecture management Risk management
Policy
Portfolio management Service financial management
Proposal
Relationship management Information security
Portfolio demand management
IT investment Supplier management
portfolio
Service portfolio
Requirement Project Project management Architecture management
to deploy
Requirement Business analysis Availability management
Service design Service design Capacity and performance
management
Source Software development and
control management Risk management
Build Service validation and testing Service continuity management
Build package Release management Information security
management
Release composition Deployment management
Infrastructure and platform
Test management
Defect
Request to Engagement Service catalogue management Capacity and performance
fulfil experience portal management
Service request management
Offer consumption Information security
Deployment management management
Offer management
Infrastructure and platform IT asset management
Catalogue management
composition Service configuration
Knowledge management management
Request
rationalization Service financial management
Fulfilment execution
Usage
Chargeback/
showback
Knowledge and
collaboration
zz Cost modelling
zz Investment
zz Asset
Resource Workforce and talent -
management management
- - Organizational change -
management
Table 4.1 lists useful tools from ITIL and IT4IT that are relevant to each step of the continual improvement
model.
Table 4.1 Useful continual improvement tools from ITIL and IT4IT
Discourse on improvement in
ITIL® 4: Direct, Plan and Improve
Take action. Practice guides Functional model
Discourse on digital tools in ITIL® Functional components
4: High-velocity IT
The reference architecture model
Did we get there? Evaluation recommendations in Example KPIs
ITIL® 4: Direct, Plan and Improve
Example metrics in the practice
guides
How do we keep the momentum ITIL guiding principles -
going?
5 Conclusion
IT organizations are being challenged to manage digital ecosystems consisting of fast-changing hybrid
environments and increasing numbers of services, components, and vendors. As a response to these
challenges, organizations are working on many fragmented initiatives to improve and transform the IT
function. These include introducing new ways of working (Agile, DevOps, CI/CD) and modernizing their
IT-tooling landscape.
Typically, however, a blueprint of the target IT operating model that would connect and maximize all
this progress is missing. Without this blueprint, most initiatives will fail. To be successful, an integrated
approach that connects teams, processes, and tools, enables transparency, and optimizes end-to-end
workflows is needed.
Digital journeys should begin with modern IT operating models. One can be created by combining ITIL 4
and the IT4IT standard into a holistic blueprint. This blueprint can help to diagnose the organization’s
current state, find gaps, and create a transformation map to coordinate improvements.
Akershoek, R. (2019). DevOps + ITSM: A Merge Request. Webinar. Accessible at: www.brighttalk.com/
webinar/devops-itsm-a-merge-request/ [Accessed 18 March 2020]
Akershoek, R. (2019). ITIL 4 service value chain data flows (input and outputs). Online infographic.
Accessible at: www.slideshare.net/robakershoek/itil-4-service-value-chain-data-flows-input-and-
outputs-135507433 [Accessed 18 March 2020]
Anand, A. (2019). ITIL 4: Connecting Key Concepts – Part 1. AXELOS. Online. Available at: www.axelos.
com/news/blogs/april-2019/itil-4-connecting-the-key-concepts-blog-part-1 [Accessed 18 March 2020]
IT4IT™ Reference Architecture, Version 2.1, ©The Open Group. (2017) Online. Available at: https://pubs.
opengroup.org/it4it/refarch21/[Accessed 18 March 2020]
It is responsible for developing, enhancing and promoting a number of best practice methodologies used
globally by professionals working primarily in project, programme and portfolio management, IT service
management and cyber resilience.
The methodologies, including ITIL®, PRINCE2®, PRINCE2 Agile®, MSP®, RESILIA® and its newest
addition AgileSHIFT® are adopted in more than 150 countries to improve employees’ skills, knowledge
and competence in order to make both individuals and organizations work more effectively.
In addition to globally recognized qualifications, AXELOS equips professionals with a wide range of content,
templates and toolkits through the CPD aligned My AXELOS and our online community of practitioners and
experts.
Visit www.AXELOS.com for the latest news about how AXELOS is ‘Making organizations
more effective’ and registration details to join AXELOS’ online community. If you have specific queries,
requests or would like to be added to the AXELOS mailing list please contact
Ask@AXELOS.com.
Reuse of any content in this White Paper is permitted solely in accordance with the permission terms at
https://www.axelos.com/policies/legal/permitted-use-of-white-papers-and-case-studies
Our White Paper series should not be taken as constituting advice of any sort and no liability is accepted
for any loss resulting from or use of or reliance on its content. While every effort is made to ensure the
accuracy and reliability of information, AXELOS cannot accept responsibility for errors, omissions or
inaccuracies. Content, diagrams, logos and jackets are correct at time of going to press but may be subject
to change without notice.