PRINCE2 (TM) Issue Register

To get an editable copy of this template to use on your project go to http://www.stakeholdermap.com/project-templates/prince-2-templates.html

Kom i Gang. Det er Gratis
eller tilmeld med din email adresse
Rocket clouds
PRINCE2 (TM) Issue Register af Mind Map: PRINCE2 (TM) Issue Register

1. Document information

1.1. Project Name

1.1.1. [name]

1.2. Date

1.2.1. [date]

1.3. Release

1.3.1. Draft/Final

1.4. Author

1.4.1. [author]

1.5. Owner

1.5.1. [owner]

1.6. Client

1.6.1. [client]

1.7. Document Number

1.7.1. [number]

1.8. Revision, Approvals & Distribution

1.8.1. Revision History

1.8.1.1. Revision # [....]

1.8.1.1.1. Revision Date

1.8.1.1.2. Previous Revision Date

1.8.1.1.3. Summary of Changes

1.8.1.1.4. Changes Marked

1.8.1.2. Revision # [....]

1.8.1.2.1. Revision Date

1.8.1.2.2. Previous Revision Date

1.8.1.2.3. Summary of Changes

1.8.1.2.4. Changes Marked

1.8.1.3. Revision # [....]

1.8.1.3.1. Revision Date

1.8.1.3.2. Previous Revision Date

1.8.1.3.3. Summary of Changes

1.8.1.3.4. Changes Marked

1.8.1.4. Date of next revision:

1.8.1.4.1. [....]

1.8.2. Approvals

1.8.2.1. Approval # [....]

1.8.2.1.1. Name

1.8.2.1.2. Signature

1.8.2.1.3. Title

1.8.2.1.4. Date of Issue

1.8.2.1.5. Version

1.8.2.2. Approval # [....]

1.8.2.2.1. Name

1.8.2.2.2. Signature

1.8.2.2.3. Title

1.8.2.2.4. Date of Issue

1.8.2.2.5. Version

1.8.2.3. Approval # [....]

1.8.2.3.1. Name

1.8.2.3.2. Signature

1.8.2.3.3. Title

1.8.2.3.4. Date of Issue

1.8.2.3.5. Version

1.8.3. Distribution

1.8.3.1. Distribution # [....]

1.8.3.1.1. Name

1.8.3.1.2. Title

1.8.3.1.3. Date of issue

1.8.3.1.4. Version

1.8.3.2. Distribution # [....]

1.8.3.2.1. Name

1.8.3.2.2. Title

1.8.3.2.3. Date of issue

1.8.3.2.4. Version

1.8.3.3. Distribution # [....]

1.8.3.3.1. Name

1.8.3.3.2. Title

1.8.3.3.3. Date of issue

1.8.3.3.4. Version

2. Overview

2.1. Purpose

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

2.2. Contents

2.2.1. Issue Register

2.3. Advice

2.3.1. Derivation:

2.3.1.1. The format and composition of the Issue Register will be defined in the Configuration Management Strategy

2.3.1.2. Entries are initially made on the Issue Register once a new issue has been raised

2.3.1.3. The Issue Register is updated as the issue is progressed. Once the issue has been resolved, the entry in the Issue Register is closed.

2.3.2. Format and Presentation:

2.3.2.1. An Issue Register can take a number of formats including:

2.3.2.2. Document, spreadsheet or database

2.3.2.3. Stand-alone register or a carry forward in progress review minutes

2.3.2.4. Entry in a project management tool

2.3.3. The following quality criteria apply:

2.3.3.1. The status indicates whether action has been taken

2.3.3.2. The issues are uniquely identified, including information about which product they refer to

2.3.3.3. A process is defined by which the Issue Register is to be updated

2.3.3.4. Entries on the Issue Register that, upon examination, are in fact risks, are transferred to the Risk Register and the entries annotated accordingly

2.3.3.5. Access to the Issue Register is controlled and the register is kept in a safe place.

3. How to use this template

3.1. How to share this template with your team

3.1.1. Send an email

3.1.1.1. 1. Click Share this map

3.1.1.2. 2. Select Invite People

3.1.1.3. 3. Write a message

3.1.1.4. 4. Click Invite

3.1.2. Send a link

3.1.2.1. 1. Click Share this map

3.1.2.2. 2. Tick Link to share

3.1.2.3. 3. Copy the link to share it

3.1.3. Export

3.1.3.1. 1. Click down arrow, bottom right

3.1.3.2. 2. Select the export option you want

3.2. How to complete this template

3.2.1. Complete the sections in square brackets

3.2.1.1. [....]

3.2.2. Read these sections for help on this template

3.2.2.1. Purpose

3.2.2.2. Advice

3.2.3. Navigate using the links in Contents

3.2.3.1. Contents

3.3. Attribution

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

3.4. Get this template here

4. Issue Register

4.1. Issue ID (1 - 10)

4.1.1. 1

4.1.1.1. Issue Type (RFC, OS, P)

4.1.1.1.1. [...]

4.1.1.2. Date Raised

4.1.1.2.1. [...]

4.1.1.3. Issue Report Author

4.1.1.3.1. [...]

4.1.1.4. Description

4.1.1.4.1. [...]

4.1.1.5. Priority

4.1.1.5.1. [...]

4.1.1.6. Severity

4.1.1.6.1. [...]

4.1.1.7. Status

4.1.1.7.1. [...]

4.1.1.8. Date of last update

4.1.1.8.1. [...]

4.1.1.9. Closure Date

4.1.1.9.1. [...]

4.1.2. 2

4.1.2.1. Issue Type (RFC, OS, P)

4.1.2.1.1. [...]

4.1.2.2. Date Raised

4.1.2.2.1. [...]

4.1.2.3. Issue Report Author

4.1.2.3.1. [...]

4.1.2.4. Description

4.1.2.4.1. [...]

4.1.2.5. Priority

4.1.2.5.1. [...]

4.1.2.6. Severity

4.1.2.6.1. [...]

4.1.2.7. Status

4.1.2.7.1. [...]

4.1.2.8. Date of last update

4.1.2.8.1. [...]

4.1.2.9. Closure Date

4.1.2.9.1. [...]

4.1.3. 3

4.1.3.1. Issue Type (RFC, OS, P)

4.1.3.1.1. [...]

4.1.3.2. Date Raised

4.1.3.2.1. [...]

4.1.3.3. Issue Report Author

4.1.3.3.1. [...]

4.1.3.4. Description

4.1.3.4.1. [...]

4.1.3.5. Priority

4.1.3.5.1. [...]

4.1.3.6. Severity

4.1.3.6.1. [...]

4.1.3.7. Status

4.1.3.7.1. [...]

4.1.3.8. Date of last update

4.1.3.8.1. [...]

4.1.3.9. Closure Date

4.1.3.9.1. [...]

4.1.4. 4

4.1.4.1. Issue Type (RFC, OS, P)

4.1.4.1.1. [...]

4.1.4.2. Date Raised

4.1.4.2.1. [...]

4.1.4.3. Issue Report Author

4.1.4.3.1. [...]

4.1.4.4. Description

4.1.4.4.1. [...]

4.1.4.5. Priority

4.1.4.5.1. [...]

4.1.4.6. Severity

4.1.4.6.1. [...]

4.1.4.7. Status

4.1.4.7.1. [...]

4.1.4.8. Date of last update

4.1.4.8.1. [...]

4.1.4.9. Closure Date

4.1.4.9.1. [...]

4.1.5. 5

4.1.5.1. Issue Type (RFC, OS, P)

4.1.5.1.1. [...]

4.1.5.2. Date Raised

4.1.5.2.1. [...]

4.1.5.3. Issue Report Author

4.1.5.3.1. [...]

4.1.5.4. Description

4.1.5.4.1. [...]

4.1.5.5. Priority

4.1.5.5.1. [...]

4.1.5.6. Severity

4.1.5.6.1. [...]

4.1.5.7. Status

4.1.5.7.1. [...]

4.1.5.8. Date of last update

4.1.5.8.1. [...]

4.1.5.9. Closure Date

4.1.5.9.1. [...]

4.1.6. 6

4.1.6.1. Issue Type (RFC, OS, P)

4.1.6.1.1. [...]

4.1.6.2. Date Raised

4.1.6.2.1. [...]

4.1.6.3. Issue Report Author

4.1.6.3.1. [...]

4.1.6.4. Description

4.1.6.4.1. [...]

4.1.6.5. Priority

4.1.6.5.1. [...]

4.1.6.6. Severity

4.1.6.6.1. [...]

4.1.6.7. Status

4.1.6.7.1. [...]

4.1.6.8. Date of last update

4.1.6.8.1. [...]

4.1.6.9. Closure Date

4.1.6.9.1. [...]

4.1.7. 7

4.1.7.1. Issue Type (RFC, OS, P)

4.1.7.1.1. [...]

4.1.7.2. Date Raised

4.1.7.2.1. [...]

4.1.7.3. Issue Report Author

4.1.7.3.1. [...]

4.1.7.4. Description

4.1.7.4.1. [...]

4.1.7.5. Priority

4.1.7.5.1. [...]

4.1.7.6. Severity

4.1.7.6.1. [...]

4.1.7.7. Status

4.1.7.7.1. [...]

4.1.7.8. Date of last update

4.1.7.8.1. [...]

4.1.7.9. Closure Date

4.1.7.9.1. [...]

4.1.8. 8

4.1.8.1. Issue Type (RFC, OS, P)

4.1.8.1.1. [...]

4.1.8.2. Date Raised

4.1.8.2.1. [...]

4.1.8.3. Issue Report Author

4.1.8.3.1. [...]

4.1.8.4. Description

4.1.8.4.1. [...]

4.1.8.5. Priority

4.1.8.5.1. [...]

4.1.8.6. Severity

4.1.8.6.1. [...]

4.1.8.7. Status

4.1.8.7.1. [...]

4.1.8.8. Date of last update

4.1.8.8.1. [...]

4.1.8.9. Closure Date

4.1.8.9.1. [...]

4.1.9. 9

4.1.9.1. Issue Type (RFC, OS, P)

4.1.9.1.1. [...]

4.1.9.2. Date Raised

4.1.9.2.1. [...]

4.1.9.3. Issue Report Author

4.1.9.3.1. [...]

4.1.9.4. Description

4.1.9.4.1. [...]

4.1.9.5. Priority

4.1.9.5.1. [...]

4.1.9.6. Severity

4.1.9.6.1. [...]

4.1.9.7. Status

4.1.9.7.1. [...]

4.1.9.8. Date of last update

4.1.9.8.1. [...]

4.1.9.9. Closure Date

4.1.9.9.1. [...]

4.1.10. 10

4.1.10.1. Issue Type (RFC, OS, P)

4.1.10.1.1. [...]

4.1.10.2. Date Raised

4.1.10.2.1. [...]

4.1.10.3. Issue Report Author

4.1.10.3.1. [...]

4.1.10.4. Description

4.1.10.4.1. [...]

4.1.10.5. Priority

4.1.10.5.1. [...]

4.1.10.6. Severity

4.1.10.6.1. [...]

4.1.10.7. Status

4.1.10.7.1. [...]

4.1.10.8. Date of last update

4.1.10.8.1. [...]

4.1.10.9. Closure Date

4.1.10.9.1. [...]

4.2. Issue ID (11 - 20

4.2.1. 11

4.2.1.1. Issue Type (RFC, OS, P)

4.2.1.1.1. [...]

4.2.1.2. Date Raised

4.2.1.2.1. [...]

4.2.1.3. Issue Report Author

4.2.1.3.1. [...]

4.2.1.4. Description

4.2.1.4.1. [...]

4.2.1.5. Priority

4.2.1.5.1. [...]

4.2.1.6. Severity

4.2.1.6.1. [...]

4.2.1.7. Status

4.2.1.7.1. [...]

4.2.1.8. Date of last update

4.2.1.8.1. [...]

4.2.1.9. Closure Date

4.2.1.9.1. [...]

4.2.2. 12

4.2.2.1. Issue Type (RFC, OS, P)

4.2.2.1.1. [...]

4.2.2.2. Date Raised

4.2.2.2.1. [...]

4.2.2.3. Issue Report Author

4.2.2.3.1. [...]

4.2.2.4. Description

4.2.2.4.1. [...]

4.2.2.5. Priority

4.2.2.5.1. [...]

4.2.2.6. Severity

4.2.2.6.1. [...]

4.2.2.7. Status

4.2.2.7.1. [...]

4.2.2.8. Date of last update

4.2.2.8.1. [...]

4.2.2.9. Closure Date

4.2.2.9.1. [...]

4.2.3. 13

4.2.3.1. Issue Type (RFC, OS, P)

4.2.3.1.1. [...]

4.2.3.2. Date Raised

4.2.3.2.1. [...]

4.2.3.3. Issue Report Author

4.2.3.3.1. [...]

4.2.3.4. Description

4.2.3.4.1. [...]

4.2.3.5. Priority

4.2.3.5.1. [...]

4.2.3.6. Severity

4.2.3.6.1. [...]

4.2.3.7. Status

4.2.3.7.1. [...]

4.2.3.8. Date of last update

4.2.3.8.1. [...]

4.2.3.9. Closure Date

4.2.3.9.1. [...]

4.2.4. 14

4.2.4.1. Issue Type (RFC, OS, P)

4.2.4.1.1. [...]

4.2.4.2. Date Raised

4.2.4.2.1. [...]

4.2.4.3. Issue Report Author

4.2.4.3.1. [...]

4.2.4.4. Description

4.2.4.4.1. [...]

4.2.4.5. Priority

4.2.4.5.1. [...]

4.2.4.6. Severity

4.2.4.6.1. [...]

4.2.4.7. Status

4.2.4.7.1. [...]

4.2.4.8. Date of last update

4.2.4.8.1. [...]

4.2.4.9. Closure Date

4.2.4.9.1. [...]

4.2.5. 15

4.2.5.1. Issue Type (RFC, OS, P)

4.2.5.1.1. [...]

4.2.5.2. Date Raised

4.2.5.2.1. [...]

4.2.5.3. Issue Report Author

4.2.5.3.1. [...]

4.2.5.4. Description

4.2.5.4.1. [...]

4.2.5.5. Priority

4.2.5.5.1. [...]

4.2.5.6. Severity

4.2.5.6.1. [...]

4.2.5.7. Status

4.2.5.7.1. [...]

4.2.5.8. Date of last update

4.2.5.8.1. [...]

4.2.5.9. Closure Date

4.2.5.9.1. [...]

4.2.6. 16

4.2.6.1. Issue Type (RFC, OS, P)

4.2.6.1.1. [...]

4.2.6.2. Date Raised

4.2.6.2.1. [...]

4.2.6.3. Issue Report Author

4.2.6.3.1. [...]

4.2.6.4. Description

4.2.6.4.1. [...]

4.2.6.5. Priority

4.2.6.5.1. [...]

4.2.6.6. Severity

4.2.6.6.1. [...]

4.2.6.7. Status

4.2.6.7.1. [...]

4.2.6.8. Date of last update

4.2.6.8.1. [...]

4.2.6.9. Closure Date

4.2.6.9.1. [...]

4.2.7. 17

4.2.7.1. Issue Type (RFC, OS, P)

4.2.7.1.1. [...]

4.2.7.2. Date Raised

4.2.7.2.1. [...]

4.2.7.3. Issue Report Author

4.2.7.3.1. [...]

4.2.7.4. Description

4.2.7.4.1. [...]

4.2.7.5. Priority

4.2.7.5.1. [...]

4.2.7.6. Severity

4.2.7.6.1. [...]

4.2.7.7. Status

4.2.7.7.1. [...]

4.2.7.8. Date of last update

4.2.7.8.1. [...]

4.2.7.9. Closure Date

4.2.7.9.1. [...]

4.2.8. 18

4.2.8.1. Issue Type (RFC, OS, P)

4.2.8.1.1. [...]

4.2.8.2. Date Raised

4.2.8.2.1. [...]

4.2.8.3. Issue Report Author

4.2.8.3.1. [...]

4.2.8.4. Description

4.2.8.4.1. [...]

4.2.8.5. Priority

4.2.8.5.1. [...]

4.2.8.6. Severity

4.2.8.6.1. [...]

4.2.8.7. Status

4.2.8.7.1. [...]

4.2.8.8. Date of last update

4.2.8.8.1. [...]

4.2.8.9. Closure Date

4.2.8.9.1. [...]

4.2.9. 19

4.2.9.1. Issue Type (RFC, OS, P)

4.2.9.1.1. [...]

4.2.9.2. Date Raised

4.2.9.2.1. [...]

4.2.9.3. Issue Report Author

4.2.9.3.1. [...]

4.2.9.4. Description

4.2.9.4.1. [...]

4.2.9.5. Priority

4.2.9.5.1. [...]

4.2.9.6. Severity

4.2.9.6.1. [...]

4.2.9.7. Status

4.2.9.7.1. [...]

4.2.9.8. Date of last update

4.2.9.8.1. [...]

4.2.9.9. Closure Date

4.2.9.9.1. [...]

4.2.10. 20

4.2.10.1. Issue Type (RFC, OS, P)

4.2.10.1.1. [...]

4.2.10.2. Date Raised

4.2.10.2.1. [...]

4.2.10.3. Issue Report Author

4.2.10.3.1. [...]

4.2.10.4. Description

4.2.10.4.1. [...]

4.2.10.5. Priority

4.2.10.5.1. [...]

4.2.10.6. Severity

4.2.10.6.1. [...]

4.2.10.7. Status

4.2.10.7.1. [...]

4.2.10.8. Date of last update

4.2.10.8.1. [...]

4.2.10.9. Closure Date

4.2.10.9.1. [...]

4.3. Issue ID (21 - 30)

4.3.1. 21

4.3.1.1. Issue Type (RFC, OS, P)

4.3.1.1.1. [...]

4.3.1.2. Date Raised

4.3.1.2.1. [...]

4.3.1.3. Issue Report Author

4.3.1.3.1. [...]

4.3.1.4. Description

4.3.1.4.1. [...]

4.3.1.5. Priority

4.3.1.5.1. [...]

4.3.1.6. Severity

4.3.1.6.1. [...]

4.3.1.7. Status

4.3.1.7.1. [...]

4.3.1.8. Date of last update

4.3.1.8.1. [...]

4.3.1.9. Closure Date

4.3.1.9.1. [...]

4.3.2. 22

4.3.2.1. Issue Type (RFC, OS, P)

4.3.2.1.1. [...]

4.3.2.2. Date Raised

4.3.2.2.1. [...]

4.3.2.3. Issue Report Author

4.3.2.3.1. [...]

4.3.2.4. Description

4.3.2.4.1. [...]

4.3.2.5. Priority

4.3.2.5.1. [...]

4.3.2.6. Severity

4.3.2.6.1. [...]

4.3.2.7. Status

4.3.2.7.1. [...]

4.3.2.8. Date of last update

4.3.2.8.1. [...]

4.3.2.9. Closure Date

4.3.2.9.1. [...]

4.3.3. 23

4.3.3.1. Issue Type (RFC, OS, P)

4.3.3.1.1. [...]

4.3.3.2. Date Raised

4.3.3.2.1. [...]

4.3.3.3. Issue Report Author

4.3.3.3.1. [...]

4.3.3.4. Description

4.3.3.4.1. [...]

4.3.3.5. Priority

4.3.3.5.1. [...]

4.3.3.6. Severity

4.3.3.6.1. [...]

4.3.3.7. Status

4.3.3.7.1. [...]

4.3.3.8. Date of last update

4.3.3.8.1. [...]

4.3.3.9. Closure Date

4.3.3.9.1. [...]

4.3.4. 24

4.3.4.1. Issue Type (RFC, OS, P)

4.3.4.1.1. [...]

4.3.4.2. Date Raised

4.3.4.2.1. [...]

4.3.4.3. Issue Report Author

4.3.4.3.1. [...]

4.3.4.4. Description

4.3.4.4.1. [...]

4.3.4.5. Priority

4.3.4.5.1. [...]

4.3.4.6. Severity

4.3.4.6.1. [...]

4.3.4.7. Status

4.3.4.7.1. [...]

4.3.4.8. Date of last update

4.3.4.8.1. [...]

4.3.4.9. Closure Date

4.3.4.9.1. [...]

4.3.5. 25

4.3.5.1. Issue Type (RFC, OS, P)

4.3.5.1.1. [...]

4.3.5.2. Date Raised

4.3.5.2.1. [...]

4.3.5.3. Issue Report Author

4.3.5.3.1. [...]

4.3.5.4. Description

4.3.5.4.1. [...]

4.3.5.5. Priority

4.3.5.5.1. [...]

4.3.5.6. Severity

4.3.5.6.1. [...]

4.3.5.7. Status

4.3.5.7.1. [...]

4.3.5.8. Date of last update

4.3.5.8.1. [...]

4.3.5.9. Closure Date

4.3.5.9.1. [...]

4.3.6. 26

4.3.6.1. Issue Type (RFC, OS, P)

4.3.6.1.1. [...]

4.3.6.2. Date Raised

4.3.6.2.1. [...]

4.3.6.3. Issue Report Author

4.3.6.3.1. [...]

4.3.6.4. Description

4.3.6.4.1. [...]

4.3.6.5. Priority

4.3.6.5.1. [...]

4.3.6.6. Severity

4.3.6.6.1. [...]

4.3.6.7. Status

4.3.6.7.1. [...]

4.3.6.8. Date of last update

4.3.6.8.1. [...]

4.3.6.9. Closure Date

4.3.6.9.1. [...]

4.3.7. 27

4.3.7.1. Issue Type (RFC, OS, P)

4.3.7.1.1. [...]

4.3.7.2. Date Raised

4.3.7.2.1. [...]

4.3.7.3. Issue Report Author

4.3.7.3.1. [...]

4.3.7.4. Description

4.3.7.4.1. [...]

4.3.7.5. Priority

4.3.7.5.1. [...]

4.3.7.6. Severity

4.3.7.6.1. [...]

4.3.7.7. Status

4.3.7.7.1. [...]

4.3.7.8. Date of last update

4.3.7.8.1. [...]

4.3.7.9. Closure Date

4.3.7.9.1. [...]

4.3.8. 28

4.3.8.1. Issue Type (RFC, OS, P)

4.3.8.1.1. [...]

4.3.8.2. Date Raised

4.3.8.2.1. [...]

4.3.8.3. Issue Report Author

4.3.8.3.1. [...]

4.3.8.4. Description

4.3.8.4.1. [...]

4.3.8.5. Priority

4.3.8.5.1. [...]

4.3.8.6. Severity

4.3.8.6.1. [...]

4.3.8.7. Status

4.3.8.7.1. [...]

4.3.8.8. Date of last update

4.3.8.8.1. [...]

4.3.8.9. Closure Date

4.3.8.9.1. [...]

4.3.9. 29

4.3.9.1. Issue Type (RFC, OS, P)

4.3.9.1.1. [...]

4.3.9.2. Date Raised

4.3.9.2.1. [...]

4.3.9.3. Issue Report Author

4.3.9.3.1. [...]

4.3.9.4. Description

4.3.9.4.1. [...]

4.3.9.5. Priority

4.3.9.5.1. [...]

4.3.9.6. Severity

4.3.9.6.1. [...]

4.3.9.7. Status

4.3.9.7.1. [...]

4.3.9.8. Date of last update

4.3.9.8.1. [...]

4.3.9.9. Closure Date

4.3.9.9.1. [...]

4.3.10. 30

4.3.10.1. Issue Type (RFC, OS, P)

4.3.10.1.1. [...]

4.3.10.2. Date Raised

4.3.10.2.1. [...]

4.3.10.3. Issue Report Author

4.3.10.3.1. [...]

4.3.10.4. Description

4.3.10.4.1. [...]

4.3.10.5. Priority

4.3.10.5.1. [...]

4.3.10.6. Severity

4.3.10.6.1. [...]

4.3.10.7. Status

4.3.10.7.1. [...]

4.3.10.8. Date of last update

4.3.10.8.1. [...]

4.3.10.9. Closure Date

4.3.10.9.1. [...]