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

Date

Release

Author

Owner

Client

Document Number

Revision, Approvals & Distribution

Overview

Purpose

Contents

Advice

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

How to complete this template

Attribution

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]