logo for information-management-architect.com

Configuration Management Plan

Improve efficiency with David Bowman’s information management best practices for data warehouse configuration management plan

This site is designed for Information Technology professionals who need  to improve effectiveness and require guidance and direction to help teams consistently produce error free results.

It provides a checklist of information management guidelines for configuration management and a template that can help jump-start a project.
 
What is Configuration Management?

Configuration management is a set of processes and procedures required to ensure that all hardware and software components in production environments are clearly identified and are not modified without some authorized process.

Configuration management should apply to all software code, documentation, test results and other deliverables that are produced during a data warehouse or business intelligence project.

Why is Configuration Management Important?

Configuration management is a vital component of project planning and requires that standards or best practices be documented and communicated to all stakeholders

Configuration Management Guidelines

Management Roles

Should define software configuration management responsibilities.

Management Activities
  • Should specify the tools (hardware or software) necessary to perform the assigned activities on each project; and
  • Should define the criteria for updating the configuration management plan.
Configuration Identification
  • Should identify the project work products, how they will be controlled, where they will be stored and what tool will be used;
  • Should identify the naming and identification scheme that will be applied to all project work products;
  • Should describe the process that will be followed to baseline all work products;
  • Should identify how labels will be used to support code migration; and
  • Should identify how labels will be used to support concurrent code development and merging.
Managing Configuration Items
  • Should describe how software work products will be stored;
  • Should describe how code and data model repository access will be controlled; and
  • Should describe the plan to recover development work products in the event of failure.
Configuration Control
  • Should specify how change control for the software configuration management plan will be governed e.g. interface control should describe the process to control change to interface specifications;
  • Should describe the release planning and object migration plan i.e. how objects will be migrated thru each environment to production; and
  • Should describe the approach to control configuration items during the build phase.
Configuration Status Accounting

Should specify the configuration status accounting process.

Configuration Audits
  • Should describe the configuration item audit process;
  • Should describe how configuration audit reports will be distributed; and
  • Should describe any vendor or subcontractor work product audit process.
Metrics

Should define project software configuration management metric requirements.

Postmortem Activities
  • Should define the work product archival and retention process; and
  • Should define what configuration management data should be collected at project close.
Configuration Management Plan Template

Under Construction  

Summary...

Configuration management is a set of processes and procedures required to ensure that all hardware and software components in production environments are clearly identified and are not modified without some authorized process.

This site provided a checklist of information management guidelines for configuration management and a template that can help jump-start a project.