[Author Prev][Author Next][Thread Prev][Thread Next]
[Author Index (this month)][Thread Index (this month)][Top of Archive]

Re: The Technical Writer vs. Agile Development Methodologies

Subject: Re: The Technical Writer vs. Agile Development Methodologies
From: "Gene Kim-Eng" <techwr -at- genek -dot- com>
To: "Kevin McGowan" <thatguy_80 -at- hotmail -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 31 Jan 2006 12:52:27 -0800

My guess is that the person who said that is someone who
wouldn't be concerned about user docs in any development
environment. Developing user docs in an "agile" environment
is not much different from doing it in a "non-agile" one. You
determine what documents are needed, when they are
needed, what is needed to create them and when that is
needed, then go make developers' lives miserable until you
get access to it. All that is different is the details of how all
of that is portioned and scheduled in the process. While it
is true that agile development methodology puts less of an
emphasis on *developer* documentation, it has no more and
no less "bias" against *user* documentation than the people
who are doing the developing.

Gene Kim-Eng



----- Original Message ----- From: "Kevin McGowan" <thatguy_80 -at- hotmail -dot- com>

Is anyone else out there struggling with a development team determined to use Agile Development methodologies? I'm trying to research on what the ideal role for the tech writer in all of this Agile madness.

In one of our courses, we actually had a trainer say something to the effect that end-user docs aren't a concern in agile... I know that's not exactly the best way to say it, but it seems that Agile methodology may well be suffering with a bias (intentional or not) against the tech writers who must keep up with all the Agile-ness to create end-user documentation.


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

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.

Follow-Ups:

References:
The Technical Writer vs. Agile Development Methodologies: From: Kevin McGowan

Previous by Author: Re: Items in a Series and Comma Use?
Next by Author: Re: The Technical Writer vs. Agile Development Methodologies
Previous by Thread: Re: The Technical Writer vs. Agile Development Methodologies
Next by Thread: Re: The Technical Writer vs. Agile Development Methodologies

[Top of Archive] | [Author Index (this month)] | [Thread Index (this month)]

What this post helpful? Share it with friends and colleagues:

Sponsored Ads