The Cove Business Standards Discussion Forums
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > >
Forum Username

Elsmar Cove Forum Visitor Notice(s)

Wooden Line

ITIL vs. ISO 20000 Change Management Requirements

Monitor the Elsmar Forum
Courtesy Quick Links

Links Elsmar Cove visitors will find useful in the quest for knowledge and support:

Jennifer Kirley's
Conway Business Services

International Quality Services

Marcelo Antunes'
SQR Consulting, and
Medical Devices Expert Forum

Bob Doering
Bob Doering's Blogs and,
Correct SPC - Precision Machining

Ajit Basrur
Claritas Consulting, LLC

International Standards Bodies - World Wide Standards Bodies

AIAG - Automotive Industry Action Group

ASQ - American Society for Quality

International Organization for Standardization - ISO Standards and Information

NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest

IEST - Institute of Environmental Sciences and Technology

Some Related Topic Tags
change management, iso 20000 - it service management, requirements and specifications
Thread Tools Search this Thread Rate Thread Content Display Modes
  Post Number #1  
Old 3rd March 2011, 11:30 PM

Total Posts: 84
Please Help! ITIL vs. ISO 20000 Change Management Requirements

Hi Everyone,

I was thinking what is the difference of the Change Management of ITIL and ISO20000. Since ITIL states types of Changes as Normal,Standard, Emergency Change. While ISO20000 places an "e.g" where it sites urgent, emergency, major, minor.

Please enlighten me on what should be the types of changes that we should have.

Thank you

Sponsored Links
  Post Number #2  
Old 4th March 2011, 02:57 AM
pldey42's Avatar

Total Posts: 429
Re: ITIL vs. ISO 20000 Change Management Requirements

ISO 20000 says, "All requests for change shall be recorded and classified, e.g. urgent, emergency, major, minor."

So if you're going for ISO 20000 Certification all changes have to be recorded and classified. The actual classifications are a matter for you and your organization to determine, depending on the nature of your business and the characteristics of change requests.

For example, I once operated a system in a software development organization where our classifications were:

- nice to have
- must fix, one person cannot work
- must fix, several people cannot work
- must fix, network security or availability compromized

This scheme enabled the sysadmins to prioritize change requests based upon impact to the business rather than political weight of requestors or arbitrary judgement. Also, they didn't need me there all the time to take such decisions - I could do useful things like fending off senior managers who wanted to interfere with their work, or writing proposals to buy new stuff.

Had we wanted ISO 20000 certification, this would have been fine.

Hope this helps,
Thank You to pldey42 for your informative Post and/or Attachment!
  Post Number #3  
Old 5th March 2011, 03:59 AM

Total Posts: 84
Re: ITIL vs. ISO 20000 Change Management Requirements

Thank you. because the debate we have is as to whether what type of change we will use. either the ITIL one or the ISO20000
  Post Number #4  
Old 18th March 2011, 02:25 AM

Total Posts: 82
Re: ITIL vs. ISO 20000 Change Management Requirements

As already covered changes should relate to whatever you need to track. There are some other interesting related ideas (based out of IT work).

standard or routine change: since the general ideas behind change management are to keep track of things, to control risk, and to document approval and implementation steps setting up a standard category of routine changes helps streamline the approval process by pre-approving some types, or at least limiting the processing steps.

emergency change: since the process might be different in urgent cases using a separate category of emergency changes could make sense.

change versus service request versus incident: ITIL is the general reference for what these related ideas mean but again setting up processes and records that make sense for your requirements is critical. If you design in too much complexity implementation will fail quickly.

change versus configuration management: too complicated to say much about, but depending on what changes you are tracking they might correspond to a central configuration reference (see ITIL and related thread in this forum, geared more towards physical design configurations than IT scope).

Lower Navigation Bar
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > >


Visitors Currently Viewing this Thread: 1 (0 Registered Visitors (Members) and 1 Unregistered Guest Visitors)
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Forum Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Emoticons are On
[IMG] code is On
HTML code is Off

Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
ISO 20000 Mapping to ITIL and COBIT tziel IT (Information Technology) Service Management 4 23rd April 2013 08:49 AM
ISO/IEC 20000-1 (IT Managed Services) Configuration Management Database? nomisd Other ISO and International Standards and European Regulations 2 23rd March 2012 04:51 AM
A few Questions on ISO 20000 - IT Service Management System (ITSMS) mjflkitty IT (Information Technology) Service Management 8 2nd March 2011 04:15 AM
Has anyone compared ISO 19011:2002 to ISO 20000-2 (Service Management)? Pataha Internal Auditing 4 5th July 2007 01:55 PM
Change Management - How do you Manage Change Management between Two Sister Companies MonikaG Document Control Systems, Procedures, Forms and Templates 7 6th September 2006 02:42 AM

The time now is 05:06 PM. All times are GMT -4.
Your time zone can be changed in your UserCP --> Options.

Misc. Internal Links

NOTE: This forum uses "Cookies"