COOP in DoD – Part #1 of 10 – Define the Landscape

Click here to download “Coop in DoD – Part 01 of 10” now!

This paper, the first in a ten-part series, analyzes how a full Continuity of Operations (COOP) program can be implemented for a small, non-mission-critical Army program operating under tight budgetary and personnel constraints.

The Department of Defense (DoD) and the federal government recognize the value of ensuring continuity of government (COG) for all operations deemed critical to the health of the nation. However, this emphasis on protecting only the “most critical” systems can detract from the resiliency of smaller operations. The “iron triangle” of project scope, cost, and schedule can prove difficult enough to work under during the best times as an organization works to accomplish its mission; adding the expense of maintaining resiliency when things go massively wrong can sometimes be seen as a misdirection of scarce resources.

This paper begins by understanding the policy guidelines that drive the larger organization and the Army program. It then analyzes the program to determine what areas either hinder or support the establishment of a COOP program. The paper then closes by providing recommendations on how some possible COOP program implementation problems can, as well as the steps to be addressed in the next paper.

Team-oriented systems mentor with deep knowledge of numerous software methodologies, technologies, languages, and operating systems. Excited about turning emerging technology into working production-ready systems. Focused on moving software teams to a higher level of world-class application development. Specialties:Software analysis and development...Product management through the entire lifecycle...Discrete product integration specialist!

Leave a Reply

Your email address will not be published. Required fields are marked *