<Insert Project Name> Created on 8 May 2008

PRINCE2® - Acceptance Criteria

Project Name:
Date: Release: Draft/Final
Author:

Owner:

Client:

Document Number:

Note: This document is only valid on the day it was printed

The source of this document will be found in the Quality file

Revision History
Date of next revision:
Revision Date Previous Summary of Changes Changes
Revision Date Marked

Approvals
This document requires the following approvals. A signed copy should be placed in
the project files.
Name Signature Title Date of Issue Version

Distribution

This document has been distributed to:

Name Title Date of Issue Version

© Crown copyright 2008. Crown copyright material is reproduced with the permission of the Controller of HMSO and
the Queen’s Printer for Scotland
PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other
countries page 1 of 4
Acceptance Criteria <Insert Project Name> Created on 8 May 2008

Overview

Purpose A definition in measurable terms of the characteristics required of the final

product(s) for it/them to be acceptable to the customers and staff who will be
affected. In many cases, the Acceptance Criteria will be the same as the quality
criteria in the Product Description of the final product.

Note: This is not a stand-alone PRINCE2 management product, but its inclusion
may help in understanding what the content might be.

Contents Acceptance Criteria could cover, for example, the following topics. There may
be other unique criteria for a specific project or final product

Reference to meeting quality expectations................................................................................2

Target dates................................................................................................................................2
Major functions............................................................................................................................2
Appearance.................................................................................................................................3
Personnel level required to use/operate the product.................................................................3
Performance levels.....................................................................................................................3
Capacity......................................................................................................................................3
Accuracy.....................................................................................................................................3
Availability...................................................................................................................................3
Reliability.....................................................................................................................................3
Development cost.......................................................................................................................3
Running costs.............................................................................................................................3
Security.......................................................................................................................................3
Ease of use.................................................................................................................................3
Timings.......................................................................................................................................4
Advice The criteria are either provided by corporate or programme management, or
developed during Starting up a Project (SU) and are derived from The Senior
User and customer’s quality expectations.

For each topic there may be one or more criteria. Each criterion should
consider the following entries. ‘Current level’ shows what the situation is before
the project. ‘Acceptance level’ is what is acceptable at hand-over time. If the
customer and supplier agree that it is reasonable that the product might
undergo some tuning once in use in order to achieve the final desired level of
acceptability, the other entries may be used. Criteria must be realistic both
individually and as a group and if possible should be measurable.

Criteria

Reference to meeting quality expectations

Target dates

Major functions

© Crown copyright 2008. Crown copyright material is reproduced with the permission of the Controller of HMSO and
the Queen’s Printer for Scotland
PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other
countries page 2 of 4
Acceptance Criteria <Insert Project Name> Created on 8 May 2008

Appearance

Personnel level required to use/operate the product

Performance levels

Capacity

Accuracy

Availability

Reliability
(mean/maximum time to repair, mean time between failures)

Development cost

Running costs

Security

Ease of use

© Crown copyright 2008. Crown copyright material is reproduced with the permission of the Controller of HMSO and
the Queen’s Printer for Scotland
PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other
countries page 3 of 4
Acceptance Criteria <Insert Project Name> Created on 8 May 2008

Timings

© Crown copyright 2008. Crown copyright material is reproduced with the permission of the Controller of HMSO and
the Queen’s Printer for Scotland
PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other
countries page 4 of 4