One or more changes to an IT service that are built, tested and deployed together
Release
Scope of a Release (3)
- Process
- System
- Function
covers release numbering, frequency and the level in the IT infrastructure that will be controlled by definable releases.
Release Policy
Releases should be uniquely identified according to a scheme defined in the release policy.
Release Identification
will help to ensure repeatability and consistency.
Automation
Release design options and considerations (3)
- Big bang
- Phased approach
- Push and pull
The new or changed service is deployed to all user areas in one operation.
Big bang
The service is deployed to a part of the user base initially, and then this operation is repeated for subsequent parts of the user base via a scheduled rollout plan.
Phased approach
is used where the service component is deployed from the centre and pushed out to the target locations.
Push approach
is used for software releases where the software is made available in a central location but users are free to pull the software down to their own location at a time of their choosing.
Pull approach
will define what approach to use when transitioning from the current service to the new one.
Service design
should be authorized as part of the change management process
Release and deployment plans
Release and deployment plans should define (4)
- Scope and content of the release
- Risk assessment and risk profile for the release
- Customers affected by the release
- CAB members that approved the change request for the release and deployment
establishes the approach to building, testing and maintaining the environments prior to production.
Build and test planning
are useful for testing the service with a small part of the user base before rolling it out to the whole business.
Planning pilots
Logistics and delivery planning aspects (3)
- Delivery of release units and service components.
- Typical lead times.
- Progress tracking.
Key aspects that need to be managed during the activities to build and test a service (3)
- Usage of the build and test environments
- Recording the complete record of the build so that it can be rebuilt if required
- Maintaining evidence of testing, e.g. test results and test report
key activities to build a release package (4)
- Assemble and integrate the release components in a controlled manner
- Create the build and release documentation
- Install and verify the release package
- Send a notification to relevant parties
When reviewing a deployment the following activities should be included (3)
- Capture experiences and feedback on customer, user and service provider satisfaction with the deployment
- Review quality criteria that were not met
- Check that any actions, necessary fixes and changes are complete
