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: Agile software development and effect on techwriting
Subject:Re: Agile software development and effect on techwriting From:eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com To:Solveig Haugland <solveig -at- techwriterstuff -dot- com> Date:Tue, 13 Jan 2004 11:26:41 -0500
Would seem to me that such an environment would mean the techwriter should be
more closely tied to UI design and concentrate on context sensitive on-line
help.
Seems that at the end of the project, a quick-start guide would then be about
the only printed material you'd produce. Bigger off-line documentation would be
the domain of third-party vendors or follow-up sales and support.
Of course SOME tracking and documentation is required. Otherwise, how are
decisions to incorporate user requests made or supported? How would
configuration management and builds be handled?
