Not a sermon - just a misunderstanding. I *NEVER* allow a project to begin without a design phase. BUT that doesn't mean I don't have to fight the client every step through it because they feel it is unnecessary.

Also, many people on UT are employees - if their boss says "start coding, we'll worry about validation and final table structure later" they may have to choose between starting to code without a design and looking for a new job.

Barbara

>Hi Barbara ----
>
>I know this sounds like a "sermon on the mount" but you should never allow the client to determine the steps you feel comfortable with taking to arrive at a successful conclusion....After all: 1) If it fails it's your ass no matter how vociferously you claim it due to the lack of a design phase... 2) You don't tell the client how to build houses, sell insurance, et al? Why should he/she dictate your business processes? (I have found this to be the BEST defense).
>
>>
>>Even a pencil-and-paper design phase beats many clients' feeling that a design phase is unnecessary!