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.
Beth Kane wrote:
>
> It looks like I'm about to get my first independent contract, since leaving
> captive tech writing.
Congratulations: you're now one of the few, the proud, the ...
terminally stressed.
>
> Can someone give me suggestions on how to come up with a fairly accurate
> estimate?
Not really, but here's a few comments:
- it's better to over-estimate than under-estimate. Over-estimating
gives you some leeway, and is probably more realistic. If you do finish
earlier than you officially estimated, you make yourself look good.
Personally, I add about 25 to 50% to the estimate based on my working
speed, and usually use about 10 to 20% of that extra due to unexpected
delays and setbacks.
- try to frame the estimate as plus or minus 10%. Your clients should
know that you can't be exact.
- include the dependencies in the estimate: for example, that the
programmers have to be on schedule, and that you need to be able to talk
to the SMEs. At the bottom of the list of dependencies, state clearly
that, if these dependencies do not come through, then the documentation
will be late, too.
- promise the client that you will provide timely updates, so that no
one is surprised by an over-run or a failed dependency.
> I expect to meet with the client by tomorrow. I plan to get plenty of
> details -- ask how many windows and dialog boxes are in the UI, whether
> development is complete or ongoing, how many SMEs I'll be working with and
> what their availability is like, whether troubleshooting docs need to be
> written, or error message explanations...what else? Any more thoughts on
> realistic variables I can ask the company to supply, to assist me in drawing
> up an estimate? Any special estimation techniques out there??
What about basic hardware and software? Do you need a test bed where you
can install and test to destruction as often as you like? Are you
working off-site, in which case you might be justified in charging
travel expenses when you come in for a conference?
Basically, be as forthright as you can about what you require and the
fact that the estimate is not exact. The less that clients understand
about what they are getting into, the more likely they are to feel they
have a grievance if something goes wrong. Educate them, and the contract
will go more smoothly for everyone.
--
Bruce Byfield 604.421.7177 bbyfield -at- axionet -dot- com
"He did like the ladies, the rise and the fall
Of their ankles and dresses out on the dance floor,
The roll of the dice, the turn of the wheel,
But he took most delight in those slip jigs and reels."
-House Band, "Slip Jigs and Reels"
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Cub Lea, specialist in low-cost outsourced development
and documentation. Overload and time-sensitive jobs at exceptional
rates. Unique free gifts for all visitors to http://www.cublea.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.
