Joined: Mar 04, 2008 Posts: 1884 Location: Newcastle-under-Lyme
Posted: Tue Sep 25, 2012 7:59 pm Post subject:
Do you have a specific reason for your question? something that we may be able to comment on?
As John says the theoretical or abstract relationship is documented in ITIL texts. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Based on the search that i have done, my understanding is both Change management and Release management go together.
Change management encompasses all changes in technology, systems, applications, hardware, tools, documentation, processes, as well as roles and responsibilities of people. A change could be anything from performing a server hardware upgrade, applying Exchange service packs, updating backup procedures, to simply adding a new user. Although change management takes a structured, phased approach, it should also be able to respond to urgent changes immediately, thus minimizing service interruption. In addition, it should be able to satisfy minor or standard changes with minimal administrative efforts.
However, change management without release management is virtually impossible in an enterprise simply due to the volume of changes involved. The goal of release management is to ensure that all changes are deployed successfully into the production IT environment in the least disruptive manner.
Release management makes the change management process more proactive and predictable. It groups a series of changes into a collection known as a release, which is based on defined common characteristics of the changes. In the case of Exchange server deployment, a release can be the building of a group of servers based on a defined set of roles. The single release of multiple servers with the same server build and a similar impact on the environment can be tracked easily with change management, thereby reducing management complexity.
The Release Management process works by providing a consistent framework for defining and creating new services, and ensuring that the correct versions of tested and approved software are implemented on a day-to-day basis (that is, after initial rollout).
Release Management process interfaces with the Change Management process to enable implementation and to the Configuration Management process to maintain configuration records.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum