PRINCE2 (TM) Project Product Description

1. Sign-up FREE to edit this map

2. Document information

2.1. Project Name

2.1.1. [name]

2.2. Date

2.2.1. [date]

2.3. Release

2.3.1. Draft/Final

2.4. Author

2.4.1. [author]

2.5. Owner

2.5.1. [owner]

2.6. Client

2.6.1. [client]

2.7. Document Number

2.7.1. [number]

2.8. Revision, Approvals & Distribution

2.8.1. Revision History

2.8.1.1. Revision # [....]

2.8.1.1.1. Revision Date

2.8.1.1.2. Previous Revision Date

2.8.1.1.3. Summary of Changes

2.8.1.1.4. Changes Marked

2.8.1.2. Revision # [....]

2.8.1.2.1. Revision Date

2.8.1.2.2. Previous Revision Date

2.8.1.2.3. Summary of Changes

2.8.1.2.4. Changes Marked

2.8.1.3. Revision # [....]

2.8.1.3.1. Revision Date

2.8.1.3.2. Previous Revision Date

2.8.1.3.3. Summary of Changes

2.8.1.3.4. Changes Marked

2.8.1.4. Date of next revision:

2.8.1.4.1. [....]

2.8.2. Approvals

2.8.2.1. Approval # [....]

2.8.2.1.1. Name

2.8.2.1.2. Signature

2.8.2.1.3. Title

2.8.2.1.4. Date of Issue

2.8.2.1.5. Version

2.8.2.2. Approval # [....]

2.8.2.2.1. Name

2.8.2.2.2. Signature

2.8.2.2.3. Title

2.8.2.2.4. Date of Issue

2.8.2.2.5. Version

2.8.2.3. Approval # [....]

2.8.2.3.1. Name

2.8.2.3.2. Signature

2.8.2.3.3. Title

2.8.2.3.4. Date of Issue

2.8.2.3.5. Version

2.8.3. Distribution

2.8.3.1. Distribution # [....]

2.8.3.1.1. Name

2.8.3.1.2. Title

2.8.3.1.3. Date of issue

2.8.3.1.4. Version

2.8.3.2. Distribution # [....]

2.8.3.2.1. Name

2.8.3.2.2. Title

2.8.3.2.3. Date of issue

2.8.3.2.4. Version

3. Overview

3.1. Purpose

3.1.1. The Project Product Description is a special form of Product Description that defines what the project must deliver in order to gain acceptance. It is used to:

3.1.1.1. Gain agreement from the user on the project’s scope and requirements

3.1.1.2. Define the customer’s quality expectations

3.1.1.3. Define the acceptance criteria, method and responsibilities for the project.

3.1.2. The Product Description for the project product is created in the Starting up a Project process as part of the initial scoping activity, and is refined during the Initiating a Project process when creating the Project Plan. It is subject to formal change control and should be checked at stage boundaries (during Managing a Stage Boundary) to see if any changes are required. It is used by the Closing a Project process as part of the verification that the project has delivered what was expected of it, and that the acceptance criteria have been met.

3.2. Contents

3.2.1. A Product Description should cover the following topics.

3.2.2. Title

3.2.3. Purpose

3.2.4. Composition

3.2.5. Derivation

3.2.6. Development Skills Required

3.2.7. Customer’s Quality Expectations

3.2.8. Acceptance Criteria

3.2.9. Project Level Quality Tolerances

3.2.10. Acceptance Method

3.2.11. Acceptance Responsibilities

3.3. Advice

3.3.1. The Project Product Description is derived from the project mandate, discussions with the Senior User and Executive – possibly via scoping workshops and the request for proposal (if in a commercial customer/supplier environment).

3.3.2. A Product Description for the project product can take a number of formats, including: Document, presentation slides or mind map; or Entry in a project management tool.

3.3.3. The following quality criteria should be observed:

3.3.3.1. The purpose is clear

3.3.3.2. The composition defines the complete scope of the project

3.3.3.3. The acceptance criteria form the complete list against which the project will be assessed

3.3.3.4. The acceptance criteria address the requirements of all the key stakeholders (e.g. operations and maintenance)

3.3.3.5. The Project Product Description defines how the users and the operational and maintenance organizations will assess the acceptability of the finished product(s):

3.3.3.5.1. o All criteria are measurable

3.3.3.5.2. o Each criterion is individually realistic

3.3.3.5.3. o The criteria are realistic and consistent as a set. For example, high quality, early delivery and low cost may not go together

3.3.3.5.4. o All criteria can be proven within the project life (e.g. the maximum throughput of a water pump), or by proxy measures that provide reasonable indicators as to whether acceptance criteria will be achieved post-project (e.g. a water pump that complies with design and manufacturing standards of reliability)

3.3.3.6. The quality expectations have considered:

3.3.3.6.1. o The characteristics of the key quality requirements (e.g. fast/slow, large/small, national/global)

3.3.3.6.2. o The elements of the customer’s quality management system that should be used

3.3.3.6.3. o Any other standards that should be used

3.3.3.6.4. o The level of customer/staff satisfaction that should be achieved if surveyed.

4. How to use this template

4.1. How to share this template with your team

4.1.1. Send an email

4.1.1.1. 1. Click Share this map

4.1.1.2. 2. Select Invite People

4.1.1.3. 3. Write a message

4.1.1.4. 4. Click Invite

4.1.2. Send a link

4.1.2.1. 1. Click Share this map

4.1.2.2. 2. Tick Link to share

4.1.2.3. 3. Copy the link to share it

4.1.3. Export

4.1.3.1. 1. Click down arrow, bottom right

4.1.3.2. 2. Select the export option you want

4.2. How to complete this template

4.2.1. Complete the sections in square brackets

4.2.1.1. [....]

4.2.2. Read these sections for help on this template

4.2.2.1. Purpose

4.2.2.2. Advice

4.2.3. Navigate using the links in Contents

4.2.3.1. Contents

4.3. Attribution

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

4.4. Get this template here

5. Project Quality

5.1. Acceptance Criteria

5.1.1. Acceptance Criterion

5.1.1.1. [A criterion that the project's product must meet]

5.1.2. Project Level Quality Tolerance(s)

5.1.2.1. [The tolerance(s) that may apply to the acceptance criterion]

5.1.3. Acceptance Method

5.1.3.1. [State the method by which the criterion will be accepted]

5.1.4. Acceptance Responsibilitie(s)

5.1.4.1. [State who will be responsible for confirming acceptance]

5.2. Acceptance Criteria

5.2.1. Acceptance Criterion

5.2.1.1. [A criterion that the project's product must meet]

5.2.2. Project Level Quality Tolerance(s)

5.2.2.1. [The tolerance(s) that may apply to the acceptance criterion]

5.2.3. Acceptance Method

5.2.3.1. [State the method by which the criterion will be accepted]

5.2.4. Acceptance Responsibilitie(s)

5.2.4.1. [State who will be responsible for confirming acceptance]

5.3. Acceptance Criteria

5.3.1. Acceptance Criterion

5.3.1.1. [A criterion that the project's product must meet]

5.3.2. Project Level Quality Tolerance(s)

5.3.2.1. [The tolerance(s) that may apply to the acceptance criterion]

5.3.3. Acceptance Method

5.3.3.1. [State the method by which the criterion will be accepted]

5.3.4. Acceptance Responsibilitie(s)

5.3.4.1. [State who will be responsible for confirming acceptance]

5.4. Acceptance Criteria

5.4.1. Acceptance Criterion

5.4.1.1. [A criterion that the project's product must meet]

5.4.2. Project Level Quality Tolerance(s)

5.4.2.1. [The tolerance(s) that may apply to the acceptance criterion]

5.4.3. Acceptance Method

5.4.3.1. [State the method by which the criterion will be accepted]

5.4.4. Acceptance Responsibilitie(s)

5.4.4.1. [State who will be responsible for confirming acceptance]

5.5. Acceptance Criteria

5.5.1. Acceptance Criterion

5.5.1.1. [A criterion that the project's product must meet]

5.5.2. Project Level Quality Tolerance(s)

5.5.2.1. [The tolerance(s) that may apply to the acceptance criterion]

5.5.3. Acceptance Method

5.5.3.1. [State the method by which the criterion will be accepted]

5.5.4. Acceptance Responsibilitie(s)

5.5.4.1. [State who will be responsible for confirming acceptance]

5.6. Acceptance Criteria

5.6.1. Acceptance Criterion

5.6.1.1. [A criterion that the project's product must meet]

5.6.2. Project Level Quality Tolerance(s)

5.6.2.1. [The tolerance(s) that may apply to the acceptance criterion]

5.6.3. Acceptance Method

5.6.3.1. [State the method by which the criterion will be accepted]

5.6.4. Acceptance Responsibilitie(s)

5.6.4.1. [State who will be responsible for confirming acceptance]

5.7. Acceptance Criteria

5.7.1. Acceptance Criterion

5.7.1.1. [A criterion that the project's product must meet]

5.7.2. Project Level Quality Tolerance(s)

5.7.2.1. [The tolerance(s) that may apply to the acceptance criterion]

5.7.3. Acceptance Method

5.7.3.1. [State the method by which the criterion will be accepted]

5.7.4. Acceptance Responsibilitie(s)

5.7.4.1. [State who will be responsible for confirming acceptance]

5.8. Acceptance Criteria

5.8.1. Acceptance Criterion

5.8.1.1. [A criterion that the project's product must meet]

5.8.2. Project Level Quality Tolerance(s)

5.8.2.1. [The tolerance(s) that may apply to the acceptance criterion]

5.8.3. Acceptance Method

5.8.3.1. [State the method by which the criterion will be accepted]

5.8.4. Acceptance Responsibilitie(s)

5.8.4.1. [State who will be responsible for confirming acceptance]

5.9. Acceptance Criteria

5.9.1. Acceptance Criterion

5.9.1.1. [A criterion that the project's product must meet]

5.9.2. Project Level Quality Tolerance(s)

5.9.2.1. [The tolerance(s) that may apply to the acceptance criterion]

5.9.3. Acceptance Method

5.9.3.1. [State the method by which the criterion will be accepted]

5.9.4. Acceptance Responsibilitie(s)

5.9.4.1. [State who will be responsible for confirming acceptance]

5.10. Acceptance Criteria

5.10.1. Acceptance Criterion

5.10.1.1. [A criterion that the project's product must meet]

5.10.2. Project Level Quality Tolerance(s)

5.10.2.1. [The tolerance(s) that may apply to the acceptance criterion]

5.10.3. Acceptance Method

5.10.3.1. [State the method by which the criterion will be accepted]

5.10.4. Acceptance Responsibilitie(s)

5.10.4.1. [State who will be responsible for confirming acceptance]

6. Title

6.1. [Give the name by which the project is known]

7. Purpose

7.1. [Define the purpose that the project’s product will fulfil and who will use it. This is helpful in understanding the product’s functions, size, quality, complexity, robustness etc.)]

8. Composition

8.1. [Describe the major products to be delivered by the project]

9. Derivation

9.1. [List the source products from which this product is derived. Examples are: Existing products to be modified; design specifications; a feasibility report or project mandate]

10. Development Skills Required

10.1. [Give an indication of the skills required to develop the product, or a pointer to which area(s) should supply the development resources]

11. Customer’s Quality Expectations

11.1. [Describe the quality expected of the project’s product and the standards and processes that will need to be applied to achieve that quality. The quality expectations are captured in discussions with the customer. Where possible, expectations should be prioritized]