The project result must fulfil a number of quality requirements. This also applies to the various intermediate products of the project. When managing a project, it is particularly important for quality requirements to be determined, agreed upon and recorded in writing during the definition phase. These requirements should never remain implicit. A clear list of requirements can be checked at the end of the implementation phase. This can allow the project team to prove that they have carried out the project according to specifications. Additional quality requirements may be specified for various tasks within the project. For example, a particular task can be carried out only by certified personnel.
Quality in project plans:
- Establish the desired quality of the project result and the intermediate products (this takes place primarily in the definition phase).
- Establish the desired quality of the carrying out of the various activities in the project.
Quality in progress monitoring:
- Test the (intermediate) results.
- Address any quality problems.
Quality in the project reporting:
- Confirm that the desired quality has been attained.
- Address any complaints (particularly in the follow-up phase).
Perfectionism impedes project management. A pragmatic attitude toward the quality levels of a project can be expressed as ‘Good enough is good’. Projects that strive to achieve the highest possible level of quality are often at great risk of never being completed.