Issue Register Template

From PRINCE2 wiki
Jump to: navigation, search

Download Issue Register Template

Click here to download


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


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
  • Part of an integrated project register for all risks, actions, decisions, assumptions, issues, lessons etc.

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.



Issue register

Issue ID[1] Issue Type (RFC, OS, P)[2] Date Raised[3] Raised By[4] Issue Report Author[5] Description[6] Priority[7] Severity[8] Status[9] Date of last update[10] Closure Date[11]
1                    
2                    
3                    
4                    
5                    
6                    
7                    
8                    
9                    
10                    
  1. Provides a unique reference for every issue entered into the Issue Register.
  2. Issue Type: Defines the type of issue being recorded, namely: Request for Change, Off-Specification, Problem/concern
  3. Date Raised: The date on which the issue was originally raised
  4. Raised By: The name of the individual or team who reaised the issue
  5. Issue Report Author: The name of the individual or team who created the Issue Report
  6. Description: A Statement describing the issue, its cause and impact
  7. Priority: This should be given in terms of the project's chosen categories. Priority should be re-evaluated after impact analysis
  8. Severity: This should be given in terms of the project's chosen scale. Severity will indicate what level of management is required to make a decision on the issue
  9. Status: The current status of the issue
  10. Date of last update: The date this issue was last updated
  11. Closure Date: The date the issue was closed