Re: Scoping a DocumentationProject??

Subject: Re: Scoping a DocumentationProject??
From: "Gene Kim-Eng" <techwr -at- genek -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 5 Jan 2006 11:32:14 -0800

My experience has been that there is very little being
developed in either hardware or software that is so
new and unprecedented that there is nothing previous
upon which to base an estimate of effort required to
document. Even if you're in a startup company that
is crunching away at its very first product, the chances
are that there's some competitor somewhere whose
product and documentation is going to have enough
similarities to your intended product that it can be used
as an example of what you propose to deliver and the
effort required. Then, after management finishes laughing at your estimate of the resources required,
you can start squeezing out of them some idea of what
they're actually willing to invest in time and effort, what you can deliver for it and what essentials they can't live
without in the finished documents. The "scope" of what
the developers intend to create is almost never relevant
to the final document, because you'll almost never get
what you need to document it all.

Gene Kim-Eng

----- Original Message ----- From: "Tony Markos" <ajmarkos -at- yahoo -dot- com>

To create such a doc in such situations, the TW has to
draw the scope out of the developers. And, for
larger-scale systems, a fairly rigorous and formal
process seems to be required. It is this process of
proding the developers (and/or SMEs) that I am asking


Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today!

Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author content and configure Help in MS Word or any HTML editor. No proprietary editor! *August release.

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
To unsubscribe send a blank email to techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

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

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

RE: Scoping a DocumentationProject??: From: Tony Markos

Previous by Author: Re: Controlling Document Sizes
Next by Author: Re: HELP! A monumental pickle
Previous by Thread: Re: Scoping a DocumentationProject??
Next by Thread: Re: Scoping a DocumentationProject??

What this post helpful? Share it with friends and colleagues:

Sponsored Ads