• All projects, bundled changes to an existing service (releases containing multiple enhancements/fixes), and cyclical changes to an existing service must go through the Release Management process and must have a completed request for change (RFC) with appropriate approvals.
  • Whenever possible, changes to an existing service should be bundled together and released on a regular (e.g., monthly) basis using the Release Management process.
  • A single “Release Engineer” must be identified for every release. The release engineer will be responsible for the successful coordination and execution of the release, as well as ensuring all required documentation related to the release exists.
  • Proof that controls (initiation, testing, and approval) have been followed for all auditable Releases shall be stored with the ability to be reproduced.
  • Each Release shall be initiated through a standardized and approved process (service request, incident management, problem management, or PRIME)
  • Each Release should be well tested and verified prior to implementation.
  • All implementation work on the Release should be completed by the Planned End Date/Time.
  • Validation that the Release has been completed successfully should be confirmed through post‐Release testing.