Basic Ideas behind ITIL

From IT Process Wiki
Jump to: navigation, search

share this page on LinkedInshare this page on Twittershare this page
Basic Ideas behind ITIL


ITIL® describes several processes, organized around five service lifecycle stages. An example would be the Incident Management process in the Service Operation stage.

So it is tempting to conclude that "adopting ITIL" means "implementing" the ITIL processes as described in the books, one after another.

ITIL basic ideas and concepts
ITIL basic concepts and ideas
Yet these processes cannot be seen in isolation.

The purpose of the ITIL processes is to bring to bear a number of key principles, and in many cases a number of ITIL processes work together to achieve a common goal.

And what is more, ITIL is not a standard but a set of recommendations.

Organizations that wish to adopt the ITIL approach will have to adapt the ITIL advice to their particular situation and needs. There is no question of implementing every ITIL process to the letter.

The key to successfully using ITIL® is a good understanding of the ideas and principles behind the IT Infrastructure Library. Once these principles are understood, service providers are in a position to decide which ITIL processes address their specific requirements, and to adopt those parts of the ITIL advice that solve their particular needs.

There is no definitive list of ITIL principles, so the list below should be seen as a summary of some important key ideas behind ITIL.

Strategic thinking

Strategic thinking helps service providers stay relevant in the longer term.

Once in a while, organizations should take time to assess their current situation and likely future developments. Based on this assessment, they should define a strategy or road-map, for example for developing new capabilities and service offerings.

  • Strategic thinking in ITIL is covered to a large extent by the Strategy Management process.
  • But other processes contribute, too: For example, the Business Relationship Management process ensures that service providers learn about the customers' needs - which are an important input for developing the Service Strategy.

Customer focus

Customer-focus is about keeping customers happy and providing adequate services for certain groups of customers, based on their needs.

To this end, service providers should understand their customers' needs, design a range of services according to those needs, and collect feedback from their customers.

ITIL processes that contribute to customer-centricity are, for example,

Service definitions

Delivering services to expectations is an all-important theme in ITIL, and this is not possible if the services are not properly defined.

So service definitions are very important concept in ITIL, and ITIL refers to several documents for defining the services, such as

There are a number of processes in ITIL where we define the service properties:

All services with their properties are listed in the Service Portfolio.

Excellent customer support

ITIL puts strong emphasis on creating a good customer experience, based on a consistent, professional approach to managing Incidents and Service Requests.

Good customer support obviously means resolving incidents swiftly and keeping customers informed. But customer support is also about detecting issues early, so incidents can be dealt with before a large number of users are affected.

Accordingly, Incident Management and Request Fulfilment are essential ITIL processes for creating the perfect customer experience.

In addition, the Event and Problem Management processes try to keep the number of incidents low:

  • Event Management ensures that any deviations from normal operation are detected before they develop into incidents,
  • while Problem Management takes care of resolving the root causes of recurring incidents.

Continual improvement

The purpose of Continual Service Improvement (CSI) is to avoid dangerous stagnation.

The world around us is changing all the time, and we have to ask ourselves on a regular basis if we are doing a good job or if there is anything that could be done in a different, better way.

Continual improvement has a long history and it is often associated with a well-established management method for continual improvement, known as the "Deming Cycle" with four steps: Plan, Do, Check, and Act.

Continual Service Improvement is the last of the five ITIL service lifecycle stages, and it is here where most of the improvement activities take place. But many other ITIL processes provide crucial inputs for service improvement. For example, Service Level Management contains activities for producing Service Level Reports with statistics about agreed vs. achieved service levels.

IT Service Management as interface between IT and the business

Traditional setup of the IT organization

Traditional Setup of the IT Organization

Traditionally, there were two separate channels for the communication between the IT organization and the business: One channel between the client and application development for the development or modification of applications, and a second channel for operational isssues.

This approach suffers from several drawbacks:

  • Operational requirements, ensuring the error-free running of an application, may not be taken into account during the development phase.
  • IT operations is not fully able to control the release of applications into the productive environment; this might cause unforeseen side effects.


Setup of the IT organization according to ITIL

Setup of the IT Organization according to ITIL

An implementation method based on ITIL resolves these problems by placing IT service management after application Management and ICT infrastructure management: Thus, IT service management mediates between development and production on the side of the IT organization, and the client on the business-side.

The activities in application development and IT operations are now co-ordinated and there is one communication channel for the provision of IT "as a service".

 

By:  Stefan Kempter   and  Andrea Kempter Contributor: Andrea Kempter, IT Process Maps GbR, IT Process Maps.