Re: More on converting a team to XP/TDD ...

We took an approach like that.  We had already done Big Requirements 
Analysis with full use cases, but we were having trouble understanding 
exactly what would be delivered when.  So we extracted stories from the use 
cases and did a small number of discrete stories every week or two. That 
got customers, QA, developers, managers et al used to doing story-sized 
work.  Then it was a pretty easy jump to doing story planning, a little 
bigger jump to doing the use cases one story at a time instead of all up 
front. Going the whole route had a bigger impact on the customer. They have 
to answer analysis questions, determine success criteria, test and evaluate 
continuously instead of all up front.

At 07:23 PM 2/5/03 -0800, you wrote:
>So, what I'm introducing for this next feature we will
>be working on, is to have the QA team extract from the
>requirements document and translate it into user
>stories with the corresponding acceptance tests, in
>cooperation with the developers and "customer" (in
>this case marketing). This shouldn't be a big impact
>on the customer, but rather just a "we want to confirm
>this ... " conversation.



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/LIgTpC/vN2EAA/xGHJAA/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/