Re: Unit Testing Non-Believer

From: Captain Jake (jake[nospam)
Date: 12/19/04 

Date: Sun, 19 Dec 2004 09:44:47 -0600

Ingvar Nilsen <telcontr@online-not-this-part-.no> wrote in message
<41c57960$1@newsgroups.borland.com>
> To look at it from the other extreme viewpoint, and according to this,
> you're application will never be finished! You'll have to put your foot
> down and say stop. And you have to do that on every iteration in any
> case. The user cannot pop in and interrupt you while you are doing
> sequence diagrams, doing tests, doing implementation, the user has to
> politely wait on the station until your train completes the circle.

Why? I have developed plenty of software where the user changed his mind
about the specs in the middle of an iteration. In fact, at any specific point
in time, any sufficiently large yet agile project will have several
iterations going on at the same time, staggered and not always synchronized,
so that if you told the user to wait until there was no iteration going on,
you'd be holding him off until the first beta. That's definitely not a recipe
for success. If the user was going to interrupt you it was because he wanted
to change something, which implies that at least one of your current
iterations is producing the wrong thing anyway. Why make him wait until you
are done doing something he doesn't want anyway? 

-- 
***Free Your Mind***
Posted with JSNewsreader-BETA 0.9.4.360