Change Management Print

  • computerfundamentals, computer, guide, howto, solution, zillionkinghost, hosting, support
  • 0

Controlling what is altered.

WHY IT MATTERS

Most incidents follow a change.

WHAT A CHANGE PROCESS REQUIRES

A description of what will change An assessment of risk and impact A plan, with steps A way to reverse it Approval, proportionate to risk Notification of those affected A record of what was done

WHAT TO CLASSIFY

Changes by risk, so routine work is not obstructed.

WHAT STANDARD CHANGES ARE

Low-risk, repeated, pre-approved work following a documented procedure.

WHAT EMERGENCY CHANGES ARE

Changes required immediately, with approval afterwards.

WHAT TO REQUIRE EVEN THEN

A record, and a review.

WHAT TO SCHEDULE

Risky work in defined windows.

WHAT TO FREEZE

Changes during critical business periods.

WHAT TO RECORD ALWAYS

What changed, when, by whom.

WHY

It answers the first question in every incident.

WHAT TO REVIEW

Changes that caused incidents, and why the risk was not identified.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot