Difference between revisions of "Issue Report Template"

From PRINCE2 wiki
Jump to: navigation, search
(Issue Report Template)
(Issue Report Template)
Line 44: Line 44:
 
| style="width: 360pt;" |  
 
| style="width: 360pt;" |  
 
|-
 
|-
| style="height: 100px; width: 240pt;" | Issue Description<ref>A statement describing the issue in terms of its cause and impact</ref>
+
| style="width: 240pt;" | Issue Description<ref>A statement describing the issue in terms of its cause and impact</ref>
| style="height: 100px; width: 360pt;" | &nbsp;
+
| style="width: 360pt;" | &nbsp;
 
|-
 
|-
 
|}
 
|}

Revision as of 04:16, 9 December 2015

Purpose

An Issue Report is a report containing the description, impact assessment and recommendations for a request for change, off-specification or a problem/concern. It is only created for those issues that need to be handled formally. The report is initially created when capturing the issue, and updated both after the issue has been examined and when proposals are identified for issue resolution. The Issue Report is later amended further in order to record what option was decided upon, and finally updated when the implementation has been verified and the issue is closed.


Note: this is a default template format, please check with the Configuration Management Strategy for precise format and composition requirements

Advice The Issue Report is derived from the: Highlight Report(s), Checkpoint Report(s) and End Stage Report(s); Stage Plan together with actual values and events; Users and supplier teams working on the project; The application of quality controls; Observation and experience of the processes; Quality Register, Risk Register and Lessons Log; and Completed Work Packages.

The Issue Report can take a number of formats, including: Document, spreadsheet or database; Entry in a project management tool.

Not all entries in the Issue Register will need a separately documented Issue Report.

The following quality criteria should be observed:

  • The issue stated is clear and unambiguous
  • A detailed impact analysis has occurred
  • All implications have been considered
  • The issue has been examined for its effect on the tolerances
  • The issue has been correctly registered on the Issue Register
  • Decisions are accurately and unambiguously described.



Issue Report Template

Issue ID[1]   Issue Type[2]  
Date raised[3]   Raised by[4]  
Issue Report Author[5]  
Issue Description[6]  
  1. As shown in the Issue Register (provides the unique reference for every Issue Report)
  2. Defines the type of Issue being recorded, namely: request for change; off-specification or problem/concern
  3. As shown in the Issue Register (provides the unique reference for every Issue Report)
  4. The name of the individual or team who raised the issue
  5. The name of the individual or team who created the Issue Report
  6. A statement describing the issue in terms of its cause and impact