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.
> .. Plans are only useful when they make people work faster,
> more efficiently.
Or improve the quality of the output.
> Planning should NEVER take more than 10% of a project's time.
> (I read that in book.)
Another book suggests, for software projects: 1/3 design and specify,
1/6 coding (including developers' tests; get it to the point where
everything compiles and programmers think they've met the spec), 1/2
of total time for testing and debugging.
