Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: SMahler
New Today: 24
New Yesterday: 72
Overall: 143771

People Online:
Visitors: 61
Members: 1
Total: 62 .

Languages
Select Interface Language:


Major ITIL Portals
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

Related Resources
Service related resources
Service Level Agreement
Outsourcing

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 - Change Mgmt versus Release Mgmt
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Change Mgmt versus Release Mgmt

 
Post new topic   Reply to topic    ITIL Forum Index -> Change Management
View previous topic :: View next topic  
Author Message
LouisSavalli
Newbie
Newbie


Joined: Apr 19, 2012
Posts: 5

PostPosted: Fri Apr 20, 2012 12:12 am    Post subject: Change Mgmt versus Release Mgmt Reply with quote

I've read over some ITIL material and haven't found a practical explanation of the difference between these two. My understanding is that change mgmt is any single change, whereas release mgmt is a bundle of changes linked together that must also go live together.

Is this accurate? If not, what's wrong with it? Or is there a better explanation?
Back to top
View user's profile
ClaireAgutter
Newbie
Newbie


Joined: Mar 21, 2012
Posts: 19

PostPosted: Fri Apr 20, 2012 2:11 am    Post subject: Reply with quote

Hi Louis

This is a common cause of confusion in ITIL. The simple way we used to put it on Foundation courses was:

Change Management authorises
Release Management does the job

So Change Mgt is where all the discussions happen - is this okay? is this necessary? Should we go ahead?
Once a decision is made to go ahead, Release Mgt handles the physical building of the change and deployment to the live environment (after testing of course). As part of Release Mgt they might bundle changes together for convenience.

Hope that helps,

Claire
Back to top
View user's profile Visit poster's website
LouisSavalli
Newbie
Newbie


Joined: Apr 19, 2012
Posts: 5

PostPosted: Fri Apr 20, 2012 6:18 am    Post subject: Reply with quote

Thanks Claire. That's interesting. In most of my ITIL-based deployments of change management, the change management process handles the actual changes to the environments as well as discussion/approval. It's handled as phases in one change type (i.e. change types of "normal", "emergency", etc).

So what you're saying is that "change management" is meant in a more general sense - it's the management of true organizational change, not granular changes to production or test IT environments. And then when it comes time for the production/test IT environments, it's handled in release management. Am I summarizing what you said accurately?
Back to top
View user's profile
ClaireAgutter
Newbie
Newbie


Joined: Mar 21, 2012
Posts: 19

PostPosted: Fri Apr 20, 2012 5:44 pm    Post subject: Reply with quote

Hi Louis

I think what you're saying is that in your experience Change Mgt has handled physical implementation as well as assessment and authorisation, is that correct? Of course there is no right or wrong way to implement ITIL, it a case of whatever works for the organisation.

From an ITIL theory sense, every organisation will have some kind of business change management that handles changes that affect the whole organisation (for example: we are moving our headquarters to another city - how does this affect staff etc). This will be supported by an IT change management process which looks at the IT considerations (how do we move the servers? When do we do it etc).

IT Change Mgt will assess and authorise the change and then Release Mgt would include physically implementing it - so staff under the control of Release Mgt would do the work and then report back to Change Mgt.

Change Mgt is a purely 'management' process in that it's role is to assess and authorise changes. Release Mgt (from an ITIL perspective) is a 'doing' process that carries out work based on what's been authorised by Change Mgt.

Hope that helps Smile

Claire
Back to top
View user's profile Visit poster's website
LouisSavalli
Newbie
Newbie


Joined: Apr 19, 2012
Posts: 5

PostPosted: Fri Apr 20, 2012 11:08 pm    Post subject: Reply with quote

Thanks Claire, all of that was really helpful. It's interesting to learn how different people apply the ITIL processes. It helps me to understand through experience what people mean when they say that ITIL is "descriptive", not "prescriptive".
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Change Management All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
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

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.