ITIL Implementation - Process Design

From IT Process Wiki
Revision as of 17:41, 16 September 2011 by Andrea (talk | contribs)

<seo metakeywords="itil process design, itil process flow" metadescription="ITIL Process Design - Designing ITIL Processes ... a consensus must be reached and documented in the form of detailed process flow diagrams." />

DE - ES - ITIL Process Design - Designing the ITIL Processesdiese Seite auf Deutschesta página en español
DE - ES - ITIL Process Design - Designing the ITIL Processes


Step 8: Designing the ITIL Processes in Detail

 

Determining the sequences of single activities within each process is bound to be relatively labor-intensive. This makes it very important to concentrate on the areas which really matter.

 

Objective of this Project Step

ITIL process design
Figure 1: Detailed Process Descriptions (ITIL process flows)
  • Detailed definition of the individual activities within the ITIL processes ("ITIL process flows")
  • Definition of guidelines/ checklists to support process execution
  • Detailed definition of the process outputs

 

Description

The detailed activities within the individual processes must be discussed with all relevant parties, in order to include into the design as much experience and knowledge as possible. The Process Owner is responsible for this task.

As a result, a consensus must be reached and documented in the form of detailed process flow diagrams.

The framework of process structure and interfaces for this task was set up within the previous project steps: Due to the prior definition of the project interfaces, it is already established upon which inputs a process may build, and which results it must deliver for successive processes. With this information clearly specified it becomes much easier to define a process flow in a simple, straightforward way.

Additional information to facilitate the process execution, describing procedures or deliverables in detail, can be added in the form of linked checklists/ document templates. For example there could be a couple of extra pages describing what sort of information is to be collected during the initial registration of an Incident.

 

Prerequisites

 

Results/ Deliverables

  • Detailed process descriptions in the form of Activity Chains
  • Guidelines/ checklists
  • Definitions of the process outputs

 

Success Factors

  • Being well prepared is essential at this point in order to avoid the risk of producing a large number of uncorrelated and oversized documents: Process descriptions should give a clear idea of the required activities and their sequential order, but too many details should be avoided. Too much detail usually means that these documents are soon out of date, as they are too bulky to be an effective tool for the Process Owners.
  • It is recommended to confine further details into linked documents (e. g. guidelines and definitions of process outputs).
  • It is decisive for a successful process implementation to include all the relevant parties in this phase of the project, in order to make use of their wide range of experiences from daily business, and to ensure that the redesigned processes will be accepted and adhered to.

 

Relevant Views of the ITIL Process Map V3

ITIL checklists
ITIL checklists are used to enhance the ITIL process flows

The ITIL Process Map V3 makes detailed process flows available for all ITIL processes (see Figure 1). These models fulfill the requirements of ITIL and ISO 20000.

Modifications will often be necessary to allow for special circumstances or preferences; these alterations are of course permitted, as long as the ITIL guiding ideas are followed.

As an addition to the detailed ITIL process flows, checklists/ document templates (see Figure 2) are available within the ITIL Process Map, describing procedures or process outputs in detail where necessary. We make samples of our ITIL checklists/ document templates available for you in this IT Process Wiki:

"The most sought-after ITIL V3 Checklists".

 

Following Project Activity

→ ITIL Implementation - Step 9: Selection and Implementation of Application Systems