RE: Agile tech writing

Subject: RE: Agile tech writing
From: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
To: Wade Courtney <wade -dot- courtney -at- gmail -dot- com>, "Blount, Patricia A" <Patricia -dot- Blount -at- ca -dot- com>
Date: Fri, 9 Apr 2010 14:28:41 -0400

Wade Courtney admitted:

> Hi Patricia,
> My company just started Agile too. I am the sole writer. I am
> on 3 scrums. I
> go to design meetings, stakeholder demos, planning meetings, and daily
> standups. I am never on sprint behind. Our sprints are 2
> weeks long. I
> maintain a cumulative set of release notes. I think we are planning 2
> releases a year.

We don't do Agile, though:

a) somebody is talking about giving it a go for one product line

b) Agile is also the name of an Oracle plug-in that we use...
great for purposes of confusion...

For the rest of our ... waterfall? projects, we have two
or more releases per year.

Meanwhile, the term "code freeze" remains a standing joke.

We have various sorts of meetings all the time. Per product.
So I'm in lots of meetings. I chime in when it seems to make
sense. I keep my yap shut when that seems a better path.
Sometimes it turns out that I'm right in one choice or
the other....

We don't do GUI around here. It's all toolkit and
command-line administration of the hardware and software.

All of that to say, I'm still not clear on how my life
will really change if we "formally" adopt agile methods
across the board.

- Kevin

The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.


Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial:

Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at:

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

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

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:

Agile tech writing: From: Blount, Patricia A
Re: Agile tech writing: From: Wade Courtney

Previous by Author: MadCap Flare v6
Next by Author: RE: Agile tech writing
Previous by Thread: Re: Agile tech writing
Next by Thread: Re: Agile tech writing

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

Sponsored Ads