ITIL 4 Managing Professional ITIL-4-Transition Full Course Free

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

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 the customers’ 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.

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