Checklist Release Policy: Difference between revisions
From IT Process Wiki
No edit summary |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<itpmch><title>Checklist Release Policy | IT Process Wiki</title> | <itpmch><title>Checklist Release Policy | IT Process Wiki</title> | ||
<meta name="keywords" content="release policy, itil release policy, release policy itil" /> | <meta name="keywords" content="release policy, itil release policy, release policy itil" /> | ||
<meta name="description" content="Release Policy | <meta name="description" content="The Release Policy represents a set of rules for deploying releases into the live operational environment, defining different approaches for releases depending on their urgency and impact." /> | ||
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/Checklist_Release_Policy" /> | |||
<meta property="og:title" content="Checklist Release Policy | IT Process Wiki" /> | |||
<meta property="og:description" content="The Release Policy represents a set of rules for deploying releases into the live operational environment, defining different approaches for releases depending on their urgency and impact." /> | |||
<meta property="og:site_name" content="IT Process Wiki - the ITIL® Wiki"> | |||
<meta property="og:type" content="article" /> | |||
<meta property="article:publisher" content="https://www.facebook.com/itprocessmaps" /> | |||
<meta property="fb:admins" content="100002035253209" /> | |||
<meta property="fb:admins" content="100002592864414" /> | |||
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/1/15/Release-policy-itil.jpg" /> | |||
<meta property="og:image:width" content="1200" /> | |||
<meta property="og:image:height" content="600" /> | |||
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/4/49/Release-policy.jpg" /> | |||
<meta property="og:image:width" content="519" /> | |||
<meta property="og:image:height" content="778" /> | |||
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" /> | |||
</itpmch> | </itpmch> | ||
<imagemap> | <imagemap> | ||
| Line 10: | Line 25: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
< | '''<span id="Definition">Definition:</span>''' <html><span id="md-webpage-description" itemprop="description">The <i>Release Policy</i> represents a set of rules for deploying releases into the live operational environment, defining different approaches for releases depending on their urgency and impact.</span></html> | ||
'''ITIL Process''': [[ITIL | '''ITIL Process''': [[ITIL Service Transition]] - [[Release and Deployment Management]] | ||
''' | '''ITIL 4 Practice''': Release management | ||
''' | '''Checklist Category:''' [[ITIL-Checklists#ITIL_Templates|ITIL Templates]] | ||
<p> </p> | <p> </p> | ||
__TOC__ | __TOC__ | ||
==Release Policy - Contents== | ==Release Policy - Contents== | ||
[[image:Release-policy.jpg|link=https://wiki.en.it-processmaps.com/index.php/File:Release-policy.jpg|thumb|400px|right|alt=Checklist Release Policy|Fig. 1: [[media:Release-policy.jpg|ITIL Release Policy: Definition and information flow (view full size)]]]] | |||
''The Release Policy typically contains the following information:'' | ''The Release Policy typically contains the following information:'' | ||
| Line 39: | Line 51: | ||
(Requirement that only software from the DML may be included in Releases) | (Requirement that only software from the DML may be included in Releases) | ||
====Release levels==== | ====<span id="release-levels">Release levels</span>==== | ||
For each release level, e.g. major, minor, emergency releases: | For each release level, e.g. major, minor, emergency releases: | ||
# Definition of release level | # Definition of release level | ||
| Line 50: | Line 62: | ||
## Emergency Release deployment requires authorization by [[ITIL Roles#Emergency Change Advisory Board (ECAB)|ECAB]] and is planned, coordinated and documented by a [[ITIL Roles#Major Incident Team|Major Incident Team]] | ## Emergency Release deployment requires authorization by [[ITIL Roles#Emergency Change Advisory Board (ECAB)|ECAB]] and is planned, coordinated and documented by a [[ITIL Roles#Major Incident Team|Major Incident Team]] | ||
====Guidelines for different approaches to Release deployment==== | ====<span id="guidelines-release-deployment">Guidelines for different approaches to Release deployment</span>==== | ||
What are the specific conditions which make a certain approach the preferred option, e.g. | What are the specific conditions which make a certain approach the preferred option, e.g. | ||
# "Big-bang" vs. phased deployment | # "Big-bang" vs. phased deployment | ||
| Line 56: | Line 68: | ||
# Automated vs. manual deployment | # Automated vs. manual deployment | ||
====Constraints for Release deployment==== | ====<span id="constraints-release-deployment">Constraints for Release deployment</span>==== | ||
Service Level and Operational Level Agreements typically specify availability targets, including allowed windows for maintenance during which the service might be unavailable. Unless Emergency Releases are required, Releases are routinely deployed during these maintenance windows. Release Management therefore needs to translate the service-specific constraints into Release deployment constraints for the systems, applications and other components which are required for the service to be available. | Service Level and Operational Level Agreements typically specify availability targets, including allowed windows for maintenance during which the service might be unavailable. Unless Emergency Releases are required, Releases are routinely deployed during these maintenance windows. Release Management therefore needs to translate the service-specific constraints into Release deployment constraints for the systems, applications and other components which are required for the service to be available. | ||
# Service-specific Release deployment constraints as defined in the [[Checklist SLA OLA|Service Level and Operational Level Agreements]] | # Service-specific Release deployment constraints as defined in the [[Checklist SLA OLA|Service Level and Operational Level Agreements]] | ||
| Line 76: | Line 88: | ||
<p> </p> | <p> </p> | ||
<html><a rel="author" href="https:// | ==Notes== | ||
<html>Is based on: Checklist 'Release Policy' from the <a href="https://en.it-processmaps.com/products/itil-process-map.html" title="The ITIL Process Map - the ITIL process model" class="external text">ITIL Process Map</a></p> | |||
<p>By:  Stefan Kempter <a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p> | |||
<p> </p> | |||
<p><small> | |||
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList"> | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Checklist_Release_Policy#Release_levels"> <span itemprop="name">Release levels</span></a><meta itemprop="position" content="1" /></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Checklist_Release_Policy#Guidelines_for_different_approaches_to_Release_deployment"> <span itemprop="name">Guidelines for different approaches to Release deployment</span></a><meta itemprop="position" content="2" /></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Checklist_Release_Policy#Constraints_for_Release_deployment"> <span itemprop="name">Constraints for Release deployment</span></a> | |||
<meta itemprop="position" content="3" /></span> | |||
</span> | |||
</small></p> | |||
<!-- define schema.org/WebPage --> <span itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description"> | |||
<meta itemprop="name Headline" content="Checklist Release Policy" /> | |||
<meta itemprop="alternativeHeadline" content="Release Policy" /> | |||
<link itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Checklist_Release_Policy" /> | |||
<link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/4/49/Release-policy.jpg" /> | |||
<meta itemprop="isBasedOnUrl" content="https://en.it-processmaps.com/products/itil-process-map.html" /> | |||
<link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL-Checklists#ITIL_Templates" /> | |||
<meta itemprop="inLanguage" content="en" /> | |||
<link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/Checkliste_Release_Policy" /> | |||
<link itemprop="author" href="https://www.linkedin.com/in/stefankempter" /> | |||
<meta itemprop="author" content="Stefan Kempter" /> | |||
<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | |||
</span><p></html> | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:Checklist (ITIL)|Release Policy]] | [[Category:Checklist (ITIL)|Release Policy]] | ||
[[Category:Template (ITIL)|Release Policy]] | |||
[[Category:Service Transition|Release Policy]] | [[Category:Service Transition|Release Policy]] | ||
[[Category:Release & Deployment Management|Release Policy]] | [[Category:Release & Deployment Management|Release Policy]] | ||
<!-- --- --> | <!-- --- --> | ||
Latest revision as of 12:08, 31 December 2023
Definition: The Release Policy represents a set of rules for deploying releases into the live operational environment, defining different approaches for releases depending on their urgency and impact.
ITIL Process: ITIL Service Transition - Release and Deployment Management
ITIL 4 Practice: Release management
Checklist Category: ITIL Templates
Release Policy - Contents
The Release Policy typically contains the following information:
Release identification
(Release identification, numbering and naming conventions)
Requirements
(Requirement that only software from the DML may be included in Releases)
Release levels
For each release level, e.g. major, minor, emergency releases:
- Definition of release level
- Expected frequency
- Roles and responsibilities as well as entry and exit criteria for the different stages of the Release and Deployment Management process (these may be modified for specific transitions as the necessity arises)
- Approach and guidelines for grouping Changes into Releases
- Planning and documentation requirements, e.g.
- Minor Release deployment uses the simpler Minor Change Deployment process and is documented in Release Records and Change Records
- Major Release deployment requires setting up a formal project with full documentation
- Emergency Release deployment requires authorization by ECAB and is planned, coordinated and documented by a Major Incident Team
Guidelines for different approaches to Release deployment
What are the specific conditions which make a certain approach the preferred option, e.g.
- "Big-bang" vs. phased deployment
- "Push" vs. "pull" deployment
- Automated vs. manual deployment
Constraints for Release deployment
Service Level and Operational Level Agreements typically specify availability targets, including allowed windows for maintenance during which the service might be unavailable. Unless Emergency Releases are required, Releases are routinely deployed during these maintenance windows. Release Management therefore needs to translate the service-specific constraints into Release deployment constraints for the systems, applications and other components which are required for the service to be available.
- Service-specific Release deployment constraints as defined in the Service Level and Operational Level Agreements
- Service A
- Allowed frequency of new releases according to Release type
- Release windows and constraints (e.g. Saturday 01:00 – 04:00, not in December)
- Service B
- …
- Service A
- Release deployment constraints for systems, applications and other components supporting the above services
- System A
- Allowed frequency of new releases according to Release type
- Release windows and constraints (e.g. Saturday 01:00 – 04:00, not in December)
- System B
- …
- System A
Preferred mechanisms
(Preferred mechanisms to automate the deployment of Releases)
Notes
Is based on: Checklist 'Release Policy' from the ITIL Process Map
By: Stefan Kempter 
, IT Process Maps.
Release levels › Guidelines for different approaches to Release deployment › Constraints for Release deployment
