Tuesday, February 9, 2010

Understanding your client

Some day you may release software with too many bugs.

And your client may say something like "Whats going on man? Do you guys do code reviews?".

The normal reaction to this is to say that you always do code reviews. Then, you make sure that you have documentation to prove it.

But then the client doesn't care whether you do code reviews or not, as long as you deliver a good product. What he really wants to know is this -

  • Are you aware that the last release had a problem?
  • Do you know what caused the problem?
  • What are you doing about it?

No comments: