re: Agile: Story Completion Problems

Tana — Tue, 20 Mar 2007 17:47:55 GMT

I was interested in this article because as a tech writer I face a similar problem as do testers in an Agile environment... my end-user documentation Stories and/or Tasks are usually not complete at the end of each iteration... so should the Dev group be able to "close" the story or not? Sounds like your team decided that the Story had to be customer-accepted before the story was considered done... but am I reading it correctly that your solution was to have developers help out QA, and add automation where necessary, and that's it? And did you dispense with the final week-long "release" iteration? So far, such a "hardening" iteration has been my only saviour... that and a patient Dev team who allow me to carry over Stories from previous iterations. We have decided that a story won't be complete until the doc tasks in it are done... but that does mean a lot of carry-overs, as you found.

thanks for any insight, and if your tech writer(s) has any inclination to correspond, I would be very interested.

tana

re: Agile: Story Completion Problems

Bill Caputo — Wed, 10 Mar 2004 23:56:00 GMT

Very interesting experience report Wayne. You should consider turning this into an article.

New Article: Agile: Story Completion Problems

TrackBack — Mon, 29 Dec 2003 23:01:00 GMT