The most effective disaster recovery plans and programs depend on the people involved. Working strategies depend on stakeholder cooperation and collaboration, combining needs and capabilities to form a cohesive program that incorporates business continuity, security and safety. Read on to learn more about how to take a "team approach" to disaster recovery planning.
To create a full-fledged program for disaster recovery, the right resources must be pulled together, at the right time, and for the right purpose. As a process, structured disaster recovery planning flows through a series of phases designed to facilitate requirements definition, response planning, and when necessary, related action. DRP team structure should be designed to mirror phase structure and workflow, ensuring that all essential planning bases are covered.
A "team approach" to disaster recovery planning provides three (3) primary advantages:
As can be expected, skill, knowledge and staffing requirements may vary according to the scope and purpose of the disaster recovery planning process (considering requirements, planning and implementation). In order to maintain a consistent process flow, appropriate resources must be identified, allocated and assigned accordingly. Considering this results-driven organizational approach, each team "unit" must be structured to suit process goals, skills, roles and responsibilities. (Download our free whitepaper Needs Based Planning for IT Disaster Recovery).
Every team deserves the opportunity to succeed. In order to give your "team" a head start to deliver required results, it must properly assembled and tasked, given all of the necessarily operational tools. To achieve these results, the following questions must be addressed as part of organizational planning:
To deliver actionable results, an effective DRP team must be organized according to standardized principles for operational management. In this fashion, roles and responsibilities can be clearly defined to ensure that all "interests" are being served, and that you have the broadest level of input needed to deliver successful results. Considering these goals, team composition must account for the following:
Further, as a matter of "good practice", every DRP "team" should "organize and operate" according to the following defining principles:
And, communication is key. Team resources should be well-informed and well aware of all DRP goals and objectives. Any significant disaster event will impact a business as a "whole", and as such, all sides of the business entity must be represented in the DRP team. This is essential to ensure that the actual "Disaster Recovery Plan" covers all the angles (technical, financial, operational and administrative).
About Us - ITtoolkit.com has been around since 2001. We started with a few articles about IT projects, and since then have developed our own series of time-saving practices and Toolkits for managing projects and IT services. The article above is part of of our full catalog of "how-to" articles, filled with these techniques (which you won't find elsewhere) to help you get better results in less time. We cover all the basics and then some - including projects, IT services, team building, disaster recovery and more. You can continue with our recommendations above, browse the articles catalog, or download free templates and whitepapers. And, visit our home page to learn all that our Service Strategy and Fast Track Project Toolkits can do for you!
Subscribe to the ITtoolkit newsletter for the latest articles and updates.
See the latest in our collection of IT Management Infographics. Visualize I.T.!
It's certainly possible to manage IT without having a strategic vision, but why would you want to? A strategic vision makes it easier to achieve IT management success, realize added value and fulfill service expectations. A strategic vision is the quick path to make IT more relevant, realistic, responsive and accepted. And that's what IT's all about!
There's no doubt about it - projects are risky propositions. Surrounding conditions are unpredictable - sometimes capabilities meet demands, and sometimes they don't But one thing is for sure -- you are always expected to deliver. That's what strategic fast tracking is for -- to make sure you can deliver even when project conditions are not what you need them to be.