RE: Documentation and Master Plan

["Barb Einarsen" <barb -dot- einarsen -at- navtelcom -dot- com>]

If you mean that documentation milestones are included as part of the
Release Project Plan, then, sure. Lots of times. It would strike me as
odd if documentation was left off. 

This is especially handing when you are doing Risk Management and want
to show dependencies (see, we really can't deliver on time when code
freeze misses its date/reviews are late and so forth).

Here is the philosophy you need to sell to R&D upper management:
documentation (including, and perhaps especially, online help) is as
much a part of the product as the GUI. 

If you need any other specifics, feel free to email me. 

Barb

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

WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:
http://www.webworks.com/techwr-l

Doc-To-Help 7.5 Professional: New version with new features, improved performance and reliability, plus much more!  Download your free trial today at www.componentone.com/techwrlfeb.

---
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- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.