In response to Jerrylaster - I found that article interesting too, but I don't think you can draw a direct line from the value a customer places on your software (e.g purchase price) to the productivity of the developers or the process you used to produce it. For example, if I took every shortcut and hack I could to ship a functionally equivalent product ahead of some other company that built the software in a flexible, patchable, scalable way, the customer might "value" my inferior process by buying the 1.0 but then wait forever for the 2.0 to come out because I've built an unmaintainable mess. I think I'm making an argument for considering the longevity of the endeavor before equating customer satisfaction with development productivity...