TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Project estimates From:Sue Ellen Adkins <sea -at- NETCOM -dot- COM> Date:Sat, 23 Dec 1995 05:28:11 -0800
> But, if you *don't* have the years of experience with the type of
> projects you're required to estimate, you have to start *somewhere*.
I've used similar documents to help me estimate the number of pages. When I
revised a software reference manual, I compared the number of software spec
headings to the number of pages. By applying this number (2 headings per
page) to the revised spec, I developed a rough estimate of the number of
pages. I knew the company expected me to use parts of the prior version with
few changes. I guessed 20% could be reused; I think I'm close but at least I
have associated a number with my guess.
Once you've identified your assumptions and developed your estimate, discuss
it with a colleague. I'm usually more concerned with overlooking something
than I am with making an hours-per-page estimate that's a little low.
As tech writers, we frequently put ourselves in the role of a user. Imagine
being a manager and having to evaluate a contractor's quote. How much detail
would you want to see? What questions would you ask?