Re: Agile Environment Opinions Wanted

Subject: Re: Agile Environment Opinions Wanted
From: Robert Lauriston <robert -at- lauriston -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 11 Oct 2013 08:51:31 -0700

The advantage of having a doc story in the tracking system is that you
can assign tasks to engineers to check the docs, and they have to
complete them before the end of the sprint.

In my last job I always sized my doc stories as zero points, unless
there was a significant development component, such as the code
changes required when we switched from RoboHelp to WebWorks.

On Fri, Oct 11, 2013 at 1:01 AM, Jen <jennee -at- gmail -dot- com> wrote:
> My former company wasn't doing Agile very well, I suppose, so there were a
> few hitches.
> Tech writers were invited to scrum meetings, but doc tasks weren't tracked
> anywhere and the writers usually weren't asked for a status. ...

New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.

Learn more:


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-leave -at- lists -dot- techwr-l -dot- com

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

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Re: Agile Environment Opinions Wanted: From: Jen

Previous by Author: Re: Perform vs. do
Next by Author: Re: Perform vs. do
Previous by Thread: RE: Perform vs. do
Next by Thread: Legal notices and other typical documentation requirements

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

Sponsored Ads