I did a presentation today on Story Test Driven Development (SDD) with a small start-up in NYC. The company comprises of just four programmers, but they seem to be very enthusiastic. They are proud of what they do and seem to be looking for continuous ways to improve. I got the standard question on SDD “How can you make sure that the story tests are exhaustive?”
Story Tests are examples of how the system should behave. Joshua calls it executable documentation. I like that term also. Jim Shore calls them executable specification. Brain Marick calls them examples.
Coming back to the question, how do we make sure that story tests are exhaustive. The answer is we do not, the customers do. If customers want to cover several scenarios related to the story, they can. If the iteration budget does not permit several scenarios to be covered, customers do not write them. They can add them in later iteration. Story tests are just an effective and efficient tool to help the customer steer the project more effectively.
Tags: No Comments
0 responses so far ↓
There are no comments yet...Kick things off by filling out the form below.