John,

>Listen, Write Code, Test, and Refactor....anything else is waste.

I've not read the entire article about this topic so correct me if i'm wrong...
I've got the feeling something is missing.

If the only communication you've with your client is listening, you're probably on the wrong way. Often clients themselves don't know what they want.

Sure they have a general idea of what the system must do, but they seldom give you an exact and correct implentation-plan. I've had many project where clients used to do something in one way, and expect a system to do the same. But if you think it could be better another way it is certainly worth a try to explain the other way and tell the client which advantages this leads to.

The chances are fairly good that the client will give you some valuable extra information which justifies the one way, or another third way.

Therefore I rather would replace the word 'listen' with 'interactive communication' or just communication.

My experience says that this kind of communication if a very good key to a succesfull implementation.

Just a thought....


Regards, Walter