Update on Me: Recent Reading, Freelance Work, Job-Hunting, Jews and Comic Books, Money etc. - Mo's Journal
Update on Me: Recent Reading, Freelance Work, Job-Hunting, Jews and Comic Books, Money etc.|
|Date:||March 16th, 2010 07:55 pm (UTC)|| |
A Business Continuity Plan (BCP) is a very important document, but it does require some specialized skills to write it. It's what used to be called a "Disaster Recovery Plan" - but that was soooo negative. It's a plan for how a business will continue in the event of an incident that disrupts normal operations. It could be something major like 9/11 or something as small as a storm. The most common reason for businesses to activate their BCPs is an extended power outage. Writing the BCP is the end of the project. First you have to determine which functions are essential and which can just not be done for a while, how you'll recover the ones that are essential, how to notify staff, where your data and software will be backed up, where you'll recover if you have to use an alternate location, and so on. The BCP documents the results of all that.
Excellent -- I think I may make (find) some scenarios and play with that, with my biggest focus being "who needs to know what?" (My whole class is all about audience and anticipating/meeting their needs more than the memos the students thought it would be. )
That could also give me an EXCELLENT focus for my summer version (6 weeks) of this class, too. I will definitely play with this concept more. Thanks!
|Date:||March 16th, 2010 08:11 pm (UTC)|| |
It's a great exercise for "who needs to know what?" BCP development and writing can get so bogged down in the technical details (because most often people writing them are computer geeks) that the document isn't appropriate at all for the people who have to actually implement it. By definition, in a recovery situation you don't have all your people, all your materials, all your facilities so you need something that clearly tells you what to do, not a lot of engineering schematics of the recovery servers.
Another really important (and oft-neglected) task is testing the plan. It's only in the testing process that you find out the flaws in your plan and can fix them. Also, testing teaches staff the plan. Ideally, one should test annually and have different folks involved in the test each time.