So what is this thing called SCM? Different versions of software components can be put together in different configurations, but what does the industry term "Software Configuration Management" mean? I like the Carnegie Mellon Software Engineering Institute's definition: "SCM can be defined as the discipline of controlling the evolution of software" (SEI technical report TR-CMU/SEI-90-TR-23). However, this definition is a bit ambiguous (therefore, threatening, to some) as to what exactly it means by "control".
Good SCM ensures that the particular configurations of software baselines and releases are well-identified and reproducible (can be recreated as originally built, or modified if desired). It can also contribute to change control and project planning functions by the information and process controls it provides. Developers, QA, product support and managers often see different sides of SCM.
See Resources for more info. You can also email me at cm@sarahelkins.org.