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.
From Ken's second link: "System overviews are best written towards the end
of the development of a release because you know what you've actually
built."
I think what the author (Scott Ambler) meant to say was, "System overviews
are *often* written towards the end of the development of a release because
no one had the skills, experience, or personality required to do things the
right way. However, system overviews are *best* written before development
begins."
Maybe I'm missing something here. Is "agile" development haphazard by
definition?
Dan Goldstein
> -----Original Message-----
> From: Stitzel, Ken
> Sent: Wednesday, March 03, 2004 1:01 PM
> To: TECHWR-L
> Subject: IT documentation
>
> Two interesting pointers about an IT manager's view of
> documentation. This
> might ruffle a few feathers, although buried deep in the agile modeling
> treatise is a positive comment about the value of hiring real
> tech writers:
>
>http://www.infoworld.com/article/04/02/27/09OPconnection_1.html
>
>http://www.agilemodeling.com/essays/agileDocumentation.htm#Str
ategiesForAgileDocumentation
