Step 5: Define Scope, Objectives, and Assumptions

Step 5: Define Scope, Objectives, and Assumptions

Design Clear Objectives

One measurement of the Organization DR Coordinator’s success will be whether the final product satisfies the Executive Management’s requirements.

In much the same way as the Organization DR Coordinator needs to know what is expected of him or her, it is essential that there be agreement as to what exactly the DR Planning implementation is going to achieve the desired outcome from the project.

One of the important outcomes is to understand the business goals of DR. Though this is initial and brief, it will provide good directions on what functional areas to be recovered, what length of time and data loss is acceptable for recovery.

Develop Clear Scope

The Organization DR Coordinator needs to consider how much of the operations will be covered. For example, whether it will be a phased recovery and whether PCs should be included if you are in a minicomputer or mainframe environment. It should also consider whether the organization expects an "immediate" recovery of all applications and business functions to full operating level or only the critical applications or business functions or something in between.

While defining the scope of the DR Planning project, the planning team will need to identify:

• Ane entire organization or just its specific business unit.
• The nature and impact of the disaster such as the worst-case scenario.
• The resources required for the project.

Document Limitations and Assumptions

In a standard project management exercise, it is important to identify the “IS” and “IS NOT” of a project. You can ensure that there is no confusion or disagreement about what will, or will not, be included within the scope of the DR Planning project. If, for example, the DR Planning project will not be addressing multiple site disasters or loss of key personnel, document this as a limitation that will be treated in a subsequent DR Planning project.

Here are some examples of assumptions:

• Staff are denied access to the office building for a sustained period of seven calendar days.
• Extend planning to commence on day two or three if the crisis is projected to exceed seven calendar days.
• Address only critical business functions and not daily operational contingencies.
• Only critical business functions will be accorded priority during the seven-calendar day period.
• No more than one country will be affected concurrently by the same disaster.
• Disaster occurs at the most vulnerable time for each business function.
• DR Plan for an IT functional unit is already in place and tested.
• Alternate staff and replacement equipment are available within planned timeframes.

It is imperative that these objectives, scope, limitations, and assumptions be in writing and signed off by the Executive Management. Any subsequent changes must also be in writing and the timeframe and resource allocations amended.

Reference 

Goh, M. H. (2016). A Manager's Guide to Implementing Your IT Disaster Recovery Plan. Business Continuity Management Specialist Series (2nd ed.). Singapore: GMH Pte Ltd.

Extracted from "Step 5: Define Scope, Objectives, and Assumptions"