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:Solveig Haugland <solveig -at- techwriterstuff -dot- com> To:TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 13 Jan 2004 10:17:22 -0700
>>And how is this is different from other software development theories? ;->
Right, exactly. ;> but there's the theory in "regular" doc that the program specs
are correct and the theory that the UI won't change and so you're expected to
write to those. If it's explicit that everything's up in the air then one has to
address reality more directly.
It sounds from the respondents who've worked on this that groups that adopt and
stick to Agile Development are actually simply really good to work with. TWs
adapt by taking notes on the info but not trying to shove it into Frame or
something with all the page breaks, right there at the beginning. And the Agile
folks really do invite the TWs along to the meetings.
I guess it all comes down to throwing out the Waterfall model of lockstep 1 2 3
and doing, and most importantly expecting, iterative stuff. Do only what you have
to. Accept reality and work with it instead of denying it. Guess I'm Waxing
Philosophical and getting a little excited but I'm more of an iterative person by
nature anyway so this seems kind of cool. If I ever go back to a Regular Job I'll
look for this.
Thanks for the info and personal experiences, y'all.
Solveig
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
solveig -at- techwriterstuff -dot- com
"Tell Me About the Typos When the Software Works."
http://www.techwriterstuff.com
Products expressing the agony and ecstacy of being a techwriter.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bruce Byfield wrote:
> Quoting Solveig Haugland <solveig -at- techwriterstuff -dot- com>:
>
> > So in a world where you get great software at the very last minute, with
> > few docs along the way on the program except some UML and without a
> > solid UI to code to (I believe, not positive), how the heck do
> > techwriters do any docs without an extra two months at the end of the
> > process?
>
> And how is this is different from other software development theories? ;->
>
> --
> Bruce Byfield bbyfield -at- axionet -dot- com 604-421.7177
>
