From: Phlip <phlip2005@...>
Date: 2008-08-17T04:36:58+09:00
Subject: Re: BDD and TDD - What are they for?

David Masover wrote:

> I would say that such a project is very much in need of some requirements,
> even informal ones.

Here's a nice post by one Scott Ambler (who I suspect is down with BDD):

http://www.ddj.com/architect/204200877

He ran a survey comparing projects that called themselves "Agile" to those 
that called themselves "traditional".

One big difference between them is Agile uses "just in time requirements", 
while "traditional" uses "big requirements up front".

Scott then very politely tries to rationalize why the Agile projects claim a 
higher success rate - despite the survey also stated more folks called their 
own process "traditional". Put another way, the survey was about 
traditionalists decrying their own failures - but of course Scott is too 
polite to come right out and state that.

The point of TDD is to reduce the risk that your requirements are wrong. 
Rapidly delivering small increments of new features, every week, complete 
with literate test cases, helps keep your client "in the loop".

-- 
  Phlip