Disaster recovery planning is not immune to such surprise
requirements.
Because I work as a consultant, I have the luxury of demanding a discovery process??”
that is, time to do nothing but look for requirements. If surprises occur later, I didn??™t do
my job very well. However, surprise does happen, and it continues to happen, regardless
of the activity I??™m doing. No one can think of everything on his or her own.
Techniques to Remove This Roadblock
When performing discovery, I try to include as many people in the discovery process
as possible, or at least attempt to identify who may have additional input. Avoiding surprises
in disaster recovery planning works the same way.
Usually with disaster recovery, the surprises come from a business unit??™s ???true???
requirements. Be sure when performing discovery to take the time to truly understand
what a business unit??™s requirements might be. Keep in mind that what the people in that
business unit tell you is a requirement might not be the real requirement that they need
met. Reword and repeat back to whomever you??™re talking to.
Pages:
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593