ITIL Implementation - Process Controlling: Difference between revisions

From IT Process Wiki
No edit summary
 
mNo edit summary
Line 1: Line 1:
<seo metakeywords="itil process control, itil control, itil procedures and processes" metadescription="A coherent strategy for ITIL process control not only helps to assess whether the objectives followed with the ITIL introduction are achieved, ..." />
<imagemap>
Image:ITIL-Wiki-de-es.jpg|DE - ES - ITIL Process Control - ITIL Control|100px
rect 0 0 50 30 [https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_Prozess-Controlling diese Seite auf Deutsch]
rect 50 0 100 30 [https://wiki.es.it-processmaps.com/index.php/Implementaci%C3%B3n_de_ITIL_-_Controles_de_procesos esta página en español]
desc none
</imagemap>
<br style="clear:both;"/>
{|
{|
! align="right" width="80%"|
|-
! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_Prozess-Controlling diese Seite auf Deutsch]
| style="border-bottom:1px solid grey;" |<big><strong> Step 7: Establishing ITIL Process Control </strong></big>
|}
|}


'''''Step 7: Establish Process Controlling'''''


Now it is known which ITIL processes are to be introduced, how these are structured, and which interfaces to other processes exist.
==== Description ====


Before these processes are defined in more detail, one should think about ways to judge if they are running according to expectations. This takes place by the establishment of a suitable process controlling.
Once the [[ITIL Implementation - Process Structure|structure of processes]] and [[ITIL Implementation - Process Interfaces|their interfaces]] are clear one should define the approach for ensuring that those processes are running according to expectations (known as “Process Control”).


A coherent process controlling not only helps to assess whether the objectives followed with the ITIL introduction are achieved, but also has long-term benefits, in that it delivers the necessary data for a continuous process improvement.
A coherent strategy for process control not only helps to assess whether the objectives followed with the ITIL introduction are achieved, but also has long-term benefits, in that it delivers the necessary data for a continuous process improvement.


How to decide whether a process “runs well” or not? Objective criteria (quality measurements,  
How to decide whether a process “runs well” or not? Objective criteria (quality measurements,  
also known as Key Performance Indicators [KPIs]) must be determined for this purpose.
also known as [[ITIL Key Performance Indicators|Key Performance Indicators or KPIs)]] must be determined for this purpose.


Only then, when it is clear which quality measurements a process must achieve, can its inner details be confi­dently designed with these goals in mind.
Only then, when it is clear which quality measurements a process must achieve, can its inner details be confi­dently designed with these goals in mind.


 
===== Determine the Process Owners =====
== Determine the Process Owners ==


Successful management of a process depends on Process Owners who identify themselves closely with their task, and who are sufficiently empowered and equipped with the necessary means.
Successful management of a process depends on Process Owners who identify themselves closely with their task, and who are sufficiently empowered and equipped with the necessary means.
It is therefore important to have the Process Owners (as the ones responsible for running the processes after their implementation) as active participants in the implementation project, so they should be named at an early stage.
In most cases, this step was taken implicitly during an earlier project phase: With the assignment of the ITIL roles, the choice of the Process Owners is often straightforward (the Problem Manager will, for example, be the owner of the Problem Management process).
== Define IT Metrics and Measurement Procedures ==


With the aid of objective, pre-defined quality criteria the Process Owners are in a position to assess whether their processes are running “well”, and are thus able to decide upon the need for process improvements.
It is therefore important to have the Process Owners (being the ones responsible for running the processes after their implementation) as active participants in the implementation project, so they should be named at an early stage.


There are also quantitative measurements, which are used by the Process Owner to steer the resources within a process (e.g. the number of Incidents received by the Service Desk over the course of time).
In most cases, the selection of Process Owners is rather straightforward (the Problem Manager will, for example, be the owner of the Problem Management process).


==== Objective of this Project Step ====
===== Define IT Metrics and Measurement Procedures =====


* Determination of measurements (KPIs) for the processes to be introduced
Process Owners use objective quality criteria to assess whether their processes are running “well”. This puts them in a position to decide upon the need for process improvements.
* Definition of measurement procedures for the KPIs


==== Prerequisites ====
The first step when selecting suitable KPIs must always be to decide upon the overall objectives of a process (Example: A high first-resolution rate at the Service Desk). With these objectives in mind, it will be possible to select KPIs which are suitable to measure a successful process execution.
 
* Structure of the Service Management processes to be introduced
 
==== Results/ Deliverables ====
* Measurements (KPIs) for the processes to be introduced
* Measurement procedures for the KPIs
 
==== Description ====


Quality criteria (or KPIs) help to decide whether a process is running accor­ding to expectations. The first step when selecting suitable KPIs must therefore be to decide upon the overall objectives of a process (Example: a high first-resolution rate at the Service Desk).
There are also quantitative measures, which are used by the Process Owner to steer the resources within a process (e.g. the number of Incidents received by the Service Desk over the course of time).


With these objectives in mind, it will be possible to select KPIs which are suitable to measure a successful process execution.
Which KPIs are eventually chosen is dependent, amongst other things, upon the available possibilities for their measurement. Ideally, KPIs can be computed automatically, e. g. via a Service Desk system. The measurement procedures defined here are therefore also requirements for the systems to be implemented.


The ITIL Wiki contains a choice of [[ITIL Key Performance Indicators|suitable KPIs]]. These KPIs were taken from the ITIL recommendations; they have been in some parts supplemented with elements from COBIT. Where necessary, further suggestions for KPIs are available in several books on IT Service Management.
This ITIL Wiki contains a choice of [[ITIL Key Performance Indicators|suitable KPIs]]. These KPIs were taken from the ITIL recommendations; they have been in some parts supplemented with elements from COBIT. Where necessary, further suggestions for KPIs are available in several books on IT Service Management.
It should however be noted, that process controlling is not about setting up as extensive an arsenal of KPIs as possible: Practice has proven that an over-complex structure of measurements creates a disproportionate amount of effort, gains little acceptance, and after a short period, is no longer applied.


Quality measurements should also not be seen as a “universal cure”, but as a practical assistance for process participants and Process Owners. If too much importance is placed upon the achievement of isolated measurements, this often restricts the view for the greater good of all parties envolved in an undesired way.
Process control should not be about setting up as extensive an arsenal of KPIs as possible: Practice has proven that an over-complex structure of measures creates a disproportionate amount of effort, gains little acceptance, and after a short period, is no longer applied.Rather, few significant measures should be defined so that KPI measurement and reporting may be executed with a justifiable amount of time and effort.


Which KPIs are eventually chosen is dependent, amongst other things, upon the available possibilities for their measurement. A measurement procedure is to be defined for every KPI.
===== Set KPI targets =====
Ideally, KPIs can be computed automatically, e. g. via a Service Desk system. The measurement procedures defined here are therefore also requirements for the systems to be implemented.


Target values for the KPIs define “success” in an objective way and set goals for the Process Owner. It must be noted, however, that target values (like first-time resolution rates) cannot be easily transferred from business to business without precaution.
Target values for the KPIs define “success” in an objective way and set goals for the Process Owner. It must be noted, however, that target values (like first-time resolution rates) cannot be easily transferred from business to business without precaution.


It is recommendable not to define fixed KPI targets initially, but to merely select suitable KPIs and start measuring. Once a statistically significant number of measurement results are present after a certain time, there will be a more solid base for setting targets.
It is recommendable not to define fixed KPI targets initially, but to merely select suitable KPIs and start measuring. Once a statistically significant number of measurement results are present after a certain time there will be a more solid base for setting targets.


==== Success Factors ====
===== Define the Reporting Procedures =====


Only KPIs which are actually measurable must be used
Reporting on process quality is the final element within process control. Reporting procedures must be defined, specifying which KPIs are reported in which form to particular recipients.
Not as many as possible, but rather few significant measurements should be defined, so that the measurement and the reporting of the KPIs may be executed with a justifiable amount of time and effort.


IT Management should make a point of the fact that the use of KPIs serves the purpose of improving processes and not the penalisation of employees. There might otherwise be the danger of the participants developing strategies in order to tweak the statistics in their favour, which would be against the interests of the IT organisation on the whole.
==== Objective of this Project Step ====


Targets for KPIs (especially in the initial phase after the introduction of new processes) are to be reviewed at regular intervals; it is not always necessarily best to strive for top grades – under certain circumstances it is, for example, acceptable to have a lower initial resolution-rate at the Service Desk, if many of the enquiries necessitate specialist knowledge.
* Determination of [[ITIL Key Performance Indicators|measurements (KPIs)]] for the processes to be introduced
* Definition of measurement procedures for the KPIs
* Definition of reporting procedures


==== Prerequisites ====


== Define the Reporting Procedures ==
* [[ITIL Implementation - Process Structure|Structure of the ITIL processes]] to be introduced
* [[ITIL Processes|Process objectives]]


Reporting on process quality is the final element within process control.
==== Results/ Deliverables ====
* Assignment of Process Owners
* Measurements (KPIs)
* Measurement procedures for the KPIs
* Specification of reporting procedures


Reporting procedures define which KPIs are reported in which form to particular recipients.
==== Success Factors ====


==== Objective of this Project Step ====
* Only KPIs which are actually measurable must be used
* IT Management should make a point of the fact that the use of KPIs serves the purpose of improving processes and not the penalisation of employees. There might otherwise be the danger of the participants developing strategies in order to tweak the statistics in their favour, which would be against the interests of the IT organization on the whole.
* Targets for KPIs (especially in the initial phase after the introduction of new processes) are to be reviewed at regular intervals; it is not always necessarily best to strive for top grades – under certain circumstances it is, for example, acceptable to have a lower initial resolution-rate at the Service Desk, if many of the enquiries necessitate specialist knowledge.


* Definition of contents and recipients of the reports on process quality


==== Prerequisites ====
==== <span style="color:#5d5d5d">Relevant Views of the ITIL Process Map V3</span>====
 
* Measurements (KPIs) for the processes to be introduced


==== Results/ Deliverables ====
<span style="color:#5d5d5d">The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3] contains a choice of suitable KPIs for the most important ITIL processes. Additional suggestions for KPIs are available in the [[Additional Information on ITIL|ITIL core books]] and in several other books on IT Service Management.</span>


* Overview of the different reports on process quality
* Recipients or target-groups for the reports
* Structures/ templates for the different reports


==== Description ====
'''Following Project Activity''':
Starting from a list of the target-groups, the information needs of the recipients are determined.
 
This allows to define a variety of reports, with targeted selections of KPIs or statistical evaluations, resulting in a template for each of these reports.
 
==== Success Factors ====


* The reports should show a degree of detail which is adjusted to the requirements of the relevant target-group, so that for instance, IT Management receives an overview of important metrics, problem areas and measures for process improvement
&#8594; ITIL Implementation - Step 8: '''[[ITIL Implementation - Process Design|Designing the Processes in Detail]]'''


* The Process Owners, however, require more detailed information in order to manage their processes




== Following Process Activity ==
<!-- This page is assigned to the following categories: -->
''Step 8:'' '''''[[ITIL Implementation - Process Design|Design the Processes in Detail]]'''''
[[Category:ITIL V3]][[Category:ITIL implementation]]
<!-- --- -->

Revision as of 20:29, 26 July 2011

<seo metakeywords="itil process control, itil control, itil procedures and processes" metadescription="A coherent strategy for ITIL process control not only helps to assess whether the objectives followed with the ITIL introduction are achieved, ..." />

DE - ES - ITIL Process Control - ITIL Controldiese Seite auf Deutschesta página en español
DE - ES - ITIL Process Control - ITIL Control


Step 7: Establishing ITIL Process Control


Description

Once the structure of processes and their interfaces are clear one should define the approach for ensuring that those processes are running according to expectations (known as “Process Control”).

A coherent strategy for process control not only helps to assess whether the objectives followed with the ITIL introduction are achieved, but also has long-term benefits, in that it delivers the necessary data for a continuous process improvement.

How to decide whether a process “runs well” or not? Objective criteria (quality measurements, also known as Key Performance Indicators or KPIs) must be determined for this purpose.

Only then, when it is clear which quality measurements a process must achieve, can its inner details be confi­dently designed with these goals in mind.

Determine the Process Owners

Successful management of a process depends on Process Owners who identify themselves closely with their task, and who are sufficiently empowered and equipped with the necessary means.

It is therefore important to have the Process Owners (being the ones responsible for running the processes after their implementation) as active participants in the implementation project, so they should be named at an early stage.

In most cases, the selection of Process Owners is rather straightforward (the Problem Manager will, for example, be the owner of the Problem Management process).

Define IT Metrics and Measurement Procedures

Process Owners use objective quality criteria to assess whether their processes are running “well”. This puts them in a position to decide upon the need for process improvements.

The first step when selecting suitable KPIs must always be to decide upon the overall objectives of a process (Example: A high first-resolution rate at the Service Desk). With these objectives in mind, it will be possible to select KPIs which are suitable to measure a successful process execution.

There are also quantitative measures, which are used by the Process Owner to steer the resources within a process (e.g. the number of Incidents received by the Service Desk over the course of time).

Which KPIs are eventually chosen is dependent, amongst other things, upon the available possibilities for their measurement. Ideally, KPIs can be computed automatically, e. g. via a Service Desk system. The measurement procedures defined here are therefore also requirements for the systems to be implemented.

This ITIL Wiki contains a choice of suitable KPIs. These KPIs were taken from the ITIL recommendations; they have been in some parts supplemented with elements from COBIT. Where necessary, further suggestions for KPIs are available in several books on IT Service Management.

Process control should not be about setting up as extensive an arsenal of KPIs as possible: Practice has proven that an over-complex structure of measures creates a disproportionate amount of effort, gains little acceptance, and after a short period, is no longer applied.Rather, few significant measures should be defined so that KPI measurement and reporting may be executed with a justifiable amount of time and effort.

Set KPI targets

Target values for the KPIs define “success” in an objective way and set goals for the Process Owner. It must be noted, however, that target values (like first-time resolution rates) cannot be easily transferred from business to business without precaution.

It is recommendable not to define fixed KPI targets initially, but to merely select suitable KPIs and start measuring. Once a statistically significant number of measurement results are present after a certain time there will be a more solid base for setting targets.

Define the Reporting Procedures

Reporting on process quality is the final element within process control. Reporting procedures must be defined, specifying which KPIs are reported in which form to particular recipients.

Objective of this Project Step

  • Determination of measurements (KPIs) for the processes to be introduced
  • Definition of measurement procedures for the KPIs
  • Definition of reporting procedures

Prerequisites

Results/ Deliverables

  • Assignment of Process Owners
  • Measurements (KPIs)
  • Measurement procedures for the KPIs
  • Specification of reporting procedures

Success Factors

  • Only KPIs which are actually measurable must be used
  • IT Management should make a point of the fact that the use of KPIs serves the purpose of improving processes and not the penalisation of employees. There might otherwise be the danger of the participants developing strategies in order to tweak the statistics in their favour, which would be against the interests of the IT organization on the whole.
  • Targets for KPIs (especially in the initial phase after the introduction of new processes) are to be reviewed at regular intervals; it is not always necessarily best to strive for top grades – under certain circumstances it is, for example, acceptable to have a lower initial resolution-rate at the Service Desk, if many of the enquiries necessitate specialist knowledge.


Relevant Views of the ITIL Process Map V3

The ITIL Process Map V3 contains a choice of suitable KPIs for the most important ITIL processes. Additional suggestions for KPIs are available in the ITIL core books and in several other books on IT Service Management.


Following Project Activity:

→ ITIL Implementation - Step 8: Designing the Processes in Detail