How to manage unauthorized changes
By ITIL® from Experience©
Unauthorized changes are mentioned profusely in ITIL®. For example, unauthorized changes are mentioned 7 times in the Change Management section and 15 times in the Configuration Management section of ITIL® Service Transition1
. On the other hand, unauthorized changes are mentioned 12 times in ITIL® v2, primarily in the Configuration Management Chapter2
.
Readers are advised to read sections 4.2 and 4.3 of ITIL® Service Transition for guidance. However, since ITIL® is a framework and not a prescriptive cookbook of recipes, readers may find the following articles useful as they discuss nuances of process design and implementation which are left uncovered by ITIL®.
- Should RFCs be logged when an undocumented or unauthorized change is discovered
- Should unauthorized changes have their own process
- Why approve a change that was already made
Also, more than 50 answers to Change Management questions can be found here.
Published on: 2017-12-06
"Implementing Change Management is like driving from New Hampshire where you "Live Free or Die" to Missouri, "The Show Me State."
Related:
- Should RFCs be logged when an undocumented or unauthorized change is discovered
- Why approve a change that was already made
- What level should the Change Manager position be to have the authority to reject RFCs
- Do we need to log an RFC for a Standard Change
From Around the Web:
Category:
ITIL Process > Change Management
Implementation > Process
Copyright 2017 - ITIL® from Experience© - D.Matte
<HR>