Re: Agile tech writing

Subject: Re: Agile tech writing
From: Julie Stickler <jstickler -at- gmail -dot- com>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Fri, 9 Apr 2010 10:22:55 -0400

In order to be successful you *must* be part of the Scrum team. With
less written communication (specs) there is more verbal communication
(meetings, informal hallway conversations.) And that really means
that you need to be located in the same country, building, floor, and
office space as your teammates. If not, you totallly lose out on

You really have to be considered a "pig" and not a "chicken" in the
Scrum meeting. (
TWs tend to be second class citizens in a lot of dev oraganizations,
this is your chance to avoid that. Your company ships two things to
customers, product and doc. You have a customer facing deliverable.
Stress that. Get managment to back you.

Lagging a sprint behind is not a bad thing. I've heard of several
organizations that do that. Sometimes the code isn't checked in until
the last day or two of the sprint, so if you need to see screens to
document them, a sprint behind is just about the only way you can do

And our organization has a quarterly "bug bash" week, where the team
only works on issues. So all those little piddly things can get fixed
then. Also, my team has on occasion let me edit the text strings!

And as Peter noted, there are a wide variety of different ways to
implement Agile. They range from the poor end of the spectrum
(waterfall with daily standups and no specs) to the other end of the
spectrum where the team is completely empowered, runs itself, and has
reached optimum productivity that generates well tested code.

Julie Stickler
Blogging about Agile and technical writing

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

Previous by Author: COntract Reston, VA
Next by Author: Bullets and numbers living together?
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