Project Brief Template

PROGRAMME NAME

PROJECT BRIEF

Project Title

Release Status: DRAFT, REVIEW, FOR INFORMATION or FINAL

Author: Insert Name

Date: 01 January 2016

Filename & Version: Insert details

Project ID: Insert ID

Methodology: PRINCE2™ 2009

FMD Consultants Limited assumes no responsibility for the usage of any information contained in this document and the way it is handled and disclaims all liability in respect of such information and its provision. Subject to this disclaimer, you may copy and utilise the material contained in the document.

This information is based on OGC PRINCE2™ material. PRINCE2™ is a registered trade mark of the Office of Government Commerce in the United Kingdom and other countries. All registered trademarks recognised & accepted. 1 Document History

1.1 Location This document is stored in the following location: Filename

Location

1.2 Revision History This document has been through the following revisions:

Version Revision Filename/Location Brief Summary of Changes No. Date stored:

1.3 Authorisation This document requires the following approvals:

AUTHORISATION Name Signature Date Executive

Senior User

Senior Supplier

1.4 Distribution This document has been distributed to:

Name Title Version Issued Date of Issue

2 1.5 Related Documents Summary of filenames and locations of related documents:

Document Type Filename/Location stored:

Project Mandate

Project Product Description

Outline Business Case

Project Management Team Role Descriptions

Lessons Log

Project ID:

Doc Ref: Project Brief Page 3 of 6

Date of Issue: 2 Contents

4 3 Purpose The objective of the Project Brief is to enable a controlled start to the project by ensuring that adequate information is documented to inform all necessary persons that a new project is underway. A Project Brief is a key document that gives a description of what the project is to do and is intended to achieve. It is effectively a Mini Project Identification Document. The purpose of the Project Brief is for the Project Manager to write a detailed foundation of the project, covering the project’s scope. This will then be submitted to and assessed by the Project Board. If the project is considered to be justifiable, the Project Board should authorise the initiation of the Project. When and if authorisation is received, the Project Manager should start preparing the Project Initiation Document (PID). The contents of the Project Brief will be extended and refined into the Project Initiation Document. 4 Project Definition

4.1 Background

4.2 Project Objectives

4.3 Outline Project Deliverables / Desired Outcomes

4.4 Scope and Exclusions

4.5 Constraints and assumptions

4.6 User Groups and Other Interested Parties

4.7 Project Tolerances

4.8 Interfaces 5 Outline Business Case 6 Project Product Description 7 Project Approach 8 Project Management Team Structure 9 Project Management Team Role Descriptions 10 Additional Role Descriptions 11 References

Project ID:

Doc Ref: Project Brief Page 5 of 6

Date of Issue: 6