Re: meaning & practice of a "doc freeze"

["Mark Baker" <listsub -at- analecta -dot- com>]

stacy naus asked:

> Does anyone out there use a "documentation freeze" approach in their doc
> development/production strategy?

Documentation freeze is the triumph of process over purpose. Your purpose is
to produce documentation that is as complete and accurate as possible. Your
process should therefore be organized so as to accept input of all kinds for
as long as possible. If you have trouble accommodating the input you are
receiving, the correct question to ask is not, "how can we change our
process to cut off this input", but "how can we change out process to
accommodate this input".

By modularizing your review process, you can extend your ability to receive
input, act on it, and verify the result, right down to the moment at which
the build process starts.
---
Mark Baker
Analecta Communications
www.analecta.com
+1 613 614 5881



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ROBOHELP X5 - ALL NEW VERSION!! 

Have you tried the latest in Help Authoring from RoboHelp?
Try ROBOHELP X5 for Free - Now with Word 2003 support, Content 
Management, Multi-Author support, PDF and XML support and much more! 

Download a free trial today: http://www.ehelp.com/techwr-l4

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.