Software Change and Configuration Management (SCCM)
Software Change and Configuration Management (SCCM) is the set of tools and processes used in software development and IT operations to track, test, and control changes to software. Learn how it works, how it relates to change management, and why it matters for stability and security.
What is Software Change and Configuration Management (SCCM)?
Software Change and Configuration Management (SCCM) is the discipline of controlling how software and its configuration evolve. It makes sure every change is identified, recorded, reviewed, tested, and approved before it reaches production, and that teams always know which version of each component is running where. It combines version control, change control, build and release management, and configuration tracking.
How does SCCM work?
- Identify configuration items: source code, libraries, configuration files, infrastructure definitions, and documentation that must be controlled.
- Version control: store every item in a system that records each change, who made it, and why.
- Change control: propose changes through requests or pull requests that are reviewed and approved.
- Build and test: integrate and test changes automatically before release.
- Release and deploy: promote approved versions through environments in a controlled way.
- Audit and status accounting: report which versions are deployed and confirm they match what was approved.
Note that the abbreviation SCCM is also widely used for Microsoft's System Center Configuration Manager, a product for managing Windows devices. This glossary entry refers to the broader practice.
SCCM vs. change management
IT change management governs whether and when a change to a service should happen, through approvals and scheduling. Software change and configuration management covers how the change is built, tracked, versioned, and deployed. The two work together.
Why does SCCM matter?
Uncontrolled changes are a common cause of outages and security problems. Tracking every change makes it possible to reproduce builds, roll back safely, and investigate incidents. It also protects the pipeline itself: access to source repositories, build systems, and deployment credentials should be limited and logged.
Frequently asked questions
What is Software Change and Configuration Management?
It is the tools and processes used in software development and IT operations to track, test, and control changes to software and its configuration.
Is this the same as Microsoft SCCM?
No. Microsoft's System Center Configuration Manager shares the abbreviation but is a specific product for managing Windows devices. This term refers to the general practice.
What is a configuration item?
A configuration item is any component placed under control, such as source code, a configuration file, or a server definition, whose versions are tracked.
Keep IT changes organized and traceable
Track activity with audit trails and logs on every session your team opens.
Related terms
IT Asset Management (ITAM)
IT asset management (ITAM) is the administration, often offered as a service, of software, hardware, and cloud resources to ensure compliance, monitor usage, maintain proper licensing, and support other IT functions, typically following the ISO/IEC 19770 family of standards.
Read now →Software
Software is the set of instructions, stored and executed by hardware, for running tasks on and operating a computer.
Read now →Incident
An incident is a disruptive event in a software or hardware system due to an operational failure or security compromise.
Read now →