November 29, 2009

Making the Transition to Agile

Filed under: Uncategorized — heratech @ 11:31 pm
Tags: , , ,

Ready Set Go When I first started thinking about making the transition to Agile, I decided that rather than focus on how different Agile was from my current workflow, that it might be less anxiety producing to focus on what I was already doing that seemed Agile.

I’d always been part of a cross-functional team that included (depending on the company) product managers, developers, QA testers, technical writers, support personnel, and training course developers. Although I was used to the teams meeting once a week for an hour, with Agile that would change to meeting daily for 15 minutes.

I already had experience working with skimpy product specifications. There is a great deal of variety in the quality of design and functional specifications that product managers write. I’ve never worked anywhere with what I thought were “extensive” specs, so this idea that a company could spent all their time defining requirements and never get around to writing code was alien to me. It seemed to me that one of the appeals of Agile for developers is that they’d get to write code instead of documentation.

I’d always written the documentation against the product, working through the UI in a development sandbox, not against the specs. So while I was worried about how I was going to estimate without specs, I wasn’t too worried about how I’d do the actual writing.

I liked the idea of a product backlog. Due to time constraints, there was always something that was getting cut at the last minute so that I could hit my deadlines. So I was already keeping a documentation backlog of topics to write or revise for the next release.

The whole concept of “done is done” seemed to require that the writing be broken down into small chunks. I was trained to do modular writing, breaking things down into topics of a page or less. And for the past couple of years I’ve adopted a watered down form of DITA, organizing my content into into Concept, Task, and Reference topics.

But when I started as an Agile writer, I had more questions than answers. And after a couple of months, I still have more questions than answers about how to be the most Agile writer that I can be.



  1. Good blog, but shouldn’t it be “Tenet” rather than “Tenant” (A tenet being a belief or doctrine considered true, whilst a
    tenant is a renter or occupant.)


    John Green

    Comment by John Green — December 16, 2009 @ 9:39 am | Reply

    • *looks sheepish* Thanks for the catch. And you just made my point about spell check, which doesn’t catch homophones. *fixes word choice*

      Comment by heratech — December 16, 2009 @ 10:22 am | Reply

  2. But what if the writer is a shared resource across 4 teams, 5 if another manager had his way, and stand up meetings started to overrun its daily 15 mins and turned to 30m to 45m because of backlog issue planning?
    What should I do if I have to attend 4 standups a day, then it turned to 5 standups because of the time zones – how am I able to get in some writing done?
    There’s 5 groups , then when it comes to planning sessions of 2 -3 hours max each, that week is a nightmare for me.
    Is this really what agile/scrum is all about?

    Comment by fwriter — July 27, 2011 @ 9:18 am | Reply

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: