ITIL Implementation - Process Structure: Difference between revisions
From IT Process Wiki
mNo edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
|} | |} | ||
Following the analysis of the initial situation, it can be decided in more detail where the ITIL project will put its focus. In practice this means to determine which ITIL processes are to be introduced, resulting in in a structured process breakdown. | |||
<p> </p> | |||
==== Objective of this Project Step ==== | |||
* Determination of the Service Management processes which are to be introduced | |||
* Breakdown of processes into sub-processes | |||
<p> </p> | |||
==== Description ==== | ==== Description ==== | ||
[[image:Thumb_to_be_process_structure.jpg|frame|right|Figure 1: Selection of Relevant ITIL Processes from the Reference Process Structure]] | [[image:Thumb_to_be_process_structure.jpg|frame|right|alt=ITIL Process Structure|Figure 1: Selection of Relevant ITIL Processes from the Reference Process Structure]] | ||
The [[ITIL Processes|ITIL processes]] to be introduced often result in a direct way from the project objectives: | The [[ITIL Processes|ITIL processes]] to be introduced often result in a direct way from the project objectives: | ||
If the project serves the objective of enhancing user support, | If the project serves the objective of enhancing user support, the "[[Incident Management|Incident Management]]" process is to be established or improved. Because of their close links with Incident Management, the "[[Problem Management|Problem Management]]" and "[[Service Asset and Configuration Management|Service Asset and Configuration Management]]" processes should also be included in the project scope. | ||
The aim of this project step is primarily to choose the ITIL processes and sub-processes. The to-be process structure does not contain detailed process descriptions - these are developed at a later stage. | The aim of this project step is primarily to choose the ITIL processes and sub-processes. The to-be process structure does not contain detailed process descriptions - these are developed at a later stage. | ||
| Line 27: | Line 35: | ||
ITIL process templates (e.g. the [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3]) can be used to support this step because they contain a generic process structure. | ITIL process templates (e.g. the [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3]) can be used to support this step because they contain a generic process structure. | ||
<p> </p> | |||
==== Prerequisites ==== | ==== Prerequisites ==== | ||
* Results of the [[ITIL Implementation - ITIL Assessment|as-is process assessment]] | * Results of the [[ITIL Implementation - ITIL Assessment|as-is process assessment]] | ||
* Project objectives ( | * Project objectives ("What is the motivation for introducing ITIL Best Practice?"). | ||
<p> </p> | |||
==== Results/ Deliverables ==== | ==== Results/ Deliverables ==== | ||
* Structured breakdown of the ITIL processes to be introduced | * Structured breakdown of the ITIL processes to be introduced | ||
<p> </p> | |||
==== Success Factors ==== | ==== Success Factors ==== | ||
| Line 45: | Line 54: | ||
* The definition of the process structure should not try to anticipate later project steps; the aim of this step is to identify the processes and sub-processes to be introduced, not to specify processes in great detail. | * The definition of the process structure should not try to anticipate later project steps; the aim of this step is to identify the processes and sub-processes to be introduced, not to specify processes in great detail. | ||
<p> </p> | |||
[[image:thumb-itil-process-overview.jpg|frame|right|Figure 2: Overview diagram, depicting ITIL process interdependencies]] | [[image:thumb-itil-process-overview.jpg|frame|right|alt=ITIL overview diagram|Figure 2: Overview diagram, depicting ITIL process interdependencies]] | ||
==== <span style="color:#5d5d5d">Relevant Views of the ITIL Process Map V3</span>==== | ==== <span style="color:#5d5d5d">Relevant Views of the ITIL Process Map V3</span>==== | ||
<span style="color:#5d5d5d">The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3] contains a complete ITIL-compliant process structure, arranged in a hierarchical way (see Figure 1). This generic process structure can be used in many cases with only minor changes.</span> | <span style="color:#5d5d5d">The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3] contains a complete ITIL-compliant process structure, arranged in a hierarchical way ''(see Figure 1)''. This generic process structure can be used in many cases with only minor changes.</span> | ||
<span style="color:#5d5d5d">Process overviews (see Figure 2) depict the process interdependencies and help to choose an adequate to-be process structure.</span> | <span style="color:#5d5d5d">Process overviews ''(see Figure 2)'' depict the process interdependencies and help to choose an adequate to-be process structure.</span> | ||
<p> </p> | |||
'''Following Project Activity''': | '''Following Project Activity''': | ||
| Line 60: | Line 71: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
<p> </p> | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V3]][[Category:ITIL implementation]] | [[Category:ITIL V3]][[Category:ITIL implementation]] | ||
<!-- --- --> | <!-- --- --> | ||
Revision as of 16:53, 16 September 2011
<seo metakeywords="itil process structure, itil structure, it process structure" metadescription="Definition of the To-Be Process Structure - Fig. 1: Selection of Relevant ITIL Processes from the Reference Process Structure." />
| Step 5: Definition of the To-Be Process Structure |
Following the analysis of the initial situation, it can be decided in more detail where the ITIL project will put its focus. In practice this means to determine which ITIL processes are to be introduced, resulting in in a structured process breakdown.
Objective of this Project Step
- Determination of the Service Management processes which are to be introduced
- Breakdown of processes into sub-processes
Description
The ITIL processes to be introduced often result in a direct way from the project objectives:
If the project serves the objective of enhancing user support, the "Incident Management" process is to be established or improved. Because of their close links with Incident Management, the "Problem Management" and "Service Asset and Configuration Management" processes should also be included in the project scope.
The aim of this project step is primarily to choose the ITIL processes and sub-processes. The to-be process structure does not contain detailed process descriptions - these are developed at a later stage.
ITIL process templates (e.g. the ITIL Process Map V3) can be used to support this step because they contain a generic process structure.
Prerequisites
- Results of the as-is process assessment
- Project objectives ("What is the motivation for introducing ITIL Best Practice?").
Results/ Deliverables
- Structured breakdown of the ITIL processes to be introduced
Success Factors
- The definition of the process structure should not try to anticipate later project steps; the aim of this step is to identify the processes and sub-processes to be introduced, not to specify processes in great detail.
Relevant Views of the ITIL Process Map V3
The ITIL Process Map V3 contains a complete ITIL-compliant process structure, arranged in a hierarchical way (see Figure 1). This generic process structure can be used in many cases with only minor changes.
Process overviews (see Figure 2) depict the process interdependencies and help to choose an adequate to-be process structure.
Following Project Activity:
→ ITIL Implementation - Step 6: Definition of Process Interfaces
