Free Practice Questions for ITIL ITIL-4-Transition Exam

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 a continuous 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 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

Identifying consumer roles in service relationships is a benefit because it helps the service provider to understand the needs, expectations, and responsibilities of each type of consumer. This enables effective stakeholder management, which is the process of identifying, analyzing, planning, and communicating with the people or groups involved in or affected by a service. By knowing the consumer roles, the service provider can tailor the service offerings, agreements, and interactions to suit each role and create value for them. For example, the service provider can communicate with the customer (the person who defines the requirements and pays for the service) about the service strategy and value proposition, while communicating with the user (the person who uses the service) about the service features and feedback. The sponsor (the person who authorizes the budget and supports the service) can also be involved in the decision-making and governance of the service. By identifying and managing the consumer roles, the service provider can build trust, collaboration, and alignment with the consumers and deliver better service outcomes. References: 1, 2, 3

Comprehensive Explanation:

The guiding principle Keep it simple and practical advises:

Use the minimum number of steps required.

Eliminate unnecessary complexity.

Choose simple, easy-to-follow solutions whenever possible.

Option C aligns directly with this: adopting a simple, easy-to-use practice reflects the core idea of keeping things simple and practical.

Comprehensive Explanation:

The ITIL 4 definition states:

Service configuration management ensures that accurate and reliable information about the configuration of services and the configuration items (CIs) that support them is available when needed.

Therefore, the missing word is “services”.

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 correct answer is B because planning is the process of defining and organizing the activities and resources needed to achieve the objectives of a service or product. Planning should always consider the risks that may affect the delivery of value, and how to mitigate them. Risk management is the practice of identifying, analyzing, evaluating, and treating uncertainties that could prevent the achievement of goals or objectives. Risk management is an integral part of planning, as well as other service management practices, such as governance, continual improvement, and change control.

The other options are not correct because they do not describe the relationship between planning and risk accurately. Option A is wrong because planning and risk management are both strategic and tactical functions, depending on the scope and level of detail. Option C is wrong because planning does not only focus on what needs to be accomplished, but also how, when, who, and why. Risk management is not just part of how work is to be performed, but also why and what. Option D is wrong because risk management is not the exclusive domain of dedicated risk managers, but a shared responsibility of all stakeholders involved in service management.

 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