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.
> Can anyone comment in detail on the technique(s) you
> use to give the most accurate estimate possible and
> any possible caveats you warn your clients of?
Ask them when they need it by.
The caveats:
First, my statement:
"I have alays delivered my project 100% on schedule. I never miss a
deadline."
Now, what's behind that:
Most times, you don't dictate how long you have to create a
deliverable. These criteria are usualy out of your control. What
dictates the timing is release to market, next step in the process
flow, etc.
Therefore..someone will say "We want to deliver the product, along
with documentation, October 31."
Now, I work toward that deadline. Think of the creation of the
document as a layered process. Take the approach that at the end of
any layer, someone is going to rip the document out of your hands.
The first later is the document structure. 2 days, it's done. It will
be modified later, so don't sweat the details. The next layer is
details that MUST absolutely be in the document. The next layer is
details about the details that are in the document. The next layer is
details about the details about the details that are in the document.
The more time you have, the richer the document is.
Example:
Note---these are my approaches to the layers (the mind-set I'm under
while I'm writing), not the sections of the document
Layer 1. How to run the software if nothing goes wrong.
Layer 2. How to run the software if some things goe wrong.
Layer 3. How to run the ssoftware if everything goes wrong.
Layer 4. How to run optional parts of the software.
Layer 5. How to customize the software.
Layer 6. etc.
My point is that a document can be created in 5 days or the document
can take 4 months. Just that the more it ages, the better it is.
The trick is to accept that the "finished" document after layer 2 is
in a condition to use it, but it may not be fun. The more time, the
more polished.
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.
