ITIL ITIL-4-Transition Dumps

The best way for the organization to collect the information needed to address the complaints is to collect customer experience and service level metrics. Customerexperience metrics are measures of how customers perceive the quality and value of the service and the interactions they have with the service provider. Service level metrics are measures of how well the service meets the agreed requirements and expectations of the customers and users. By collecting both types of metrics, the organization can identify the gaps and issues in the service delivery and the customer journey, and take actions to improve them. Some examples of customer experience metrics are customer satisfaction, net promoter score, customer effort score, and customer loyalty. Some examples of service level metrics are availability, reliability, performance, and incident resolution time. References:https://www.axelos.com/resource-hub/blog/itil-4-leads-to-value

Value stream mapping is a lean tool that documents the step-by-step processes required to bring a product or service to market. It helps visualize, analyze, and improve all the steps involved by identifying waste and reducing process cycle times. The ultimate goal of VSM is to create more value for customers while improving overall efficiency1. An organization that receives a high volume of calls from users complaining that their issues are not being resolved efficiently should use value stream mapping to help understand the end-to-end flow of user support. By laying out each step in detail within the user support process, VSM helps the organization better understand and more easily identify optimization opportunities. VSM also helps the organization see more than waste in their user support process, including the sources of waste, the value-adding and non-value-adding activities, the material and information flow, and the decisions that affect the flow2. Using value stream mapping, the organization can create a current state map that shows the actual condition of the user support process, and a future state map that shows the target image of how the user support process should work after making improvements. VSM also forms the basis of an implementation plan, a blueprint for improvement, that helps the organization design how the whole user supportprocess should operate2. Therefore, using value stream mapping is the first step the organization should take to start to improve the situation. References:

• Understanding the Fundamentals of Value-Stream Mapping
• Value stream mapping: Examples, process, template, and symbols

This working practice is not focused on creating value because it does not involve the customers or users in defining the requirements and expectations of the service. It also assumes that the developers’ previous experience is relevant and sufficient for the current situation, which may not be the case. This practice may lead to delivering a servicethat does not meet the needs and preferences of the customers or users, or that is not aligned with the organization’s strategy and objectives. References:

• ITIL 4 Managing Professional Transition Module Sample Paper - English1, page 6, question 1, answer A
• ITIL 4 Foundation: ITIL 4 Edition2, page 67, section 4.1.1, paragraph 2
• ITIL 4 Managing Professional: Create, Deliver and Support3, page 9, section 1.1, paragraph 3
• ITIL 4 Managing Professional: Direct, Plan and Improve4, page 11, section 1.1, paragraph 2

 The best approach for validating service value in a partnership relationship with a service consumer is to work together to identify methods of checking service value andcheck that value propositions are still valid. This is because this approach aligns with the ITIL 4 guiding principles of focus on value, collaborate and promote visibility, and progress iteratively with feedback1.

By working together, the service provider and the service consumer can co-create value and ensure that the services delivered meet the needs and expectations of the service consumer and other stakeholders. They can also share information and feedback, and adjust the services accordingly to respond to changing requirements and opportunities. Moreover, they can jointly define the criteria and indicators for measuring and validating the value of the services, such as the outcomes, costs, risks, and benefits23.

The value propositions of the services are the statements that describe the benefits and value that the services offer to the service consumer and other stakeholders. They are based on the understanding of the service consumer’s needs, preferences, and goals. The value propositions should be regularly reviewed and validated to ensure that they are still relevant and accurate, and that they reflect the current and future value of the services45.

The other options are not the best approach for validating service value, because they are either too narrow, too passive, or too reactive. They do not involve the active collaboration and co-creation of value between the service provider and the service consumer, nor do they account for the complexity and agility of the services provided.

References: 1: ITIL 4 Foundation: ITIL 4 Edition, AXELOS, 2019, p. 13-15 2: ITIL 4 Direct, Plan and Improve, AXELOS, 2019, p. 97-98 3: Reporting on value in service management, AXELOS, 2021, 3 4: ITIL 4 Create, Deliver and Support, AXELOS, 2019, p. 17-18 5: ITIL 4 Drive Stakeholder Value, AXELOS, 2019, p. 25-26

 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”

Toyota Kata is a way of managing teams, teaching them to adopt the methods used and perfected by Toyota. It is based on the idea of practicing routines or patterns that help people learn new skills and behaviors. By encouraging the practicing of routines to unlearn old habits and learn new ones, managers can help employees adjust to the different ways of working that Agile and DevOps require. For example, managers can use the Improvement Kata to help teams set challenging goals, experiment with solutions, learn from obstacles, and adapt to changing conditions. Managers can also use the Coaching Kata to provide feedback and guidance to teams, and help them develop scientific thinking and problem-solving skills. References:

• Toyota Kata - Wikipedia
• What is the Toyota Kata? | Kanban Tool
• Toyota Kata - Habits for Continuous Improvements

The value driven approach to service design is one of the seven guiding principles of ITIL 4, which are part of the ITIL 4 service value system (SVS). The SVS provides a flexible and adaptable approach to address service management challenges and utilize opportunities. It supports organizations in delivering value to their stakeholders in the form of goods, services, or other results1. The value driven approach to service design is based on the principle of focus on value, which states that everything an organization does should link back, directly or indirectly, to value for stakeholders2. This principle implies that service design should not be driven by technology, processes, or resources, but by the outcomes and benefits that customers and users expect from the service. To achieve this, service design should adopt an iterative approach based on frequent feedback, continual experimentation, and learning to ensure value co-creation. This means that service design should not be a one-time activity, but acontinuous cycle of improvement that involves testing, measuring, and validating assumptions and hypotheses about what customers and users value, and how the service can deliver it3. This approach also enables service design to respond to changing customer needs and expectations, as well as to emerging opportunities and threats in the market. By focusing on value, service design can ensure that the service is fit for purpose and use, and that it contributes to the organization’s overall goals and objectives. References:

• ITIL 4 Managing Professional Transition Module, page 16
• ITIL Service Design: Principles, Process and Its Importance, section 3.2.3
• The ITIL 4 Service Value System Explained, paragraph 1
• ITIL Service Value System (SVS), paragraph 1

The best way to start working on developing new services while addressing the issues faced by the IT department is to develop a clear understanding of the customers’ intended goals and expectations, and track each of them from start to finish to ensure that the service supports the required outcomes. This is because ITIL 4 emphasizes the importance of co-creating value with customers and focusing on the outcomes that they need and want, rather than just the outputs that the service provider delivers1. By understanding the customers’ goals and expectations, the IT department can design and deliver services that are aligned with the customer’s needs, preferences, and context, and that provide value for both parties2. Moreover, by tracking the customers’ goals and expectations throughout the service lifecycle, the IT department can ensure that the service remains relevant, effective, and efficient, and that any changes or improvements are based on customer feedback and satisfaction3.

Developing a clear set of system requirements and tracking each of them from start to finish to ensure that the delivered service meets the stated requirements (option A) is not the best way to start working on developing new services, because it focuses on the functional aspects of the service, rather than the outcomes that the customer values. System requirements are the specifications of what the service should do, but they do not necessarily reflect the customer’s needs, wants, and context. Therefore, a service that meets the system requirements may not meet the customer’s expectations or provide value for them4.

Involve senior management as early as possible to define requirements and help with ‘organizational change management’ to ensure successful implementation of the service (option C) is not the best way to start working on developing new services, because it does not involve the customer in the service design and delivery process. Senior management may have a different perspective and agenda than the customer,and may not fully understand the customer’s goals and expectations. Therefore, involving senior management alone may not result in a service that meets the customer’s needs or provides value for them. Moreover, organizational change management is a process that helps the organization adapt to changes in the internal or external environment, but it does not necessarily address the issues faced by the IT department in developing new services.

Assess and improve capabilities of IT teams prioritizing areas that are required to deliver the service in a way that meets customer expectations (option D) is not the best way to start working on developing new services, because it assumes that the IT department already knows what the customer expects from the service. However, without developing a clear understanding of the customer’s goals and expectations, the IT department may not be able to identify the areas that need improvement or the capabilities that are required to deliver the service in a way that meets customer expectations. Therefore, assessing and improving capabilities of IT teams is a secondary step that should follow after developing a clear understanding of the customer’s goals and expectations.

Therefore, the best way to start working on developing new services while addressing the issues faced by the IT department is to develop a clear understanding of the customers’ intended goals and expectations, and track each of them from start to finish to ensure that the service supports the required outcomes.

References: 1: ITIL 4 Foundation, page 4 2: ITIL 4 Foundation, page 6 3: ITIL 4 Foundation, page 8 4: ITIL 4 Foundation, page 9 : ITIL 4 Foundation, page 10 : ITIL 4 Foundation, page 11 : ITIL 4 Foundation, page 12

The correct answer is B. The service value chain because it is the core component of the ITIL 4 service management framework that describes how an organization orchestrates its IT capabilities to achieve its strategic objectives. The service value chain is an operating model that covers all the key activities to flexibly manage products and services1. It consists of six interconnected value chain activities: plan, improve, engage, design and transition, obtain/build, and deliver and support2.

Option A is not correct because the four dimensions of service management are not an operating model, but rather a holistic perspective that should be considered for the effective and efficient facilitation of value co-creation2. The four dimensions are: organizations and people, information and technology, partners and suppliers, and value streams and processes2.

Option C is not correct because the ITIL guiding principles are not an operating model, but rather a set of recommendations that can guide an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure2. The ITIL guiding principles are: focus on value, start where youare, progress iteratively with feedback, collaborate and promote visibility, think and work holistically, keep it simple and practical, and optimize and automate2.

Option D is not correct because continual improvement is not an operating model, but rather a recurring organizational activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations2. Continual improvement is based on the continual improvement model, which consists of four steps: what is the vision, where are we now, where do we want to be, and how do we get there2.

References: : ITIL 4 Models - A New Operating Model in ITIL 4 - KnowledgeHut : ITIL® 4 Managing Professional Transition Course Online - Simplilearn

Onboarding is one of the six activities in the service value chain, which is the set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and other stakeholders1. Onboarding involves providing the consumer with the agreed service and ensuring that they can use it as intended1. This includes building awareness of the new consumer, such as informing them about theservice features, benefits, and costs, as well as ensuring resources are prepared for service provision, such as allocating staff, equipment, and facilities2. Negotiating service targets with customers is part of the engage activity, which involves understanding the needs and expectations of the stakeholders and establishing agreements on how to meet them1. Designing the service components and infrastructure is part of the design and transition activity, which involves ensuring that products and services continually meet stakeholder expectations for quality, costs, and time to market1. References:

• ITIL 4 Foundation: Service Value Chain
• Transforming customer journeys with ITIL 4 DSV

 Employee satisfaction management is the process of measuring and improving how happy and engaged employees are with their work, their employer, and their organization. It involves conducting surveys, analyzing data, implementing strategies, and monitoring outcomes. Employee satisfaction management can help organizations improve productivity, retention, innovation, and customer satisfaction12.

An organization that designs a survey to assess the needs and expectations of its staff is engaging in employee satisfaction management, as it is trying to understand what factors influence employee satisfaction and how to address them. A survey is a common and effective method of collecting feedback from employees, as it can provide quantitative and qualitative data on various aspects of employee satisfaction, such as work environment, compensation, recognition, development, and alignment34.

The other options are not correct because they are not related to employee satisfaction management. CI/CD stands for continuous integration and continuous delivery, which are software development practices that aim to deliver high-quality software faster and more frequently5. Integration and data sharing are processes of connecting different systems and applications and exchanging information between them6. Customer-orientation is a business philosophy that focuses on meeting the needs and expectations of customers and creating value for them7. References:

• 1: How To Improve Employee Satisfaction (With 11 Strategies) | Indeed.com
• 2: The Five Fundamentals Of Employee Satisfaction - Forbes
• 3: The Key To Employee Satisfaction and How To Achieve It | Indeed.com
• 4: How To Measure Employee Satisfaction | Indeed.com
• 5: ITIL 4 Managing Professional: Transition Module | Axelos
• 6: ITIL® 4 Managing Professional Transition Course Online - Simplilearn
• 7: ITIL 4 MP Transition: a transformed framework | Axelos

The value chain activity that ensures that products and services continually meet stakeholder expectations for quality, costs and time to market is design and transition. This activity involves the following steps12:

• Defining the requirements and specifications of the products and services based on the demand and feedback from the customers and other stakeholders.
• Designing the products and services according to the requirements and specifications, as well as the best practices and standards of the organization and the industry.
• Developing and testing the products and services to ensure that they meet the quality criteria and the expected outcomes.
• Deploying and releasing the products and services to the customers and users, ensuring that they are ready for use and operation.
• Validating and evaluating the products and services to ensure that they deliver the intended value and meet the stakeholder expectations.
• Transitioning the products and services from the development stage to the operational stage, ensuring that they are integrated with the existing processes, systems and resources of the organization. References: 1: ITIL 4 Create, Deliver and Support, AXELOS, 2019, p. 23-24 2: Value Chain Activity: Design & Transition - Altervista, 3

 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

 Running safe to fail experiments that provide learning opportunities is the best option to improve staff behaviour, as it aligns with the ITIL 4 guiding principle of progress iteratively with feedback1. This principle encourages the use of experimentation and learning from failures to improve the service and the organization. By running safe to fail experiments, the staff can test new ideas, learn from the outcomes, and adapt their behaviour accordingly. This can foster a culture of innovation, collaboration, and continuous improvement in the IT department. The other options are not directly related to improving staff behaviour, but rather to improving the efficiency and effectiveness of the service delivery. Comparing the cost of delay between work items to ensure that financially valuable work is prioritized is a technique for value stream optimization, which is part of the ITIL 4 practice of service value stream management2. Implementing CI/CD tools to deploy software quickly is a method for achieving high-velocity IT, which is one of the ITIL 4 specialist modules3. Adopting Kanban boards to visualize the flow of work across software development teams is a tool for implementing agile and lean approaches, which are also part of the ITIL 4 framework3. While these options may have some positive impact on staff behaviour, they are not the primary focus or the best way to achieve it. References: 3, 2, 1

 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

Resilient operations is the high velocity IT objective that considers an organization’s ability to continue providing business services when disruptive events affect its digital products. Resilient operations ensure the availability, reliability, and performance of the digital products and services, as well as the ability to recover quickly from failures and incidents. Resilient operations also involve proactive practices such as technical debt management, chaos engineering, and site reliability engineering, which aim to improve the quality and resilience of the digital solutions. References:

• ITIL® 4 High-velocity IT (HVIT) - Your companion to the ITIL 4 Managing Professional HVIT certification, Chapter 7: Ensuring resilient operations
• ITIL 4 Specialist: High-Velocity IT Training, Course Outline, Module 2: The digital product lifecycle

The correct answer is B. Value stream mapping. This is because value stream mapping is a technique that helps to visualize how a service delivers value to the stakeholders, and identify the risks, dependencies, inefficiencies, and opportunities for improvement along the way12. Value stream mapping involves defining the service vision, mapping the current state, analyzing the current state, designing the future state, and implementing the future state12. By considering how each set of stakeholders will experience the service, the organization is defining the service vision and mapping the current state of the service.

A. An agile approach is not the correct answer, because an agile approach is a way of working that is flexible, iterative, and adaptive to changing requirements and feedback34. An agile approach does not necessarily involve compiling information about how a new service will be used, or considering how each set of stakeholders will experience the service.

C. Workforce planning is not the correct answer, because workforce planning is a process that ensures that an organization has the right people with the right skills at the right time to deliver its objectives . Workforce planning does not necessarily involve compiling information about how a new service will be used, or considering how each set of stakeholders will experience the service.

D. Shift left is not the correct answer, because shift left is a practice that aims to resolve issues as close as possible to their source, and prevent them from escalating to higher levels of support . Shift left does not necessarily involve compiling information about how a new service will be used, or considering how each set of stakeholders will experience the service. References:

• ITIL 4 Managing Professional Transition Module Sample Paper - English, page 9, question 2, answer B
• ITIL 4 Managing Professional Transition Module Candidate Syllabus - English, page 10, learning outcome 1.4
• ITIL 4 Managing Professional Transition Course Online - Simplilearn, section 3.2, lesson 3.2.1, topic “Agile Approach”
• ITIL 4 Managing Professional: Transition Module | Axelos, page 2, section “ITIL 4 Managing Professional Transition Module”
• [ITIL 4 Managing Professional Transition Course Online - Simplilearn], section 3.2, lesson 3.2.3, topic “Workforce Planning”
• [ITIL 4 MP Transition: a transformed framework | Axelos], paragraph 4, sentence 2
• [ITIL 4 Managing Professional Transition Course Online - Simplilearn], section 3.2, lesson 3.2.4, topic “Shift Left”
• [Course: ITIL 4 Managing Professional Transition | ITIL USA], paragraph 3, sentence 3