For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone
Note: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
The Itil Community Forum: Forums
ITIL :: View topic - What is the difference between Change and release mgt
Release Management starts at the need for an enhancement to IT and continues through design, build, test activities, deployment plans, training plans, etc. Many distinguish between IT Projects and Software projects. I don't since many of the process activities are the same. At the end of this process, you'll have potentially many changes that need to occur to meet the objective of a singular release.
Change Management picks up the ball from Release by assessment of risk and impact for all those individual changes coupled with potentially many other changes from other releases, projects, maintenance activities, facilities work etc. The process ensures all prerequisites are met, no schedules conflict, stakeholders are informed and the appropriate bodies have approved.
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Wed Nov 30, 2011 8:38 pm Post subject:
abu1 wrote:
Release Management starts at the need for an enhancement to IT
No it does not. A need for an enhancement to IT leads to an enhancement specification, design, development and testing, preferably preceded by a change request and approval, but at least at an early stage so that the development activity is not wasted on something that will not be accepted.
abu1 wrote:
and continues through design, build, test activities, deployment plans, training plans, etc.
This is misleading. The only development and testing to be performed by release management is the development and testing of the release plan.
abu1 wrote:
Change Management picks up the ball from Release by assessment of risk and impact
Managing the release is a step in implementing the change. I.e. it is a step in the change plan.
Not only does change management not pick up the ball from release management, but also the reverse is untrue because change management continues beyond the end of release management as well as starting before it. _________________ "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
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
Forum FAQ
Search
Usergroups
Profile
Log in to check your private messages
Log in
