11.1 Quality Definitions, Management, and Quality Planning

11.1 Quality Definitions, Management, and Quality Planning

Definition (APM BoK7 glossary): Quality is the fitness for purpose or the degree of conformance of the outputs of a process or the process itself to requirements.

Read the second half carefully. APM’s definition reaches both the outputs of a process and the process itself — which is why "the fitness for purpose of outputs and processes" is the wording that scores, and why answers framed purely around value for money, stakeholder satisfaction or the thoroughness of the plan are wrong.

In project delivery, completing work on schedule and within budget is meaningless if the resulting asset fails to function as intended or proves unsafe, unreliable, or unusable. In the classic project "iron triangle" (time, cost, and scope/quality), quality represents the standard to which deliverables must be completed to realize the benefits promised in the Business Case. Without disciplined quality management, projects succumb to defect propagation, runaway rework costs, stakeholder dissatisfaction, and failed business investments.

For candidates preparing for the APM Project Fundamentals Qualification (PFQ), mastering this domain requires understanding the formal definitions of quality and quality management according to the APM Body of Knowledge 7th Edition (BoK7), appreciating why quality is not synonymous with luxury or grade, and understanding how structured quality planning establishes the benchmark for all delivery activities.

---

Defining Quality: Fitness for Purpose and Requirements

The APM Body of Knowledge (BoK7) defines quality through two interconnected principles: fitness for purpose, and conformance to requirements — of the outputs of a process, or of the process itself. (International quality standards such as ISO 9000 express the same idea through "stated and implied requirements"; the exam wants APM’s wording.)

1. Fitness for Purpose

A deliverable is of acceptable quality if it does what its intended users need it to do within its operational environment. Fitness for purpose emphasizes practical utility, operational capability, and user satisfaction over cosmetic embellishment or unnecessary technical complexity.

2. Stated vs. Implied Requirements

• Stated Requirements: The explicit, documented needs, performance metrics, and functional specifications defined in contracts, requirements documentation, product descriptions, and the Project Management Plan (PMP). Examples include: "The cloud database must support 5,000 concurrent transactions per second" or "The highway bridge deck must bear commercial vehicles weighing up to 44 metric tonnes."
• Implied Requirements: Unwritten, unspoken, but fundamental expectations that a customer, user, or regulator has a legitimate right to expect. These encompass statutory safety standards, regulatory compliance, basic durability, operational reliability, and ergonomic usability. For example, a customer does not need to explicitly state in a contract that a new commercial office building must not collapse during normal occupancy, or that an electronic handheld scanner must not cause electric shocks.

---

Quality vs. Grade: A Critical Distinction

A primary source of confusion in project management—and a frequent testing point on the APM PFQ examination—is the distinction between quality and grade. In common conversation, people often use the word "quality" to denote luxury, high cost, or premium materials. In project management, however, quality and grade represent fundamentally distinct concepts:

• Grade: A category, rank, or design classification assigned to deliverables that share the same functional use but have different technical capabilities, materials, features, or levels of luxury. Grade is an intentional design choice determined by budget, target audience, and business case objectives.
• Quality: The degree to which the deliverable conforms to its agreed specifications and fulfills its intended purpose without defects.

+-----------------------------------------------------------------------------------------+
|                               QUALITY VERSUS GRADE                                      |
+-----------------------------------------------------------------------------------------+
|   HIGH GRADE / LOW QUALITY                      |   LOW GRADE / HIGH QUALITY            |
|   - Luxury supercar with hand-stitched leather, |   - Utilitarian economy delivery van  |
|     carbon-fiber bodywork, and state-of-the-art |     with stamped steel wheels, manual |
|     active telemetry.                           |     windows, and durable cloth seats.   |
|   - Suffers chronic sensor malfunctions, leaks  |   - Starts reliably every morning,    |
|     oil, and spends weeks in repair workshops.  |     hauls freight flawlessly, and has   |
|   - High specification, but poor fitness for    |     zero mechanical defects.            |
|     purpose and unacceptable quality.           |   - Economy grade, but outstanding    |
|                                                 |     fitness for purpose and quality.    |
+-----------------------------------------------------------------------------------------+

Core Rule for Project Managers

• Low grade may not be a problem: Delivering an economy, low-grade product is completely acceptable as long as it matches the approved scope, satisfies user needs, and fits within the client's financial budget.
• Low quality is always a problem: Delivering a product with defects, substandard materials, or unreliability is never acceptable, regardless of whether the product was designed as high-grade luxury or economy utility. Low quality damages reputation, creates safety hazards, and forces expensive rework.

---

Quality Management: Definition and Strategic Purpose

Quality does not happen by chance; it must be planned, assured, controlled and continuously refined. Quality management is the coordinated set of activities that direct and control an organisation with regard to quality. AC 8.2 asks for its purpose: to ensure that project outputs and the processes that produce them are fit for purpose and conform to requirements, so that the deliverables are acceptable to the sponsor.

The Core Purpose of Quality Management

Within project delivery, quality management fulfills several vital functions:

1. Ensuring Deliverables are Fit for Purpose: Validating that project outputs fulfill the business objectives that justified the initial capital investment.
2. Preventing Defects and Eliminating Rework: Discovering errors at the earliest possible stage—or preventing them entirely—drastically reduces the exponential cost of scrapping, redesigning, or rebuilding defective work.
3. Satisfying Stakeholder Needs: Instilling confidence across sponsors, clients, users, and regulators that deliverables will operate safely and reliably.
4. Driving Continuous Improvement: Using process data, audit findings, and lessons learned to eliminate operational waste and enhance delivery performance across the project and wider organization.

The Four Pillars of Quality Management

The APM quality framework comprises four interlinked pillars:

• Quality Planning: Identifying standards, acceptance criteria, metrics, and procedures documented in the Quality Management Plan.
• Quality Assurance (QA): Providing confidence through independent process audits and reviews that quality standards will be satisfied.
• Quality Control (QC): Inspecting, testing, and measuring physical and digital outputs to verify conformance to technical specifications.
• Continual Improvement: Applying structured cycles like the Deming/Shewhart Plan-Do-Check-Act (PDCA) cycle to refine delivery processes and prevent recurring root causes of failure.

---

Quality Planning: The Strategic Foundation

Definition (APM BoK7 4.1.5): "Quality planning takes the defined scope of the project (or the next phase or time period in an iterative life cycle) and specifies the criteria to be used to validate that the outputs are fit for purpose and acceptable to the sponsor." The glossary condenses this to: "Quality planning takes the defined scope and specifies the acceptance criteria used to validate that the outputs are fit for purpose to the sponsor."

The examinable heart of quality planning is specifying acceptance criteria. BoK7 says so directly: "statements in quality plans, often called ‘acceptance criteria’, provide guidance to the team about the requirements and essential conditions for the deliverable that they are working on." Answers about planning audits, or about confidence that objectives will be met in the required timeframe, describe assurance rather than quality planning.

BoK7 lists what the quality plan documents: methods of verifying that the outputs meet requirements; pass/fail criteria for each method; the frequency of the tests, checks or audits; and the resources required (test equipment, suitably qualified and experienced staff, stakeholder approvals). It stresses that this must be done "after scope definition and before any further planning as quality control and assurance activities take time and consume resources that need to be scheduled and costed".

Quality Planning is undertaken predominantly during the Definition phase of the project life cycle. Its fundamental purpose is to determine which quality standards, statutory regulations, and customer expectations apply to the project, and to establish the concrete mechanisms by which the project team will satisfy and verify them.

Key Elements Established During Quality Planning

1. Identifying Regulatory & Technical Standards: Determining mandatory statutory frameworks (e.g., UK Building Regulations, CDM health and safety regulations, GDPR data privacy rules) and industry-specific standards (e.g., ISO 9001 for quality systems, ISO 27001 for information security, or IEEE engineering standards).
2. Defining Measurable Quality Metrics: Converting subjective user wishes into quantifiable, verifiable engineering targets with defined tolerances (e.g., maximum permissible tensile deflection, database query response latency $\le 250\text{ ms}$, or concrete compressive strength $\ge 40\text{ N/mm}^2$).
3. Formulating Acceptance Criteria: The core of quality planning in APM’s terms. BoK7 defines acceptance criteria as "the requirements and essential conditions that have to be achieved before a deliverable is accepted" — the explicit, unambiguous pass/fail criteria that deliverables must satisfy before the sponsor will accept them. BoK7 adds that obtaining stakeholder agreement on these "facilitates the handover of the project’s outputs on completion and planning early how this will be done is a key success factor for project management".
4. Allocating Quality Roles & Responsibilities: Clarifying who performs inspections, who conducts independent assurance audits, and who possesses the formal authority to sign off on deliverables.
5. Producing the Quality Management Plan (QMP): Consolidating all quality policies, processes, tools, schedules, and standards into an authorized governance document integrated into the overall Project Management Plan (PMP).

---

The Quality Management Plan (QMP)

The Quality Management Plan (QMP) is the central component of the PMP that defines how quality will be governed throughout the project life cycle. Approved by the Project Sponsor, the QMP ensures that the delivery team, suppliers, and external contractors operate under a unified quality regime.

The following table details the primary components of a comprehensive Quality Management Plan and their operational purpose:

---

The Role of Product Descriptions in Quality Planning

While the Quality Management Plan establishes project-wide quality governance, quality planning must also operate at the granular deliverable level. This is accomplished through the drafting of Product Descriptions (also referred to as deliverable specifications).

What is a Product Description?

A Product Description is a structured document prepared during the planning and definition stage that defines the purpose, composition, quality criteria, and acceptance method for each major deliverable before physical development begins.

Core Contents of a Product Description:

• Identifier and Title: Unique Work Breakdown Structure (WBS) reference and unambiguous deliverable title.
• Purpose: Explanation of what the product does and why it is required by the project business case.
• Composition: The internal sub-elements, materials, components, or modules that make up the deliverable.
• Derivation / Source: The source documents, specifications, or prerequisite inputs required to build it.
• Quality Criteria: The measurable technical specifications and performance characteristics the finished product must exhibit (e.g., dimensions, load capacity, speed, thermal limits).
• Quality Tolerances: The permissible range of variation from target values (e.g., $500\text{ mm} \pm 0.5\text{ mm}$, or service availability $\ge 99.95%$).
• Quality Method / Verification: The specific inspection, testing, demonstration, or review technique used to prove compliance.
• Acceptance Authority: The designated individual or role with formal authority to approve and accept the finished deliverable.

By defining these parameters upfront, Product Descriptions eliminate ambiguity, establish objective targets for the delivery team, and provide the exact benchmark against which Quality Control testing will be conducted.