Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

PRINCE2 (TM) Project Brief by Mind Map: PRINCE2 (TM) Project
Brief
0.0 stars - 0 reviews range from 0 to 5

PRINCE2 (TM) Project Brief

Document information

Project Name

[name]

Date

[date]

Release

Draft/Final

Author

[author]

Owner

[owner]

Client

[client]

Document Number

[number]

Revision, Approvals & Distribution

Revision History, Revision # [....], Revision Date, [date], Previous Revision Date, [date], Summary of Changes, [change], Changes Marked, [change mark], Revision # [....], Revision Date, [date], Previous Revision Date, [date], Summary of Changes, [change], Changes Marked, [change mark], Revision # [....], Revision Date, [date], Previous Revision Date, [date], Summary of Changes, [change], Changes Marked, [change mark], Date of next revision:, [....]

Approvals, Approval # [....], Name, [name], Signature, [signature], Title, [title], Date of Issue, [date], Version, [version], Approval # [....], Name, [name], Signature, [signature], Title, [title], Date of Issue, [date], Version, [version], Approval # [....], Name, [name], Signature, [signature], Title, [title], Date of Issue, [date], Version, [version]

Distribution, Distribution # [....], Name, [name], Title, [title], Date of issue, [date], Version, [version], Distribution # [....], Name, [name], Title, [title], Date of issue, [date], Version, [version]

Overview

Purpose

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.

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.

Contents

The Project Brief should cover the following topics.

Project Definition

Outline Business Case

Project Product Description

Project Approach

Project Management Team Structure

Role Descriptions

References

Advice

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.

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

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).

Project Definition

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

Background

[...]

Project objectives

covering time, cost, quality,scope, risk and benefit performance goals

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

Desired outcomes

[...]

Project scope and exclusions

[...]

Constraints and assumptions

[...]

The user(s) and any other known interested parties

[...]

Interfaces

[...]

Project Approach

To define the choice of solution that will be used in the project to deliver the business option selected from the Business Case, taking into consideration the operational environment into which the solution must fit

[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]

Outline Business Case

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

[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]

Project Management Team Structure

A chart showing who will be involved with the project

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

Role Descriptions

For the project management team and any other key resources identified at this time

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

How to use this template

How to share this template with your team

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

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

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

How to complete this template

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

Read these sections for help on the template, Purpose, Advice

Navigate using the links in Contents, Contents

Attribution

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

Get this template here

Project Product Description

Including the customer’s quality expectations, user acceptance criteria, and operations and maintenance acceptance criteria

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

References

To any associated documents or products

[Provide references to any associated documents or products]