Configuration Management Policy

EFFECTIVE DATE: December 17, 2008

APPROVED BY: Mike McCoy

LAST UPDATED: December 20, 2018

PURPOSE

The purpose of this policy is to ensure systems and software configuration is effectively managed within InnovaSystems International, LLC (ISI).

SCOPE OF THE POLICY

This policy defines standards for Configuration Management (CM) and is applicable to all ISI software development project teams developing software business solutions and services.

APPLICABILITY

Responsibility for CM shall be divided among multiple Roles. Project Leads must ensure the team is adhering to this Policy. The organizational set of standard process CM processes will address the Roles involved and their level of participation.

AUTHORITY AND COMPLIANCE

This policy is authorized by the Chief Operating Officer (COO). Compliance to this policy is evaluated through an appraisal/audit process. Results will be provided to the appropriate personnel and non-compliance/issues will be submitted to the Business Unit Leads and the Executive team for remediation.

POLICY STATEMENT

This policy is intended to establish configuration management practices across the organization. When utilized successfully, configuration management will allow for controlling and tracking changes to work products (e.g., software code, documentation, etc.) throughout their lifecycle.

This policy declares the necessary infrastructure needed to allow the adoption of configuration management practices and mindsets. The items listed below are intended to pave the path toward successful configuration management implementation.

Configuration Management activities shall:

  1. Define a set of processes to establish structure and expectations for the execution of configuration management activities.
  2. Develop a configuration management system (CMS) for storage, tracking, and management of configuration items, in alignment with the ISI Application Lifecycle Maintenance Tool Policy.
  3. Establish a project-level configuration management plan that declares version control branching strategy, methods for ensuring the specific configuration items are present in environments under configuration control.
  4. Establish a project-level change control authority.
  5. Identify project-level configuration items.
  6. Perform configuration audits to maintain integrity to configuration items.

Process Guidance Version: 10.4