PRINCE2 Agile 2016
Previous Section   Next Section

A.6 Configuration management strategy

A.6.1 Purpose

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.

A.6.2 Composition

  • Introduction States the purpose, objectives and scope, and identifies who is responsible for the strategy
  • Configuration management procedure A description of (or reference to) the configuration management procedure to be used. Any variance from corporate or programme management standards should be highlighted, together with a justification for the variance. The procedure should cover activities such as planning, identification, control (including storage/retrieval, product security, handover procedures etc.), status accounting, and verification and audit
  • Issue and change control procedure A description (or reference to) the issue and change control procedures to be used. Any variance from corporate or programme management standards should be highlighted, together with a justification for the variance. The procedure should cover activities such as capturing, examining, proposing, deciding and implementing
  • Tools and techniques Refers to any configuration management systems or tools to be used and any preference for techniques that may be used for each step in the configuration management procedure
  • Records Definition of the composition and format of the issue register and configuration item records
  • Reporting Describes the composition and format of the reports that are to be produced (issue report, product status account), their purpose, timing and chosen recipients. This should include reviewing the performance of the procedures
  • Timing of configuration management and issue and change control activities States when formal activities (for example, configuration audits) are to be undertaken
  • Roles and responsibilities Describes who will be responsible for what aspects of the procedures, including any corporate or programme management roles involved with the configuration management of the project’s products. Describes whether a change authority and/or change budget will be established
  • Scales for priority and severity For prioritizing requests for change and off-specifications and for determining the level of management that can make decisions on severity of issue.
Previous Section   Next Section