Michael, the issue here is that the customers idea of 'didn't work properly' is open to interpretation. A television has a list of defined features, and these features are homogeneous across the same models.
Any custom development that is built to specifications has no comparison product, the specifications are as clear as the language used in the scoping document. Like 'system takes information about a user and stores in database', the actual system could be storing name and address but the client might assume far more information would be stored - like IP address, total orders made, number of times user logs in. In my experience, it is only when the client actually signs off on the application and starts using it in situ before they realise that their expectations were not met. The process of then meeting those expectations is a delicate process, but any reasonable client would understand that more development means more money to be paid. As for truly broken features, I would see these being fixed by the developer free of charge. Unit testing goes a long way to making sure broken code doesn't become a problem. Cheers, Stig Michael wrote, on 27/07/2009 9:36 AM: > If the product you supply is broken, fix it and stop making excuses or trying > to wriggle out. > > I am sure if you went and bought a TV set from Noel Leeming, and it didn't > work properly, you would not be in the mood to discuss service contracts and > who's responsibility it is. > -- Stig Manning http://www.sdm.co.nz --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
