ITIL for Small and Medium-Sized Businesses

From IT Process Wiki
Revision as of 19:06, 7 October 2007 by Andrea (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
diese Seite auf Deutsch

An opinion repeatedly heard, is that ITIL is purely suitable for large businesses, where extensive resources are available for the implementation of the ITIL processes.

In actual fact however, the guiding ideas behind ITIL are valuable for businesses of all sizes, from large corporations to small and medium-sized businesses. What counts is to leverage the benefits of the ITIL principles, concentrating upon feasibility and relevance during the implementation.


Establishing Responsibilities

In the various ITIL disciplines, process owners are nominated, whose task in the role of a „Manager“, comprises ensuring the seamless and efficient flow of processes within a particular field of IT activity.

Doing what's already Done Today, only Better

Correctly implemented, an alignment according to ITIL will not involve the creation of additional work: The reason for the great success of ITIL lies in its proven contribution to more economical working practices.

Notifications of service interruptions have, for example, always been received from users, and registered and eliminated by the IT organisation. It has however become common wisdom that a technical specialist does not have to be engaged for the elimination of every interruption: Simple circumstances can in many cases be processed by a Service Desk.

Example: Problem Management

The introduction of Problem Management does not necessarily have to involve the hiring of an additional Problem Manager. It is rather a matter of someone taking responsibility for the identification of the causes behind repetitive interruptions (Incidents), or for ensuring that interruptions are pro-ac­tively avoided wherever feasible.

For this purpose, the Problem Manager uses existing personnel resources: The aim is to avoid conflicting and unnecessary action, ant to co-ordinate all activities within the IT organisation for the technical analysis and root cause elimination. The Problem Manager commissions the colleagues from Application Development and IT Operations, ensuring that the necessary information flows, and thereby contributes to the fast solution of the problem.

Such an approach is evidently expedient and necessary for large and small IT organisations alike. In smaller businesses however, the role of Problem Manager might be assumed by a single employee in conjunction with the role of Incident Manager.

Example: Change Management

A similar strategy could be used in the case of Change Management, which ensures the co-ordinated processing of alterations to the IT infrastructure. The effort involved in Change Management is directly connected to the size of the business, so that this task is usually less extensive and therefore more ea­sily accomplishable within smaller and medium-sized businesses. In this case, the role of Change Manager can perhaps be assumed by a line manager from IT operations – who could, at the same time, possibly take on the role of the Release Manager, who is responsible for the roll-out of changes. The CAB, whose task consists of deciding on substantial and complex changes, will also become more manageable, and will not be convened as often as it is in the case of larger businesses.