Abstract
Software configuration management (SCM) may seem like unreasonable overhead during software development, but when change requests start appearing on the manager's desk, discipline is required to maintain the integrity and consistency of project documentation and source components. This article gives advice and rigorous procedures on implementing SCM; project managers with small development groups and limited resources may assign critical SCM tasks to existing personnel to attain some of the benefits of SCM.