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.
TechComm Dood (not to be confused with TechComm ;-D) says :
After you're done with the conceptual chunking you can then estimate from there.
-----------
Now I am getting curious. Don't most writers do what I do and create relative dates? After you do the required research and plan/scope/chunk the project, you create a schedule. And the dates in that schedule identify what you need and what you can and cannot control, such as:
~ First draft on Friday of existing functionality.
~ Second draft one week after the software is complete (in testing) which includes full functionality available and all existing review comments.
~ Final draft and multiple outputs released with software, which include all changes and review comments to that point or at any specified time based on the writer's schedule.
So, who uses relative dates? Because until this thread, I kind of assumed everyone did.
