Pass the ITIL ITIL 4 Managing Professional ITIL-4-Transition Questions and answers with CertsForce

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 to resolution, 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.

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.

The customer journey is the complete end-to-end experience customers have with one or more service providers and/or their products through the touchpoints and service interactions with those providers1. The purpose of the customer journey is to understand the needs, expectations, and preferences of the customers and users, and to design, deliver, and improve services that meet those requirements and create value for them. The customer journey also helps to identify the opportunities and challenges for co-creating value with the customers and users, and to optimize the customer experience throughout the service relationship23. By mapping the customer journey, the service provider can ensure that the services are aligned with the customer outcomes and that the service interactions are positive and satisfying for the customers and users4. References:

ITIL 4 Managing Professional: Drive Stakeholder Value5, page 14, section 2.1, paragraph 1

ITIL 4 Foundation: ITIL 4 Edition, page 20, section 2.3, paragraph 2

ITIL 4 Managing Professional: Create, Deliver and Support, page 10, section 1.1, paragraph 4

ITIL 4 Managing Professional: Direct, Plan and Improve, page 12, section 1.1, paragraph 3

ITIL 4: Connecting the key concepts Part 4 | Axelos3, paragraph 2

The customer journey and ITIL 4 | Axelos1, paragraph 2

ITIL®4 – Mapping the Customer Journey - ITSM Professor2, paragraph 2

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 support process 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

The organization should follow the approach of creating one value stream for the entire project, to enable an end-to-end, holistic vision of the service. A value stream is a series of steps that an organization undertakes to create and deliver products and services to consumers. A value stream should cover the whole service value chain, from the demand to the value delivery. Creating one value stream for the entire project helps to ensure that the service is aligned with the customer needs, expectations, and outcomes, and that the value is co-created by the provider and the consumer. Creating one value stream also helps to identify the value, waste, and opportunities for improvement in each step, and to optimize the service delivery process. The other options are not correct, as they would result in fragmented, incomplete, or inconsistent value streams. Creating separate value streams for practices, people, tools and suppliers would not consider the ‘four dimensions’ equally, but rather isolate them from each other. Creating separate value streams for every project phase would not ensure that each milestone is achieved in an Agile manner, but rather create gaps and delays between the phases. Creating one value stream for each team would not allow the teams to focus on their different objectives, but rather create silos and conflicts among the teams. References:

ITIL 4 & swarming – finding the right people & process | Axelos1

Swarming vs Tiered Support Models Explained - BMC Software2

What ITSM Practitioners Need to Know About Value Stream Mapping3

ITIL 4 Value Streams: do the right things for customer | Axelos4

 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

A transformation to high velocity IT is a change that involves adopting digital operating models and practices that enable organizations to deliver products and services faster, better, and cheaper. High velocity IT is not suitable for all organizations or all parts of an organization, as it depends on the context, culture, and objectives of each situation. Therefore, statements A and C are incorrect. High velocity IT is especially relevant for customer-facing systems, as they need to meet the changing needs and expectations of customers in a competitive and dynamic environment. Therefore, statement D is also incorrect. High performance is usually part of the change, as high velocity IT aims to improve the quality, value, and outcomes of the products and services delivered, as well as the efficiency, effectiveness, and agility of the processes and practices involved. Therefore, statement B is correct. References:

ITIL 4 Specialist: High-velocity IT | Axelos

ITIL 4 High-velocity IT: the digital enterprise | Axelos

ITIL 4 High Velocity IT (HVIT) Book - EVERYONE - Skillsoft

ITIL® 4 Specialist: High Velocity IT - Good e-Learning

Comprehensive Explanation:

The Service Desk is the single point of contact for users and must:

Communicate effectively

Show empathy

Understand the user’s emotional state

Provide reassurance and support

ITIL emphasizes people skills as essential for service desk interaction.

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]

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 the service 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