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 and CMM? From:"Huber, Mike" <mrhuber -at- SOFTWARE -dot- ROCKWELL -dot- COM> Date:Fri, 19 Feb 1999 09:07:53 -0500
> From: Maaike Groenewege [mailto:mgr -at- MEDIASYS -dot- NL]
...
> My manager has suggested that documentation somehow should be
> fit into this model too, so that the well known "It's three weeks before
> the final release date, and oh yeah, we should have some documentation" issue
> can be avoided. Although many people within the company have already advised
> me on how to do this, I'd like to hear your opinions too.
One minor point: the "oh, yeah - I guess we need documentation" problem can't be solved by documentation procedures. It is solved by product development procedures, which should either include or refer to documentation procedures.
---
Office:
mike -dot- huber -at- software -dot- rockwell -dot- com
Home:
nax -at- execpc -dot- com
