Issue Register Template

Document Sample
Issue Register Template Powered By Docstoc
					                                  PROGRAMME NAME



                    ISSUE REGISTER TEMPLATE

                                        Project Title



          Release Status: DRAFT, REVIEW, FOR INFORMATION or FINAL

                                    Author: Project Support


                                   Date: 13 September 2011


                              Filename & Version: Insert details


                                       Project ID: Insert ID

                                   Methodology: PRINCE2™ 2009




FMD Consultants Limited assumes no responsibility for the usage of any information contained in this
document and the way it is handled and disclaims all liability in respect of such information and its
provision. Subject to this disclaimer, you may copy and utilise the material contained in the document.

This information is based on OGC PRINCE2™ material. PRINCE2™ is a registered trade mark of the
Office of Government Commerce in the United Kingdom and other countries. All registered trademarks
recognised & accepted.
1 Document History
1.1 Location
This document is stored in the following location:

 Filename                  P2_issue_register_template_v01

 Location                  www.fmdconsultants.co.uk\web




1.2 Revision History
This document has been through the following revisions:

  Version       Revision        Filename/Location stored:           Brief Summary of Changes
    No.           Date

 01           13/09/11     P2_issue_register_template_v01     FINAL VERSION




1.3 Authorisation
This document requires the following approvals:

 AUTHORISATION                   Name                         Signature              Date
 Project Manager

 Project Assurance (reviewer)




1.4 Related Documents
Summary of filenames and locations of related documents:

 Document Type                    Filename/Location stored:

 Configuration     Management
 Strategy

 Issue Report




Project ID:                                                         Doc Ref:
                                           Page 2 of 5
BLANK TEMPLATE                                                      Date of Issue:
2 Contents

1     DOCUMENT HISTORY ................................................................................................ 2
    1.1       LOCATION ......................................................................................................................2
    1.2       REVISION HISTORY ..........................................................................................................2
    1.3       AUTHORISATION .............................................................................................................2
    1.4       RELATED DOCUMENTS .....................................................................................................2
2     CONTENTS ................................................................................................................ 3
3     OVERVIEW ............................................................................................................... 4
4     QUALITY CRITERIA .................................................................................................... 4




Project ID:                                                                                         Doc Ref:
                                                              Page 3 of 5
BLANK TEMPLATE                                                                                      Date of Issue:
3 Overview
An Issue Register captures and maintains 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.

The source of the issue data is the Issue Report which is submitted for those issues
which need to be managed formally.

Overleaf is an example which may be appropriate to a project.

An Issue Register can be:
    A document or spreadsheet or database designed specifically for a project
    A stand-alone issue register
    A record which is carried forwards in progress review minutes and presented at
       Project Board meetings
    An entry in a project management tool
    Part of an integrated Issue Register for company (or programme) wide management
       of risks, actions, decisions, assumptions, issues and project or programme lesson


The format, structure and mechanism for managing risks should be defined in the
Configuration Management Strategy, although for established organisations this CM
Strategy is usually clearly defined therefore needs only to be followed.

4 Quality Criteria
         The status of the risk indicates whether any action has been taken
         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 which are deemed to be risks are transferred to the
          Risk Register and the entries on the Issue Register annotated accordingly
         Access to the Issue Register is controlled and it is kept in a safe place




Project ID:                                                         Doc Ref:
                                           Page 4 of 5
BLANK TEMPLATE                                                      Date of Issue:
ISSUE REGISTER                                                       FORM [Form ID if applicable]
                                                                     Ref:    [Location/Filename]         Version:
Programme Name: [If applicable]                                      Project Name:


  Issue               Issue              Date          Raised        Author            Priority       Severity          Status          Closure
Identifier            Type              Raised           By                                                                               Date
 [Unique      [e.g. Request For        [Date        [Individual or   [Individual or    [In terms of   [In terms of   [Current status   [Date issue
reference     Change, Off-             issue        team who         team who          project’s      project’s      and date of       closed]
e.g. 0001]    specification, Problem   originally   raised the       created the       chosen         chosen         last update]
              or Concern]              raised]      issue]           issue report]     scale]         scale]
Issue Description
[A statement describing the issue, its cause and impact ]



  Issue               Issue              Date          Raised        Author            Priority       Severity          Status          Closure
Identifier            Type              Raised           By                                                                              Date
  [0002]
Issue Description



  Issue               Issue              Date          Raised        Author            Priority       Severity          Status          Closure
Identifier            Type              Raised           By                                                                              Date
  [0003]

Issue Description

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:70
posted:11/7/2012
language:Latin
pages:5