Its true, there is a cost associated with building quality into your applications, but there is also a cost associated with not having quality! If you sum up both cost functions you'll end up with the 'total cost of quality' as shown in the diagram below. As the graph clearly indicates, both ends of the spectrum - no quality or too much quality - are undesirable.
The goal must be to work towards a sweet spot where costs balance each other out.
PingBack from http://blog.a-foton.ru/index.php/2009/03/23/the-cost-of-having-or-not-having-quality-in-your-software/
Visual Studio Magazine   on Inside VSTS: Inside the TFS Databases, Part 2 Jakob Ehn on How To: automatically