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: Documentation Estimates From:Richard Lippincott <rlippinc -at- BEV -dot- ETN -dot- COM> Date:Mon, 28 Nov 1994 09:23:49 EST
Chuck Martin commented on these figures:
Writing new text: 3-5 hours per page
Revising Existing Text: 1-3 hours per page
Editing: 6-8 pages per hour
Indexing: 5 pages per hour
Production: 5% of all other activities
Project Management: 15% of all other activities
He commented that "testing" was left out.
Good point, it's a major block of time. The figures used when I was doing
hardware manual validations assumed two pages per hour.
I'm curious, though, about the rate for "indexing." Using an indexing function
on FrameMaker, I can apparently work much faster than that. On the othe hand,
certain parts of the task are "invisible", setting up the properly coded info
in the text ahead of time. Has the estimated time for indexing gone down? Or
is it just moved to a different location? What's the opinion on this?
Rick Lippincott
Eaton Semiconductor
rlippinc -at- bev -dot- etn -dot- com
