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.
> Most of what I've been able to find on the web about
> documentation in
> agaile environments is about internal code
> documentation rather than about
> product user documentation. Does anyone who has
> worked in an
> agile/rapid/extreme environment have any
> recommendations about managing
> user documentation in that environment?
If your internal code is well documented and you have
solid specifications to work from (which you need in a
successful rapid dev environment) then Hackos'
workflow should still be valid from an end-user doc
perspective. You shouldn't look at it as a "chasing
after development" situation, rather, a "harmonizing
with development" one, in which a writer or group of
writers work hand-in-hand with them to completely
document the underlying code. Preferably this should
be done in a way that end-user doc writers can use
portions of source docs or gleen from them more than
enough to pull together the end-user processes.
=====
Goober Writer
(because life is too short to be inept)
"As soon as you hear the phrase "studies show",
immediately put a hand on your wallet and cover your groin."
-- Geoff Hart
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
