Re: Re: Agile Baby Steps

I guess we are making this work because a) the QA folk are very close to 
the developers. Every story has a QA Buddy assigned and they work together 
from cradle to grave. Our QA folk are the best critics of the use cases. 
And b) the developer bears the bulk of the responsibility for updating the 
doc, and they don't get story credit until it's done. Of course it's always 
done late the day before the iteration hand-off to the customer meeting :-)

At 12:08 AM 6/12/03 +0000, you wrote:

>
> > BTW: How did the idea of someone turning stories into use cases work out?
> > My line is that if a story is a promise to have a conversation, the use
> > case is the record of the story. I think we're doing well with that. Our
> > formal testers and others rely heavily on the requirements in ReqPro that
> > we build up in the use cases, so I don't think we'll stop writing them any
> > time soon.
>
>It didn't work as well as I had hoped due to the QA guy eventually
>disconnecting from the team until we had our first fully functional 
>version.  His
>involvement during the Release Planning was helpful to him as he generated
>his Use Cases and we generated Stories.  But as he drifted away, our
>conversations with the Customer cleared up some misunderstandings and
>brought out some new Stories.  Now that he's finally testing, several of the
>Use Cases are out of date.
>
>--Dave


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Looking for the latest Free IT White Papers?
Visit SearchSecurity.com to access over 500 white papers.
Get instant access at SearchSecurity.com Today
http://us.click.yahoo.com/ayjvfD/QLNGAA/uitMAA/nhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/