That has been my experience also - and even when you THINK you’ve defined it well - misinterpretations are easy if you’re dealing with technology or language that the client is unfamiliar with!

“If requirement’s definition is an issue why does the project manager get the blame?”

It always happens. They should just get miracle workers and get 100% success. Still, on a more serious note, I agree with what John said.

Scope creep is another major hurdle. It’s funny you mention the written signoff, because I have faced the same issues. Getting the client to agree verbally and writing does takes some work.

Thanks for stopping by.

Now, having said that, here’s the true cause: As a free and independent consultant, it is MY job to help the client define the goals and to put them in writing. That way, whey they begin to shift a bit (and they often can) I can bring out the goals and go over them with the client. If we need to make adjustments, we can then re-adjust the entire project. But to let the goals either drift or start out blurry is dangerous.

Plus, I build in a series of checkpoints on each project. We do not go to step five until step four is approved…once again, in writing. (I’ve had clients who would give me a verbal, “looks good,” but when I asked for a signed signoff, they balked.)

Remember, it’s our job to help the client…for our sake and for his.

– JRIngrisano (The Freestyle Entrepreneur)