ITIL Implementation - Key Factors - Revision history

Andrea at 17:40, 4 February 2016

2016-02-04T17:40:13Z

← Older revision		Revision as of 19:40, 4 February 2016
Line 2:		Line 2:
	<meta name="keywords" content="itil key factors" />		<meta name="keywords" content="itil key factors" />
	<meta name="description" content="ITIL Key Factors. It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers ..." />		<meta name="description" content="ITIL Key Factors. It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers ..." />
	</itpmch>		</itpmch>
	<imagemap>		<imagemap>
	Image:ITIL-Wiki-deutsch.jpg\|right\|ITIL Implementation - Key Factors		Image:ITIL-Wiki-deutsch.jpg\|right\|ITIL Implementation - Key Factors
Line 11:		Line 11:

	It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers the IT organization as a whole, taking into account the complete spectrum of IT processes. This creates the context for defining the IT Service Management processes in more detail.		It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers the IT organization as a whole, taking into account the complete spectrum of IT processes. This creates the context for defining the IT Service Management processes in more detail.
	[[Image:thumb_implementation_method.jpg\|~~frame~~\|right]]		[[Image:thumb_implementation_method.jpg\|thumb\|180px\|right\|link=https://wiki.en.it-processmaps.com/index.php/File:Thumb_implementation_method.jpg]]

	In order to ensure the long-term success of the project, any [[ITIL Implementation\|ITIL introduction]] must not be reduced to the introduction of "ITIL-compliant" application systems, like e.g. a Help Desk system.		In order to ensure the long-term success of the project, any [[ITIL Implementation\|ITIL introduction]] must not be reduced to the introduction of "ITIL-compliant" application systems, like e.g. a Help Desk system.
Line 18:		Line 18:

	In line with these requirements, the suggested ITIL Implementation Method describes how – starting from an analysis of the as-is situation – an IT Service Management according to ITIL and related application systems are introduced in stages. At the same time, Process Management principles take root step-by-step within the IT organization.		In line with these requirements, the suggested ITIL Implementation Method describes how – starting from an analysis of the as-is situation – an IT Service Management according to ITIL and related application systems are introduced in stages. At the same time, Process Management principles take root step-by-step within the IT organization.

	~~<p> </p>~~

	== Focus on Processes and Organizational Framework ==		== Focus on Processes and Organizational Framework ==
Line 39:		Line 37:
	The implementation phase therefore lends itself to standardization far less than the first conceptual part, and the project manual at hand cannot be quite as specific.		The implementation phase therefore lends itself to standardization far less than the first conceptual part, and the project manual at hand cannot be quite as specific.
	It does, however, name the project steps which are usually required as part of the project schedule.		It does, however, name the project steps which are usually required as part of the project schedule.

	~~<p> </p>~~

	== The Pivotal Point: Defining Responsibilities and Procedures ==		== The Pivotal Point: Defining Responsibilities and Procedures ==
Line 54:		Line 50:

	→ '''[[ITIL Implementation\|ITIL Implementation - ITIL Implementation in 10 Steps]]'''		→ '''[[ITIL Implementation\|ITIL Implementation - ITIL Implementation in 10 Steps]]'''

	~~<p> </p>~~

	<!-- This page is assigned to the following categories: -->		<!-- This page is assigned to the following categories: -->
	[[Category:ITIL implementation]]		[[Category:ITIL implementation]]
	<!-- --- -->		<!-- --- -->

Andrea: /* The Pivotal Point: Defining Responsibilities and Procedures */

2013-06-11T14:10:19Z

The Pivotal Point: Defining Responsibilities and Procedures

← Older revision		Revision as of 16:10, 11 June 2013
Line 1:		Line 1:
	<~~seo metakeywords~~="itil key factors" ~~metadescription~~="ITIL Key Factors. It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers ..." />		<itpmch><title>ITIL Implementation - Key Factors \| IT Process Wiki</title>
			<meta name="keywords" content="itil key factors" />
			<meta name="description" content="ITIL Key Factors. It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers ..." />
			</itpmch>
	<imagemap>		<imagemap>
	Image:ITIL-Wiki-deutsch.jpg\|right\|ITIL Implementation - Key Factors		Image:ITIL-Wiki-deutsch.jpg\|right\|ITIL Implementation - Key Factors
Line 7:		Line 10:
	<br style="clear:both;"/>		<br style="clear:both;"/>

	It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers the IT ~~organisation~~ as a whole, taking into account the complete spectrum of IT processes. This creates the context for defining the IT Service Management processes in more detail.		It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers the IT organization as a whole, taking into account the complete spectrum of IT processes. This creates the context for defining the IT Service Management processes in more detail.
	[[Image:thumb_implementation_method.jpg\|frame\|right]]		[[Image:thumb_implementation_method.jpg\|frame\|right]]

	In order to ensure the long-term success of the project, any [[ITIL Implementation\|ITIL introduction]] must not be reduced to the introduction of ~~“ITIL~~-~~compliant”~~ application systems, like e.g. a ~~Helpdesk~~ system.		In order to ensure the long-term success of the project, any [[ITIL Implementation\|ITIL introduction]] must not be reduced to the introduction of "ITIL-compliant" application systems, like e.g. a Help Desk system.

	Practice has repeatedly shown that this way of thinking is too short-term, and will often result in investments not showing the expected benefits: The emphasis must be firmly on defining suitable, effective, and efficient processes, and selecting adequate technical equipment in a subsequent step, as required by the processes.		Practice has repeatedly shown that this way of thinking is too short-term, and will often result in investments not showing the expected benefits: The emphasis must be firmly on defining suitable, effective, and efficient processes, and selecting adequate technical equipment in a subsequent step, as required by the processes.

	In line with these requirements, the suggested ITIL Implementation Method describes how – starting from an analysis of the as-is situation – an IT Service Management according to ITIL and related application systems are introduced in stages. At the same time, Process Management principles take root step-by-step within the IT ~~organisation~~.		In line with these requirements, the suggested ITIL Implementation Method describes how – starting from an analysis of the as-is situation – an IT Service Management according to ITIL and related application systems are introduced in stages. At the same time, Process Management principles take root step-by-step within the IT organization.

	== Focus on Processes and ~~Organisational~~ Framework ==		<p> </p>

			== Focus on Processes and Organizational Framework ==

	The first stages at the beginning of an ITIL project are of great importance, because the cornerstones for a functioning IT Service Management are being laid in the form of process definitions and responsibility assignments.		The first stages at the beginning of an ITIL project are of great importance, because the cornerstones for a functioning IT Service Management are being laid in the form of process definitions and responsibility assignments.
Line 32:		Line 37:
	* whether processes will be handled internally, or procured from external service providers.		* whether processes will be handled internally, or procured from external service providers.

	The implementation phase therefore lends itself to ~~standardisation~~ far less than the first conceptual part, and the project manual at hand cannot be quite as specific.		The implementation phase therefore lends itself to standardization far less than the first conceptual part, and the project manual at hand cannot be quite as specific.
	It does, however, name the project steps which are usually required as part of the project schedule.		It does, however, name the project steps which are usually required as part of the project schedule.

			<p> </p>

	== The Pivotal Point: Defining Responsibilities and Procedures ==		== The Pivotal Point: Defining Responsibilities and Procedures ==

	There is one big question when setting out to introduce ITIL: How to thoroughly instil the ITIL principles within the IT ~~organisation~~? Experience from various implementation projects shows that this calls, above all else, for a clear definition of processes with all the participants.		There is one big question when setting out to introduce ITIL: How to thoroughly instil the ITIL principles within the IT organization? Experience from various implementation projects shows that this calls, above all else, for a clear definition of processes with all the participants.
	ITIL will not get into full swing before it is clearly and unmistakably determined [[Roles ~~within ITIL~~\|which members of IT staff are in charge of which activities]], which deliveries they are meant to produce, and what they, in turn, can expect from others.		ITIL will not get into full swing before it is clearly and unmistakably determined [[ITIL Roles\|which members of IT staff are in charge of which activities]], which deliveries they are meant to produce, and what they, in turn, can expect from others.

	In practical terms this means that process descriptions/ work instructions have to be drawn up within the context of the IT ~~organisation~~.		In practical terms this means that process descriptions/ work instructions have to be drawn up within the context of the IT organization.

			<p> </p>

	''' Back to: '''		''' Back to: '''
Line 47:		Line 55:
	→ '''[[ITIL Implementation\|ITIL Implementation - ITIL Implementation in 10 Steps]]'''		→ '''[[ITIL Implementation\|ITIL Implementation - ITIL Implementation in 10 Steps]]'''

			<p> </p>

	<!-- This page is assigned to the following categories: -->		<!-- This page is assigned to the following categories: -->
	[[Category:ITIL implementation]]		[[Category:ITIL implementation]]
	<!-- --- -->		<!-- --- -->

Andrea at 18:32, 26 July 2011

2011-07-26T18:32:57Z

@@ Line 1: / Line 1: @@
-{|
+<seo metakeywords="itil key factors" metadescription="ITIL Key Factors. It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers ..." />
-! align="right" width="80%"|
+<imagemap>
-! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_Schl%C3%BCsselfaktoren diese Seite auf Deutsch]
+Image:ITIL-Wiki-deutsch.jpg|right|ITIL Implementation - Key Factors
-|}
+default [https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_Schl%C3%BCsselfaktoren diese Seite auf Deutsch]
 It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers the IT organisation as a whole, taking into account the complete spectrum of IT processes. This creates the context for defining the IT Service Management processes in more detail.
@@ Line 38: / Line 41: @@
 In practical terms this means that process descriptions/ work instructions have to be drawn up within the context of the IT organisation.

Andrea: /* The Pivotal Point: Defining Responsibilities and Procedures */

2007-11-02T15:20:00Z

The Pivotal Point: Defining Responsibilities and Procedures

New page

{|
! align="right" width="80%"|
! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_Schl%C3%BCsselfaktoren diese Seite auf Deutsch]
|}

It must be ensured that the new, ITIL-compliant processes are put into a coherent framework that covers the IT organisation as a whole, taking into account the complete spectrum of IT processes. This creates the context for defining the IT Service Management processes in more detail.
[[Image:thumb_implementation_method.jpg|frame|right]]

In order to ensure the long-term success of the project, any [[ITIL Implementation|ITIL introduction]] must not be reduced to the introduction of “ITIL-compliant” application systems, like e.g. a Helpdesk system.

Practice has repeatedly shown that this way of thinking is too short-term, and will often result in investments not showing the expected benefits: The emphasis must be firmly on defining suitable, effective, and efficient processes, and selecting adequate technical equipment in a subsequent step, as required by the processes.

In line with these requirements, the suggested ITIL Implementation Method describes how – starting from an analysis of the as-is situation – an IT Service Management according to ITIL and related application systems are introduced in stages. At the same time, Process Management principles take root step-by-step within the IT organisation.

== Focus on Processes and Organisational Framework ==

The first stages at the beginning of an ITIL project are of great importance, because the cornerstones for a functioning IT Service Management are being laid in the form of process definitions and responsibility assignments.

In practice this means that one must complete these first steps with due diligence, using proven methods. The aim is to ensure that

* the effort for implementing new or changed processes is well spent
* adequate application systems become procured and implemented
* the introduction of ITIL remains a long-term success, and IT staff actually work along best practice principles

Once the conceptual project phase is completed, the actual implementation of processes and application system(s) begins. The specific activities during implementation depend upon

* how the processes were designed in detail
* which application systems will be implemented
* whether processes will be handled internally, or procured from external service providers.

The implementation phase therefore lends itself to standardisation far less than the first conceptual part, and the project manual at hand cannot be quite as specific.
It does, however, name the project steps which are usually required as part of the project schedule.

== The Pivotal Point: Defining Responsibilities and Procedures ==

There is one big question when setting out to introduce ITIL: How to thoroughly instil the ITIL principles within the IT organisation? Experience from various implementation projects shows that this calls, above all else, for a clear definition of processes with all the participants.
ITIL will not get into full swing before it is clearly and unmistakably determined [[Roles within ITIL|which members of IT staff are in charge of which activities]], which deliveries they are meant to produce, and what they, in turn, can expect from others.

In practical terms this means that process descriptions/ work instructions have to be drawn up within the context of the IT organisation.