Overview
Acceptance Criteria
are the standards required to satisfy the Customer's quality expectations and gain the Customer's acceptance of the final product. The Customer's
Acceptance Criteria
are established in
SU4 Preparing a Project Brief
as part of the
Project Brief.
The reason for this early establishment of the Customer's quality expectations is that the level of quality could impact on both time, cost and the justification of the
Business Case.
The
Acceptance Criteria
will form the basis for the
Project Quality Plan
to be created in
IP Initiating a Project
and agreed upon by the Customer and Supplier before the project begins.
The
Acceptance Criteria
can be prioritised. Some criteria that should be considered include:
- Target dates
- Major functions
- Appearance
- Personnel level required to use the product
- Performance levels
- Capacity, accuracy and availability
- Reliability
- Repair times
- Development costs
- Running costs
- Security
- Ease of use
Tips
- Keep the Risk Log close by when establishing the Acceptance Criteria, risks are likely to become apparent
- In small projects the Project Brief and therefore Acceptance Criteria may be part of developing the PID
- If Programme Management exists the Acceptance Criteria could be supplied by them
- Ensure that each of the criteria is measurable and that the means of measuring the criteria is realistic and agreed.
Notes
- What must be done for the final product to be acceptable to the Customer
- If not provided by the programme it is created during SU Starting up a Project and agreed upon no later than IP Initiating a Project
- Includes:
- Target dates
- Major functions
- Personnel level required to use or operate the product
- Availability and accuracy
- Reliability
- Costs (development and running)
- Ease of use
- Security
- This document is derived from the Senior User, and quality expectations of the Customer.
Case studies and examples
Related links
| 
