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: TKCC
New Today: 50
New Yesterday: 76
Overall: 142345

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

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

Change X Release Management

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





PostPosted: Sat Dec 04, 2004 7:14 am    Post subject: Change X Release Management Reply with quote

Hey Guys,

I'm experiencing some trouble designing the ITIL processes for change and release management. The border between these two process isn't clear in the ITIL books.

I wanna check if you guys have this clear in your minds:

- Should I have a release everytime I have a change?
- A release is a collection of several changes?
- Can I have changes deployed without a release?
- Should I use release only for large changes?
- What's the difference between the planning & testing I must do in change management and the ones I have to do in release management?

Tks a lot!

[]s

Leo
Back to top
leebc
Newbie
Newbie


Joined: Sep 14, 2004
Posts: 14
Location: Australia

PostPosted: Mon Dec 06, 2004 8:32 pm    Post subject: Reply with quote

Change and Release go hand-in-hand, so there is a very tight link between them.
The question you should ask is "What is the impact of the change"?. i.e. impact on people, processes and technology. The answer will tell you whether the a "formal" release process should be followed in order to implement the change or not.

The planning and testing carried out in Change Management is effectively for the release of a patch etc. which need to be identifed during the change discussions.

I hope this gives you some insight.
Back to top
View user's profile
blamblam
Itiler


Joined: Jan 16, 2005
Posts: 37
Location: New Zealand

PostPosted: Tue Feb 08, 2005 12:22 pm    Post subject: Reply with quote

For us... Change and Release go hand in hand, as leebc said. Whether it goes through Release Management is dictated by the type of Change. Standard Changes do not need to go through the Release Management process. Minor, major, etc. Changes (we group these as Non-Standard Changes) always go through Release.

A release doesn't have to be a collection of changes. If the Change is major, it may have it's own Release. The most important aspect of the Release process (where it interacts with Change) is the scheduling (to ensure that Changes don't trip each other up) and the maintenance of data respositories - CMDB, DSL, etc.

The planning and testing in Change are proving the Change will result in the desired outcome. The planning and testing in Release are ensuring it's implementation goes smoothly.

That's how it works for us. I hope this helps...
Back to top
View user's profile Visit poster's website
fair_n_hite_451
Newbie
Newbie


Joined: Feb 23, 2005
Posts: 7

PostPosted: Thu Feb 24, 2005 8:09 am    Post subject: Reply with quote

I would define it thusly (and certainly feel free to disagree)...

All "releases" are changes.
Not all changes are releases.

Certainly over in my corner of the world, the connotation to a "release" is that you're talking about end user software - be it code, drivers, database schema changes, whatever.

It may be that that is the major source of change within an organization, but there are also the infrastructure driven changes (new servers, new disk clustering, backup/restore software). For my organization, these constitute a large percentage of change, and therefore we are driving out "change manangement" faster than we are driving out "release management".

We know we'll have to get to them both, but CM seems to proffer the short term advantage of harnessing all changes as opposed to only some. As well, once rigorous CM is in place, it becomes the stick used to drive out proper RM practices back into the organziation ... in effect RM will become a subset of CM (along the lines of CM having a checklist item asking "have all standard RM elements been completed?")

Makes sense?
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.