3 ms·
I think it would be wrong to focus on the number. The important piece of wisdom here is that bugs get more expensive, even exponentially more expensive, to fix
by mytailorisrich 5y ago
I think it would be wrong to focus on the number. The important piece of wisdom here is that bugs get more expensive, even exponentially more expensive, to fix the later they are found.
If you find a bug during unit testing while developing a feature you just fix it.
If the bug is found in integration tests it may pull more resources and people to process. Even more so if found during integration tests.
If found after release to customer it might get very, very expensive.
The takeaway is to find and fix bugs as early as possible.
If you want to put an actual number on how much more expensive, you indeed need to carry a study but that will probably vary with the field or type of products and may in the end not provide additional actionable insights. Especially, I think this is risk mitigation so one would want to consider the worst case and its likelihood and not only an average number. That's probably difficult to capture in a generic study and product teams will know best what applies to their specific product.
- ckastner 5y ago> I think it would be wrong to focus on the number. The important piece of wisdom here is that bugs get more expensive, even exponentially more expensive, to fix the later they are found. This is always how I interpreted it. It thought this was the obvious interpretation, since it's all but certain that no universally applicable number exists.
- TheOtherHobbes 5y agoThey don't though. Bugs have three costs. Immediate corporate costs, corporate restitution costs, and cost-to-fix. Immediate corporate costs are loss of customers, loss of sales, and loss of goodwill leading to future loss of customers/sales. Restitution costs are costs to repair reputational damage and make good on customer losses. This element can be zero or it can be billions, depending on the exact nature of the loss. Cost-to-fix can be trivial, or it can be months of work. Cost-to-fix is unrelated to corporate costs. There is absolutely no relationship of any kind between the ease with which a bug can be fixed in code/production and the amount of corporate loss it caused. There is a very rough relationship between age and cost-to-fix, but it's very approximate. If code is documented and maintained and there are no forgotten areas written by people who have left, age effects should be minor. If the code is an impenetrable ball of mouldy spaghetti written by people who are long gone without leaving docs, you're screwed.
- mytailorisrich 5y agoIt's not later as 'old', it's later in the production pipeline. If you fix a bug before production then you don't incur 'immediate corporate costs' and 'restitution costs' and the cost-to-fix is also lower the earlier in the pipeline the bug is found.