Policy 7230A - Department of Administration

5.1.3.a Change Documentation
• An implementation plan that identifies the specific tasks to be
executed prior to implementation, during implementation and
subsequent to implementation.
• A rollback plan that indicates the decision points at which
rollback could be triggered and the tasks that will be used to
return to pre-implementation status should the
implementation fail.
• An escalation plan that identifies the personnel to be
contacted and appropriate contact information should a
problem occur with the implementation that requires either
deviation from the plan or the triggering of the roll back plan.
• A communications plan that identifies all communications
checkpoints that exist during the implementation, the parties
to be contacted and the individuals responsible for
establishing contact.
5.1.3.b Impact Assessment Scheme
• Identify risks associated with the change or with any of the
components of the change.
o Identify systems that are dependent on the system
undergoing change.
o Identify systems that are dependent on the personnel
performing the change.
o Identify systems that share maintenance windows (and
may not be able to be maintained) with the system
undergoing change.
• Determine risk factor by establishing the likelihood of the risk
occurred versus the impact of the risk should it occur.
o Very High risk constitutes high likelihood and high
impact. Risks of this nature must be mitigated.
o High risk constitutes high likelihood and medium
impact or medium likelihood and high impact. Risks of
this nature have a strong need for mitigation and are
unlikely to be accepted.
o Medium risk constitutes high likelihood and low
impact, low likelihood and high impact or medium
likelihood and medium impact. Risks of this nature
have a moderate need for mitigation and may be
accepted.
o Low risk constitutes medium likelihood and low impact
or low likelihood and medium impact. Risks of this
nature have a low need for mitigation and are likely to
be accepted.
12