Exin ITIL - ITIL Foundation (V4)

ITIL® has defined four dimensions that collectively are critical to the effective and efficient delivery of value to customers and other stakeholders in the form of products and services. These dimensions are:

Organizations and People

Information and Technology

Partners and Suppliers

Value Streams and Processes

https://www.bmc.com/blogs/itil-four-dimensions-service-management/

More complex incidents will usually be escalated to a support team for resolution, or even suppliers and partners who offer support for products and services they provide.

Organizations maximize co-creation of value with their customers by facilitating the outcomes they want to achieve. The four dimensions of service management have shown that a holistic approach is the best way for an organization to:

Achieve its goals in delivering quality and cost effective services

Meet the needs of its customers

Satisfy the requirements of its stakeholders

https://www.bmc.com/blogs/itil-service-value-system/

A change that must be implemented as soon as possible without strictly following the standard process e.g. to resolve an incident or implement a security patch.

The process for assessment and authorization is expedited to ensure quick implementation, so scheduling and documentation is not a priority.

The change authority may be separate from what is standard or normal practice, typically smaller in number but with greater capacity to expedite approval.

https://www.bmc.com/blogs/itil-change-enablement/

To protect the information needed by the organization to conduct its business. This includes understanding and managing risks to the confidentiality, integrity, and availability of information, as well as other aspects of information security such as authentication and non-repudiation.

https://www.bmc.com/blogs/itil-management-practices/

https://www.bmc.com/blogs/itil-service-level-management/

The purpose of the release management practice is to make new and changed services and features available for use.

Release: A version of a service or other configuration item, or a collection of configuration items, that is made available for use.

https://wiki.process-symphony.com.au/framework/lifecycle/process/release-management-itil-4/

The purpose of the service request management practice is to support the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner. Service request management is dependent upon well-designed processes and procedures, which are operationalized through tracking and automation tools to maximize the efficiency of the practice. To be handled optimally, service request management should follow these guidelines:

Service requests and their fulfilment should be standardized and automated to the greatest degree possible.

Policies should define which service requests will be fulfilled with limited or even no additional approvals so that fulfilment can be streamlined.

The expectations of users regarding fulfilment times and costs should be clearly set, based on what the organization can realistically deliver.

Opportunities for improvement should be identified and implemented to produce faster fulfilment times and take advantage of automation.

https://www.bmc.com/blogs/itil-service-request-management/

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

The first important step is identifying and managing all the stakeholder groups that an organization deals with. The first and most obvious stakeholder group is the customers, as in service management the organization’s main goal is to facilitate customer outcomes. Other examples of stakeholder collaboration include:

Developers working with other internal teams

Suppliers collaborating with the organization

Relationship managers collaborating with service consumers

Customers collaborating with each other

Internal and external suppliers collaborating with each other

The contribution to improvement of each stakeholder group at each level should be understood, as should the most effective methods to engage with them. Depending on the service and the relationship between the service provider and the service consumer, the expectations about the level and type of collaboration can vary significantly. It is important to involve stakeholders, and address their needs at all levels. Determining the type, method, and frequency of such messaging is one of the central activities related to communication.

https://www.bmc.com/blogs/itil-guiding-principles/