Change Trigger

[Benson112]

Hi All,

Happy new year to you all first of all.

Now ive settled back into work its time i pulled my finger out on the change management process.

My first port of call is going to be creating a procedure for when a change is required. Now i understand that this would vary from company to company but i was just hoping for some direction.

We currently only change manage IT activities. We require a change record for: A. Planned maintenance / enhancements. B. Incident resolution whereby the resolution will negatively impact the service. What else would you include in a document detailing "what requires a change record"??

Im trying to word this without sounding daft, i understand change management however i just wonered how other people approach this so am trying to ask an open question.

Thanks in advance

Benson

[UKVIKING]

Have you looked into the Blue book ?

The definition of a change says it all

Change The addition, modification or removal of approved, supported or baselined hardware, network, software, application, environment, system, desktop build or associated documentation.
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[Benson112]

Thanks mate, ive read the description but im just struggling as to where to start with the actualy documentation.

Thanks anyway, its a baseline or me to start as best i can!