Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Project Issues Register Template and Guide

Project Issues Register Template and Guide

Ratings: (0)|Views: 143 |Likes:
Published by hamed

More info:

Published by: hamed on Sep 29, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Project Issues Register 
Template & Guide
Version 1.2, April 2008 
This Guide is intended to be read in conjunction with the following template for the development of aProject Issues Register. As such, the Guide should be removed from the front of your final document. 
What is a Project Issues Register?
Issues Register 
records details of allthe issues identified at the beginning andduring the life of the project, the actiontaken to address each issue and thesubsequent results.It usually includes:
a unique number;
a description;
who raised the issue;
date reported;
the person or group who isresponsible for resolution;
status, usually open, or closed;
date resolved; and
how resolved (eg. included as actionin the project work plan and budget,documented in the
Risk Register 
, or closed).This Register should be maintainedthroughout the project and updatedregularly, as existing issues are closed asa result of successful actions and newissues added as they are identified.
Why would you develop a ProjectIssues Register?
Project Issues Register 
is developed to:
provide a useful tool for managingand addressing the issues identifiedbefore and during the project;
identify and document actions takento address the identified issues andtheir subsequent resolution;
provide the Project Sponsor, SteeringCommittee/senior management with adocumented framework from whichthe status of issues can be reported;
ensure the communication of issuesto key stakeholders; and
provide a mechanism for seeking andacting on feedback regarding projectissues to encourage the involvementof the key stakeholders.
When would you develop a ProjectIssues Register?
Issues Register 
should becreated at the start of the project.
The frequency of issues reporting willvary depending on the size of theproject.
With very small projects this mayconsist of fortnightly consideration of any issues that could affect progressand/or a meeting with the Senior Manager/Project Sponsor.
For larger projects the
forms an integral part of theproject, as information for theRegister is drawn from the projectmanagement processes in place for the project.
What you need before you start:
An agreed
Project Business Plan
Project Proposal 
Knowledge and understanding of theproject.
Knowledge and understanding of issues management and riskmanagement.
 What you will have when you arefinished:
A complete
Project Issues Register 
that isready for ongoing use and reporting of issue status to the Senior Manager,Project Sponsor or the SteeringCommittee, depending on the size of theproject.
How to use this template
The template consists of a simpletable that reflects the nature of theinformation that is to be addressed.
The completed
Issues Register 
should be brief and to the point, so itconveys quickly the essentialinformation.
The column for ‘Cross Refs’ isoptional; it can be used to crossreference related or dependantissues, activities in a project plan, or any other related document.A number of 
different text styles
havebeen used within the template, as follows:
Text in
blue italics
is intended toprovide a guide as to the kind of information that can be included in asection and to what types of projectsit might be applicable. It should bedeleted from the final document.
Text in normal font is intended asexamples.
Text enclosed in <angle brackets>is intended to be replaced bywhatever it is describing.
This document has been formattedfor duplex printing. If you intend toprint single sided, you may need todelete some page breaks.
ChecklistHave you remembered to remove
The versioning statement from thefront cover of your document?
This guide and checklist from thefront of your document?All
blue italic 
instructional text and<prescriptive text enclosed in anglebrackets> within the template?

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->