<Organization>
Business continuity management test plan
<Year>
<Version>
<Date of Approval>
This document describes the planned BCM testing activities at <organization>. It provides a comprehensive overview and outline of these activities for different aspects of the testing process and deliverables. The overall purpose of testing is to ensure that all critical processes and applications meet all business, functional, and BCM requirements.
In order to ensure the readiness of vital critical systems in <organization> for disasters, the BCM team prepares an annual business continuity test plan. The plan details the targeted processes and systems, suggested test dates, and test types.
The BIA contains all processes and applications in <organization>; these processes and applications are rated according to criticality: high, medium, and low. The test frequency for any application will depend on its criticality as shown in the table below.
Criticality |
High |
Medium |
Low |
Frequency tests per month* |
1 test per 12 months |
1 test per 18 months |
1 test per 24 months |
* Numbers are only for display and are purely examples.
There are several types of business continuity test:
The testing process is conducted as follows:
1 A meeting is conducted to brief all test team members one week before the test date. In this meeting, the exact scope and scenario of the test is determined. Also, the roles of the test team and vendors, if applicable, are also specified.
2 The test team should fill in and sign the test preparation form before the test is conducted. The form should be approved by all parties.
3 The test is conducted.
4 The test assessment form should be completed by the test team. The form should be signed and approved by the test parties.
5 If the test fails and needs to be rerun, a meeting with the test team should be conducted. A thorough analysis of the failure reasons is done and a new schedule is determined to conduct the test.
Month |
Process/system |
Stakeholders involved |
January |
|
|
February |
|
|
March |
|
|
April |
|
|
May |
|
|
June |
|
|
July |
|
|
August |
|
|
September |
|
|
October |
|
|
November |
|
|
December |
|
|
Ref |
Process/system name |
Test date |
Test type |
1 |
|
|
|
2 |
|
|
|
3 |
|
|
|
4 |
|
|
|
5 |
|
|
|
6 |
|
|
|
7 |
|
|
|
8 |
|
|
|
9 |
|
|
|
10 |
|
|
|
11 |
|
|
|
12 |
|
|
|
13 |
|
|
|
14 |
|
|
|
15 |
|
|
|
16 |
|
|
|
|
|
|
|
18 |
|
|
|
19 |
|
|
|
20 |
|
|
|
21 |
|
|
|
<organization> |
Test preparation form |
|
General information |
|
|
Test reference |
|
|
Process/system name |
|
|
Business units |
|
|
Planned test date and time |
|
|
Test period (hours) |
|
|
Test team |
1 |
|
Test type |
|
|
Test scope |
|
|
<Mention the detailed scope of the test> |
||
Test prerequisites |
|
|
<Any specific preparations for the test> |
||
|
||
Exception |
Justification |
|
|
|
|
|
|
|
|
|
|
Test procedure |
|
|
Activity |
Owner |
Expected time needed |
|
|
|
|
|
|
|
|
|
|
|
|
Affected business units |
|
|
1 |
|
|||
|
|||
Endorsements |
|
||
Designation |
Name |
Date |
Signature |
Team members |
|
|
|
|
|
|
|
|
|
|
|
Test assessment form |
||
General information |
|
|
Test reference |
|
|
System name |
|
|
IT custodian center |
|
|
Planned test date and time |
|
|
Test period (hours) |
|
|
Test team |
1 |
|
Test type |
|
|
Test scope |
|
|
|
|
||||
Exception |
Justification |
|||
|
|
|||
Test result |
|
|||
Fully satisfactory |
Adequate |
Failed |
||
Test procedure |
|
|||
Activity |
Owner |
Time needed |
Result |
|
|
|
|
|
|
Issues and problems identified |
|
|||
1 |
||||
Recommendations |
|
|||
1 |
|
|||
1 2 |
|||
Test team endorsements |
|
||
Designation |
Name |
Date |
Signature |
|
|
|
|
|
|
|
|
|
|
|
|
18.225.255.168