Release Management: Difference between revisions
From IT Process Wiki
mNo edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
==Sub-Processes== | ==Sub-Processes== | ||
[[Image:overview_rm.jpg| | [[Image:overview_rm.jpg|thumb|573px|none|link=https://wiki.en.it-processmaps.com/index.php/File:Overview_rm.jpg|Overview of Release Management]] | ||
'''Plan Rollout''' | '''Plan Rollout''' | ||
*Process objective: Planning of the Rollout in detail and devising the necessary technical concepts for the distribution of the Release. | *Process objective: Planning of the Rollout in detail and devising the necessary technical concepts for the distribution of the Release. | ||
'''Develop Distribution and Back-out Procedures''' | '''Develop Distribution and Back-out Procedures''' | ||
*Process objective: Development of technical and/ or organizational procedures for the distribution of the new Release components, as well as back-out solutions in case of unpredicted problems. | *Process objective: Development of technical and/ or organizational procedures for the distribution of the new Release components, as well as back-out solutions in case of unpredicted problems. | ||
'''Test Release''' | '''Test Release''' | ||
*Process objective: The Release components and the distribution and back-out procedures are to be submitted to a realistic test, so that a substantiated decision can be made with regards to the go-ahead of the Rollout. | *Process objective: The Release components and the distribution and back-out procedures are to be submitted to a realistic test, so that a substantiated decision can be made with regards to the go-ahead of the Rollout. | ||
'''Carry out Rollout''' | '''Carry out Rollout''' | ||
*Process objective: Rolling-out of the Release components into the productive IT environment and ensuring that the Rollout was successful. | *Process objective: Rolling-out of the Release components into the productive IT environment and ensuring that the Rollout was successful. | ||
==Involved Roles== | ==Involved Roles== | ||
| Line 48: | Line 41: | ||
*'''<span id="Release-Manager-ITIL-V2">Release Manager</span>''': As a central body, the Release Manager is responsible for the implementation of changes to the IT Infrastructure, so that these are carried out effectively, safely, and verifiably. His tasks include planning, monitoring and implementation of respective Rollouts or Rollins in co-ordination with Change Management. | *'''<span id="Release-Manager-ITIL-V2">Release Manager</span>''': As a central body, the Release Manager is responsible for the implementation of changes to the IT Infrastructure, so that these are carried out effectively, safely, and verifiably. His tasks include planning, monitoring and implementation of respective Rollouts or Rollins in co-ordination with Change Management. | ||
*[[ITIL Roles#Test-QS-Manager|Test and QS Manager]] | *[[ITIL Roles#Test-QS-Manager|Test and QS Manager]] | ||
==Related Checklists and KPIs== | ==Related Checklists and KPIs== | ||
| Line 58: | Line 49: | ||
====KPIs==== | ====KPIs==== | ||
*[[KPIs Release Management|Key Performance Indicators "Release Management" according to ITIL V2]] | *[[KPIs Release Management|Key Performance Indicators "Release Management" according to ITIL V2]] | ||
==Related [[ITIL Glossary]] Terms== | ==Related [[ITIL Glossary]] Terms== | ||
*[[ITIL Glossary/_ITIL_Terms_R#Release Plan|Release Plan]] | *[[ITIL Glossary/_ITIL_Terms_R#Release Plan|Release Plan]] | ||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V2]][[Category:ITIL process]][[Category:Service Support]][[Category:Release & Deployment Management]] | [[Category:ITIL V2]][[Category:ITIL process]][[Category:Service Support]][[Category:Release & Deployment Management]] | ||
<!-- --- --> | <!-- --- --> | ||
Latest revision as of 17:54, 4 February 2016
ITIL Version: ITIL V2 → see also Release and Deployment Management - ITIL V3
Process-Objective: Release Management is the central responsible body for the implementation of Changes to the IT Infrastructure, so that these are carried out in an effective, secure and verifiable manner. Their tasks include planning, monitoring and implementation of respective Rollouts or Rollins in co-ordination with Change Management.
Part of: Service Support
Process Owner: Release Manager
Sub-Processes
Plan Rollout
- Process objective: Planning of the Rollout in detail and devising the necessary technical concepts for the distribution of the Release.
Develop Distribution and Back-out Procedures
- Process objective: Development of technical and/ or organizational procedures for the distribution of the new Release components, as well as back-out solutions in case of unpredicted problems.
Test Release
- Process objective: The Release components and the distribution and back-out procedures are to be submitted to a realistic test, so that a substantiated decision can be made with regards to the go-ahead of the Rollout.
Carry out Rollout
- Process objective: Rolling-out of the Release components into the productive IT environment and ensuring that the Rollout was successful.
Involved Roles
- Application Manager
- ITC Infrastructure Manager
- Release Manager: As a central body, the Release Manager is responsible for the implementation of changes to the IT Infrastructure, so that these are carried out effectively, safely, and verifiably. His tasks include planning, monitoring and implementation of respective Rollouts or Rollins in co-ordination with Change Management.
- Test and QS Manager
