Re: The Technical Writer vs. Agile Development Methodologies

Subject: Re: The Technical Writer vs. Agile Development Methodologies
From: Tracy Taylor <ipsque -at- yahoo -dot- com>
To: Anna Junglas <ajunglas -at- hotmail -dot- com>, techwr-l -at- lists -dot- techwr-l -dot- com, bonnie -dot- turner -at- oracle -dot- com
Date: Tue, 31 Jan 2006 15:58:36 -0800 (PST)

Hiya -

Agile doesn't preclude reviews.

With Agile, you're trying to get one small piece of
functionality designed, coded, and ready to release in
an iteration (two or three weeks). You know the
functionality is ready to release because it meets
acceptance tests such as a code review. So a
documentation review is considered part of the
acceptance tests. They also do acceptance tests at
the release level as well.

I know every devevelopment team is different, but ours
was very open to incorporating doc processes into
Agile.

Also, I found that the writers I managed got the
information they needed easiest on the teams with the
strictest Agile processes.

Oh, and by a lot of time in development meetings, I
meant about 20 hours a week.

Cheers, Tracy

--- Anna Junglas <ajunglas -at- hotmail -dot- com> wrote:


---------------------------------

This sounds like the description that I was provided
in a recent interview.

Additionally it was mentioned that if I slow down the
development process by trying to collect doc info,
then I'd be out the door.... :)

I'm all for the gleening process. But it seems like
there would also need to be time allotted for
reviews...? Under your definition below, I guess that
would happen in code reviews? Do Agile developers do
code reviews?

-Anna





---------------------------------

From: Tracy Taylor <ipsque -at- yahoo -dot- com>
To: techwr-l -at- lists -dot- techwr-l -dot- com,
bonnie -dot- turner -at- oracle -dot- com
Subject: Re: The Technical Writer vs. Agile
Development Methodologies
Date: Tue, 31 Jan 2006 13:18:26 -0800 (PST)
>--- 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
ajunglas -at- hotmail -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/ajunglas%40hotmail.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.
>



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

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:

Previous by Author: Re: The Technical Writer vs. Agile Development Methodologies
Next by Author: RE: Hourly vs. Salaried
Previous by Thread: RE: The Technical Writer vs. Agile Development Methodologies
Next by Thread: Re: The Technical Writer vs. Agile Development Methodologies


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


Sponsored Ads