Pass the Exin Exin-ITIL ITIL Questions and answers with CertsForce

The purpose of the change enablement practice is to maximize the number of successful IT changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule.

A change is defined as the addition, modification, or removal of anything that could have a direct or indirect effect on services

https://www.bmc.com/blogs/itil-change-enablement/#:~:text=A%20change%20is%20defined%20as,or%20indirect%20effect%20on%20services.

“Service desk staff require training and competency across a number of broad technical and business areas. In particular, they need to demonstrate excellent customer service skills such as empathy, incident analysis and prioritization, effective communication, and emotional intelligence.

https://www.servicedeskinstitute.com/the-case-for-itil4-foundation-service-desk-analyst-training/#:~:text=%E2%80%9CService%20desk%20staff%20require%20training,effective%20communication%2C%20and%20emotional%20intelligence .

The second step is to conduct an objective current-state assessment of existing services and service management practices. This should include consideration of the users’ perception of the value being received, along with a review of people’s competencies and skills, the processes and procedures involved, the capabilities of the available technological solutions and the prevailing organizational culture. The success of an improvement initiative depends on a clear and accurate understanding of the starting point and the required impact of the initiative.

For example, an organization can measure the current net promoter score (NPS) from a customer satisfaction survey, conduct a benchmark survey against its competitors or review findings of operational statistics or audit reports to understand its current state. If this step is skipped, the current state will not be understood and there will not be an objective baseline measurement against which improvement can be measured.

https://www.bmc.com/blogs/itil-continual-improvement/

Individual metrics without a specified service context are unhelpful. They should relate to defined outcomes and not simply operational metrics. This can be achieved with balanced bundles of metrics, such as customer satisfaction and key business outcomes.

https://www.bmc.com/blogs/itil-service-level-management/#:~:text=Service%20Level%20Agreements%20(SLAs) &text=Individual%20metrics%20without%20a%20specified,satisfaction%20and%20key%20business%20outcomes.

The key inputs to the SVS are opportunity and demand. The output of the SVS is value delivered by products and services. Opportunity refers to options or possibilities to add value for stakeholders or otherwise improve the organization

https://www.bmc.com/blogs/itil-service-value-system/#:~:text=The%20key%20inputs%20to%20the,or%20otherwise%20improve%20the%20organization .

Problem Control. Problem control activities include problem analysis and documenting workarounds and known errors.

Just like incidents, problems will be prioritized based on the risk they pose in terms of probability and impact to services. Focus should be given to problems that have highest risk to services and service management.

https://www.bmc.com/blogs/itil-problem-management/#:~:text=2.,probability%20and%20impact%20to%20services .

CIs are simply any component that needs to be managed in order to deliver an IT service. A server, a virtual server, or even the configuration of an application could be considered a CI, for example

https://www.bmc.com/blogs/itil-asset-configuration-management/#:~:text=among%20your%20CIs-,Configuration%20items%20(CIs),considered%20a%20CI%2C%20for%20example .

A SWOT (also known as SLOT) analysis is a powerful strategic planning tool used to evaluate the Strengths, Weaknesses/Limitations, Opportunities and Threats to a project or business

http://steppingstonesforbusiness.co.uk/wp-content/uploads/2012/07/FS116-SWOT-Analysis-for-Continuous-Improvement.pdf

https://assyst.ifs.com/blog/the-7-guiding-principles-of-itil-4-0

Don't over-engineer solutions. Think about what you can do now.

Like focus on value, this principle is heavily focused on the prevention of waste. Waste correlates with complexity. Higher complexity means there are more opportunities for waste to creep into a system.

Focus on delivering the desired outcome, not building the most elegant and elaborate solution. Use the minimum number of steps to deliver that outcome, ensuring you are not over-processing (delivering quality above and beyond what is required).