creating user guides in an agile environment

[Robert Lauriston]

I've worked with varying degrees of "agility" including strict,
by-the-book Scrum. Documentation *must* be loosely coupled and
sometimes must follow one or more sprints after the development.

My major example for why this is was an update to OpenLDAP that took
the developer a few days to implement. Documenting migration to the
new version took me over two months because it was so complex and had
so many variables.

The big plus of strict Scrum for me was that I never had any
surprises. All work that developers were doing was defined at the
beginning of each sprint, and I could see from JIRA or Bugzilla what
was ready for me to start work (typically when the developer assigned
the task to QA). That was the only time I've ever known for sure that
my documentation was 100% complete.

On Fri, May 15, 2015 at 9:16 AM, Johnson, Joyce <JJohnson at abtg.com> wrote:
> Is anyone writing software user guides for end users in an environment in
> which the software is being developed following agile guidelines? If so, are
> you writing portions of the user guide at each software iteration? How do
> you handle major revisions to the software? That is, if you wrote a section
> of the user guide on the deliverables produced in the first iteration, then
> learned that the software you wrote about changed in the 4th iteration, what
> did you do? How did that affect your timeline? Do you find writing in
> iterations more beneficial than waiting until the software is in a more
> finished state?