Release and Deployment Management: Difference between revisions

From IT Process Wiki
No edit summary
 
mNo edit summary
Line 1: Line 1:
{|
<imagemap>
! align="right" width="80%"|
Image:ITIL-Wiki-de-es.jpg|Release and Deployment Management|100px
! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/Release_und_Deployment_Management diese Seite auf Deutsch]
rect 0 0 50 30 [https://wiki.de.it-processmaps.com/index.php/Release_und_Deployment_Management diese Seite auf Deutsch]
|}
rect 50 0 100 30 [https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_Ediciones_e_Implementacion esta página en español]
desc none
</imagemap>
<br style="clear:both;"/>


'''ITIL Version''': ITIL Version 3 (ITIL V3)
== ITIL Release and Deployment Management: Overview ==


'''Process Objective''': To plan, schedule and control the movement of releases to test and live environments. The primary goal of Release and Deployment Management is to ensure that the integrity of the live environment is protected and that the correct components are released.
'''Process Objective''': To plan, schedule and control the movement of releases to test and live environments. The primary goal of Release and Deployment Management is to ensure that the integrity of the live environment is protected and that the correct components are released.
Line 10: Line 13:
'''Part of''': [[ITIL V3 Service Transition|Service Transition]]
'''Part of''': [[ITIL V3 Service Transition|Service Transition]]


'''Process Owner''': [[Roles within ITIL V3#ITIL V3 roles and boards within Service Transition|Release Manager]]
'''Process Owner''': [[Release and Deployment Management#ITIL Roles in Release and Deployment Management|Release Manager]]




==ITIL V3 vs. ITIL V2: Release and Deployment Management==
== ITIL Release and Deployment Management: Process Definition ==


* Essentially, the activities and process objectives of the Release and Deployment Management process in ITIL V3 are identical to Release Management in ITIL V2
<imagemap>
* ITIL V3 provides considerably more details in the areas of Release planning and testing; this led to the addition of two dedicated processes in ITIL V3 which were subsumed under Release Management in the previous ITIL version:
Image:overview_release_and_deployment_management_itilv3_thumb.jpg|left|Release and Deployment Management|350px|thumb
**Project Management (Transition Planning and Support)
default [https://wiki.en.it-processmaps.com/images/pdf/process_overview_release_and_deployment_management_itilv3.pdf Release and Deployment Management (.pdf)]
**Service Validation and Testing
desc bottom-left
</imagemap>




==Sub-Processes of Release and Deployment Management (ITIL V3)==
Essentially, the activities and process objectives of the Release and Deployment Management process in ITIL V3 are identical to Release Management in ITIL V2. ITIL V3 provides considerably more details in the areas of Release planning and testing; this led to the addition of two dedicated processes in ITIL V3 which were subsumed under Release Management in the previous ITIL version:
*Project Management (Transition Planning and Support)
*Service Validation and Testing


[[Image:overview_release_and_deployment_management_itilv3_thumb.jpg|frame|left|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_release_and_deployment_management_itilv3.pdf  Overview of the Release and Deployment Management Process, ITIL V3 (.pdf)]]]
The following sub-processes are part of [[Release and Deployment Management|Release and Deployment Management according to ITIL V3]]:
<br style="clear:both;"/>
 
 
=== Sub-Processes ===


;Release Management Support
;Release Management Support
Line 44: Line 54:




== Related Key Performance Indicators ==
=== Related ITIL Glossary Terms ===
 
;Development Work Order
:A Work Order for the development or customization of an application or system, typically issued from Release Management.
 
;Installation Work Order
:A Work Order for the installation of an application, system or infrastructure component, typically issued from Release Management.
 
;Release Policy
:A set of rules for deploying releases into the live operational environment, defining different approaches for releases depending on their urgency and impact.
 
;Release Record
:A Release Record contains all details of a Release, documenting the history of the Release from the first planning stages to closure.
 
 
 
== Additional Information on Release and Deployment Management ==
 
==== ITIL KPIs ====
 
* [[ITIL KPIs Service Transition#ITIL KPIs Release and Deployment Management|Key Performance Indicators (KPIs) Release and Deployment Management]]
 
 
==== ITIL Roles in Release and Deployment Management ====
 
;Release Manager - Process Owner
:The Release Manager is responsible for planning, scheduling and controlling the movement of Releases to test and live environments.
:His primary objective is to ensure that the integrity of the live environment is protected and that the correct components are released.


* [[ITIL KPIs Service Transition#ITIL KPIs Release and Deployment Management|KPIs Release and Deployment Management]]
;IT Operator
:IT Operators are the staff who perform the day-to-day operational activities.
:Typical responsibilities include: Performing backups, ensuring that scheduled jobs are performed, installing standard equipment in the data centre.




==Roles within Release and Deployment Management (ITIL V3)==


* [[Roles within ITIL V3#ITIL V3 roles and boards within Service Transition|Release Manager]] (Process Owner)


* [[Roles within ITIL V3#ITIL V3 roles and boards within Service Operation|IT Operator]]
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V3]][[Category:ITIL process]][[Category:Service Transition|Release & Deployment Management]][[Category:Release & Deployment Management|!]]
<!-- --- -->

Revision as of 10:38, 12 April 2010

Release and Deployment Managementdiese Seite auf Deutschesta página en español
Release and Deployment Management


ITIL Release and Deployment Management: Overview

Process Objective: To plan, schedule and control the movement of releases to test and live environments. The primary goal of Release and Deployment Management is to ensure that the integrity of the live environment is protected and that the correct components are released.

Part of: Service Transition

Process Owner: Release Manager


ITIL Release and Deployment Management: Process Definition

Release and Deployment Management


Essentially, the activities and process objectives of the Release and Deployment Management process in ITIL V3 are identical to Release Management in ITIL V2. ITIL V3 provides considerably more details in the areas of Release planning and testing; this led to the addition of two dedicated processes in ITIL V3 which were subsumed under Release Management in the previous ITIL version:

  • Project Management (Transition Planning and Support)
  • Service Validation and Testing

The following sub-processes are part of Release and Deployment Management according to ITIL V3:


Sub-Processes

Release Management Support
Process Objective: To provide guidelines and support for the deployment of Releases.
Minor Release Deployment
Process Objective: To deploy minor, low-risk Releases into the productive environment. This process is used as a streamlined way to deploy Releases which do not require full-scale project planning and quality assurance, as they are limited in size and their associated risk is low and well understood.
Release Build
Process Objective: To issue all necessary Work Orders and Purchase Requests so that Release Components are either bought from outside vendors or developed/ customized in-house.
Release Deployment
Process Objective: To deploy the Release components into the live production environment. This process is also responsible for training end-users and operating staff, as well as circulating information/ documentation on the newly deployed Release or the services it supports.
Early Life Support
Process Objective: To resolve operational issues quickly during an initial period after Release deployment, and to remove any remaining errors or deficiencies.
Release Closure
Process Objective: To formally close a Release after verifying if activity logs and CMS contents are up to date.


Related ITIL Glossary Terms

Development Work Order
A Work Order for the development or customization of an application or system, typically issued from Release Management.
Installation Work Order
A Work Order for the installation of an application, system or infrastructure component, typically issued from Release Management.
Release Policy
A set of rules for deploying releases into the live operational environment, defining different approaches for releases depending on their urgency and impact.
Release Record
A Release Record contains all details of a Release, documenting the history of the Release from the first planning stages to closure.


Additional Information on Release and Deployment Management

ITIL KPIs


ITIL Roles in Release and Deployment Management

Release Manager - Process Owner
The Release Manager is responsible for planning, scheduling and controlling the movement of Releases to test and live environments.
His primary objective is to ensure that the integrity of the live environment is protected and that the correct components are released.
IT Operator
IT Operators are the staff who perform the day-to-day operational activities.
Typical responsibilities include: Performing backups, ensuring that scheduled jobs are performed, installing standard equipment in the data centre.
Retrieved from "https://wiki.en.it-processmaps.com/index.php?title=Release_and_Deployment_Management&oldid=3400"