>>For one of my client, I am presently working on a project where no specification is done. This is my first experience in this type of project.
>>
>>In the middle of the development, this has caused major reconstruction of several modules, discussion of several points we have discussed before, redesign of the same icons several times, several developers working on about the same thing and the list is long.
>>
>>I'm used to work with specifications as most of us are. When there is no specification coming from the client and when this is for a fix cost, I insist to receive specification or I do it and the client is charged for. However, in this case, it's on site and the consultants are paid by the hour and the client doesn't care about specification. So, if it takes 200 hours for something, the consultants are paid for 200 hours. Yes, it's true deadlines are blown away. There is no project management.
>>
>>I was wondering what kind of approach anyone of you who faced this situation before have taken.
>
>Working for a company as an employee and not as a consultant, I have to deal with this everyday. Granted this is a simplistic list but,
>
>1. You can quit.
>2. You can try your best to teach them the value of doing a spec of front.
> (Sometimes this is not possible)
>3. Take the money and do the best you can with what they give you.
> (This method requires you to turn your brain off when you leave the building
> are you will become so frustrated that you will revert to item #1)
>
>Jeff

Jeff, currently, I'm in the same position, but for #3, instead of #1, I revert to UT :)