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: Techniques for Estimating Time From:"Leslie Johnson" <lesliej -at- microsoft -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 20 Sep 2001 08:50:31 -0700
Hi Anthony!
Welcome to the list - I think you'll find it a great resource.
Techniques - the only fool-proof technique I've ever found is to create
a TOC for the job early, and then break the job down into its component
tasks at a granular level. Then you can estimate the time required for
each of the granular tasks. If you use a calendar and your time
estimates, you can come up with dates. For example:
You get the idea. If you don't know how much to estimate for each task,
there are 2 possible solutions:
1. In a current job, for the purposes of learning how to estimate, take
the time to track the time you require for each task, then when you're
finished, divide the number of pages by the total hours for the task to
get an estimated page count/hour. You can use this as a metric going
forward (obviously you'll need to refine the metric as you go).
2. If you dig a bit, you'll find that industry-standard metrics exist.
(I used to know where to find them, but I grabbed a hard copy for my
records and have gotten lazy about tracking an online source since
then.) You can use this as the basis for how you estimate your own time.
The granular task-level estimating process is not something that I
enjoy, obviously because it's grinding work that I *have* to do rather
than doing the writing, which I *like* to do. However, if a client
requests an estimate (and they all do), this is a way to estimate the
time for a project. If you're a contractor, you can use this as the
basis for your cost estimate as well.
Good luck! Anthony, please let me know if I can help in any other way.
A landmark hotel, one of America's most beautiful cities, and
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe. http://ieeepcs.org/2001/
+++ Miramo -- Database/XML publishing automation. See us at +++
+++ Seybold SFO, Sept. 25-27, in the Adobe Partners Pavilion +++
+++ More info: http://www.axialinfo.comhttp://www.miramo.com +++
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.