Release and Deployment Management: Difference between revisions
No edit summary |
|||
Line 8: | Line 8: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
<html><div itemscope="itemscope" itemtype="https://schema.org/WebPage"><!-- define schema.org/WebPage --><p></html> | |||
<p> </p> | <p> </p> | ||
'''<span id="Overview">Objective:</span>''' <html><span itemprop="description"><i><span itemprop="alternativeHeadline">ITIL <span itemprop="name Headline">Release and Deployment Management</span></span></i> aims to plan, schedule and control the movement of releases to test and live environments. The primary goal of Release Management and Deployment Management is to ensure that the integrity of the live environment is protected and that the correct components are released.</span></p> | |||
<p><b>Part of</b>: <a itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Transition" title="ITIL Service Transition">Service Transition</a></html> | |||
''' | |||
'''Process Owner''': [[Release and Deployment Management#Release Manager|Release Manager]] | '''Process Owner''': [[Release and Deployment Management#Release Manager|Release Manager]] | ||
Line 20: | Line 18: | ||
<p> </p> | <p> </p> | ||
== Process Description == | ==Process Description== | ||
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 Release Management provides considerably more details in the areas of ''Release planning and testing''; this led to the addition of two dedicated processes which were subsumed under Release Management in the previous ITIL version: [[Project Management - Transition Planning and Support]] and [[Service Validation and Testing]]. | 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 Release Management provides considerably more details in the areas of ''Release planning and testing''; this led to the addition of two dedicated processes which were subsumed under Release Management in the previous ITIL version: [[Project Management - Transition Planning and Support]], and [[Service Validation and Testing]]. | ||
<p> </p> | <p> </p> | ||
Line 33: | Line 31: | ||
The process overview of [[Media:Release-and-deployment-management-itil.jpg|Release & Deployment Management (.JPG)]] is showing the most important interfaces (see Figure 1). | The process overview of [[Media:Release-and-deployment-management-itil.jpg|Release & Deployment Management (.JPG)]] is showing the most important interfaces (see Figure 1). | ||
The latest ITIL 2011 guidance also specifies that [[Change Management#Minor Change Deployment ITIL|Minor Changes]] are implemented by Change Management without the involvement of Release Management, so the Minor Release Deployment sub-process has been removed. | The latest ITIL 2011 guidance also specifies that [[Change Management#Minor-Change-Deployment-ITIL|Minor Changes]] are implemented by Change Management without the involvement of Release Management, so the Minor Release Deployment sub-process has been removed. | ||
<p> </p> | <p> </p> | ||
== | ==Sub-Processes== | ||
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | |||
<meta itemprop="itemListOrder" content="Ascending" /> | |||
<p><span itemprop="name" content="Release Management sub-processes:">These are the <strong class="selflink">ITIL Release Management</strong> sub-processes and their process objectives:</span> | |||
</p> | |||
<p> </p> | |||
<p><b><span id="ITIL_Release_Management_Support" itemprop="itemListElement">Release Management Support</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To provide guidelines and support for the deployment of <a href="/index.php/Release_and_Deployment_Management#Release" title="Release and Deployment Management">Releases</a>. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="ITIL_Release_Management_Planning" itemprop="itemListElement">Release Planning</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To assign authorized Changes to <a href="/index.php/Release_and_Deployment_Management#Release" title="Release and Deployment Management">Release Packages</a> and to define the scope and content of Releases. Based on this information, the Release Planning process develops a schedule for building, testing and deploying the Release. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="ITIL_Release_Build" itemprop="itemListElement">Release Build</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To issue all necessary Work Orders and <a href="/index.php/Supplier_Management#Purchase_Request" title="Supplier Management">Purchase Requests</a> so that Release components are either bought from outside vendors or developed/ customized in-house. At the end of this process, all required Release components are ready to enter the testing phase. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="ITIL_Release_Deployment" itemprop="itemListElement">Release Deployment</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To deploy the Release components into the live production environment. This process is also responsible for training end-users and operating staff and circulating information/ documentation on the newly deployed Release or the services it supports. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="ITIL_Early_Life_Support" itemprop="itemListElement">Early Life Support</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To resolve operational issues quickly during an initial period after <a href="/index.php/Release_and_Deployment_Management#ITIL_Release_Deployment" title="Release and Deployment Management">Release deployment</a>, and to remove any remaining errors or deficiencies. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="ITIL_Release_Closure" itemprop="itemListElement">Release Closure</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To formally close a Release after verifying if activity logs and <a href="/index.php/Checklist_CMS_CMDB" title="Checklist CMS CMDB">CMS</a> contents are up to date. | |||
</li></ul> | |||
</div><!-- end of schema.org/ItemList --><p></html> | |||
<p> </p> | <p> </p> | ||
==Definitions== | |||
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | |||
<meta itemprop="itemListOrder" content="Ascending" /> | |||
<p><span itemprop="name">The following <a href="/index.php/ITIL%20Glossary#ITIL%20Glossary%20A-Z" title="ITIL Glossary">ITIL terms and acronyms</a> (<i>information objects</i>) are used in the ITIL Release Management process to represent process outputs and inputs:</span> | |||
</p> | |||
<p> </p> | |||
<p><b><span id="Development_Work_Order" itemprop="itemListElement">Development Work Order</span></b> | |||
</p> | |||
<ul><li itemprop="description">A Work Order for the development or customization of an application or system, typically issued from <strong class="selflink">Release Management</strong>. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="Installation_Work_Order" itemprop="itemListElement">Installation Work Order</span></b> | |||
</p> | |||
<ul><li itemprop="description">A Work Order for the installation of an application, system or infrastructure component, typically issued from <strong class="selflink">Release Management</strong>. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="Release_Policy" itemprop="itemListElement">Release Policy</span></b> | |||
</p> | |||
<ul><li itemprop="description">A set of rules for deploying <a href="/index.php/Release_and_Deployment_Management#Release" title="Release and Deployment Management">releases</a> into the live operational environment, defining different approaches for releases depending on their urgency and impact (see also: <a href="/index.php/Checklist_Release_Policy" title="Checklist Release Policy">ITIL Checklist Release Policy</a>). | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="Release" itemprop="itemListElement">Release</span></b> | |||
</p> | |||
<ul><li itemprop="description">A Release (also referred to as a <i>Release Package</i>) consists of a single <a href="/index.php/Release_and_Deployment_Management#Release_Unit" title="Release and Deployment Management">Release Unit</a> or a structured set of Release Units. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="Release_Record" itemprop="itemListElement">Release Record</span></b> | |||
</p> | |||
<ul><li itemprop="description">A Release Record contains all details of a <a href="/index.php/Release_and_Deployment_Management#Release" title="Release and Deployment Management">Release</a>, documenting the history of the Release from the first planning stages to closure. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="Release_Unit" itemprop="itemListElement">Release Unit</span></b> | |||
</p> | |||
<ul><li itemprop="description">A Release Unit is a set of new, changed and/or unchanged <a href="/index.php/Service_Asset_and_Configuration_Management#CI" title="Service Asset and Configuration Management">Configuration Items</a>, which are tested and introduced into the live environment together to implement one or several approved Changes. | |||
</li></ul> | |||
</div><!-- end of schema.org/ItemList --><p></html> | |||
<p> </p> | <p> </p> | ||
== | ==<span id="Checklists_.7C_KPIs">Templates | KPIs</span>== | ||
* [[ITIL KPIs Service Transition#ITIL KPIs Release and Deployment Management|Key Performance Indicators (KPIs) Release and Deployment Management]] | *[[ITIL KPIs Service Transition#ITIL KPIs Release and Deployment Management|Key Performance Indicators (KPIs) Release and Deployment Management]] | ||
*[[ITIL-Checklists# | *[[ITIL-Checklists#Release Management|Release Management templates and checklists]]: | ||
** [[Checklist Release Plan]] | **[[Checklist Release Policy]], and | ||
**[[Checklist Release Plan]] | |||
<p> </p> | <p> </p> | ||
== Roles | Responsibilities == | ==Roles | Responsibilities== | ||
'''<span id="Release Manager">Release Manager - Process Owner</span>''' | |||
*The Release Manager is responsible for planning 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. | |||
<p> </p> | <p> </p> | ||
{| border="1" cellpadding="5" cellspacing="0" style="text-align:center;" valign="top" | {| border="1" cellpadding="5" cellspacing="0" style="margin-left: auto; margin-right: auto; text-align:center;" valign="top" | ||
|- | |- | ||
| | |style="vertical-align:top; text-align:center" colspan="5" style="background:#ffffdd;"| '''<span id="RACI-Matrix-Release-Management">Responsibility Matrix: ITIL Release Management</span>''' | ||
|- | |- | ||
! | !style="background:#ffffee; width: 40%; text-align:center" | ITIL Role / Sub-Process | ||
! style="background:#ffffee;" | [[Release and Deployment Management#Release Manager|Release Manager]] | ! style="background:#ffffee;" | [[Release and Deployment Management#Release Manager|Release Manager]] | ||
! style="background:#ffffee;" | Project Manager[[Release and Deployment Management#Team|<small>[3]</small>]] | ! style="background:#ffffee;" | Project Manager[[Release and Deployment Management#Team|<small>[3]</small>]] | ||
Line 114: | Line 139: | ||
! style="background:#ffffee;" | Other roles involved | ! style="background:#ffffee;" | Other roles involved | ||
|- | |- | ||
| | |style="text-align:left;" |[[#ITIL Release Management Support|Release Management Support]] | ||
| A[[Release and Deployment Management#Accountable|<small>[1]</small>]]R[[Release and Deployment Management#Responsible|<small>[2]</small>]] | | A[[Release and Deployment Management#Accountable|<small>[1]</small>]]R[[Release and Deployment Management#Responsible|<small>[2]</small>]] | ||
| - | | - | ||
Line 120: | Line 145: | ||
| - | | - | ||
|- | |- | ||
| | |style="text-align:left;" |[[#ITIL Release Management Planning|Release Planning]] | ||
| AR | | AR | ||
| R | | R | ||
Line 126: | Line 151: | ||
| - | | - | ||
|- | |- | ||
| | |style="text-align:left;" |[[#ITIL Release Build|Release Build]] | ||
| AR | | AR | ||
| - | | - | ||
Line 132: | Line 157: | ||
| - | | - | ||
|- | |- | ||
| | |style="text-align:left;" |[[#ITIL Release Deployment|Release Deployment]] | ||
| AR | | AR | ||
| - | | - | ||
Line 138: | Line 163: | ||
| R[[Release and Deployment Management#ITIL Release Management Group 1|<small>[4]</small>]] | | R[[Release and Deployment Management#ITIL Release Management Group 1|<small>[4]</small>]] | ||
|- | |- | ||
| | |style="text-align:left;" |[[#ITIL Early Life Support|Early Life Support]] | ||
| AR | | AR | ||
| - | | - | ||
Line 144: | Line 169: | ||
| R[[Release and Deployment Management#ITIL Release Management Group 2|<small>[5]</small>]] | | R[[Release and Deployment Management#ITIL Release Management Group 2|<small>[5]</small>]] | ||
|- | |- | ||
| | |style="text-align:left;" |[[#ITIL Release Closure|Release Closure]] | ||
| AR | | AR | ||
| - | | - | ||
Line 160: | Line 185: | ||
<span id="Responsible">[2] ''R: Responsible'' according to the RACI Model: Those who do the work to achieve a task within Release Management.</span> | <span id="Responsible">[2] ''R: Responsible'' according to the RACI Model: Those who do the work to achieve a task within Release Management.</span> | ||
<span id="Team">[3] see [[Roles | <span id="Team">[3] see [[ITIL Roles|→ Role descriptions]]</span> | ||
<span id="ITIL Release Management Group 1">[4] Process Owner, IT Operator, Facilities Manager (and others, as appropriate) | <span id="ITIL Release Management Group 1">[4] Process Owner, IT Operator, Facilities Manager (and others, as appropriate)</span> | ||
<span id="ITIL Release Management Group 2">[5] ... and others, as appropriate. | <span id="ITIL Release Management Group 2">[5] ... and others, as appropriate.</span> | ||
<p> </p> | <p> </p> | ||
<p> </p> | |||
==[ Infobox ]== | |||
<html><table class="wikitable"> | |||
<tr> | |||
<td>Link to this page:</td> | |||
<td><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management">https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management</a></td> | |||
</tr> | |||
<tr> | |||
<td>Languages:</td> | |||
<td><span itemprop="inLanguage" content="en">English</span> | <span><a itemprop="citation" class="external text" href="https://wiki.de.it-processmaps.com/index.php/Release_und_Deployment_Management" title="Release and Deployment Management">Deutsch</a></span> | <span><a itemprop="citation" class="external text" href="https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_Ediciones_e_Implementacion" title="Gestión de Ediciones e Implementación">español</a></span></td> | |||
</tr> | |||
<tr> | |||
<td>Image:</td> | |||
<td style="vertical-align:top"><a itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/8/86/Release-and-deployment-management-itil.jpg" title="Release Management">ITIL Release & Deployment Management (.JPG)</a></td> | |||
</tr> | |||
<tr> | |||
<td>Author:</td> | |||
<td><span itemprop="author">Stefan Kempter</span>, <span itemprop="creator copyrightHolder publisher">IT Process Maps</span> <a rel="author" href="https://plus.google.com/111925560448291102517"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a></td> | |||
</tr> | |||
</table> | |||
<p><small> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management#Process_Description" itemprop="url"><span itemprop="title">Process Description</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management#Sub-Processes" itemprop="url"><span itemprop="title">Sub-Processes</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management#Definitions" itemprop="url"><span itemprop="title">Definitions</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management#Roles_.7C_Responsibilities" itemprop="url"><span itemprop="title">Roles</span></a> | |||
</span> | |||
</small></p> | |||
</div><!-- end of schema.org/WebPage --><p></html> | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL process]][[Category:Service Transition|Release & Deployment Management]][[Category:Release & Deployment Management|!]] | [[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL process]][[Category:Service Transition|Release & Deployment Management]][[Category:Release & Deployment Management|!]] | ||
<!-- --- --> | <!-- --- --> |
Revision as of 14:31, 15 December 2013
<seo metakeywords="release management process, deployment management, release and deployment management, itil release management, itil release and deployment" metadescription="Release and Deployment Management: ITIL process definition - Sub-processes - Terms - Additional information on ITIL Release Management." />
![DE - ES - Release and Deployment Management](/images/thumb/6/6d/ITIL-Wiki-de-es.jpg/100px-ITIL-Wiki-de-es.jpg)
Objective: ITIL Release and Deployment Management aims to plan, schedule and control the movement of releases to test and live environments. The primary goal of Release Management 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
Process Description
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 Release Management provides considerably more details in the areas of Release planning and testing; this led to the addition of two dedicated processes which were subsumed under Release Management in the previous ITIL version: Project Management - Transition Planning and Support, and Service Validation and Testing.
![ITIL Release Management & ITIL Deployment Management ITIL](/images/thumb/8/86/Release-and-deployment-management-itil.jpg/375px-Release-and-deployment-management-itil.jpg)
In ITIL 2011 Release Management is called upon from Project Management to perform the detailed planning of Release build, Release test and Release deployment.
Additional interfaces between Release Management and ITIL Project Management have been introduced to make sure that Project Management is constantly provided with current planning information.
The process overview of Release & Deployment Management (.JPG) is showing the most important interfaces (see Figure 1).
The latest ITIL 2011 guidance also specifies that Minor Changes are implemented by Change Management without the involvement of Release Management, so the Minor Release Deployment sub-process has been removed.
Sub-Processes
These are the ITIL Release Management sub-processes and their process objectives:
Release Management Support
- Process Objective: To provide guidelines and support for the deployment of Releases.
Release Planning
- Process Objective: To assign authorized Changes to Release Packages and to define the scope and content of Releases. Based on this information, the Release Planning process develops a schedule for building, testing and deploying the Release.
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. At the end of this process, all required Release components are ready to enter the testing phase.
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 and 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.
Definitions
The following ITIL terms and acronyms (information objects) are used in the ITIL Release Management process to represent process outputs and inputs:
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 (see also: ITIL Checklist Release Policy).
Release
- A Release (also referred to as a Release Package) consists of a single Release Unit or a structured set of Release Units.
Release Record
- A Release Record contains all details of a Release, documenting the history of the Release from the first planning stages to closure.
Release Unit
- A Release Unit is a set of new, changed and/or unchanged Configuration Items, which are tested and introduced into the live environment together to implement one or several approved Changes.
Templates | KPIs
- Key Performance Indicators (KPIs) Release and Deployment Management
- Release Management templates and checklists:
Roles | Responsibilities
Release Manager - Process Owner
- The Release Manager is responsible for planning 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.
Responsibility Matrix: ITIL Release Management | ||||
ITIL Role / Sub-Process | Release Manager | Project Manager[3] | Service Owner[3] | Other roles involved |
---|---|---|---|---|
Release Management Support | A[1]R[2] | - | - | - |
Release Planning | AR | R | - | - |
Release Build | AR | - | - | - |
Release Deployment | AR | - | R | R[4] |
Early Life Support | AR | - | R | R[5] |
Release Closure | AR | - | - | - |
Remarks
[1] A: Accountable according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the ITIL Release & Deployment process.
[2] R: Responsible according to the RACI Model: Those who do the work to achieve a task within Release Management.
[3] see → Role descriptions
[4] Process Owner, IT Operator, Facilities Manager (and others, as appropriate)
[5] ... and others, as appropriate.
[ Infobox ]
Link to this page: | https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management |
Languages: | English | Deutsch | español |
Image: | ITIL Release & Deployment Management (.JPG) |
Author: | Stefan Kempter, IT Process Maps ![]() |