Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

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

Date

Release

Author

Owner

Client

Document Number

Revision, Approvals & Distribution

Overview

Purpose

Contents

Advice

How to use this template

How to share this template with your team

How to complete this template

Attribution

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

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]