Software Configuration Management Checklist

Software Configuration Management - Basics

Software configuration management (SCM) is a task to track and control major and minor changes inside software product. It is a part of larger cross-disciplinary field of configuration management. The most extensive goal is to identify the configurations by controlling its items and baselines, configuration status accounting and auditing, building a management along with tools and teamwork.

Need for SCM Checklist

Although, we plan strategy or apply serious effort on any approach, there will be certain things which might remains uncovered. Project managers and configuration managers of software configuration management faces the similar challenges while planning and identifying process activities. In this context, the checklist idea provides a systematic methodology and enables a team to effectively cover all in-depth areas of SCM.

Some of the key-points which portray SCM in a correct way:

  • Orderly release and process implementation of new or updated software with organized documentation.
  • The approved changes must be applied to both new and existing software.
  • It is important to verify changes in software which comply with approved specifications.
  • Whatever the changes made in software, must be reflected and updated in project documentation with proper visibility of changes to the project manager.
  • After the changes, it is important to evaluate and communicate about the impact of changes.
  • It is also more important that the changes must be authorised or validate by the system administrator.
  • Be an expert to plan configuration management activities for prescribed project.
  • By using configuration management strategy, the complete project is extensively identified and properly controlled by the professionals.
  • There should a well-defined procedure to measure or determine the status of software configuration management.

Basically, Software Configuration Management has three different types of audits that must be performed for better implementation and accuracy of results:

  • Functional Configuration Audit:It may be defined as the evaluation of software product to carry out conformance with respect to completeness, performance metrics, functional characteristics and requirement specifications.
  • Physical Configuration Audit: It may be defined as the estimation of each configuration item to evaluate conformance of technical documentation.
  • In-progress SCM Audit: It is an ongoing evaluation which is processed by life cycle to provide management with SCM policies, processes and plans.

Best Practices

  • The version control is in the exact place; sometimes it is quite mandatory to store the entire configuration item in VCS.
  • The structuring of VCS should be managed properly according to guidelines. The team must take care of trunk, branches and tags. The structuring of database object must be in a right way.
  • Continuous integration is necessary to get rid of problems w.r.t. integration and schedule deployment in test environment.
  • When we talk about the size and repository of content, we must have to ensure that team do not store binaries or binary files.
  • Continuous integration is necessary to get rid of problems with respect to integration and schedule deployment in test environment.


Software Configuration Management Checklist derives a semantic procedure to manage and control everything w.r.t configuration within software product. A well-structured and pre-defined methodology executes every process in synchronized way, and represent expected outcome.