Scoping a Product Was RE: complete documentation

Subject: Scoping a Product Was RE: complete documentation
From: Tony Markos <ajmarkos -at- yahoo -dot- com>
To: Fred Ridder <docudoc -at- hotmail -dot- com>, ipsque -at- yahoo -dot- com, techwr-l -at- lists -dot- techwr-l -dot- com
Date: Sat, 14 Jan 2006 08:19:02 -0800 (PST)

Since, evidently, there is no published tech writer
literature on the scoping a product, we should follow
the lead of the communities that have written about it
- the Requirements Analysts and (real) Systems

Tony Markos

--- Fred Ridder <docudoc -at- hotmail -dot- com> wrote:

.... But I'll admit that this begs the question
becuase there was never a good resolution of what we
all meant by scoping and how we each go about
accomplishing it.....

Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around

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: complete documentation: From: Fred Ridder

Previous by Author: RE: The non-learning organization?
Next by Author: RE: Rhetoric and technical writing
Previous by Thread: RE: complete documentation
Next by Thread: Re: Scoping a Product Was RE: complete documentation

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

Sponsored Ads