Release and Deployment Management: Difference between revisions
From IT Process Wiki
mNo edit summary |
|||
| Line 1: | Line 1: | ||
<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 - | <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." /> | ||
<imagemap> | <imagemap> | ||
Image:ITIL-Wiki-de-es.jpg|DE - ES - Release and Deployment Management|100px | Image:ITIL-Wiki-de-es.jpg|DE - ES - Release and Deployment Management|100px | ||
| Line 8: | Line 8: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
== ITIL Release and Deployment Management | == ITIL Release and Deployment Management == | ||
''' | ''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''': [[ITIL V3 Service Transition|Service Transition]] | '''Part of''': [[ITIL V3 Service Transition|Service Transition]] | ||
'''Process Owner''': [[Release and Deployment Management#ITIL Roles | '''Process Owner''': [[Release and Deployment Management#ITIL Roles|Release Manager]] | ||
<p> </p> | |||
== ITIL Release and Deployment Management | == Process: ITIL Release and Deployment Management == | ||
[[Image:Release-and-deployment-management.jpg|thumb= | [[Image:Release-and-deployment-management.jpg|left|thumb|350px|alt=ITIL Release Management & ITIL Deployment Management ITIL|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_release_and_deployment_management_itilv3.pdf ITIL Release & 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: | 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|Release & Deployment Management]] according to ITIL V3: | The following sub-processes are part of [[Release and Deployment Management|Release & Deployment Management]] according to ITIL V3: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
== Sub-Processes == | |||
;Release Management Support | ;Release Management Support | ||
:Process Objective: To provide guidelines and support for the deployment of Releases. | :Process Objective: To provide guidelines and support for the deployment of [[Release and Deployment Management#Release|Releases]]. | ||
;Minor Release Deployment | ;Minor Release Deployment | ||
:Process Objective: To deploy minor, low-risk Releases into the productive environment. This process is used as a streamlined | :Process Objective: To deploy minor, low-risk [[Release and Deployment Management#Release|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 | ;Release Build | ||
:Process Objective: To issue all necessary Work Orders and Purchase Requests so that Release | :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 | ;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 | :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 | ;Early Life Support | ||
| Line 47: | Line 49: | ||
;Release Closure | ;Release Closure | ||
:Process Objective: To formally close a Release after verifying if activity logs and CMS contents are up to date. | :Process Objective: To formally close a Release after verifying if activity logs and [[Checklist CMS CMDB|CMS]] contents are up to date. | ||
<p> </p> | |||
== | == ITIL Terms: ITIL Release & Deployment Management == | ||
;Development Work Order | ;<span id="Development Work Order">Development Work Order</span> | ||
:A Work Order for the development or customization of an application or system, typically issued from Release Management. | :A Work Order for the development or customization of an application or system, typically issued from Release Management. | ||
;Installation Work Order | ;<span id="Installation Work Order">Installation Work Order</span> | ||
:A Work Order for the installation of an application, system or infrastructure component, typically issued from Release Management. | :A Work Order for the installation of an application, system or infrastructure component, typically issued from Release Management. | ||
;Release Policy | ;<span id="Release Policy">Release Policy</span> | ||
:A set of rules for deploying releases into the live operational environment, defining different approaches for releases depending on their urgency and impact. | :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 | ;<span id="Release">Release</span> | ||
:A Release Record contains all details of a Release, documenting the history of the Release from the first planning stages to closure. | :A Release (also referred to as a “Release Package”) consists of a single Release Unit or a structured set of [[Release and Deployment Management#Release Unit|Release Units]]. | ||
;<span id="Release Record">Release Record</span> | |||
:A Release Record contains all details of a [[Release and Deployment Management#Release|Release]], documenting the history of the Release from the first planning stages to closure. | |||
;<span id="Release Unit">Release Unit</span> | |||
:A Release Unit is a set of new, changed and/or unchanged [[ITIL Glossary#CI (Configuration Item)|Configuration Items]], which are tested and introduced into the live environment together to implement one or several approved Changes. | |||
<p> </p> | |||
== Additional Information | == Additional Information == | ||
==== ITIL KPIs ==== | ==== ITIL KPIs ==== | ||
| Line 80: | Line 81: | ||
* [[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 Roles ==== | |||
==== ITIL Roles | |||
;Release Manager - Process Owner | ;Release Manager - Process Owner | ||
| Line 91: | Line 91: | ||
:Typical responsibilities include: Performing backups, ensuring that scheduled jobs are performed, installing standard equipment in the data centre. | :Typical responsibilities include: Performing backups, ensuring that scheduled jobs are performed, installing standard equipment in the data centre. | ||
<p> </p> | |||
== Downloads == | |||
==== Overview ITIL Release & Deployment Management ==== | |||
{| | |||
| valign="top" | | |||
Use the following links to open the process overview of Release & Deployment Management showing the most important interfaces: | |||
* [[Media:Release-and-deployment-management.jpg|Release & Deployment Management (.JPG)]] | |||
* [https://wiki.en.it-processmaps.com/images/pdf/process_overview_release_and_deployment_management_itilv3.pdf Release & Deployment Management (.PDF)]'' | |||
| valign="top" | | |||
[[Image:Release-and-deployment-management.jpg|thumb|150px|left|none|alt=ITIL Release Management & ITIL Deployment Management|Release & Deployment Management at a glance]] | |||
|- | |||
|} | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V3]][[Category:ITIL process]][[Category:Service Transition|Release & Deployment Management]][[Category:Release & Deployment Management|!]] | [[Category:ITIL V3]][[Category:ITIL process]][[Category:Service Transition|Release & Deployment Management]][[Category:Release & Deployment Management|!]] | ||
<!-- --- --> | <!-- --- --> | ||
Revision as of 20:52, 4 September 2011
<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." />
ITIL Release and Deployment Management
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: ITIL 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 & 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 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.
ITIL Terms: ITIL Release & Deployment Management
- 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
- 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.
Additional Information
ITIL KPIs
ITIL Roles
- 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.
Downloads
Overview ITIL Release & Deployment Management
|
Use the following links to open the process overview of Release & Deployment Management showing the most important interfaces: |
|
