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.
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Fri Jul 20, 2012 7:36 pm Post subject:
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
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?
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Thu Jul 26, 2012 4:10 am Post subject:
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
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;
All times are GMT + 10 Hours Goto page Previous1, 2
Page 2 of 2
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
