PRINCE2 (TM) Project Product Description

1. Project Quality

1.1. Acceptance Criteria

1.1.1. Acceptance Criterion

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

1.1.2. Project Level Quality Tolerance(s)

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

1.1.3. Acceptance Method

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

1.1.4. Acceptance Responsibilitie(s)

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

1.2. Acceptance Criteria

1.2.1. Acceptance Criterion

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

1.2.2. Project Level Quality Tolerance(s)

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

1.2.3. Acceptance Method

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

1.2.4. Acceptance Responsibilitie(s)

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

1.3. Acceptance Criteria

1.3.1. Acceptance Criterion

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

1.3.2. Project Level Quality Tolerance(s)

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

1.3.3. Acceptance Method

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

1.3.4. Acceptance Responsibilitie(s)

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

1.4. Acceptance Criteria

1.4.1. Acceptance Criterion

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

1.4.2. Project Level Quality Tolerance(s)

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

1.4.3. Acceptance Method

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

1.4.4. Acceptance Responsibilitie(s)

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

1.5. Acceptance Criteria

1.5.1. Acceptance Criterion

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

1.5.2. Project Level Quality Tolerance(s)

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

1.5.3. Acceptance Method

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

1.5.4. Acceptance Responsibilitie(s)

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

1.6. Acceptance Criteria

1.6.1. Acceptance Criterion

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

1.6.2. Project Level Quality Tolerance(s)

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

1.6.3. Acceptance Method

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

1.6.4. Acceptance Responsibilitie(s)

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

1.7. Acceptance Criteria

1.7.1. Acceptance Criterion

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

1.7.2. Project Level Quality Tolerance(s)

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

1.7.3. Acceptance Method

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

1.7.4. Acceptance Responsibilitie(s)

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

1.8. Acceptance Criteria

1.8.1. Acceptance Criterion

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

1.8.2. Project Level Quality Tolerance(s)

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

1.8.3. Acceptance Method

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

1.8.4. Acceptance Responsibilitie(s)

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

1.9. Acceptance Criteria

1.9.1. Acceptance Criterion

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

1.9.2. Project Level Quality Tolerance(s)

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

1.9.3. Acceptance Method

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

1.9.4. Acceptance Responsibilitie(s)

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

1.10. Acceptance Criteria

1.10.1. Acceptance Criterion

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

1.10.2. Project Level Quality Tolerance(s)

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

1.10.3. Acceptance Method

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

1.10.4. Acceptance Responsibilitie(s)

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

2. Title

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

3. Purpose

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

4. Composition

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

5. Derivation

5.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]

6. Development Skills Required

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

7. Customer’s Quality Expectations

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

8. Sign-up FREE to edit this map

9. Document information

9.1. Project Name

9.1.1. [name]

9.2. Date

9.2.1. [date]

9.3. Release

9.3.1. Draft/Final

9.4. Author

9.4.1. [author]

9.5. Owner

9.5.1. [owner]

9.6. Client

9.6.1. [client]

9.7. Document Number

9.7.1. [number]

9.8. Revision, Approvals & Distribution

9.8.1. Revision History

9.8.1.1. Revision # [....]

9.8.1.1.1. Revision Date

9.8.1.1.2. Previous Revision Date

9.8.1.1.3. Summary of Changes

9.8.1.1.4. Changes Marked

9.8.1.2. Revision # [....]

9.8.1.2.1. Revision Date

9.8.1.2.2. Previous Revision Date

9.8.1.2.3. Summary of Changes

9.8.1.2.4. Changes Marked

9.8.1.3. Revision # [....]

9.8.1.3.1. Revision Date

9.8.1.3.2. Previous Revision Date

9.8.1.3.3. Summary of Changes

9.8.1.3.4. Changes Marked

9.8.1.4. Date of next revision:

9.8.1.4.1. [....]

9.8.2. Approvals

9.8.2.1. Approval # [....]

9.8.2.1.1. Name

9.8.2.1.2. Signature

9.8.2.1.3. Title

9.8.2.1.4. Date of Issue

9.8.2.1.5. Version

9.8.2.2. Approval # [....]

9.8.2.2.1. Name

9.8.2.2.2. Signature

9.8.2.2.3. Title

9.8.2.2.4. Date of Issue

9.8.2.2.5. Version

9.8.2.3. Approval # [....]

9.8.2.3.1. Name

9.8.2.3.2. Signature

9.8.2.3.3. Title

9.8.2.3.4. Date of Issue

9.8.2.3.5. Version

9.8.3. Distribution

9.8.3.1. Distribution # [....]

9.8.3.1.1. Name

9.8.3.1.2. Title

9.8.3.1.3. Date of issue

9.8.3.1.4. Version

9.8.3.2. Distribution # [....]

9.8.3.2.1. Name

9.8.3.2.2. Title

9.8.3.2.3. Date of issue

9.8.3.2.4. Version

10. How to use this template

10.1. How to share this template with your team

10.1.1. Send an email

10.1.1.1. 1. Click Share this map

10.1.1.2. 2. Select Invite People

10.1.1.3. 3. Write a message

10.1.1.4. 4. Click Invite

10.1.2. Send a link

10.1.2.1. 1. Click Share this map

10.1.2.2. 2. Tick Link to share

10.1.2.3. 3. Copy the link to share it

10.1.3. Export

10.1.3.1. 1. Click down arrow, bottom right

10.1.3.2. 2. Select the export option you want

10.2. How to complete this template

10.2.1. Complete the sections in square brackets

10.2.1.1. [....]

10.2.2. Read these sections for help on this template

10.2.2.1. Purpose

10.2.2.2. Advice

10.2.3. Navigate using the links in Contents

10.2.3.1. Contents

10.3. Attribution

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

10.4. Get this template here

11. Overview

11.1. Purpose

11.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:

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

11.1.1.2. Define the customer’s quality expectations

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

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

11.2. Contents

11.2.1. A Product Description should cover the following topics.

11.2.2. Title

11.2.3. Purpose

11.2.4. Composition

11.2.5. Derivation

11.2.6. Development Skills Required

11.2.7. Customer’s Quality Expectations

11.2.8. Acceptance Criteria

11.2.9. Project Level Quality Tolerances

11.2.10. Acceptance Method

11.2.11. Acceptance Responsibilities

11.3. Advice

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

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

11.3.3. The following quality criteria should be observed:

11.3.3.1. The purpose is clear

11.3.3.2. The composition defines the complete scope of the project

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

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

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

11.3.3.5.1. o All criteria are measurable

11.3.3.5.2. o Each criterion is individually realistic

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

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

11.3.3.6. The quality expectations have considered:

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

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

11.3.3.6.3. o Any other standards that should be used

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