Configuration Management

What

Configuration Management is the Process of keeping track of all of the interdependencies of all of the components of the project's Product Breakdown Structure (PBS).

Process Diagram

Configuration Management consists of the following major Procedures:

Why

If you do not keep track of all of the interdependencies, you will find:

1. Versions do not match.
   
   
2. Some components are missing at critical times.
   
   
3. People do not know what is in a particular release.
   
   
4. Programmers could be working on the wrong versions of source code.
   
   
5. Programs could be accessing data files created by mismatched other programs.
   
   
6. Defects that were repaired previously could crop up in subsequent releases (ie, they don't stay fixed).
   
   
7. Infrastructure mismatches could occur (eg, wrong version of system software and/or Development, Maintenance and Support Tools is used).

When and Where

This technique is used throughout the whole project lifecycle and is not limited to any specific project lifecycle phase.

How

Specific Configuration Management issues that need to be addressed include:

1. Hardware configuration
   
   
2. System software configuration
   
   
3. Application software configuration
   
   
4. Module version number
   
   
5. Module integration
   
   
6. Multiple Releases of the Application System being developed
   
   
7. Release numbering and management
   
   
8. Libraries
   
   
9. Version numbers of Development, Maintenance and Support Tools required
   
   
10. Different Releases in each of the different Systems Development Pipeline environments:
    • Development Environment
      
      
    • Integration Testing Environment
      
      
    • System Testing Environment
      
      
    • Training Environment
      
      
    • Production Environment
11. Demonstration configuration
    
    
12. Conference Room Piloting
    
    
13. System Interfaces
    
    
14. Customisations of the base software package
    
    
15. Defect Reports (tracking and what Release fixed in)
    
    
16. Change Request Forms (tracking and what Release implemented in)
    
    
17. Currency of data
    
    
18. Data base layout changes
    
    
19. Retrofitting emergency Defect Repairs into the Production Environment and replicating into all other Systems Development Pipeline environments
    
    
20. Record keeping:
    • Register of the number and location of all originals and copies of all:
      • Software
        
        
      • Hardware
        
        
      • Documentation
        
        
      • Serial numbers
        
        
      • Version numbers

      from external vendors.

    • What is loaded on each platform:
      • Central server
        
        
      • Client workstations
21. Procedures for releasing from one Systems Development Pipeline environment to another
    
    
22. Inter-team communications

All Project Team Member's Responsibilities

All project team members are expected to take a very strong and proactive approach to Configuration Management. Because of the integrated nature of the Application System, changes in one module can easily affect another module.

Every project team member is required to discuss with the Configuration Manager if there is an intent to do any of the following PRIOR TO DOING IT:

1. Install any new hardware
   
   
2. Change any existing hardware
   
   
3. Apply any field change orders to any existing hardware
   
   
4. Remove any hardware
   
   
5. Install any new system software
   
   
6. Install any new version of any system software
   
   
7. Apply any patches to any system software
   
   
8. Delete any system software
   
   
9. Install any new development tool
   
   
10. Install any new version of any development tool
    
    
11. Apply any patches to any development tool
    
    
12. Delete any development tool
    
    
13. Install any new telecommunications equipment
    
    
14. Change any existing telecommunications equipment
    
    
15. Apply any field change orders to any existing telecommunications equipment
    
    
16. Remove any telecommunications equipment
    
    
17. Change Requirements Traceability Verification Matrix (RTVM)
    
    
18. Place anything into the Integration Testing Environment
    
    
19. Place anything into the System Testing Environment
    
    
20. Place anything into the Training Environment
    
    
21. Place anything into the Production Environment
    
    
22. Create a new Systems Development Pipeline environment
    
    
23. Write any assembler source code
    
    
24. Develop anything which is dependant upon any specific hardware
    
    
25. Develop anything which is dependent upon any specific operating system
    
    
26. Develop anything which is dependent upon any specific Data Storage System
    
    
27. Develop anything which is dependent upon any specific WAN or LAN hardware or software
    
    
28. Develop anything which is dependent upon any specific development, maintenance or support tool
    
    
29. Make any changes to the legacy Application Systems after date XX/XX/XXXX
    
    
30. Make any change that will affect any project Key Performance Indicator (KPI)
    
    
31. Make any change that will affect any Application System Key Performance Indicator (KPI)
    
    
32. Make any Scope Change to the project
    
    
33. Review or implement any Change Request Form
    
    
34. Issue any User Documentation
    
    
35. Issue any Technical Documentation
    
    
36. Issue any Training Material

Discussions will focus on identification of all components and their impact on other components and other Development Teams as well as updating the Configuration Change Register and the Current Configuration Record to ensure that the new or changed component is installed in an orderly manner.

Scaling

Also See

Configuration Management is one of the significant Processes that exist throughout PMMentor (PMM). To print a "Handout Pack" on this Process, create and print a title page and then click on the "Print" button (to print this topic to act as a Table of Contents) and then click on each of the following topics in turn. When the topic is displayed, click on the "Print" button, then click on the "Back" button to return to this topic and choose the next topic to print.

Configuration Change Register

Configuration Manager

Current Configuration Record

Deliverables Register

Impact Assessment

Key Performance Indicators (KPI's)

Maintain High-Level Project Scope Definition

Product Breakdown Structure (PBS)

Release to Integration Testing Environment

Release to Production Environment

Release to System Testing Environment

Release to Training Environment

Requirements Management

Requirements Traceability Verification Matrix (RTVM)

Scope Change Management

Systems Integration (SI)