KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesProject Quality Assurance and ControlProject Delivery · Principles of Project ManagementLesson 33/58← PrevNext →
GuidePublished 13 Aug 20269 min readBy Kevin Joginproject managementproject deliveryprinciples of project managementquality
On this page

Ask about this page

KEVOS AIProject Quality Assurance and Control

KEVOS knowledge first · trusted web sources when needed

Home/ Project Delivery/ Principles of Project Management

KEVOS® Project Delivery Handbook

Project Quality Assurance and Control

Why Quality Management Deserves Your Full Attention A practical KEVOS handbook for project delivery teams.

9 min read1,794 words Guide 32 of 57Reviewed 2026-08-13
In this handbook article
  1. Why Quality Management Deserves Your Full Attention
  2. The "What": Defining Quality in Project Management
  3. Perform Quality Assurance: Inputs, Tools & Outputs
  4. Inputs → Tools & Techniques → Outputs
  5. The PDCA Cycle: The Engine of Continuous Improvement
  6. The Pareto Principle: Focus Where It Matters
  7. The Origin Story
  8. The Pareto Technique (Step-by-Step)
  9. Control Quality: The Seven Basic Quality Tools (7QC)
  10. The Seven Tools at a Glance
  11. Control Quality: Inputs → Tools & Techniques → Outputs
  12. Key Principles of Quality Control
  13. Total Quality Management (TQM): The Cultural Shift
  14. TQM Success Strategies
  15. Connecting Quality to Value Management
  16. The Pitfalls: Where Quality Management Goes Wrong
  17. Key Takeaways

Source and edition context

Source basis: This handbook article is adapted from the supplied file(s): 33. Project Quality Assurance & Control.md.

Interpretation rule: Named scenarios, schedules, percentages, monetary values and thresholds are source examples or illustrative proposals unless an identified authority, contract or approved baseline makes them mandatory.

PMI edition context: The supplied notes primarily teach fifth- and sixth-edition process groups and knowledge areas. PMI currently publishes the PMBOK® Guide—Eighth Edition, which retains the principles and performance-domain foundation while presenting evolved, non-prescriptive process guidance. Historical counts in this article remain for source/course context, not as a claim about the current edition.

Why Quality Management Deserves Your Full Attention

Here's a paradox that haunts project management: everyone agrees quality is essential, yet quality discussions in the boardroom rarely move beyond vague commitments to "doing it right." As one industry observer noted, executive debates tend to focus on what quality is and how to measure it rather than on whether it matters — because the need is already self-evident.

The real challenge isn't convincing stakeholders that quality counts. It's building a systematic, repeatable framework that prevents defects before they occur (Quality Assurance) and catches them when they slip through (Quality Control).

In heavy engineering and defence — where a single weld defect can ground a fleet or a procurement non-conformance can delay a multi-billion dollar programme — this framework isn't theoretical. It's operational survival.


The "What": Defining Quality in Project Management

Two competing definitions of quality collide in every project team:

Perspective Definition of Quality Typical Advocates
Perfection Zero defects; flawless technical workmanship Engineers, technical specialists
Value for money Fitness for purpose at acceptable cost Executives, commercial managers, clients

Neither is wrong — but neither is complete. The PMBOK framework resolves this by splitting quality management into two complementary processes:

Perform Quality Assurance (QA): The application of planned and systematic processes to ensure quality requirements are met. QA is proactive — it builds quality into the process itself.

Control Quality (QC): The application of specific techniques and activities for checking that given requirements are being achieved and can be sustained. QC is reactive — it inspects outputs to detect defects.

The critical insight: QA prevents problems. QC finds them. A project that relies solely on QC is essentially saying, "We'll build it however we want, then test at the end to see if it works." That approach is expensive, risky, and — in safety-critical industries — unacceptable.

Process and relationship map
Quality Assurance (Proactive)
Process Design
Continuous Improvement
Quality Audits
Quality Control (Reactive)
Inspection & Testing
Defect Identification
Corrective Action
Relationship details
FromRelationshipTo
Process Designleads toContinuous Improvement
Continuous Improvementleads toQuality Audits
Inspection & Testingleads toDefect Identification
Defect Identificationleads toCorrective Action
Quality Assurance (Proactive)Feeds standards intoQuality Control (Reactive)
Quality Control (Reactive)Feeds lessons back intoQuality Assurance (Proactive)

Perform Quality Assurance: Inputs, Tools & Outputs

Quality Assurance operates as a structured process with clearly defined inputs, techniques, and deliverables.

Inputs → Tools & Techniques → Outputs

Inputs Tools & Techniques Outputs
Quality Management Plan Quality management and control tools Change requests
Process Improvement Plan Quality audits Project Management Plan updates
Quality metrics (definitions) Process analysis (PDCA and root cause analysis) Project documents updates
Project control measurements Organisational process assets updates
Project documents

The PDCA Cycle: The Engine of Continuous Improvement

At the core of QA sits the Plan-Do-Check-Act (PDCA) cycle — also known as the Deming Cycle. It's an iterative four-stage model for continuous improvement.

Process and relationship map
PLAN — Identify the problem — Analyse root causes — Develop improvement plan
DO — Implement the plan — on a small scale
CHECK — Measure results — Compare to expectations
ACT — Standardise if successful — Revise if not
Relationship details
FromRelationshipTo
PLAN — Identify the problem — Analyse root causes — Develop improvement planleads toDO — Implement the plan — on a small scale
DO — Implement the plan — on a small scaleleads toCHECK — Measure results — Compare to expectations
CHECK — Measure results — Compare to expectationsleads toACT — Standardise if successful — Revise if not
ACT — Standardise if successful — Revise if notleads toPLAN — Identify the problem — Analyse root causes — Develop improvement plan

The PDCA cycle is not a one-time exercise. Each completed cycle feeds the next, creating a spiral of continuous improvement across the project lifecycle.


The Pareto Principle: Focus Where It Matters

The Origin Story

In 1906, Italian economist Vilfredo Pareto observed that 80% of Italy's income was received by 20% of the population. In 1950, quality pioneer Joseph Juran generalised this observation into a universal principle:

The Pareto Principle states that for many phenomena, 80% of the consequences stem from 20% of the causes.

In project quality management, this translates directly: a small number of defect categories typically account for the vast majority of quality failures. Identifying and attacking those vital few — rather than spreading resources across the trivial many — produces the largest improvement with the least effort.

The Pareto Technique (Step-by-Step)

  1. List all problems or causes to be compared
  2. Count how often each occurred over a defined period
  3. Sort from highest frequency to lowest frequency
  4. Chart causes as a column (bar) graph, overlaid with a cumulative percentage line graph
  5. Identify the breakpoint in the cumulative line — the point where the curve flattens indicates you've captured the vital few
Pareto Chart — Paint Nonconformities
CategoryBarLine
Light Spray3030
Runs2252
Drips1365
Blister1176
Splatter985
Bad Paint792
Overspray597
Other3100

In this example, the first three defect categories — Light Spray, Runs, and Drips — account for approximately 65% of all nonconformities. Concentrating corrective action on these three categories will deliver far greater quality improvement than distributing effort across all eight.

Process and relationship map
Defect Categories →
Frequency
Cumulative %
Defect A — 40
Defect B — 25
Defect C — 15
Defect D — 10
Defect E — 10
40%
65%
80%
90%
100%
80% Threshold
Relationship details
FromRelationshipTo
Defect A — 40leads toDefect B — 25
Defect B — 25leads toDefect C — 15
Defect C — 15leads toDefect D — 10
Defect D — 10leads toDefect E — 10
40%leads to65%
65%leads to80%
80%leads to90%
90%leads to100%
80%leads to80% Threshold
Defect Categories →leads toDefect A — 40
Frequencyleads toDefect A — 40
Cumulative %leads to100%

Control Quality: The Seven Basic Quality Tools (7QC)

Quality Control relies on a toolkit known as the 7QC Tools — seven foundational techniques that can be applied within the PDCA cycle to diagnose and resolve quality issues.

The Seven Tools at a Glance

Tool Purpose Best Used When...
Cause-and-Effect Diagram (Ishikawa / Fishbone) Identifies root causes of a problem by category You need to explore why a defect is occurring
Flowchart Maps a process to identify inefficiencies or failure points You need to understand how a process works
Checksheet Structured form for collecting and organising data You need to count how often something happens
Pareto Diagram Ranks causes by frequency to identify the vital few You need to prioritise which problems to attack first
Histogram Shows frequency distribution of data You need to understand the shape of your data
Control Chart Plots data over time to distinguish normal variation from special causes You need to determine if a process is stable
Scatter Diagram Plots two variables to identify correlation You need to test whether two factors are related
Concept map
root((7QC Tools
  • Cause & Effect
    • Ishikawa Diagram
    • Root Cause Analysis
  • Flowchart
    • Process Mapping
    • Decision Points
  • Checksheet
    • Data Collection
    • Tally Tracking
  • Pareto Diagram
    • 80/20 Rule
    • Vital Few
  • Histogram
    • Frequency Distribution
    • Data Shape
  • Control Chart
    • Upper/Lower Limits
    • Process Stability
  • Scatter Diagram
    • Correlation
    • Variable Relationships

Control Quality: Inputs → Tools & Techniques → Outputs

Inputs Tools & Techniques Outputs
Project Management Plan Seven basic quality tools Quality control measurements
Quality metrics Statistical sampling Validated changes
Quality checklists Inspection Validated deliverables
Work performance data Approved change requests review Work performance information
Approved change requests Change requests
Deliverables Project management plan updates
Project documents Project documents updates
Organisational process assets Organisational process assets updates

Key Principles of Quality Control

These four principles underpin every QC activity:

  1. Observation and testing are essential to ensure requirements for quality are met — but testing alone does not guarantee zero defects.
  2. Testing validates functionality but does not necessarily identify all potential defects in a product.
  3. Quality is a continuous improvement process, not a single gate or milestone.
  4. Follow-up is mandatory: review corrective actions to ensure new problems or defects do not result from the changes themselves.

Total Quality Management (TQM): The Cultural Shift

While QA and QC address processes and outputs, Total Quality Management addresses the organisational culture that produces them.

TQM is a methodology for the continuous improvement of the quality of processes and products. It involves an organisational culture shift affecting all staff — not just the quality department.

TQM Success Strategies

To achieve long-term success through customer satisfaction, a TQM programme develops strategies for:

  • Education and training on the job for all staff
  • Eliminating fear — staff must feel safe reporting defects and proposing improvements
  • Removing barriers between functional areas — quality is everyone's responsibility
  • Encouraging pride of workmanship — intrinsic motivation outperforms compliance-driven behaviour
  • Adopting models for leadership — quality starts at the top
Process and relationship map
Leadership Commitment
Education & Training — for All Staff
Cross-Functional — Collaboration
Process Improvement — (PDCA Cycle)
Measurement & — Feedback
Customer — Satisfaction
Relationship details
FromRelationshipTo
Leadership Commitmentleads toEducation & Training — for All Staff
Education & Training — for All Staffleads toCross-Functional — Collaboration
Cross-Functional — Collaborationleads toProcess Improvement — (PDCA Cycle)
Process Improvement — (PDCA Cycle)leads toMeasurement & — Feedback
Measurement & — Feedbackleads toCustomer — Satisfaction
Customer — SatisfactionContinuous LoopLeadership Commitment

Connecting Quality to Value Management

Quality management and value management are not parallel tracks — they converge. The study notes for this topic explicitly position VM as a component that can be incorporated into the Quality Management Plan.

Value Management is the process of identifying the required outcome and arriving at the least possible cost. The aim is to achieve cost savings and better "value for money" for the customer.

The connection is logical: if quality means "fitness for purpose" and value means "function divided by cost," then both disciplines are asking the same question from different angles — "Are we delivering what the customer needs, efficiently?"


The Pitfalls: Where Quality Management Goes Wrong

1. Treating QC as a substitute for QA. Inspection catches defects — it doesn't prevent them. Over-reliance on end-of-line testing is expensive and reactive.

2. Ignoring the Pareto Principle. Teams that try to fix everything simultaneously fix nothing effectively. Prioritise the vital 20%.

3. Quality theatre. Producing checklists and audit reports that nobody reads or acts on creates the appearance of quality management without the substance.

4. Fear-driven cultures. If reporting a defect triggers blame rather than investigation, defects go unreported until they become crises.

5. One-and-done thinking. Quality is iterative. A single audit or review cycle is not quality management — it's a snapshot. The PDCA cycle must keep turning.


Key Takeaways

  • QA is proactive (build quality into the process); QC is reactive (inspect outputs for defects). You need both.
  • The Pareto Principle (80/20 rule) directs resources toward the vital few causes that produce the majority of defects.
  • The 7QC Tools provide a structured diagnostic toolkit applicable at any stage of the project lifecycle.
  • The PDCA cycle drives continuous improvement by iterating through Plan → Do → Check → Act.
  • TQM requires an organisational culture shift — not just new procedures, but new behaviours, from leadership down.
  • Quality management and Value Management converge around the same objective: delivering fitness for purpose at optimal cost.

Continue learning

Project PlanningPlanning Project Quality7 min readExecution Monitoring And ControlMonitoring and Controlling Projects11 min readLifecycle HandbookCarrying Out the Project Work8 min readLifecycle HandbookFoundations of Project Management9 min read

Prepared for the KEVOS® Knowledge Library. Apply the governing contract, approved project method and current standards to live work.

Continue learning

Value Management and Value EngineeringGuide · Principles of Project ManagementNEXT LESSON →Project Procurement and Contract TypesGuide · Principles of Project ManagementManaging Project CommunicationsGuide · Principles of Project ManagementProject Integration ManagementGuide · Principles of Project Management
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®