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: The Technical Writer vs. Agile Development Methodologies
Subject:RE: The Technical Writer vs. Agile Development Methodologies From:"France Baril" <France -dot- Baril -at- ixiasoft -dot- com> To:"R. Armstrong" <rarmstrong -at- alpha -dot- ipswitch -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 10 Feb 2006 10:49:55 -0500
Hi Robert, I'd be really interested in learning more about your
experience with Agile...
My direct questions at this point are:
* Where in the Agile process do you start to get involved? From the
time user stories are created? Before that? After that? Do you
participate to the daily meetings?
* Are you involved in more then one team at the time?
* What would you say is (are) the most important thing(s) an Agile
team can do to support you in your work?
* What would you say is (are) the most important thing(s)you do to
work well with the team?
* What do you provide at each iteration? Do you have
complete/reviewed deliverables at each iteration (with everything that
has been changed or created)?
* Where do you fit the localization cycle in there... Do you localize
at each iteration? At the end only?
Thanks!
-----Original Message-----
From: R. Armstrong [mailto:rarmstrong -at- alpha -dot- ipswitch -dot- com]
Sent: January 31, 2006 4:39 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: The Technical Writer vs. Agile Development Methodologies
I am currently working on an Agile with Scrum development team. While I
don't quite have time to answer all of the negative comments posted
about the methodology, let me say that it can work. It isn't that
Documentation is ignored by the Agile process, but that it assumes that
the documentation is a part of the development, not something that
happens after or before coding takes place.
Like most processes, how it is implemented determines the success or
failure of the process. We have created a tight-knit team of developers,
writers, QA members and a peripheral team of Tech Support, sales and
management. It works for us and I have heard of it working in other
places.
I am moderating a panel overview of Agile/Scrum and how the Tech Writer
fits in at the STC Conference and presenting alone at the Atlanta
Currents in March. If anyone has any specific questions for me, I'll be
glad to answer any direct questions. I just am too unorganized at the
moment to put it all together on the list. Too much information, and not
enough time at the moment to put it all together coherently.
Robert Armstrong
Senior Information Developer
Ipswitch, Inc.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l