Release and Deployment Management Policy
From IT frameworks
The Release and Deployment (R&D) Manager has the ultimate responsibility for efficient and secure deployment of approved changes to the company's IT environment.
The Change Manager (CM) has the responsibility to ensure that all consequences of the changes are mapped, and has the ultimately responsible for the results of the changes – that changes have the intended results.
The Validation and Testing (V&T) Manager works closely with the R&D Manager and is responsible for uncovering any unwanted effects from any deployments.
There are several statuses on something to be released:
- Planned (P)
- Built (B)
- Tested (T)
- Implemented (I)
- Verified (V)
A release is labelled with the appropriate status throughout the process.
When an IT release has reached status V, it enters the CMDB.
When the R&D Manager receives work orders with approved changes, it enters the queue called the "Release Schedule". The R&D Manager has full authority to stack and re-stack the Release Schedule as he wish within the boundaries set by the Work Order. If he wants to prioritize in such a way that it would contradict the Work Order, he must submit a request to do so to the Change Management.
A release would normally require a project if the RfC has Impact of 4 or 5 and the time required to do the release and deployment is two weeks or more (80 hours of work or more).
The governing policy for the company's IT releases is that the procedures for R&D Management is done thoroughly and by the book, and that all relevant data is documented along the way.
