ITIL ITIL-4-Transition - ITIL 4 Managing Professional Transition Exam

Digital transformation is the process of using digital technologies to create new or modify existing business processes, culture, and customer experiences to meet changing business and market requirements1. It is not just about implementing new technology, but also about changing the way an organization operates and delivers value to its customers. High velocity IT is one of the four dimensions of service management in ITIL 4, which refers to the rapid delivery and operation of IT-enabled products and services that can continuously evolve2. Digital organization and IT transformation are not specific terms defined in ITIL 4, but they could be related to digital transformation in some contexts. References:

ITIL 4 and Digital Transformation

[ITIL 4 Foundation: High Velocity IT]

Swarming is a technique to more effectively resolve complicated and complex issues, which typically require more than one person or group to complete an activity effectively1. Swarming involves stakeholders working together to resolve the issue, rather than escalating it through a tiered structure2. Swarming can reduce the time toresolution, improve the customer experience, and enhance the knowledge sharing and collaboration among the support teams3. Swarming is also a concept used in Agile and DevOps methodologies, which are part of the ITIL 4 framework4.

Service integration and management (SIAM) is a management methodology that can help coordinate multiple service providers and ensure consistent and seamless service delivery to the customers. However, SIAM is not a technique to resolve complex incidents within an organization, but rather a way to manage the relationships and interactions among different service providers.

Machine learning is a branch of artificial intelligence that enables systems to learn from data and improve their performance without explicit programming. Machine learning can help automate some aspects of service management, such as incident classification, routing, and resolution. However, machine learning is not a technique to resolve complex incidents that require human intervention and collaboration.

An information model is a representation of concepts, relationships, constraints, rules, and operations to specify the semantics of something. An information model can help define and structure the data and information used in service management, such as configuration items, incidents, problems, changes, etc. However, an information model is not a technique to resolve complex incidents, but rather a way to organize and manage the information.

Therefore, the best approach or technique to resolve the situation described in the question is swarming.

References: 1: ITIL 4 Foundation, page 77 2: ITIL 4 & swarming – finding the right people & process | Axelos 3: Swarming vs Tiered Support Models Explained - BMC Software 4: ITIL 4 Specialist: Create, Deliver and Support, page 33 : ITIL 4 Foundation, page 81 : ITIL 4 Specialist: High-Velocity IT, page 36 : ITIL 4 Specialist: High-Velocity IT, page 37 : ITIL 4 Foundation, page 83 : ITIL 4 Specialist: Create, Deliver and Support, page 35

 Design thinking and service-dominant logic have in common that both involve collaborating with customers to ensure their needs are met. Design thinking is a human-centered approach to problem solving that emphasizes empathy, creativity, and experimentation. Service-dominant logic is a framework for understanding value creation, which focuses on the exchange of services between two or more entities. Both concepts share the following principles:

Value is co-created by the provider and the customer in the context of use. The provider does not deliver value, but rather offers value propositions that the customer can accept or reject. The customer is an active participant in the value creation process, not a passive recipient of goods or services.

The customer is the ultimate judge of value. The provider cannot determine the value of the offering in advance, but rather has to understand the customer’s needs, preferences, and expectations. The provider has to engage with the customer in an ongoing dialogue and feedback loop to ensure that the offering meets or exceeds the customer’s expectations.

The offering is a holistic solution that integrates goods, services, and experiences. The provider does not differentiate between tangible and intangible products, but rather offers a complete solution that addresses the customer’s problem or opportunity. The provider has to design the offering in a way that delivers a positive customer experience and enhances the customer’s well-being. References:

Exploring Overlaps and Differences in Service Dominant Logic and Design Thinking

Service-Dominant Logic: Key Principles and History

Service-Dominant Logic and How It Reframes Our Business Operations

The New Paradigm: H2H Marketing

The seven guiding principles of ITIL 4 are not meant to be applied equally or rigidly in every situation. Rather, they are intended to provide guidance and encourage decision making and continual improvement at all levels. Therefore, when an organization is making a decision, it should review each guiding principle to decide how relevant it is to the specific decision, and use the ones that are most appropriate and helpful. For example, some decisions may require more collaboration and visibility than others, or some decisions may benefit from more iteration and feedback than others. The guiding principles are not rules or prescriptions, but rather suggestions and recommendations that can help the organization achieve its objectives and deliver value to its stakeholders. References:

The 7 Guiding Principles of ITIL 4 - IFS Blog1

The 7 ITIL 4 Guiding Principles: Explained in Detail2

The Seven ITIL 4 Guiding Principles & Business Value - Belgium3

 The expected outcome from using a service value chain is value realization. Value realization is the process of ensuring that the intended benefits of a product or service are achieved or exceeded. Value realization is not only about delivering value to customers, but also capturing value for the service provider and other stakeholders. The service value chain is an operating model that outlines the key activities required to respond to demand and facilitate value realization through the creation and management of products and services. The service value chain consists of six activities: plan, improve, engage, design and transition, obtain/build, and deliver and support. Each activity contributes to value creation by transforming various inputs into specific outputs. The service value chain can be configured in different ways to form service value streams, which are the end-to-end workflows that deliver a specific product or service to a customer or user. The service value chain also enables the application of practices, which are sets of organizational resources and capabilities that help perform work or accomplish an objective. The service value chain is flexible and adaptable to different contexts and scenarios, allowing the service provider to optimize the use of resources and deliver value in the most effective and efficient way. References:

ITIL 4 Foundation: ITIL 4 Edition, section 4.2.1

ITIL®4 Service Value Chain [ITIL4 SVC Activities with Examples], section “ITIL ® 4 Service Value Chain Model”

The correct answer is A because creating a clear picture of what is changing and why it is valuable is the first step in organizational change management. Organizational change management is the practice of ensuring that changes are effectively and smoothly implemented, and that the lasting benefits of change are achieved. Creating a clear picture of the change involves defining the vision, scope, objectives, and benefits of the change, and communicating them to the stakeholders. This helps to create a sense of urgency, alignment, and commitment for the change, and to overcome resistance and ambiguity.

The other options are not correct because they are not the first activity in organizational change management. Developing a value stream map of the desired future changes (option B) is a useful technique to identify and optimize the flow of value, but it is not the first activity. It requires a clear understanding of the change and its value proposition, which is established in option A. Creating corrective action plans for staff who are resistant to the change (option C) is a reactive and punitive approach to change management, which can create more resentment and distrust. It is not the first activity, nor the best practice, in organizational change management. Communicating areas of waste that can be eliminated (option D) is a part of the lean approach to service management, which aims to optimize value by reducing waste and inefficiencies. However, it is not the first activity in organizational change management, as it does not address the vision, scope, objectives, and benefits of the change, which are essential for creating a clear picture of the change.

References:

ITIL 4 Managing Professional Transition Module Sample Paper - English, Question 3, Page 5

ITIL 4 Managing Professional: Transition Module | Axelos, Section “What is the ITIL 4 Managing Professional Transition Module?”, Paragraph 3

ITIL® 4 Managing Professional Transition Course Online - Simplilearn, Section “Course Overview”, Paragraph 2

[ITIL 4 Foundation: ITIL 4 Edition], Chapter 7, Section 7.2.1, Page 146

[ITIL 4 Foundation: ITIL 4 Edition], Chapter 7, Section 7.2.2, Page 147

[ITIL 4 Foundation: ITIL 4 Edition], Chapter 7, Section 7.2.3, Page 148

[ITIL 4 Foundation: ITIL 4 Edition], Chapter 7, Section 7.2.4, Page 149

[ITIL 4 Foundation: ITIL 4 Edition], Chapter 7, Section 7.2.5, Page 150

[ITIL 4 Foundation: ITIL 4 Edition], Chapter 7, Section 7.2.6, Page 151

[ITIL 4 Foundation: ITIL 4 Edition], Chapter 7, Section 7.2.7, Page 152

[ITIL 4 Foundation: ITIL 4 Edition], Chapter 7, Section 7.2.8, Page 153

Results-based measurement and reporting is a method of measuring and reporting the outcomes and value delivered by products and services, rather than the activities and outputs involved in their creation and delivery12. Results-based measurement and reporting focuses on the achievement of objectives and the satisfaction of stakeholders, rather than the consumption of resources and the completion of tasks12.

An example of results-based measurement and reporting is measuring and reporting the customer satisfaction with closed incidents. This is because customer satisfaction is an indicator of the value and quality of the incident management practice and the service provided to the customers. Customer satisfaction reflects the extent to which thecustomers’ expectations and needs have been met by the resolution of the incidents. Customer satisfaction can also influence the customer loyalty, retention, and advocacy for the service provider34.

The other options are not examples of results-based measurement and reporting, because they measure and report the inputs and outputs of the service delivery, rather than the outcomes and value. Measuring and reporting the number of hours worked by service desk employees, the number of supplier-related interruptions to a service, and the cost of providing a service to customers and users are all examples of activity-based or output-based measurement and reporting. These metrics do not indicate the effectiveness or efficiency of the service delivery, nor the satisfaction or value perceived by the customers and users12.

References: 1: ITIL 4 Create, Deliver and Support, AXELOS, 2019, p. 29-30 2: Measurement and reporting management: ITIL 4 Practice Guide, AXELOS, 2020, p. 5-6 3: ITIL 4 Direct, Plan and Improve, AXELOS, 2019, p. 97-98 4: Reporting on value in service management, AXELOS, 2021, 3

 The most likely reason for an organization to delay a transformation to high velocity is that the organization is not ready for a cultural change. High velocity IT requires a significant shift in the mindset, values, and behaviors of the organization and its people, as well as the adoption of new ways of working, such as agile, lean, and DevOps. These changes can be challenging and disruptive for some organizations, especially those that have a traditional, hierarchical, or siloed culture. Therefore, the organization may need to assess its readiness and willingness for a cultural change before embarking on a transformation to high velocity IT. This reason is supported by the following references:

ITIL 4 Specialist: High-velocity IT explores the ways in which digital organizations and digital operating models function in high velocity environments1

ITIL 4 High-velocity IT: the digital enterprise2

ITIL®4 Specialist: High Velocity IT3