PRINCE2 (TM) Project Brief

To get an editable copy of this template to use on your project go to

Get Started. It's Free
or sign up with your email address
Rocket clouds
PRINCE2 (TM) Project Brief by Mind Map: PRINCE2 (TM) Project Brief

1. Document information

1.1. Project Name

1.1.1. [name]

1.2. Date

1.2.1. [date]

1.3. Release

1.3.1. Draft/Final

1.4. Author

1.4.1. [author]

1.5. Owner

1.5.1. [owner]

1.6. Client

1.6.1. [client]

1.7. Document Number

1.7.1. [number]

1.8. Revision, Approvals & Distribution

1.8.1. Revision History Revision # [....] Revision Date Previous Revision Date Summary of Changes Changes Marked Revision # [....] Revision Date Previous Revision Date Summary of Changes Changes Marked Revision # [....] Revision Date Previous Revision Date Summary of Changes Changes Marked Date of next revision: [....]

1.8.2. Approvals Approval # [....] Name Signature Title Date of Issue Version Approval # [....] Name Signature Title Date of Issue Version Approval # [....] Name Signature Title Date of Issue Version

1.8.3. Distribution Distribution # [....] Name Title Date of issue Version Distribution # [....] Name Title Date of issue Version

2. Overview

2.1. Purpose

2.1.1. A Project Brief is used to provide a full and firm foundation for the initiation of the project and is created in the Starting up a Project process.

2.1.2. In the Initiating a Project process, the contents of the Project Brief are extended and refined in the Project Initiation Documentation, after which the Project Brief is no longer maintained.

2.2. Contents

2.2.1. The Project Brief should cover the following topics.

2.2.2. Project Definition

2.2.3. Outline Business Case

2.2.4. Project Product Description

2.2.5. Project Approach

2.2.6. Project Management Team Structure

2.2.7. Role Descriptions

2.2.8. References

2.3. Advice

2.3.1. The Project Brief is derived from: A project mandate supplied at the start of the project; Programme management - if the project is part of a programme, the Project Brief is likely to be supplied by the programme, and therefore it will not have to be derived from a project mandate; Discussions with corporate management regarding corporate strategy and any policies and standards that apply; Discussions with the Project Board and users if the project mandate is incomplete or if no project mandate is provided; Discussions with the operations and maintenance organization (if applicable); Discussion with the (potential) suppliers regarding specialist development lifecycles that could be used; Lessons Log.

2.3.2. A Project Brief can take a number of formats, including: Document or presentation slides; Entry in a project management tool.

2.3.3. The following quality criteria should be observed: It is brief because its purpose at this point is to provide a firm basis on which to initiate a project. It will later be refined and expanded as part of the Project Initiation Documentation The Project Brief accurately reflects the project mandate and the requirements of the business and the users The project approach considers a range of solutions, such as: bespoke or off-the-shelf; contracted out or developed in-house; designed from new or a modified existing product The project approach has been selected which maximizes the chance of achieving overall success for the project The project objectives, project approach and strategies are consistent with the organization’s corporate social responsibility directive The project objectives are Specific, Measurable, Achievable, Realistic and Time-bound (SMART).

3. Project Definition

3.1. Explaining what the project needs to achieve. It should include information on the sections given below

3.2. Background

3.2.1. [...]

3.3. Project objectives

3.3.1. [covering time, cost, quality,scope, risk and benefit performance goals]

3.4. Desired outcomes

3.4.1. [...]

3.5. Project scope and exclusions

3.5.1. [...]

3.6. Constraints and assumptions

3.6.1. [...]

3.7. The user(s) and any other known interested parties

3.7.1. [...]

3.8. Interfaces

3.8.1. [...]

4. Project Approach

4.1. [Define the choice of solution that will be used in the project to deliver the business option selected from the Business Case. Take into consideration the operational environment into which the solution must fit]

5. Outline Business Case

5.1. [Give the reasons why the project is needed and the business option selected. This will later be developed into a detailed Business Case during the Initiating a Project process]

6. Project Management Team Structure

6.1. [Add a chart showing who will be involved with the project]

7. Role Descriptions

7.1. [Provide the role descriptions for the project management team and any other key resources identified at this time]

8. How to use this template

8.1. How to share this template with your team

8.1.1. Send an email 1. Click Share this map 2. Select Invite People 3. Write a message 4. Click Invite

8.1.2. Send a link 1. Click Share this map 2. Tick Link to share 3. Copy the link to share it

8.1.3. Export 1. Click down arrow, bottom right 2. Select the export option you want

8.2. How to complete this template

8.2.1. Complete the sections in square brackets [....]

8.2.2. Read these sections for help on the template Purpose Advice

8.2.3. Navigate using the links in Contents Contents

8.3. Attribution

8.3.1. Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS

8.4. Get this template here

9. Project Product Description

9.1. [Include the customer’s quality expectations, user acceptance criteria, and operations and maintenance acceptance criteria]

10. References

10.1. [Provide references to any associated documents or products]