RE: Resources on estimating documentation projects

Subject: RE: Resources on estimating documentation projects
From: "Johnson, Tom" <TJohnson -at- starcutter -dot- com>
To: "Tony Markos" <ajmarkos -at- yahoo -dot- com>, "Sharon Burton" <sharon -at- anthrobytes -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 4 Jan 2006 13:31:01 -0500


Yes, estimating requires analysis. Is that the word you're hoping someone will use?

You have to look at the thing you're documenting and find out what it is that you have to describe, teach, or convey to the reader/learner. You have to ask your SME what they want covered, to what depth, and how much do they think they want to pay (or come up with that figure on your own).

There are different ways to compile your estimate. I've even heard some people have used DFD's to get a handle on the project.

You might also find out the scope is closely related to the estimate.

Tom Johnson
Technical Writer
tjohnson -at- starcutter -dot- com

-----Original Message-----
From: techwr-l-bounces+tjohnson=starcutter -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+tjohnson=starcutter -dot- com -at- lists -dot- techwr-l -dot- com]On
Behalf Of Tony Markos
Sent: Wednesday, January 04, 2006 12:22 PM
To: Sharon Burton; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Resources on estimating documentation projects


So what is the essence of her approach to time
estimating: history (maybe Ok if your doing a
knock-off, but many - maybe most of us - don't do too
many of those)? anticipated page count? number of



P.S. You know Sharon, Hackos credits Yourdon as a
source of inspiration.

"It is only by dying (i.e., following the flow of
data) that we are born again (i.e., come to understand
the underlying logic of a software system)" - AJ

--- Sharon Burton <sharon -at- anthrobytes -dot- com> wrote:

> Nor does it cover the inportance of red licorice
> whips and pizza in a project.
> But it does the most accepted quality standards in
> the industry, such as CCM,
> and how those apply to tech pubs projects.
> It's not about analyzing your project, it's about
> managing it as tho it were a
> project in an organization that is striving for
> quality, Tony. You might want
> to get the book and then read it. It is the accepted
> bible in our
> field. It has
> a lot of important information you should know.


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.


Previous by Author: RE: Taking on a contract
Next by Author: RE: Friday Poll Idea (WAS: In love with a word)
Previous by Thread: RE: Resources on estimating documentation projects
Next by Thread: Scoping vs Estimating

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

Sponsored Ads