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 Product Description by Mind Map: PRINCE2 (TM) Project Product
Description
0.0 stars - 0 reviews range from 0 to 5

PRINCE2 (TM) Project Product Description

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

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:, Gain agreement from the user on the project’s scope and requirements, Define the customer’s quality expectations, Define the acceptance criteria, method and responsibilities for the project.

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.

Contents

A Product Description should cover the following topics.

Title

Purpose

Composition

Derivation

Development Skills Required

Customer’s Quality Expectations

Acceptance Criteria

Project Level Quality Tolerances

Acceptance Method

Acceptance Responsibilities

Advice

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

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.

The following quality criteria should be observed:, The purpose is clear, The composition defines the complete scope of the project, The acceptance criteria form the complete list against which the project will be assessed, The acceptance criteria address the requirements of all the key stakeholders (e.g. operations and maintenance), The Project Product Description defines how the users and the operational and maintenance organizations will assess the acceptability of the finished product(s):, o All criteria are measurable, o Each criterion is individually realistic, o The criteria are realistic and consistent as a set. For example, high quality, early delivery and low cost may not go together, 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), The quality expectations have considered:, o The characteristics of the key quality requirements (e.g. fast/slow, large/small, national/global), o The elements of the customer’s quality management system that should be used, o Any other standards that should be used, o The level of customer/staff satisfaction that should be achieved if surveyed.

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 this 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 Quality

Acceptance Criteria

A prioritized list of criteria that the project’s product must meet before the customer will accept it - i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance

Acceptance Criterion, [A criterion that the project's product must meet]

Project Level Quality Tolerance(s), [The tolerance(s) that may apply to the acceptance criterion]

Acceptance Method, [State the method by which the criterion will be accepted]

Acceptance Responsibilitie(s), [State who will be responsible for confirming acceptance]

Acceptance Criteria

A prioritized list of criteria that the project’s product must meet before the customer will accept it - i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance

Acceptance Criterion, [A criterion that the project's product must meet]

Project Level Quality Tolerance(s), [The tolerance(s) that may apply to the acceptance criterion]

Acceptance Method, [State the method by which the criterion will be accepted]

Acceptance Responsibilitie(s), [State who will be responsible for confirming acceptance]

Acceptance Criteria

A prioritized list of criteria that the project’s product must meet before the customer will accept it - i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance

Acceptance Criterion, [A criterion that the project's product must meet]

Project Level Quality Tolerance(s), [The tolerance(s) that may apply to the acceptance criterion]

Acceptance Method, [State the method by which the criterion will be accepted]

Acceptance Responsibilitie(s), [State who will be responsible for confirming acceptance]

Acceptance Criteria

A prioritized list of criteria that the project’s product must meet before the customer will accept it - i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance

Acceptance Criterion, [A criterion that the project's product must meet]

Project Level Quality Tolerance(s), [The tolerance(s) that may apply to the acceptance criterion]

Acceptance Method, [State the method by which the criterion will be accepted]

Acceptance Responsibilitie(s), [State who will be responsible for confirming acceptance]

Acceptance Criteria

A prioritized list of criteria that the project’s product must meet before the customer will accept it - i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance

Acceptance Criterion, [A criterion that the project's product must meet]

Project Level Quality Tolerance(s), [The tolerance(s) that may apply to the acceptance criterion]

Acceptance Method, [State the method by which the criterion will be accepted]

Acceptance Responsibilitie(s), [State who will be responsible for confirming acceptance]

Acceptance Criteria

A prioritized list of criteria that the project’s product must meet before the customer will accept it - i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance

Acceptance Criterion, [A criterion that the project's product must meet]

Project Level Quality Tolerance(s), [The tolerance(s) that may apply to the acceptance criterion]

Acceptance Method, [State the method by which the criterion will be accepted]

Acceptance Responsibilitie(s), [State who will be responsible for confirming acceptance]

Acceptance Criteria

A prioritized list of criteria that the project’s product must meet before the customer will accept it - i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance

Acceptance Criterion, [A criterion that the project's product must meet]

Project Level Quality Tolerance(s), [The tolerance(s) that may apply to the acceptance criterion]

Acceptance Method, [State the method by which the criterion will be accepted]

Acceptance Responsibilitie(s), [State who will be responsible for confirming acceptance]

Acceptance Criteria

A prioritized list of criteria that the project’s product must meet before the customer will accept it - i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance

Acceptance Criterion, [A criterion that the project's product must meet]

Project Level Quality Tolerance(s), [The tolerance(s) that may apply to the acceptance criterion]

Acceptance Method, [State the method by which the criterion will be accepted]

Acceptance Responsibilitie(s), [State who will be responsible for confirming acceptance]

Acceptance Criteria

A prioritized list of criteria that the project’s product must meet before the customer will accept it - i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance

Acceptance Criterion, [A criterion that the project's product must meet]

Project Level Quality Tolerance(s), [The tolerance(s) that may apply to the acceptance criterion]

Acceptance Method, [State the method by which the criterion will be accepted]

Acceptance Responsibilitie(s), [State who will be responsible for confirming acceptance]

Acceptance Criteria

A prioritized list of criteria that the project’s product must meet before the customer will accept it - i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance

Acceptance Criterion, [A criterion that the project's product must meet]

Project Level Quality Tolerance(s), [The tolerance(s) that may apply to the acceptance criterion]

Acceptance Method, [State the method by which the criterion will be accepted]

Acceptance Responsibilitie(s), [State who will be responsible for confirming acceptance]

Title

Name by which the project is known

[Give the name by which the project is known]

Purpose

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

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

Composition

Description of the major products to be delivered by the project

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

Derivation

What are the source products from which this product is derived? Examples are: Existing products to be modified; design specifications; a feasibility report or project mandate

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

Development Skills Required

An indication of the skills required to develop the product, or a pointer to which area(s) should supply the development resources

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

Customer’s Quality Expectations

A description of the quality expected of the project’s product and the standards and processes that will need to be applied to achieve that quality. They will impact on every part of the product development, and thus on time and cost. The quality expectations are captured in discussions with the customer. Where possible, expectations should be prioritized

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