As per my last entry about How to create a ATDD Ready Sprint Backlog in Scrum, I find Tests and Acceptance Tests a great way to clarify and discuss requirements.
Ron Jeffries has a nice entry about User Stories and their 3 aspects:
- “How can we confirm what we have discussed?”
- “How can we confirm that we have understood correctly and implemented correctly?”
At the beginning of the iteration, the customer communicates to the programmers what she wants, by telling them how she will confirm that they’ve done what is needed. She defines the acceptance tests that will be used to show that the story has been implemented correctly.
Ron suggests Acceptance Tests.
The confirmation, in terms of acceptance tests, is what keeps the Circle of Life turning.