ITIL Service Transition - Revision history

User at 17:59, 12 January 2023

2023-01-12T17:59:43Z

User at 17:57, 12 January 2023

2023-01-12T17:57:34Z

Show changes

User at 13:36, 12 January 2023

2023-01-12T13:36:25Z

User at 16:39, 23 March 2021

2021-03-23T16:39:19Z

User at 16:38, 23 March 2021

2021-03-23T16:38:23Z

User at 18:51, 22 March 2021

2021-03-22T18:51:18Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T16:17:50Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

Show changes

User at 21:43, 11 January 2021

2021-01-11T21:43:00Z

User at 21:33, 11 January 2021

2021-01-11T21:33:32Z

User at 20:57, 11 January 2021

2021-01-11T20:57:16Z

@@ Line 73: / Line 73: @@
 == Policies for Service Transition<ref>[https://www.kornev-online.net/ITIL/03%20-%20ITIL%20V3%202011%20Service%20Transition%20ST.pdf Policies for Service Transition]</ref> ==
 The following are examples of policies for service transition. Every service provider should agree to and document policies that are appropriate for their circumstances. Endorsement and visible support from senior management contribute to the overall effectiveness. Each policy is explicitly stated and its suggested application and approach are illustrated by applicable principles and best practices that help an organization deliver that principle. Examples of these policies include:
-*Define and implement a formal policy for service transition: A formal policy for service transition should be defined, documented, and approved by
+*Define and implement a formal policy for service transition: A formal policy for service transition should be defined, documented, and approved by the management team, who ensure that it is communicated throughout the organization and to all relevant suppliers and partners
 *Implement all changes to services through service transition:
 **All service changes must be managed by the service transition lifecycle stage, except for standard changes that follow a procedure defined during the service transition lifecycle stage.
@@ Line 94: / Line 93: @@
-== ITIL Service Transition Benefits and Key Aspects<ref>ITIL Service Transition Benefits and Key Aspects [https://www.certguidance.com/itil-service-transition-explained-brief/ Certguidance]</ref> ==
+== ITIL Service Transition Benefits and Key Aspects<ref>[https://www.certguidance.com/itil-service-transition-explained-brief/ ITIL Service Transition Benefits and Key Aspects]</ref> ==
 According to ITIL V3, the Service Transition process has several aspects & benefits as discussed below:
 *Quick & efficient adaptability to new requirements.

@@ Line 121: / Line 121: @@
 == See Also ==
 <div style="column-count:2;-moz-column-count:3;-webkit-column-count:3">
-[[ITIL (Information Technology Infrastructure Library)]]<br />
 </div>

← Older revision		Revision as of 16:39, 23 March 2021
Line 156:		Line 156:

	== References ==		== References ==
−	<references/	+	<references/>

@@ Line 135: / Line 135: @@
 [[ITIL Service Value System (SVS)]]<br />
 [[Service Portfolio Management]]<br />
-[[IT_Governance|IT Governance]]<br />
+[[Service Portfolio]]<br />
 [[IT Infrastructure]]<br />
 [[IT Operations (Information Technology Operations)]]<br />
 [[COBIT_(Control_Objectives_for_Information_and_Related_Technology)|Control Objectives for Information and Related Technology (COBIT)]]<br />
-[[Balanced_Scorecard|Balanced Scorecard]]<br />
+[[Balanced Scorecard]]<br />
-[[Enterprise_Risk_Management_(ERM)|Enterprise Risk Management (ERM)]]<br />
+[[Enterprise Risk Management (ERM)]]<br />
-[[Risk_Management|Risk Management]]<br />
+[[Risk Management]]<br />
-[[IT_Strategy_(Information_Technology_Strategy)|IT Strategy (Information Technology Strategy)]]<br />
+[[IT_Strategy_(Information_Technology_Strategy)|IT Strategy]]<br />
-[[Business_Strategy|Business Strategy]]<br />
+[[Business Strategy]]<br />
-[[Corporate_Governance|Corporate Governance]]<br />
+[[Corporate Governance]]<br />
-[[Corporate_Strategy|Corporate Strategy]]<br />
+[[Corporate Strategy]]<br />
 [[Enterprise_Architecture|Enterprise Architecture]]<br />
 [[COSO_Internal_Control_Integrated_Framework|COSO Internal Control- Integrated Framework]]<br />
-[[Compliance|Compliance]]<br />
+[[Compliance]]<br />
 </div>

@@ Line 1: / Line 1: @@
-The role of '''ITIL [[Service]] Transition''' is to move services and service changes into operational use. ITIL Service Transition also introduces the service knowledge [[management]] [[system]] (SKMS) which has the ability to support organizational learning and assist in increasing the effectiveness and [[efficiency]] of all stages of the [[ITIL Service Lifecycle|service life-cycle]]. This provides benefits to people with the knowledge and experience of others, helps to support decision-making and improve the management of services.<ref>What is ITIL Service Transition? [https://www.invensislearning.com/articles/itil/what-is-itil-service-transition Invensis]</ref>
+The role of '''ITIL Service Transition''' is to move [[Service|services]] and service changes into operational use. ITIL Service Transition also introduces the [[Service Knowledge Management System (SKMS)|service knowledge management system (SKMS)]] which has the ability to support organizational learning and assist in increasing the effectiveness and [[efficiency]] of all stages of the [[ITIL Service Lifecycle|service life-cycle]]. This provides benefits to people with the knowledge and experience of others, helps to support decision-making and improve the management of services.<ref>What is ITIL Service Transition? [https://www.invensislearning.com/articles/itil/what-is-itil-service-transition Invensis]</ref>
@@ Line 117: / Line 117: @@
 *Knowledge Manager
 *Application Developer
 == References ==
-<references/>
+<references/

← Older revision		Revision as of 21:43, 11 January 2021
Line 59:		Line 59:

	[[File:service transition processes.png\|300px\|TIL Service Transition Processes]]<br />		[[File:service transition processes.png\|300px\|TIL Service Transition Processes]]<br />
		+
		+
		+	== ITIL Service Transition Value to the Business<ref>ITIL Service Transition Value to the Business [https://blog.masterofproject.com/itil-service-transition/ master of Project Academy]</ref> ==
		+	*ITIL Service Transition adjusts business requirements with business operation: The ITIL Service Transition stage adjusts business requirements with business operations. Business vision, strategy, and requirements of an organization are planned, developed, tested, verified and delivered into operations during ITIL Service Transition stage.
		+	*It secures maximum value for customers and users: Maximized value for customers and users are secured. By testing, verifying, and risk planning, impacts of services that might cause customer dissatisfaction are minimized. With the help of the necessary tools, software, and resources, new requirements and market tendencies are aimed to be adopted as fast as possible. In order to adopt new technologies or service improvements, a suitable framework should be designed by the organization.
		+	*It facilitates the management of mergers, spin-offs, and acquisitions: Companies might take strategic decisions such as mergers, spin-offs, or acquisitions. These might require existing services to be updated or new services to be developed and transferred to operations. During mergers, spin-offs or acquisitions, transition management of services are done during the ITIL Service Transition stage.
		+	*It increases success rate for changes and releases: Because ITIL service transition stage works in accordance with a framework and this framework enables consistent and successful delivery of interrelated services.
		+	*It helps to forecast service levels: Since tests and verifications of new or changed services are done during the ITIL Service Transition stage, this stage also helps to forecast service levels and warranties about new services or changed services.
		+	*It reduces variation: The ITIL Service Transition stage reduces the variation between planned and actual resources and budget plans. Let’s say that your company is planning to implement a new service that will enable customer representatives to handle a customer operation in 10 seconds. During the service transition stage, with the help of testing and verification steps, you will be able to see whether you will be able to meet your targeted levels. If you cannot meet required and planned levels with existing resources or budgets, you should reevaluate how to meet targeted levels of service. Therefore, the Service Transition stage helps you to assess your status and reduce the variation between planned and actual values.

← Older revision		Revision as of 21:33, 11 January 2021
Line 59:		Line 59:

	[[File:service transition processes.png\|300px\|TIL Service Transition Processes]]<br />		[[File:service transition processes.png\|300px\|TIL Service Transition Processes]]<br />
		+
		+
		+	== Policies for Service Transition<ref>Policies for Service Transition [https://www.kornev-online.net/ITIL/03%20-%20ITIL%20V3%202011%20Service%20Transition%20ST.pdf Kornev]</ref> ==
		+	The following are examples of policies for service transition. Every service provider should agree and document policies that are appropriate for their circumstances. Endorsement and visible support from senior management contribute to the overall effectiveness. Each policy is explicitly stated and its suggested application and approach are illustrated by applicable principles and best practices that help an organization to deliver that principle. Examples of these policies include:
		+	*Define and implement a formal policy for service transition: A formal policy for service transition should be defined, documented and approved by
		+	the management team, who ensure that it is communicated throughout the organization and to all relevant suppliers and partners
		+	*Implement all changes to services through service transition:
		+	**All service changes must be managed by the service transition lifecycle stage, except for standard changes that follow a procedure defined during the service transition lifecycle stage.
		+	**The scope of service change must be documented. This scope should include all changes to the service portfolio or service catalogue and should normally exclude business process changes and some minor operational changes.
		+	*Adopt a common framework and standards: Base service transition on a common framework of standard re-usable processes and systems to improve integration of the parties involved in service transition and reduce variations in the processes.
		+	*Maximize re-use of established processes and systems: Service transition processes are aligned with the organization’s processes and related systems to improve efficiency and effectiveness, and where new processes are required they are developed with re-use in mind.
		+	*Align service transition plans with the business needs: Align service transition plans and new or changed service with the customer’s and business organization’s requirements in order to maximize the value delivered by a change.
		+	*Establish and maintain relationships with stakeholders: Establish and maintain relationships with customers, customer representatives, users and suppliers throughout service transition in order to set their expectations about the new or changed service.
		+	*Establish effective controls and disciplines: Establish suitable controls and disciplines throughout the service lifecycle to enable the smooth transition of service changes and releases.
		+	*Provide systems for knowledge transfer and decision support: Service transition develops systems and processes to transfer knowledge for effective operation of the service and enable decisions to be made at the right time by competent decision makers.
		+	*Plan release packages: Releases are planned and designed to be built, tested, delivered, distributed and deployed into the live environment in a manner that provides the agreed levels of traceability, in a costeffective and efficient way.
		+	*Anticipate and manage course corrections:
		+	**Use risk assessment and management to identify and document the range of course corrections that staff are allowed to implement.
		+	**Train staff to recognize the need for course corrections and empower them to apply necessary variations within prescribed and understood limits.
		+	*Proactively manage resources across service transitions: Provide and manage shared and specialist resources across service transition activities to eliminate delays and optimize utilization of resources.
		+	*Ensure early involvement in the service lifecycle: Establish suitable controls and disciplines to check at the earliest possible stage in the service lifecycle that a new or changed service will be capable of delivering the value required.
		+	*Provide assurance of the quality of the new or changed service: Verify and validate that the proposed changes to the operational services defined in the service and release definitions, service model and service design package can deliver the required service requirements and business benefits.
		+	*Proactively improve quality during service transition: Proactively plan and improve the quality of the new or changed service during transition

@@ Line 72: / Line 72: @@
 *Leads to timely discontinuation or changes to maintenance contracts for software and hardware when components are decommissioned.
 *Understanding and assessing the risk levels during and after a change.
 == References ==
 <references/>