The customer’s quality expectations are a statement about the quality expected from the project product.
They are defined and agreed early in the Starting up a Project process.
The expectations are captured in discussions with the customer and then refined for inclusion in the Project Product Description.
To avoid misinterpretations and inaccurate assumptions about the project’s quality requirements, the customer’s quality expectations should cover:
The key quality requirements will drive the choice of solution and, in turn, influence the time, cost, scope, risk and benefit performance targets of the project.
The quality expectation for a water pump in a remote village is that it is robust enough to ‘last a lifetime’, whereas because the oil pump in a racing car needs to be as light as possible, it may only need to last the duration of one race.
The customer’s quality expectations are often expressed in broad terms as a means to gain common understanding of general quality requirements.
They are then used to identify more detailed acceptance criteria, which should be specific and precise.
Where possible, the customer’s quality expectations should be prioritized as they will be used as inputs to define quality tolerances for the project’s products.
The customer’s quality expectations should be reviewed at the end of each management stage in case any external factors have changed them.
PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.