Release and deployment

Release and deployment is primarily responsible for managing all aspects of the end-to-end release process. The release and deployment manager will report to the Service Transition manager as will the service test manager; however theseroles should always be undertaken by separate people, and never be combined, to ensure that there is always independent testing and test verification.

The release and deployment manager
The release and deployment manager is responsible for the planning, design, build, configuration and testing of all software and hardware to create the release package for the delivery of, or changes to, the designated service.

The release and deployment manager has the following responsibilities:

• · Manages all aspects of the end-to-end release process

• · Updates the SKMS and CMS

• · Ensures coordination of build and test environment team and release teams

• · Ensures teams follow the organization’s established policies and procedures

• · Provides management reports on release progress

• · Service release and deployment policy and planning

• · Deals with release package design, build and configuration

• · Deals with release package acceptance including business sign-off

• · Deals with service roll-out planning including method of deployment

• · Deals with release package testing to predefined Acceptance Criteria

• · Signs off the release package for implementation

• · Deals with communication, preparation and training

• · Audits hardware and software before and after the implementation of release package changes

• · Installs new or upgraded hardware

• · Deals with storage and traceability/auditability of controlled software in both centralized and distributed systems

• · Deals with release, distribution and the installation of packaged software.

However, some of these responsibilities will be delegated to the relevant release
team sub-process.

The main components to be controlled are:

• Service documentation including:

· Service Portfolio
· Service catalogue
· Service level agreement, OLAs and UCs
· Service Design and specification

• · Application programs developed in-house

• · Externally developed software (including standard off-the-shelf software as well as custom-written software)

• · Utility software

• · Supplier-provided systems software

• · Hardware, and hardware specifications

• · Assembly instructions and documentation, including user manuals.

All deliverables need to be managed effectively, from development or
purchasing, through customization and configuration, through testing and
implementation, to operation in the live environment.

Release packaging and build

Release packaging and build management is the flow of work (establish requirements, design, build, test, deploy, operate and optimize) to deliver applications and infrastructure that meet the Service Design requirements.

The release packaging and build manager

The release packaging and build manager has the following responsibilities:

· Establishes the final release configuration (e.g. knowledge, information,hardware, software and infrastructure)
· Builds the final release delivery
· Tests the final delivery prior to independent testing
· Establishes and reports outstanding known errors and workarounds
· Provides input to the final implementation sign-off process.

The release packaging and build manager cannot perform this role in isolation; other functions with which there will be significant interface are:

· Security management
· Test management
· Change and Service Asset Configuration Management
· Capacity management
· Availability management
· Incident management
· Quality management.

Deployment

Deployment staff have the following responsibilities:

· Deal with the final physical delivery of the service implementation
· Coordinate release documentation and communications, including training and customer, Service Management and technical release notes
· Plan the deployment in conjunction with change and Knowledge Management and SACM

· Provide technical and application guidance and support throughout the release process, including known errors and workarounds
· Provide feedback on the effectiveness of the release
· Record metrics for deployment to ensure within agreed SLAs.