Professional Documents
Culture Documents
Project Issue
Project Name:
Date:
Author:
Release:
Draft/Final
Owner:
Client:
Document Number:
Note: This document is only valid on the day it was printed
The source of this document will be found in the Project file
Revision History
Date of next revision:
Revision Date
Previous
Revision Date
Summary of Changes
Changes
Marked
Approvals
This document requires the following approvals. A signed copy should be placed in the project files.
Name
Signature
Title
Date of Issue
Version
Distribution
This document has been distributed to:
Name
259140084.doc
Title
Date of Issue
Version
page 1 of 2
Project Issue
date:
Overview
Purpose
A generic term for any matter that has to be brought to the attention of the
project team and requires an answer. After receiving a unique reference
number, Project Issues are evaluated in terms of impact on the product, effort
and cost, risks, Project Plan and Business Case. The PM may make a decision
on what action to take or the Project Issue may be referred to the Project
Board. A Project Issue may have a negative impact on the project. Project
Issues include:
Requests for change
Off specification
Questions
Statements of concern
Contents
Advice
Anyone may submit a Project Issue. Typical sources are users and specialists
working on the project. Capturing Project Issues (CS3) deals with collating
Project Issues. They are often examined during Examining Project Issues
(CS4).
Ensure that the Project Issue has been correctly logged, that the
problem/requirement/opportunity is clear and that the implications have been
thought through.
Author:
Date:
Issue no:
Priority
Impact Analysis
Decision
259140084.doc
Decision Date:
page 2 of 2