Lower Costs are based upon
- time saving when locating valid versions (documents, sources, etc.)
- time saving in the communication between project managers, developers and QA regarding open and done bug fixes and feature implementations
- time saving when locating changes/ bugs across different versions
- time saving due to tool supported parallel development (branching/ merging)
- time saving due to automation of standard processes, particularly builds and tests
- time saving due to prompt locating of bugs when running automated builds and tests
- time saving by avoiding proliferation of development trees
- time saving when reproducing releases an customer versions
- time saving by promptly detecting misguided development on the basis of metrics
- time saving by elimination of unnecessary iterations, e.g. ping-pong between development, software production, and QA
- ....
For the entire process the 80/20 rule is valid. That means 20 percent of CM problems cause 80 percent of the cumulative time loss. The other way round the elimination of the heaviest problems imply an immense gain of real productive time and a gain in motivation of the team members participating the development process.
