Comments on: What makes a doc plan Agile? http://justwriteclick.com/2007/08/04/what-makes-a-doc-plan-agile/ Documentation as conversation Fri, 03 Sep 2010 19:26:51 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Michele http://justwriteclick.com/2007/08/04/what-makes-a-doc-plan-agile/comment-page-1/#comment-54 Michele Thu, 09 Aug 2007 18:07:39 +0000 http://justwriteclick.com/2007/08/04/what-makes-a-doc-plan-agile/#comment-54 Hmmm.... I specified the URL of this post, but my blog entry didn't get added here as a comment. Regarding updating my doc plan - I send an update out for each of the early iterations, when things are still in flux. Hmmm…. I specified the URL of this post, but my blog entry didn’t get added here as a comment.

Regarding updating my doc plan – I send an update out for each of the early iterations, when things are still in flux.

]]> By: annegentle http://justwriteclick.com/2007/08/04/what-makes-a-doc-plan-agile/comment-page-1/#comment-53 annegentle Mon, 06 Aug 2007 17:08:57 +0000 http://justwriteclick.com/2007/08/04/what-makes-a-doc-plan-agile/#comment-53 Thanks for commenting - trackbacks are enabled so I'll keep an eye out for your trackback. Just put the URL for the post itself in your trackbacks field. There's no separate trackback URL with my blogging software (Wordpress). You say that you "include updates to the doc plan in the schedule" so you're planning doc details with each iteration. I think that's an ideal middle ground, letting the writer use the doc plan for planning and organization purposes with each changing iteration. But do you run out of time for updates eventually? No one refers to doc plans after a release is out the door (other than to use it as a template for the next release), do they? I found it difficult to keep making changes to the doc plan while I was writing the end-user doc itself. As a planning tool, doc plans are useful, but only for a few iterations and only for the writers and maybe one or two other players it seems. I would go towards a lean doc plan that's throwaway after a few iterations. Oh, and I have to laugh at myself while re-reading my post -- apparently it's more "Agile" to use lowercase for the initial word in a numbered list since I did that style for my second list. Ah, quick posting is fun. And you know, I'm not going to change it now. :) Thanks for commenting – trackbacks are enabled so I’ll keep an eye out for your trackback. Just put the URL for the post itself in your trackbacks field. There’s no separate trackback URL with my blogging software (WordPress).

You say that you “include updates to the doc plan in the schedule” so you’re planning doc details with each iteration. I think that’s an ideal middle ground, letting the writer use the doc plan for planning and organization purposes with each changing iteration.

But do you run out of time for updates eventually? No one refers to doc plans after a release is out the door (other than to use it as a template for the next release), do they?

I found it difficult to keep making changes to the doc plan while I was writing the end-user doc itself. As a planning tool, doc plans are useful, but only for a few iterations and only for the writers and maybe one or two other players it seems. I would go towards a lean doc plan that’s throwaway after a few iterations.

Oh, and I have to laugh at myself while re-reading my post — apparently it’s more “Agile” to use lowercase for the initial word in a numbered list since I did that style for my second list. Ah, quick posting is fun. And you know, I’m not going to change it now. :)

]]> By: Michele Marques http://justwriteclick.com/2007/08/04/what-makes-a-doc-plan-agile/comment-page-1/#comment-52 Michele Marques Sat, 04 Aug 2007 23:58:26 +0000 http://justwriteclick.com/2007/08/04/what-makes-a-doc-plan-agile/#comment-52 Interesting post. I added my thoughts on documenting in an Agile environment in my blog (http://talk.bmc.com/blogs/blog-marques/michele-marques/). If you don't see the entry yet, check tomorrow. BTW, have you considered adding trackbacks to your blog? Interesting post. I added my thoughts on documenting in an Agile environment in my blog (http://talk.bmc.com/blogs/blog-marques/michele-marques/). If you don’t see the entry yet, check tomorrow.

BTW, have you considered adding trackbacks to your blog?

]]>