ITIL Implementation - Process Structure: Difference between revisions
From IT Process Wiki
No edit summary |
No edit summary |
||
| Line 54: | Line 54: | ||
*Determination of the service management processes which are to be introduced | *Determination of the service management processes which are to be introduced | ||
*Breakdown of processes into sub-processes | *Breakdown of processes into sub-processes | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
| Line 67: | Line 66: | ||
The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map] contains a generic process structure so it can be used to support this step. | The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map] contains a generic process structure so it can be used to support this step. | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
| Line 74: | Line 72: | ||
*Results of the [[ITIL Implementation - ITIL Assessment|as-is process assessment]] | *Results of the [[ITIL Implementation - ITIL Assessment|as-is process assessment]] | ||
*Project objectives ("What is the motivation for introducing ITIL best practice?"). | *Project objectives ("What is the motivation for introducing ITIL best practice?"). | ||
==Results/ Deliverables== | ==Results/ Deliverables== | ||
*Structured breakdown of the ITIL processes to be introduced | *Structured breakdown of the ITIL processes to be introduced | ||
==Success factors== | ==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. | *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== | ==Relevant views of the ITIL Process Map== | ||
[[image:thumb-itil-process-overview.jpg|thumb|400px|right|alt=ITIL overview diagram|link=https://wiki.en.it-processmaps.com/index.php/File:Thumb-itil-process-overview.jpg|Fig. 2: Overview diagram, depicting ITIL process interdependencies]] | [[image:thumb-itil-process-overview.jpg|thumb|400px|right|alt=ITIL overview diagram|link=https://wiki.en.it-processmaps.com/index.php/File:Thumb-itil-process-overview.jpg|Fig. 2: Overview diagram, depicting ITIL process interdependencies]] | ||
The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map] contains a hierarchical structure of ITIL processes | The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map] contains a hierarchical structure of ITIL processes - see fig. 1: [https://wiki.en.it-processmaps.com/images/pdf/generic-itil-process-structure.pdf Reference process structure (.pdf)]. This generic process structure can be used as a starting point. | ||
Process overviews (see [[media:thumb-itil-process-overview.jpg| | Process overviews (see [[media:thumb-itil-process-overview.jpg|fig. 2]]) depict the process interdependencies and help to choose an adequate to-be process structure. | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
==Resources== | ==Resources== | ||
*[1] [[ | *[1] [[ITIL_Processes#ITIL_Processes_according_to_ITIL_V3|ITIL processes - ITIL process descriptions]] | ||
*[2] [https://wiki.en.it-processmaps.com/images/pdf/generic-itil-process-structure.pdf Generic ITIL process structure (.pdf)] - Example: ITIL Service Operation | *[2] [https://wiki.en.it-processmaps.com/images/pdf/generic-itil-process-structure.pdf Generic ITIL process structure (.pdf)] - Example: ITIL Service Operation | ||
==Following project activity== | ==Following project activity== | ||
→ ITIL Implementation - Step 6: '''[[ITIL Implementation - Process Interfaces|Definition of Process Interfaces]]''' | → ITIL Implementation - Step 6: '''[[ITIL Implementation - Process Interfaces|Definition of Process Interfaces]]''' | ||
==Notes== | ==Notes== | ||
<html>By:  Andrea Kempter <a rel="author" href="https:// | <html>By:  Andrea Kempter <a rel="author" href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Andrea Kempter | Profile on LinkedIn" alt="Author: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps. | ||
<p> </p> | <p> </p> | ||
| Line 150: | Line 138: | ||
<meta itemprop="alternativeHeadline" content="Step 5: Definition of the To-Be Process Structure" /> | <meta itemprop="alternativeHeadline" content="Step 5: Definition of the To-Be Process Structure" /> | ||
<link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/1/1f/Thumb_to_be_process_structure.jpg" title="Selection of Relevant ITIL Processes" /> | <link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/1/1f/Thumb_to_be_process_structure.jpg" title="Selection of Relevant ITIL Processes" /> | ||
<link itemprop="author" href="https:// | <link itemprop="author" href="https://www.linkedin.com/in/andreakempter" /> | ||
<meta itemprop="author" content="Andrea Kempter" /> | <meta itemprop="author" content="Andrea Kempter" /> | ||
<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | <meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | ||
Revision as of 17:57, 29 March 2019
| Step 5: Definition of the To-Be Process Structure |
The conclusions drawn from the analysis of the current situation provide the basis for developing the to-be process structure.
As a first step, a list should be drawn up with the processes and sub-processes which are to be introduced or improved, resulting in a structured process breakdown.
Objectives
- 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 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 ITIL Process Map contains a generic process structure so it can be used to support this step.
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
The ITIL Process Map contains a hierarchical structure of ITIL processes - see fig. 1: Reference process structure (.pdf). This generic process structure can be used as a starting point.
Process overviews (see fig. 2) depict the process interdependencies and help to choose an adequate to-be process structure.
Resources
- [1] ITIL processes - ITIL process descriptions
- [2] Generic ITIL process structure (.pdf) - Example: ITIL Service Operation
Following project activity
→ ITIL Implementation - Step 6: Definition of Process Interfaces
Notes
By: Andrea Kempter 
, IT Process Maps.
Objectives › Description › Prerequisites › Results/ Deliverables › Success Factors
