Project No.:
Document No.:
BACK OUT PLAN
Project name
Service Release
Release
Release Date:
Draft/Final
Date:
Author:
Project
Director:
Project
Champion:
Accountable
Body:
Imperial College – Commercial in Confidence
81896648
insert project name
Date:
DOCUMENT HISTORY
Document
Location
This document is only valid on the day it was printed.
The source of the document is:
Revision History
Revision
date
Author
Distribution
Name
Summary of Changes
New Version
This document has been distributed to:
Title
Date of Issue
Version
PURPOSE
Once a project has gone live and has been handed to support, the Production team need to
have a documented project back out plan if unexpected situations arise.
This document is to be completed by Project Managers, and used in conjunction with the
‘Support Template’ and ‘Service Release Form’.
CONTENTS
New Service Description ............................................................................... 2
Contingency Strategy .................................................................................... 2
Back Out Plan ............................................................................................... 3
Attachments i.e. Deployment Plan ................................................................. 3
Imperial College – Commercial in Confidence
Page 1
81896648
insert project name
Date:
NEW SERVICE DESCRIPTION
Service Description
Enter the description of service (i.e. what purpose is the system serving and who will be affected
in the event of an unexpected situation)
Module Description
Enter the project module information (i.e. how does the module fit in with the rest of the system
and which other parts of the system may be affected? Are there any interfaces that may be
affected?)
Key People
List the key people involved in the project (i.e. lead; BA, Developer, OWB, Security, Networks,
etc) For example:
Project Role
Project Director
Project Champion
Senior Supplier
Project Manager
Business Lead
Lead Business Analyst
Lead Developer
Security Representative
Networks Representative
Infrastructure Representative
DBA
Lead data warehouse dev.
Etc…..
Name
CONTINGENCY STRATEGY
When are critical periods?
After go-live, when are the critical periods in which risks may occur? Please list and explain.
Back out period
Back out is only valid for a certain period of time, when is back out no longer appropriate?
Key Decision Makers
Who are the key decision makers? Who ultimately decides which option is most appropriate?
(E.g. Arthur Spirling, John Shemilt, Tony Morris, Faculty FOO etc)
Imperial College – Commercial in Confidence
Page 2
81896648
insert project name
Date:
If critical risk(s) occurs –
Event
Describe the potential
problem
Options
List the options and their
risks
Recommendation
Consider the options and
suggest the most
appropriate action, include
resource required
BACK OUT PLAN
What is your Back-up Plan?
How quickly can service be restored, how much data may be lost?
Timeframe; i.e. daily, weekly, monthly?
Disaster Recovery Plan – link to your DR document if a major project.
ATTACHMENTS I.E. DEPLOYMENT PLAN
Imperial College – Commercial in Confidence
Page 3