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) Issue Register by Mind Map: PRINCE2 (TM) Issue
Register
0.0 stars - 0 reviews range from 0 to 5

PRINCE2 (TM) Issue Register

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], Distribution # [....], Name, [name], Title, [title], Date of issue, [date], Version, [version]

Overview

Purpose

The Purpose of the Issue Register is to capture and maintain information on all of the issues that are being formally managed. The Issue Register should be monitored by the Project Manager on a regular basis

Contents

Issue Register

Advice

Derivation:, The format and composition of the Issue Register will be defined in the Configuration Management Strategy, Entries are initially made on the Issue Register once a new issue has been raised, The Issue Register is updated as the issue is progressed. Once the issue has been resolved, the entry in the Issue Register is closed.

Format and Presentation:, An Issue Register can take a number of formats including:, Document, spreadsheet or database, Stand-alone register or a carry forward in progress review minutes, Entry in a project management tool

The following quality criteria apply:, The status indicates whether action has been taken, The issues are uniquely identified, including information about which product they refer to, A process is defined by which the Issue Register is to be updated, Entries on the Issue Register that, upon examination, are in fact risks, are transferred to the Risk Register and the entries annotated accordingly, Access to the Issue Register is controlled and the register is kept in a safe place.

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 this template, 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

Issue Register

Issue ID (1 - 10)

1, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

2, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

3, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

4, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

5, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

6, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

7, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

8, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

9, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

10, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

Issue ID (11 - 20

11, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

12, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

13, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

14, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

15, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

16, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

17, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

18, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

19, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

20, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

Issue ID (21 - 30)

21, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

22, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

23, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

24, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

25, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

26, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

27, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

28, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

29, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]

30, Issue Type (RFC, OS, P), [...], Date Raised, [...], Issue Report Author, [...], Description, [...], Priority, [...], Severity, [...], Status, [...], Date of last update, [...], Closure Date, [...]