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:Sean Hower <hokumhome -at- freehomepage -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Wed, 14 Jan 2004 08:46:20 -0800 (PST)
------------------------------------
Gene Kim-Eng asks:
I'd be very interested in knowing how many techwriters have
ever had "an extra two months at the end of the process" to
document a SW UI.
------------------------------------
A week or two has been the average for me. Which generally works out for the kind of stuff that I'm doing, smaller applications with a pretty stable core of functions. The last week or so is usually spent verifying info, editing, and inishing up the help files. Two months though, wow, that would be cool. I think I would be lost in that kind of timeframe because I would start seeing possibilities that just weren't there before. Quick starts, lengthy tutorials, in-depth analyses, perfect grammar, you know.....hehehe
