IssueReport-ManagementPlaza.doc

PRINCE2?- Issue Report Project Name: Date: Release: Draft/Final Author: Owner: Client: Document Number: Note: This document is only valid on the day it was printed 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 Title Date of Issue Version Overview 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. Contents The Issue Report should cover the following topics. Issue Report 3 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 fo