This article is from the Configuration Management Tools FAQ, by Dave Eaton dwe@arde.com with numerous contributions by others.
This is a very controversial topic and many good discussions have
been held in this newsgroup. Some frequently voiced ideas include:
* CM is a "Good Thing".
* CM is intended to help developers.
* Integrating CM into a development environment should be
"evolutionary", and not "revolutionary". It takes time and
iterations to do it right.
* Develop a proven, bulletproof implementation of an integrated
CM/Development process, then apply it from day one on new project.
* Automation of a good CM process improves the likelyhood it will be
followed and can improve productivity and quality.
* Automation of a bad CM process can be worse than no automation.
Chances for success may be improved if you first establish a
process on which both the CM and development staff can agree.
Consider the capabilities of the tool you will use and automate the
process in a non-intrusive manner as much as possible. Process is
very site specific.
 
Continue to: