Title Page

  • Site conducted

  • Conducted on

  • Project / Software Name

  • Software Owner / SME / SCCC

  • Prepared by

  • Location


  • This checklist references to IEEE 828:2012 (IEEE Standard for Configuration
    Management in Systems and Software Engineering) as guidance on the adequacy of the Software Configuration Management Plan. Although the standards cover system and software configuration management, this checklist will focus on the software aspect.

  • (configuration items are, but not limited to, baselined requirements specifications, interface specifications, design specifications, code, code builds, build data, database-related items such as triggers, schema, and SQL script, test cases, and standards used to create such controlled items)

Software Configuration Management Planning and Setup Checklist

  • Has the Software Configuration Management Plan (SCMP) or equivalent been established?

  • Are there any other documents (eg. CMP) established that cover configuration management controls over the project development life cycles?

  • Have the configuration management environment and tools be installed and setup for the configuration management activities of the project / software?

  • Have the personnel tasked with configuration management activities been informed and trained adequately?

Software Configuration Identification and Control Checklist

  • Was a structure or hierarchy determined from the system architecture to the software component level? Were these configuration items identified in a model that is easily traceable (eg. a hierarchical family tree breakdown of system, hardware and software configuration items)?

  • Are all configuration items completely and accurately identified, described, uniquely named (tagged and versioned), and controlled in the appropriate repository?

  • Are the criteria for baselining and approving a configuration item defined and documented? (what constitutes to a baseline and who is required to formally approve the baseline status)

  • Are the configuration management procedures in place on how to retrieve and reproduce controlled items from the repository? (consideration of marking and labeling, tracking of controlled copies, projection of sensitive / security information)

  • Are the configuration management procedures in place to ensure that backup storage of project data / documentations are maintained to facilitate technical data recovery?

Software Configuration Change Control Checklist

  • Are the change control procedures in place to ensure all configuration items are controlled when performing the initiation of change requests, evaluation and approval of change requests by appropriate authorities?

  • Are approved change requests verified on the implementation, testing, and traceability? Are traceability documented?

  • Are disapproved change requests clearly stated of their disposition and recorded?

Software Configuration Status Accounting Checklist

  • Is the configuration management system in place to ensure that records and the ability to report on the configuration baselines associated with each configuration item can be retrieved at the point of time?

Software Configuration Audits Checklist

  • Are functional configuration audits planned and performed during the project development life cycle to assess the proper transition of functional requirements to the built product before the release to production environment?

  • Are physical configuration audits performed during the product development to assess whether the product is being properly assembled before releasing the product to production environment?

  • Are baseline configuration audits performed during the project development life cycle to asses the proper creation of baselines?

Release Management Checklist

  • Are the release management processes documented to ensure that the proper set of deliverables (including documentation and other required materials) are delivered to customer/user based on product requirements?

The templates available in our Public Library have been created by our customers and employees to help get you started using SafetyCulture's solutions. The templates are intended to be used as hypothetical examples only and should not be used as a substitute for professional advice. You should seek your own professional advice to determine if the use of a template is permissible in your workplace or jurisdiction. You should independently determine whether the template is suitable for your circumstances.