試験問題解答ブレーン問題集でITIL-4-Transition日本語試験問題集PDF問題 [Q24-Q38]

Explanation
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

Explanation
Customer orientation is an approach to business that focuses on assisting customers in achieving their goals, as opposed to adopting a sales oriented methodology12. It involves understanding the needs, expectations, and preferences of the customers and delivering value that meets or exceeds them. Customer orientation also implies adapting to the feedback and behavior of the customers and tailoring the service accordingly.
Therefore, when a service support agent adjusts support actions following a call from a frustrated user, they are demonstrating customer orientation, as they are trying to resolve the user’s issue in a way that suits their emotional state and satisfaction level. Customer orientation is one of the key concepts in ITIL 4, as it helps to create value co-creation and drive stakeholder value34. It is also aligned with the ITIL guiding principles of focus on value, collaborate and promote visibility, and keep it simple and practical34. References:
The customer journey and ITIL 4 | Axelos3
Holistic IT – a non-siloed approach with ITIL 4 | Axelos4
Customer Orientation: What it Is and How to Implement It [+Examples]1
Mastering Customer Orientation: Definition, Importance and Strategies2

The correct answer is A. Failing to explain service provider action that impact the customer. This is because a lack of transparency and communication can erode the trust and satisfaction of the customer, and lead to misunderstandings and conflicts. The service provider should always inform the customer of any changes, issues, or decisions that affect the customer’s services, expectations, or outcomes. The service provider should also seek feedback from the customer and address any concerns or complaints promptly and effectively.
B). Scheduling interactions between customer and service provider is not a threat, but a good practice to maintain the relationship. Regular interactions can help to align the goals, values, and needs of both parties, and foster collaboration and mutual understanding. The service provider should also use these interactions to demonstrate value and performance, and to identify opportunities for improvement or innovation.
C). Changes in service provider and customer staff is not a threat, but a challenge that can be overcome with proper knowledge management and relationship management. The service provider should ensure that the knowledge and experience of the staff are captured, shared, and transferred to the new staff, and that the new staff are trained and competent to deliver the services. The service provider should also introduce the new staff to the customer and establish rapport and trust.
D). Failing to deal with communication in a timely fashion is a threat, but not the most likely one. Delayed or ignored communication can frustrate the customer and damage the reputation of the service provider. The service provider should respond to the customer’s communication as soon as possible, and provide clear and accurate information. The service provider should also follow up on the communication and ensure that the customer’s needs are met. References:
* ITIL 4 Managing Professional Transition Module Sample Paper – English, page 8, question 1, answer A
* ITIL 4 Managing Professional Transition Module Candidate Syllabus – English, page 9, learning outcome 1.3
* ITIL 4 Managing Professional Transition Course Online – Simplilearn, section 3.2, lesson 3.2.2, topic
“Relationship Management”

Explanation
According to ITIL 4, change enablement is the practice of ensuring that risks are properly assessed, authorizing changes to proceed, and managing a change schedule in order to maximize the number of successful IT changes. ITIL 4 recognizes that changes can vary in size, complexity, and risk, and therefore proposes different types of changes that require different levels of authorization and control. One of these types is standard change, which is a low-risk, pre-authorized change that is well understood and follows an agreed procedure. Standard changes are typically delegated to the service provider or the service consumer, depending on the nature of the change. For example, a software development team that makes many hundreds of small changes every week can be authorized to approve and implement these changes themselves, as long as they follow the agreed change model and comply with the relevant policies and standards. This way, the software development team can benefit from faster and more efficient change delivery, while minimizing the overhead and bureaucracy of the change enablement process. Therefore, the best answer is D. The other members of the software development team, as they can act as the change authority for standard changes within their scope of work. References:
ITIL 4 Change Management Process | Blog | Digital.ai1
ITIL 4’s Move from Change Management to Change Enablement2

Explanation
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
ITIL4 Service Value Chain [ITIL4 SVC Activities with Examples], section “ITIL 4 Service Value Chain Model”

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

An ‘outside in’ approach is one that focuses on the customer perspective and value, rather than the internal processes and governance of the IT organization. According to ITIL 4, this approach helps to co-create value with customers and users, and align the IT services with the business strategy and outcomes. Therefore, conducting customer and user satisfaction surveys to gather feedback on how customers and users perceive the support of IT services is an example of an ‘outside in’ approach, as it helps to understand the customer needs, expectations, and experiences. The other options are examples of an ‘inside out’ approach, as they focus on the internal aspects of the IT organization, such as the suppliers, the technical teams, and the software tools, rather than the customer value and outcomes. References:
* ITIL and Value: Co-Creating Value in Organisations with ITIL 41
* Using ITIL to move to a service culture2
* ITIL 4 Managing Professional Transition Module
* ITIL 4 Managing Professional Transition Module – Courseware

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

Explanation
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