??? Don??™t stop: Never declare, ???The documentation is finished.??? Never let a project manager have
a separate step at the end of a project called ???documentation.??? If documentation is included
in a project plan, it should span the entire project, and then some. Writing documentation should
be an iterative process. Even Books Online, arguably the best piece of documentation for any
software product on the market, posts revisions now and then. Every time either you or a colleague
use the documentation, examine it for errors or omissions and take notes. Then go back
through and add what??™s missing.
Will these suggestions alleviate the agony of creating documentation? Of course not. However,
they should help you create a much more useful document quicker and with fewer errors. When I
remember to follow these rules, I always have better luck. Now if only I could remember to follow them
every time.
Key Business Constraints for BRPs
The first step to creating a BRP is to define the data-protection requirements. Those
requirements will ultimately be driven by external factors, and a compromise must be
met.
Pages:
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216