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

Sandy 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. 
>  
>
We do something like this - it is a good way of breaking in project 
managers!

Rather than produce a big requirements doc up front we start with a list 
of documents to be written (short specs, one per feature).  When we 
implement a story, we fill out the document with the help of the 
testers.  They (along with our marketing "customer") write the detail 
and the acceptance tests and we do the code.  The document is refactored 
along with the code.  Once the acceptance tests pass, the document is 
issued.

So the PMs get their much loved requirements specification, but on our 
terms.

Now if we could find a way of locking the doc to the tests, it might 
even be of some use..

Ian



------------------------ 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/