Project quality

Project quality is the degree to which a set of inherent characteristics of the project's deliverables, and the project processes, fulfil the requirements (PMBOK / ISO). Schwalbe defines quality as the totality of features and characteristics of a product or service that bear on its ability to satisfy stated or implied needs. Quality means "fitness for use" (Juran) and "conformance to requirements" (Crosby).

Aspects of project quality

1. Product quality: the deliverable meets functional and non-functional requirements.
2. Process quality: project management processes are effective and followed.
3. Customer satisfaction: expectations met or exceeded.

Dimensions (for IT products)

Relation to other constraints

Quality is linked to scope, time and cost: cutting time or budget without changing scope reduces quality.

Scope
 / \    Quality at centre of
Time-Cost   all constraints

Management of quality

Project quality management includes three processes: plan quality, perform quality assurance and control quality. Quality must be planned in, not inspected in; prevention is cheaper than correction.

Quality experts

Deming (14 points, PDCA), Juran (fitness for use), Crosby (zero defects, do it right first time), Ishikawa (fishbone), Taguchi.

Example: A hospital system with correct calculations, 99.9% uptime, easy interface and secure data is of high project quality.