Cost reduction is based on
- time savings when locating valid versions (documents, sources, etc.)
- time savings in the communication between project managers, developers and QA regarding open and closed bug fixes and feature implementations
- time savings when locating changes/bugs across different versions
- time savings due to tool supported parallel development (branching/merging)
- time savings due to automation of standard processes, particularly builds and tests
- time savings due to prompt localization of bugs when running automated builds and tests
- time savings by avoiding proliferation of development trees
- time savings when reproducing releases and customer versions
- time savings by promptly detecting misguided development on the basis of metrics
- time savings by elimination of unnecessary iterations, e.g. ping-pong between development, software production, and QA
- ...
The 80/20 rule is valid for any given entire process, which means that 20 percent of CM problems cause 80 percent of the cumulative time loss. On the flipside, elimination of the worst CM problems implies an immense gain in real productive time and in motivation of the staff involved.
