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:"Atkinson, Phil" <Phil -dot- Atkinson -at- BRAID -dot- CO -dot- UK> Date:Fri, 19 Feb 1999 15:31:23 -0000
>> Mike Huber said: One minor point: the "oh, yeah - I
>> guess we need documentation" problem can't be solved
>> by documentation procedures.
The so called problem can only be addressed properly by the right company
ethos and attitude. Regardless of the procedures in place -- for
documentation or development -- they will not be followed unless it is clear
that they are an integral part of the company's development process --
backed up by management.
When I say 'development process', I am not talking about one process
document, but the whole company structure. If a company wants to produce
good software -- design it, develop it, document & test it -- they will do
so because it is part of their ethos to do so. If anyone tries to impose
that structure upon a company they have a significant struggle ahead of them
(and I wish them the best of luck, for it is a noble struggle). If anyone
expects someone else to bring about that change for them, they may be
disappointed.
------------------------------------ * ------------------------------------
Phil Atkinson - Documentation Manager - Braid Systems Limited mailto:phil -dot- atkinson -at- braid -dot- co -dot- uk
> -----Original Message-----
> From: Huber, Mike [SMTP:mrhuber -at- SOFTWARE -dot- ROCKWELL -dot- COM]
> Sent: Friday, February 19, 1999 2:08 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: Documentation and CMM?
>
> > 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
>
> From ??? -at- ??? Sun Jan 00 00:00:00 0000=
> =
>
>
