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:John Cornellier <cornellier1 -at- stavanger -dot- oilfield -dot- slb -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Wed, 14 Jan 2004 09:09:43 +0100
In most software projects there is a short period before commercialization where the UI & functionality are stable. Not two months though.
This is just before and during beta testing, when developers go into bug fixing mode; no new features are being added -- developers are just fixing any show stoppers.
I personally have never been involved in a software project where the release waited on documentation. Knock on wood.
John Cornellier
tirsdag 13. januar 2004, 19:39, skrev Gene Kim-Eng:
> 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. I think my record for "extra time" after
> the last UI change had been made in SW I was documenting
> was around two weeks, and that was because of all the
> non-UI background changes that were being made.
