CHANGE MANAGEMENT PROCESS TEMPLATE

Change Mangagement Process for
Changes to the Production Environment

Note: For a more complete explanation, please refer to the following documents: Recommendations for Production Turnover Procedures (edavid, 3/17/2004); Turnover to Production – Internal Approval Process (collated by Pam Heath-Johnston, Apr. 22, 2004); Enhanced Change Management Process (developed by Nic Lovelace); Change Log Documentation – Template Requirements (template found in Project Management public folder), Entering Change Orders in the Events Calendar on Exchange (developed by Ann Nunes).

Change Attachment

Use this form to generate a text document to attac to your Change Order. Fill in the fields below, click the bottom button, and use the resulting text as your attachment.

Staffing Requirements:

Who will be available during and after change?
Who is to be contacted if there are problems?
For how long will staffing be available?

Predicted effects on service during and after change:

Duration of downtime ?

Change in service expected during and after change.

Who/ how many might be affected.

Web page update:

Enter notice to be placed on Status/Upcoming Changes web page. Leave blank for none.

Gauge of the Risk:

End-user visibility No/low visibility.
Moderate visibility.
Highly visible.

Potential service disruption No disruptions (or less than 10 users).
Could affect up to 100 users/could disrupt service to a single department.
Could affect more than 100 users/could disrupt service to multiple departments; could disrupt connectivity from multiple sites.

Critical dependency Multiple individuals can implement and respond to problems with respect to change.
More than one individual can implement and respond to problems.
Only 1 individual can implement and/or respond to problem.

Number of areas affected Change is localized to a single area.
2 or more areas may be affected.
3 or more areas affected.

Required timing of the implementation Change can be done at any time.
Change must be done within a specific timeframe (i.e. within 1 week).
Change must be done immediately.

Duration of downtime ?
Change in service expected during and after change.
Who/ how many might be affected.

End-user visibility	No/low visibility. Moderate visibility. Highly visible.
Potential service disruption	No disruptions (or less than 10 users). Could affect up to 100 users/could disrupt service to a single department. Could affect more than 100 users/could disrupt service to multiple departments; could disrupt connectivity from multiple sites.
Critical dependency	Multiple individuals can implement and respond to problems with respect to change. More than one individual can implement and respond to problems. Only 1 individual can implement and/or respond to problem.
Number of areas affected	Change is localized to a single area. 2 or more areas may be affected. 3 or more areas affected.
Required timing of the implementation	Change can be done at any time. Change must be done within a specific timeframe (i.e. within 1 week). Change must be done immediately.