Configuration Management Strategy

A Configuration Management Strategy is used to identify how, and by whom, the project’s products will be controlled and protected. It answers the questions:

  • How and where the project’s products will be stored
  • What storage and retrieval security will be put in place
  • How the products and the various versions and variants of these will be identified
  • How changes to products will be controlled
  • Where responsibility for configuration management will lie.

The Configuration Management Strategy should cover the following topics.  

  • Introduction  
  • Configuration Management Procedure   
  • Issue and Change Control Procedure    
  • Tools and Techniques   
  • Records   
  • Reporting 
  • Timing of Configuration Management and Issue and Change Control Activities   
  • Roles and Responsibilities   
  • Scales for Priority and Severity

 

PRINCE2® Documents to download - PDF

PRINCE2® Documents to download - WORD

The Configuration Management Strategy is derived from the: The customer’s quality expectations; Corporate configuration management system (e.g. any configuration management software in use or mandated by the user);    Programme Quality Management Strategy and information management strategy (if applicable); The user’s quality management system; The supplier’s quality management system; Specific needs of the project’s product(s) and environment; Project management team structure (to identify those with configuration management responsibilities) and Facilitated workshops and informal discussions.

A Configuration Management Strategy can take a number of formats, including: Stand-alone document or a section in the Project Initiation Document; Entry in a project management tool.

 

The following quality criteria should be observed:

  • Responsibilities are clear and understood by both user and supplier
  • The key identifier for the project’s product(s) is defined
  • The method and circumstances of version control are clear
  • The strategy provides the Project Manager with all the product information required
  • The corporate or programme strategy for configuration management has been considered
  • The retrieval system will produce all required information in an accurate, timely and usable manner
  • The project files provide the information necessary for any audit requirements
  • The project files provide the historical records required to support any lessons
  • The chosen Configuration Management Strategy is appropriate for the size and nature of the project
  • Resources are in place to administer the chosen method of configuration management
  • The requirements of the operational group (or similar group to whom the project’s product will be transitioned) should be considered.

Creation, update and use

The Configuration Management Strategy is created in the Initiating a Project process and forms a part of PID. If necessary, it could be updated in a Managing a Stage Boundary process. It defines how the issues, changes and configuration are dealt with, in the project.

 

Comments

Sign up to make a comment.

Quick information

PRINCE2 Practitioner for PMP, IPMA

Owner of PMP certificates and IPMA certificates can now pass PRINCE2 Practitioner without passing Foundation certification.


We are PRINCE2 Professionals

We reached the highest certificate PRINCE2 progfessional. Our practical experience from managing PRINCE2 projects is widely used by the commercial companies.


Do you want to be Agile?

We expanded the portfolio of our training by Agile methodologies, such as Agile Management by APMG and SCRUM by SCRUMstudy.

>>>

News

PRINCE2 in Russia

We successfully expanded to the Russian market with PRINCE2 certification. Trainings. was organized by the Voronezh Institute of High Technologies (VIHT) and will continue on the other organizations.

PRINCE2 Foundation training in Russia