How do you prepare your projects?

[eluser]Daniel Moore[/eluser]
[quote author="Ñuño Martínez" date="1237396712"]This method is a simplified version of "Extreme Programming". I use it on my current job because I never have all the information about the project. That's not my fault. My boss never, never, never explains me everything I need, he always hides something. Once I've finished something he says "Oh, nice work! Now, add this new little feature that seems simple but actually it will ruin everything you've already done". I think it's the worst way but I can't do anything else. u_u"[/quote]

I hate that. That's why I quit my "job" and went freelance. Now, if a client tells me that, I can say, "Sounds great, but it's not in the contract we signed. I'll get back to you with a quote for the additional work involved in that."

I generally try to come up with a good flowchart ahead of time that I can present to the client, showing a representation of the functionality of the site. That way, if there are any misunderstandings, they are generally cleared up then. Also, when the client sees it laid out like that, they generally start coming up with their changes before you start to code, which is much easier on me, as it is easier to modify a flow chart than to change the guts of the coding. It's just good business sense.

I generally don't come up with a quote for a job until I have charted it, because it also helps me to avoid the pitfall of "I forgot I would have to do that there..." so I don't spend a lot of extra time coding something I left out to start with that I won't be compensated for. Also, once charted, it's easier to run it by the client as part of the signed contract of the function of the application.