Re: The Technical Writer vs. Agile Development Methodologies

[Tracy Taylor <ipsque -at- yahoo -dot- com>]

--- A <aurora -at- identicloak -dot- com> wrote:

The fallacy of Agile is that software can
> be made so that
> it requires no documentation. 

I don't think that's a correct assumption about Agile
methodologies.  The principle is that developers value
working software over complete documentation, meaning
functional and technical requirements - they'd rather
have software that works than spend time writing
designs.  The main complaint about this for writers is
that they have to spend more time than usual in
meetings and absorbing information from conversations
developers have around them to get the information
they need.

I think Agile has very little to say about user
documentation or implementation guides.  I managed a
documentation group that worked with a team using
Agile methods and we never found articles or books
about how writers use Agile issues.

Cheers, Tracy


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy.  Watch the demo at http://www.componentone.com/TECHWRL/DocToHelp2005

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.