Change Control for Documentation

[Beth Agnew <Beth -dot- Agnew -at- senecac -dot- on -dot- ca>]

What change control methods do you use for documentation in your 
organization? In draft stages, I incorporate feedback, corrections and 
changes into subsequent drafts, but as we get closer to deadline, I 
typically go to a "bug priority" method that parallels those used in 
software development. Anything considered a "showstopper", in that it 
would cause the user trouble if left unchanged in (or left out of) the 
final manual gets immediate attention and may even affect release date. 
Other changes that are important but not particularly urgent may get 
into the current manual or be prioritized for the next edition, 
depending on how close we are to release. Nice-to-haves are incorporated 
into the next version of the documentation.

I'm sure there are variations on the above. What have you found to work 
in your shop?
--Beth

Beth Agnew
Professor, Technical Communication
Seneca College, Toronto

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

Create HTML or Microsoft Word content and convert to Help file formats or 
printed documentation. Features include support for Windows Vista & 2007 
Microsoft Office, team authoring, plus more.
http://www.DocToHelp.com/TechwrlList

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.