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: ErvinLeffz
New Today: 62
New Yesterday: 73
Overall: 150112

People Online:
Visitors: 47
Members: 1
Total: 48 .

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 - difference between change mgmt & release mgmt
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

difference between change mgmt & release mgmt
Goto page Previous  1, 2
 
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion
View previous topic :: View next topic  
Author Message
Diarmid
Senior Itiler


Joined: Mar 04, 2008
Posts: 1884
Location: Newcastle-under-Lyme

PostPosted: Fri Jul 20, 2012 7:36 pm    Post subject: Reply with quote

Why assume anything? From customer perspective it is irrelevant whether they lacked rigorous management procedures, technical or management competence, or the "must get everything right" attitude. It's not about did they do this thing in this way or that; it's all about whether their overall service management system is up to the job.
_________________
"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
Back to top
View user's profile Send e-mail
rebelskam
Newbie
Newbie


Joined: Jul 17, 2012
Posts: 4

PostPosted: Wed Jul 25, 2012 9:57 pm    Post subject: Reply with quote

UKIT wrote:
With reference to the NatWest Bank problems in June.
The Incident reported by the media was as a result of a software upgrade which failed,impacting millions of account customers.
Presumably an RFC had been raised and presented to a change advisory board for review.


I think this can be good answer to my question - so similar situations will not happen.

Another question from my site will be - Release or a "typical" Change procedure? Anybody have an idea of high level decision flow for this question? Idea
Back to top
View user's profile
Diarmid
Senior Itiler


Joined: Mar 04, 2008
Posts: 1884
Location: Newcastle-under-Lyme

PostPosted: Thu Jul 26, 2012 4:10 am    Post subject: Reply with quote

rebelskam,

I think you are misunderstanding something. Calling something a change or calling it a release. Or, more properly processing something as a release rather than as a change, is not an option.

Nothing should ever be released without being under the umbrella (or instruction or direction) of change management

and

change management should never oversee any implementation without ensuring that the release is managed.

They are not alternatives or mutually exclusive, but rather to aspects of managing the introduction of anything to the live environment.
_________________
"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
Back to top
View user's profile Send e-mail
rebelskam
Newbie
Newbie


Joined: Jul 17, 2012
Posts: 4

PostPosted: Thu Jul 26, 2012 5:45 pm    Post subject: Reply with quote

Diarmid wrote:

I think you are misunderstanding something. Calling something a change or calling it a release. Or, more properly processing something as a release rather than as a change, is not an option.


Diramid, i fully understand a difference and relation to change management.

Diarmid wrote:

Nothing should ever be released without being under the umbrella (or instruction or direction) of change management.


This is also a priority for a successful release.

My question was more related to release policy - so id like to trigger a question- which activities lead to raise Request for Release? Which activities will not count into Release Management.

I see it this way - Change Management invokes Release Management when:

- Emergency change is involving multiple changes;
- Software Changes on operating system level;
- Muliple Changes needed for one change;
- All operating system Changes;

any other ideas? Please share...
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion All times are GMT + 10 Hours
Goto page Previous  1, 2
Page 2 of 2

 
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.