Saving the Project Brief document under its own name

Transcription

1 HOW TO USE THIS TEMPLATE: Introduction The template reflects the steps set out in the PRINCE2 Method and is designed to prompt the Project Manager and help in the creation of the. The information for the will be found within the SU Process of the PRINCE2 Manual. There is also a Product Description for the at Appendix A of the PRINCE2 Manual. Loading the file This template has been produced using Microsoft Word 97. To use it, load up the file directly from the directory and starting from page 1 follow the prompts (in [...] brackets). Deleting the [...] text When the template is complete, the whole document can be printed and approved. Prior to printing, you should delete all [...] prompt text. Saving the document under its own name Save the document by selecting the SAVE AS command; this will avoid overwriting the standard template. You must specify your own Project Directory. Once your Document is completed check the document against the following Quality Criteria: Does the accurately reflect the Project Mandate? Does it form a firm basis on which to initiate a project (Initiating a Project (IP))? Does it indicate how the customer will assess the acceptability of the finished product(s)?

2

3 PROJECT DOCUMENTATION PROJECT BRIEF Project: Release: Date: PRINCE2 Author: Owner:

4 Client: Document Ref: Version No: Page 2

5 1 History 1.1 Document Location This document is only valid on the day it was printed. The source of the document will be found on the project's PC in location 1.2 Revision History Date of this revision: Date of Next revision: Revision date Previous revision date Summary of Changes First issue Changes marked 1.3 Approvals This document requires the following approvals. Signed approval forms are filed in the Management section of the project files. Name Signature Title Date of Issue Version 1.4 Distribution This document has been distributed to: Name Title Date of Issue Version Page 3

6 2 Table of Contents Page 1 History Document Location Revision History 1.3 Approvals 1.4 Distribution 2 Table of Contents 3 Purpose 4 Background 5 Project Definition 6 Outline Business Case 7 Customer s Quality Expectations 8 Acceptance Criteria 9 Any Known Risks Page 4

7 3 Purpose [To provide a full and firm foundation for the initiation of the project. The contents are extended and refined into the Project Initiation Document (PID), which is the working document for managing and directing the project. The is a key document in its own right. It is the basis of the PID, which gives the direction and scope of the project and forms the contract between the project management team and corporate or programme management. Any significant change to the material contained in the will thus need to be referred to corporate or programme management] 4 Background 5 Project Definition [This explains what the project needs to achieve. It will contain: Project objectives Project scope Outline project deliverables and/or desired outcomes Any exclusions Constraints interfaces] 6 Outline Business Case [Description of how this project supports business strategy, plans or programmes The reasons why the project is needed] 7 Customer s Quality Expectations 8 Acceptance Criteria 9 Any Known Risks Page 5