ITIL ITIL-4-Transition ITIL 4 Managing Professional Transition Exam Exam Practice Test

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.

Comprehensive Explanation:

Service requests are:

Requests for something to be provided

Typically standard, pre-approved, low-risk

Examples include software installation, access requests, equipment provisioning

“Providing a virtual server for a development team” is a provisioning request — a type of standard service request, provided it follows an established request model.

Option A = incident.

Option B = change.

Option C = part of problem/error control.

Thus, Option D is correct.

Comprehensive and Detailed Explanation From Exact Extract of ITIL 4 Managing Professional Transition:

ITIL 4 defines Utility as:

“The functionality offered by a product or service to meet a particular need.”

Utility is often described as ‘fit for purpose’.

It refers to what the service does — the features or functions that support desired outcomes.

Warranty, by contrast, is about how the service performs — its availability, capacity, security, etc.

Output is a deliverable or result of an activity.

Outcome is a result for a stakeholder enabled by one or more outputs.Thus, Utility most directly represents the functionality of a service, making Option C correct.

 Swarming is an alternative to the tiered support structure that would help to improve the situation. Swarming is a workflow management method that features in ITIL 4 Specialist: Create, Deliver and Support. It is designed for organizations that support complex systems or services. Swarming involves stakeholders working together to resolve the issue, rather than escalating it through different levels of support. Swarming can be used to identify the responsible group for the next action, or a swarm might be responsible for resolution. 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 effectively. Swarming can also help to disseminate knowledge and experience among the support staff, and reduce the queues and delays caused by the escalation process. The other options are not relevant to the situation. Data analytics is the process of analyzing data to generate insights and support decision making. Robotic process automation is the use of software robots to automate repetitive and rule-based tasks. Continuous integration is a software development practice that involves merging code changes frequently and testing them automatically. References:

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

Swarming vs Tiered Support Models Explained - BMC Software2

Large batch sizes of work are considered a barrier to high performance in Lean and Agile because they increase the amount of work in progress (WIP), which leads to longer cycle times, higher variability, lower quality, and reduced feedback and learning. Large batches also increase the risk of waste, rework, and delays, as well as the complexity and uncertainty of the work. Lean and Agile advocate for reducing batch sizes and limiting WIP, which enables faster flow, shorter feedback loops, higher quality, and more value delivery. Some of the practices that help reduce batch sizes and limit WIP are:

Pulling versus pushing work, which means that work is initiated only when there is a demand and capacity for it, rather than being assigned or scheduled in advance.

Making work visible, which means that the status and progress of work are transparent and accessible to all stakeholders, using tools such as Kanban boards, burn-down charts, and dashboards.

Limiting work-in-progress, which means that the number of work items in each stage of the workflow is restricted, based on the available resources and throughput, to prevent bottlenecks and overloading. References: 

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 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 you are, 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.

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

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

Limiting work-in-progress (WIP) is a technique that involves setting a maximum number of tasks that can be in progress at any given stage of the workflow. This helps to reduce the amount of time that tasks spend waiting in queues, which improves the flow of work and reduces the lead time. Limiting WIP also encourages the team to focus on completing the tasks that are already started, rather than starting new ones, which improves the quality and value of the work. Limiting WIP is a key practice of Kanban, which is one of the methods covered in the ITIL 4 Managing Professional Transition module. References:

Limiting Work in Progress (WIP) in Scrum with Kanban - What / When / Who / How

The Surprising Impact of Limiting Work in Progress on the Flow of Work …

The correct answer is D. Identifying and making request for outstanding payments for the service. This is because the service provider should ensure that the financial obligations of the customer are fulfilled before the service is terminated. The service provider should also update the billing and accounting records, and close any open invoices or disputes related to the service12.

A. Ensuring that user access rights are revoked for all services is not the correct answer, because the service provider should only revoke the user access rights for the service that is being retired, not for all services. The service provider should also ensure that the customer data and assets related to the service are securely deleted or transferred, and that the service provider staff are reassigned or released12.

B. Providing information to users about how to contact the service desk is not the correct answer, because the service desk is not relevant for the service that is being retired. The service provider should provide information to users about how to access alternative or replacement services, if any, and how to provide feedback or complaints about the service retirement process12.

C. Creating training schedules for users on how to use the service is not the correct answer, because the service is being retired, not introduced. The service provider should not invest any resources or efforts in training users on how to use a service that will no longer be available. The service provider should instead focus on communicating the service retirement plan and timeline, and managing the expectations and emotions of the users12. References:

ITIL 4 Managing Professional Transition Module Sample Paper - English, page 10, question 3, answer D

ITIL 4 Managing Professional Transition Module Candidate Syllabus - English, page 11, learning outcome 1.5

 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

Comprehensive Explanation:

IT Asset Management is defined as:

The practice responsible for planning and managing the full lifecycle of IT assets, which are financially valuable components that support service delivery.

Thus, Option D is correct.

According to ITIL 4, an effective control environment is one that ensures that the organization’s objectives are achieved in a reliable and compliant manner1. Effective controls are the mechanisms that prevent, detect, or correct errors, fraud, or non-compliance in the organization’s processes and activities2. Some of the characteristics of effective controls are that they are aligned with the organization’s goals, policies, and standards, they are proportionate to the level of risk, they are consistent and transparent, they are regularly monitored and reviewed, and they are responsive to changes and improvements3.

In the scenario given, the legacy financial system requires the user to manually enter the time and date of the transaction to meet regulatory requirements, but these fields are often blank. This indicates a lack of compliance and accuracy in the financial reporting process, which could expose the organization to legal, financial, or reputational risks. Therefore, some effective controls that could improve compliance are:

Modify the application to automatically add the current time and date when transaction is entered. This is a preventive control that reduces the risk of human error or omission by ensuring that the required information is always captured and recorded in the system. This control also enhances the efficiency and reliability of the process by eliminating the need for manual input.

Create a report showing non-compliant records and take action to correct. This is a detective and corrective control that identifies and resolves any instances of non-compliance or inaccuracy in the financial records. This control also provides feedback and evidence for the performance and effectiveness of the process and the controls.

The other options are not effective controls for improving compliance in this scenario because they do not directly address the root cause of the problem or provide a specific solution. Establishing a communication plan to remind users of the importance of time and date on transactions is a good practice, but it does not guarantee that the users will follow the instructions or comply with the requirements. Developing a goals cascade so all staff know their role in achieving company goals is a strategic activity, but it does not specify how the financial reporting process or the legacy system will be improved or controlled. Therefore, the best answer is D. 1 and 4. References:

1: ITIL 4 Managing Professional: Transition Module | Axelos

2: ITIL® 4 Managing Professional Transition Course Online - Simplilearn

3: ITIL 4 MP Transition: a transformed framework | Axelos

4: Internal Controls for Better Compliance | Reducing Risk

5: Internal Controls: The Definitive Guide for Risk and Compliance Professionals — RiskOptics

6: How to Establish an Effective Control Environment

Differential charging is a mechanism that allows the service provider to charge different prices for the same service depending on some pre-defined parameters, such as time of day, location, demand, etc. This way, the service provider can optimize the use of resources and encourage or discourage the consumption of the service at certain times or places. For example, a telecom operator may charge more for a phone call during peak hours than during off-peak hours. This is different from other charging mechanisms, such as:

Cost: The service provider charges the customer the exact amount of money that it costs to deliver the service, without any profit margin or overhead.

Cost plus: The service provider charges the customer the cost of delivering the service plus a fixed percentage or amount of profit.

Market price: The service provider charges the customer the price that is determined by the supply and demand of the service in the market, regardless of the actual cost of delivering the service. References:

Service financial management: ITIL 4 Practice Guide, section 2.2.1

Charging and ITIL Financial Management – What are the options?, section “Internal services – Living on the safe side”

 A value stream is a way of describing how an organization responds to specific types of demand and opportunity, by combining and integrating various activities from different practices. A value stream is based on the service value chain, which is a flexible operating model that outlines the key activities required to facilitate value creation through the delivery 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 can be supported by one or more practices, which are sets of organizational resources and capabilities that help perform work or accomplish an objective. By designing a value stream that includes activities from all practices that are needed, the software development team can ensure that they are creating value for their customers and users, as well as capturing value for themselves and other stakeholders. A value stream also helps to optimize the use of resources, eliminate waste, and improve efficiency and effectiveness. References:

ITIL 4 Foundation: ITIL 4 Edition, section 4.2.1

ITIL 4 Value System: Chain and Stream Differences | SysAid, section “Value Streams”

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

 Value stream mapping is a technique that helps to understand the end-to-end flow of user support, from the demand to the value delivery. It is a tool that features in ITIL 4 Specialist: Create, Deliver and Support. Value stream mapping can help to identify the steps, activities, roles, responsibilities, tools, and outcomes involved in the user support process. It can also help to identify the value, waste, and opportunities for improvement in each step. Value stream mapping can help the organization to optimize the user support process and enhance the customer experience. Therefore, using value stream mapping is the first step the organization should take to start to improve the situation. The other options are not the first steps, but they could be considered after the value stream mapping is done. Reviewing skills and competencies of user support staff, improving the integration of tools, and encouraging teams to collaborate are all possible actions that could result from the value stream mapping analysis, but they are not the first step to understand the problem and the current state of the user support process. References:

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

Swarming vs Tiered Support Models Explained - BMC Software1

What ITSM Practitioners Need to Know About Value Stream Mapping2

According to ITIL 4, one of the guiding principles is to progress iteratively with feedback. This means that IT service providers should break down complex tasks or changes into manageable chunks, seek feedback after each iteration, and use the feedback to improve and adapt their actions. Feedback is essential for co-creating value with customers and stakeholders, as well as for learning and improving the quality of IT services. Therefore, IT managers should establish effective feedback channels that enable two-way communication with staff and other parties involved in the IT service delivery. The best approach for establishing effective feedback channels is to research how individual teams communicate internally and use the most popular collaboration tools to collect feedback. This way, IT managers can leverage the existing communication preferences and habits of the staff, and avoid imposing a new tool or method that may not be suitable or convenient for them. By using the most popular collaboration tools, IT managers can also ensure that the feedback is timely, relevant, and accessible for all parties. This approach aligns with the ITIL 4 principle of collaborating and promoting visibility, which encourages IT service providers to work together across boundaries, share information, and make use of diverse perspectives and feedback. Therefore, the answer is A. Research how individual teams communicate internally and use the most popular collaboration tools to collect feedback. The other options are not the best approach for establishing effective feedback channels, because they either do not facilitate two-way communication, or do not consider the needs and preferences of the staff. For example, option B. Establish office hours where staff are encouraged to drop by without appointments and discuss any concerns they have, may not be convenient or practical for staff who work remotely or have different schedules. Option C. Initiate a project to select and implement a collaboration tool to facilitate two-way communication with staff, may take too long and may not match the expectations or requirements of the staff. Option D. Publish a printed weekly newsletter that clearly and consistently communicates change, may not be effective or efficient for collecting feedback, as it is a one-way communication channel that does not allow for immediate or interactive responses. References:

The 7 Guiding Principles of ITIL 4: Progress iteratively with feedback1

Guiding Principles of ITIL 4: Progress Iteratively with Feedback2

The customer journey and ITIL 43

Comprehensive Explanation:

For an SLA to be effective, ITIL stresses:

Clear, simple, and agreed language

Shared understanding between the provider and the customer

Terms that are meaningful to both parties

ITIL warns against:

Using technical metrics that only the provider understands

Carrying outdated SLAs forward

Avoiding user-experience metrics — these are valuable

Thus, Option A is the required necessity.

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 service that 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 service value system is a model that describes how all the components and activities of an organization work together as a system to enable value creation. The service value system consists of five elements: governance, service value chain, practices, guiding principles, and continual improvement. Governance is the means by which an organization is directed and controlled. It ensures that the organization’s strategy, policies, and objectives are aligned with the value proposition and the stakeholder needs. Service value chain is a set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization. Practices are sets of organizational resources designed for performing work or accomplishing an objective. Practices include processes, roles, tools, techniques, and methods that enable the organization to carry out its work effectively and efficiently. The other two elements of the service value system are guiding principles and continual improvement, which are not part of the answer options. References:

The ITIL 4 Service Value System Explained - ITSM.tools

Service Value System in ITIL 4 Explained | Sprintzeal

Collaborate and promote visibility is the guiding principle that would help the most in breaking down silos and eliminating conflicting goals. This principle encourages working together across boundaries and sharing information and knowledge with relevant stakeholders. By doing so, the organization can achieve a common understanding of the vision, objectives, and progress of the service value system. This also helps to avoid duplication of work, reduce errors, and improve efficiency and effectiveness. Collaborate and promote visibility also fosters a culture of trust, openness, and learning, which are essential for continual improvement and innovation. References:

ITIL 4 Foundation: ITIL 4 Edition, section 4.3.4

6 reasons why ITIL 4’s guiding principle of collaborate and promote visibility is important, section “Collaboration and value co-creation”

 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

User communities are groups of people who share a common interest or need related to a service or product. They can be formal or informal, online or offline, and may be initiated by service providers or users themselves. User communities can provide valuable feedback, insights, and support for service providers, as well as enhance the user experience and satisfaction. Therefore, service providers may recognize and support user communities that are set up by users, as long as they respect their autonomy and do not interfere with their activities. User communities are not created by service providers to investigate the cause of problems (option A), nor should they be disbanded or merged into official groups (option C). User communities may or may not have super-users, who are users with advanced skills or knowledge who can help other users, but this is not a requirement for every user community (option D). References: ITIL 4 Foundation, page 77; ITIL 4 Specialist: Drive Stakeholder Value, page 33.

Comprehensive Explanation:

A service request is a request from a user for something to be provided.

Common examples include:

Access requests

Information requests

Installation of standard services

“Access to a file” is a typical service request.

Options A and D relate to incident and problem management.

Option B is a change request.

Thus, Option C is correct.

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