False Economies Part III
A false economy is an action that saves money at the beginning but which, over a longer period of time, results in more money being spent or wasted than being saved.
Another example we see over and over, is the project team that attempts to meet a planning milestone and make up its cumulative development schedule slippage by shortening the duration and scope of the testing phases. This is often a false economy, unless you have shortened the duration by applying some automation tools, not reducing the scope.
When testing is inadequate, bugs and problems get uncovered in production, when it is much harder, takes longer and more expensive to fix. If your schedule is under pressure, there are other ways to make up time that don’t include arbitrary reductions to test cycles. Thorough testing saves money in the long run because it puts rework where it belongs, in development, before rollout.