The Release Policy is the overarching strategy for Releases and was derived from the Service Design phase of the Service Lifecycle.
The Release Plan is the operational implementation for each release.
The Deployment Plan is the documented approach for distributing a single Release.
Overview of Important Steps:
1. Release planning
2. Preparation for build, test and deployment
3. Build and test
4. Service test and pilots
5. Plan and prepare for deployment
6. Perform transfer. Deployment and retirement
7. Verify deployment
8. Early Life Support
9. Review and close the deployment
10. Review and close Service Transition.
* Defining the Release contents
* Defining the Release Schedule
* Defining the resources, roles and responsibilities required for the Release
Build and Test: (Coordinates with other Service Design and Service Transition Processes):
* Produce Release assembly and build instructions
* Create Installation scripts
* Run Test plans
* Develop Back-out procedures
* Produce tested installation procedures.
Plan and Prepare for Deployment:
* Defining timetable for distribution
* Identification of affected CIs
* Defining communication plans
* Defining training plans
* Communication and training for:
o Support staff (including the Service Desk).
Perform Transfer. Deployment and Retirement:
During the actual implementation itself, the activities performed can be grouped under the following tasks:
1. Transfer financial assets
2. Transfer changes required to business/organization
3. Deploy processes and materials
4. Deploy Service Management Capability
5. Transfer service
6. Deploy service
7. Decommissioning and service retirement
8. Remove redundant assets.
These activities will need to be modified to accommodate any items specified in the deployment plan as part of the acceptance criteria for ‘go live’.