>I like this alot. Until the user(s) "see" what is coming down the pike and actually work with a form, nothing in a spec written before seeing is accurate. I've seen too many spend too many hours updating something that shouldn't have been written in the first place because so many changes take place. Sure, there are benefits to an up-front spec as when signed off on, you can hold their feet to the money fire. But, if it's possible to be realistic with a client and inform them that no matter what is written, it's going to change so let's just quit wasting the time and let's see some screen action that the users can pound on.
>
>Just my .02 worth but I truly like the concept.
>
>Steve

Well... I read a little bit about this...

What I really like about it is... The user drives the scope.

What I reallt dislike about it is... The user drives the scope.

Some user will, as the text says, realize that 'implemented' is a very important feature and will be satisfied at some point in the process that they are ready to implement the system.

Then, there are the users who don't want the system, resent it, and will never be satisfied.

BOb