Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account? Log In

PRINCE2 (TM) Configuration Management Strategy by Mind Map: PRINCE2 (TM) Configuration
Management Strategy
0.0 stars - 0 reviews range from 0 to 5

PRINCE2 (TM) Configuration Management Strategy

Document information

Project Name

[name]

Date

[date]

Release

Draft/Final

Author

[author]

Owner

[owner]

Client

[client]

Document Number

[number]

Revision, Approvals & Distribution

Revision History, Revision # [....], Revision Date, [date], Previous Revision Date, [date], Summary of Changes, [change], Changes Marked, [change mark], Revision # [....], Revision Date, [date], Previous Revision Date, [date], Summary of Changes, [change], Changes Marked, [change mark], Revision # [....], Revision Date, [date], Previous Revision Date, [date], Summary of Changes, [change], Changes Marked, [change mark], Date of next revision:, [....]

Approvals, Approval # [....], Name, [name], Signature, [signature], Title, [title], Date of Issue, [date], Version, [version], Approval # [....], Name, [name], Signature, [signature], Title, [title], Date of Issue, [date], Version, [version], Approval # [....], Name, [name], Signature, [signature], Title, [title], Date of Issue, [date], Version, [version]

Distribution, Distribution # [....], Name, [name], Title, [title], Date of issue, [date], Version, [version], Distribution # [....], Name, [name], Title, [title], Date of issue, [date], Version, [version]

Overview

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.

Contents

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

Advice

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.

Records

Definition of the composition and format of the Issue Register and Configuration Item Records

[Definition of the composition and format of the Issue Register and Configuration Item Records]

Introduction

States the purpose, objectives and scope, and identifies who is responsible for the strategy

[State the purpose, objectives and scope, and identify who is responsible for the strategy]

How to use this template

How to share this template with your team

Send an email, 1. Click Share this map, 2. Select Invite People, 3. Write a message, 4. Click Invite

Send a link, 1. Click Share this map, 2. Tick Link to share, 3. Copy the link to share it

Export, 1. Click down arrow, bottom right, 2. Select the export option you want

How to complete this template

Complete the sections in square brackets, [....]

Read these sections for help on the PID, Purpose, Advice

Navigate using the links in Contents, Contents

Attribution

Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS

Get this template here

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.

[Describe 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

[Describe 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

[Refer to configuration management systems or tools to be used and document techniques that may be used for each step in the configuration management procedure]

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

[Describe 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

[State when formal activities are to be undertaken, for example configuration audits]

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.)

[Describe 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. Describe 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.

[Document what priority & severity scales will be used to prioritise change and off-specifications. Include what level of management will approve a certain priority or severity]