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.
Re: How much documentation for 1000 hours of programming?
Subject:Re: How much documentation for 1000 hours of programming? From:Sally Yeo <sallyyeo -at- EXECPC -dot- COM> Date:Thu, 28 Mar 1996 07:16:49 -0600
Kent Newton and Richard Mateosin both commented that it is impossible
to relate programming effort to writing effort. While I agree with
everything they said, I want to add one situation:
When you have done a thorough study to determine the variables, if you
have a new effort to develop a somewhat "normal" effort (for instance,
not object-oriented technology) then a guideline of 10% of the total
effort for documentation. This is only for paper. We never use this
number to actually estimate the work. We only use it to set customer
expectations.
