PRINCE2 Agile 2016
Previous Section   Next Section

A.19 Project brief

A.19.1 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.

A.19.2 Composition

  • Project definition Explaining what the project needs to achieve. It should include:
    • Background
    • Project objectives (covering time, cost, quality, scope, risk and benefit performance goals)
    • Desired outcomes
    • Project scope and exclusions
    • Constraints and assumptions
    • Project tolerances
    • The user(s) and any other known interested parties
    • Interfaces
  • Outline business case (see section A.2) 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 product description (see section A.21) Including the customer’s quality expectations, user acceptance criteria, and operations and maintenance acceptance criteria
  • Project approach To define the choice of solution that will be used within the project to deliver the business option selected from the business case, taking into consideration the operational environment into which the solution must fit
  • Project management team structure 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
  • References To any associated documents or products.
Previous Section   Next Section