Switching from ITIL V2 to ITIL V3 - Revision history

Andrea at 08:39, 28 April 2017

2017-04-28T08:39:54Z

← Older revision		Revision as of 10:39, 28 April 2017
Line 4:		Line 4:
	</itpmch>		</itpmch>
	<imagemap>		<imagemap>
	Image:ITIL-Wiki-de-es.jpg\|DE - ES - Switching from ITIL V2 to ITIL V3\|~~100px~~		Image:ITIL-Wiki-de-es.jpg\|right\|DE - ES - Switching from ITIL V2 to ITIL V3\|163px
	rect 0 ~~0 50 30~~ [https://wiki.de.it-processmaps.com/index.php/Umstieg_von_ITIL_V2_auf_ITIL_V3 diese Seite auf Deutsch]		rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/Umstieg_von_ITIL_V2_auf_ITIL_V3 diese Seite auf Deutsch]
	rect 50 0 ~~100 30~~ [https://wiki.es.it-processmaps.com/index.php/Cambiando_de_ITIL_V2_a_ITIL_V3 esta página en español]		rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/Cambiando_de_ITIL_V2_a_ITIL_V3 esta página en español]
	desc none		desc none
	</imagemap>		</imagemap>
	<br style="clear:both;"/>		<br style="clear:both;"/>

	~~<p> </p>~~

	=== How to Achieve the Switch from ITIL V2 to V3 2007 / ITIL 2011 ===		=== How to Achieve the Switch from ITIL V2 to V3 2007 / ITIL 2011 ===
Line 23:		Line 21:

	An overview diagram of Problem Management, for example, presents how this process is interfacing with the other Service Operation processes. This makes it easy to decide where process interfaces must be modified, and any existing documentation on the Problem Management process can be incorporated into this structure.		An overview diagram of Problem Management, for example, presents how this process is interfacing with the other Service Operation processes. This makes it easy to decide where process interfaces must be modified, and any existing documentation on the Problem Management process can be incorporated into this structure.

	~~<p> </p>~~

	=== When to Switch ===		=== When to Switch ===
Line 30:		Line 26:
	Because the new ITIL books are based very much on the principles known from ITIL V2, there is no urgent need for action for any IT organization with ITIL V2 processes in operation. But you might want to look at ITIL V3 or ITIL 2011 to see if it offers any hints about where to improve your processes.		Because the new ITIL books are based very much on the principles known from ITIL V2, there is no urgent need for action for any IT organization with ITIL V2 processes in operation. But you might want to look at ITIL V3 or ITIL 2011 to see if it offers any hints about where to improve your processes.

	~~However~~, ~~before long~~ there will be ~~only~~ "one version of ITIL" ~~around~~. This means that even in cases where the processes itself do not need to be changed, at one point in time a switch to the ~~new Service Lifecycle~~ process structure will have to be made. Such an alignment also offers the chance to benefit from the improvements of the ITIL version.		In the longer term, however, there will only be "one version of ITIL" - at least for a few years. This means that even in cases where the processes itself do not need to be changed, at one point in time a switch to the service lifecycle process structure will have to be made. Such an alignment also offers the chance to benefit from the improvements of the ITIL V3 version.

	* [[Comparison between ITIL V3 and ITIL V2 - The Main Changes# Comparison and Changes between ITIL V3 and ITIL V2 in Detail\|Comparison of ITIL V2 and ITIL V3]]		* [[Comparison between ITIL V3 and ITIL V2 - The Main Changes# Comparison and Changes between ITIL V3 and ITIL V2 in Detail\|Comparison of ITIL V2 and ITIL V3]]

Andrea at 10:44, 24 January 2012

2012-01-24T10:44:58Z

← Older revision		Revision as of 12:44, 24 January 2012
Line 1:		Line 1:
	<~~seo metakeywords~~="switching itil" ~~metadescription~~="How to Achieve the Switch from ITIL V2 to V3. The new ITIL V3 books are based very much on the principles known from ITIL V2, ..." />		<itpmch><title>Switching from ITIL V2 to ITIL V3 \| IT Process Wiki</title>
			<meta name="keywords" content="switching itil" />
			<meta name="description" content="How to Achieve the Switch from ITIL V2 to V3. The new ITIL V3 books are based very much on the principles known from ITIL V2, ..." />
			</itpmch>
	<imagemap>		<imagemap>
	Image:ITIL-Wiki-de-es.jpg\|DE - ES - Switching from ITIL V2 to ITIL V3\|100px		Image:ITIL-Wiki-de-es.jpg\|DE - ES - Switching from ITIL V2 to ITIL V3\|100px
Line 8:		Line 11:
	<br style="clear:both;"/>		<br style="clear:both;"/>

	~~=== How to Achieve the Switch from ITIL V2 to V3 ===~~		<p> </p>

	The new ITIL V3 books are based very much on the principles known from ITIL V2, but unfortunately there are no detailed instructions for switching to the new set of “[[Comparison between ITIL V3 and ITIL V2 - The Main Changes#New ITIL Structure: The ITIL V3 Service Lifecycle\|Service Lifecycle]]” processes. As a result, the only advice available is a rough outline of a two-step strategy for switching to V3:		=== How to Achieve the Switch from ITIL V2 to V3 2007 / ITIL 2011 ===

			The new ITIL books are based very much on the principles known from ITIL V2, but unfortunately there are no detailed instructions for switching to the new set of "[[Comparison between ITIL V3 and ITIL V2 - The Main Changes#New ITIL Structure: The ITIL V3 Service Lifecycle\|Service Lifecycle]]" processes. As a result, the only advice available is a rough outline of a two-step strategy for switching to the new ITIL version:

	* Take all existing ITIL processes and plug them into the new Service Lifecycle process structure		* Take all existing ITIL processes and plug them into the new Service Lifecycle process structure
	* Benchmark the existing processes against the new ITIL V3 recommendations and replace, add or improve processes as appropriate		* Benchmark the existing processes against the new ITIL recommendations and replace, add or improve processes as appropriate

	An [[ITIL Implementation with Process Templates# ITIL Reference Process Models\|ITIL reference model]], containing a complete ITIL V3 process framework, is able to support switching to the new ITIL version because existing V2 processes can be plugged into the new Service Lifecycle Structure.		An [[ITIL Implementation with Process Templates#ITIL Reference Process Models\|ITIL reference model]], containing a complete ITIL V3 or ITIL 2011 process framework, is able to support switching to the new ITIL version because existing V2 processes can be plugged into the new Service Lifecycle Structure.

	An overview diagram of Problem Management, for example, presents how this process is interfacing with the other Service Operation processes. This makes it easy to decide where process interfaces must be modified, and any existing documentation on the Problem Management process can be incorporated into this structure.		An overview diagram of Problem Management, for example, presents how this process is interfacing with the other Service Operation processes. This makes it easy to decide where process interfaces must be modified, and any existing documentation on the Problem Management process can be incorporated into this structure.

	~~=== When to Switch to ITIL V3 ===~~		<p> </p>

	Because the new ITIL V3 books are based very much on the principles known from ITIL V2, there is no urgent need for action for any IT organization with ITIL V2 processes in operation. But you might want to ~~look at ITIL V3 to see if it offers any hints about where to improve your processes.~~		=== When to Switch ===

	~~However~~, ~~before long~~ there ~~will be only one version of~~ ITIL ~~around - ITIL V3~~. ~~This means that even in cases where the processes itself do not need~~ to ~~be changed,~~ at ~~one point in time a switch to the new Service Lifecycle process structure will have~~ to ~~be made. Such an alignment also~~ offers ~~the chance~~ to ~~benefit from the improvements of ITIL V3~~.		Because the new ITIL books are based very much on the principles known from ITIL V2, there is no urgent need for action for any IT organization with ITIL V2 processes in operation. But you might want to look at ITIL V3 or ITIL 2011 to see if it offers any hints about where to improve your processes.

	~~For anyone starting with~~ ITIL ~~there is no reason~~ to ~~begin with ITIL V2~~, ~~because ITIL V3 is based on~~ the ~~same principles and contains all~~ the ~~processes~~ from ~~ITIL V2 plus a number~~ of ~~important improvements. Starting with~~ ITIL ~~V2 will only create additional work when finally switching to V3~~.		However, before long there will be only "one version of ITIL" around. This means that even in cases where the processes itself do not need to be changed, at one point in time a switch to the new Service Lifecycle process structure will have to be made. Such an alignment also offers the chance to benefit from the improvements of the ITIL version.

	* [[Comparison between ITIL V3 and ITIL V2 - The Main Changes# Comparison and Changes between ITIL V3 and ITIL V2 in Detail\|Comparison of ITIL V2 and ITIL V3]]		* [[Comparison between ITIL V3 and ITIL V2 - The Main Changes# Comparison and Changes between ITIL V3 and ITIL V2 in Detail\|Comparison of ITIL V2 and ITIL V3]]
			* [[ITIL 2011\|The main changes and differences between ITIL V3 2007 and ITIL 2011]]

			<p> </p>

	''' Back to: '''		''' Back to: '''
Line 34:		Line 41:
	→ '''[[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 version]][[Category:ITIL process]]		[[Category:ITIL version]][[Category:ITIL process]]
	<!-- --- -->		<!-- --- -->

Andrea at 18:32, 26 July 2011

2011-07-26T18:32:02Z

@@ Line 1: / Line 1: @@
-The new ITIL V3 books are based very much on the principles known from ITIL V2, but unfortunately there are no detailed instructions for switching to the new set of “[[Comparison between ITIL V3 and ITIL V2 - The Main Changes# New ITIL Structure: The ITIL V3 Service Lifecycle|Service Lifecycle]]” processes. As a result, the only advice available is a rough outline of a two-step strategy for switching to V3:
+<seo metakeywords="switching itil" metadescription="How to Achieve the Switch from ITIL V2 to V3. The new ITIL  V3 books are based very much on the principles known from ITIL  V2, ..." />
 * Take all existing ITIL processes and plug them into the new Service Lifecycle process structure
@@ Line 7: / Line 18: @@
 An overview diagram of Problem Management, for example, presents how this process is interfacing with the other Service Operation processes. This makes it easy to decide where process interfaces must be modified, and any existing documentation on the Problem Management process can be incorporated into this structure.

Andrea: New page: The new ITIL V3 books are based very much on the principles known from ITIL V2, but unfortunately there are no detailed instructions for switching to the new set of “[[Comparison between...

2008-05-05T14:39:48Z

New page: The new ITIL V3 books are based very much on the principles known from ITIL V2, but unfortunately there are no detailed instructions for switching to the new set of “[[Comparison between...

New page

The new ITIL V3 books are based very much on the principles known from ITIL V2, but unfortunately there are no detailed instructions for switching to the new set of “[[Comparison between ITIL V3 and ITIL V2 - The Main Changes# New ITIL Structure: The ITIL V3 Service Lifecycle|Service Lifecycle]]” processes. As a result, the only advice available is a rough outline of a two-step strategy for switching to V3:

* Take all existing ITIL processes and plug them into the new Service Lifecycle process structure
* Benchmark the existing processes against the new ITIL V3 recommendations and replace, add or improve processes as appropriate

An [[ITIL Implementation with Process Templates# ITIL Reference Process Models|ITIL reference model]], containing a complete ITIL V3 process framework, is able to support switching to the new ITIL version because existing V2 processes can be plugged into the new Service Lifecycle Structure.

An overview diagram of Problem Management, for example, presents how this process is interfacing with the other Service Operation processes. This makes it easy to decide where process interfaces must be modified, and any existing documentation on the Problem Management process can be incorporated into this structure.