KEVOS® Project Delivery Handbook
Project Quality Assurance and Control
Why Quality Management Deserves Your Full Attention A practical KEVOS handbook for project delivery teams.
In this handbook article
- Why Quality Management Deserves Your Full Attention
- The "What": Defining Quality in Project Management
- Perform Quality Assurance: Inputs, Tools & Outputs
- Inputs → Tools & Techniques → Outputs
- The PDCA Cycle: The Engine of Continuous Improvement
- The Pareto Principle: Focus Where It Matters
- The Origin Story
- The Pareto Technique (Step-by-Step)
- Control Quality: The Seven Basic Quality Tools (7QC)
- The Seven Tools at a Glance
- Control Quality: Inputs → Tools & Techniques → Outputs
- Key Principles of Quality Control
- Total Quality Management (TQM): The Cultural Shift
- TQM Success Strategies
- Connecting Quality to Value Management
- The Pitfalls: Where Quality Management Goes Wrong
- Key Takeaways
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.
Relationship details
| From | Relationship | To |
|---|---|---|
| Process Design | leads to | Continuous Improvement |
| Continuous Improvement | leads to | Quality Audits |
| Inspection & Testing | leads to | Defect Identification |
| Defect Identification | leads to | Corrective Action |
| Quality Assurance (Proactive) | Feeds standards into | Quality Control (Reactive) |
| Quality Control (Reactive) | Feeds lessons back into | Quality 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.
Relationship details
| From | Relationship | To |
|---|---|---|
| PLAN — Identify the problem — Analyse root causes — Develop improvement plan | leads to | DO — Implement the plan — on a small scale |
| DO — Implement the plan — on a small scale | leads to | CHECK — Measure results — Compare to expectations |
| CHECK — Measure results — Compare to expectations | leads to | ACT — Standardise if successful — Revise if not |
| ACT — Standardise if successful — Revise if not | leads to | PLAN — 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)
- List all problems or causes to be compared
- Count how often each occurred over a defined period
- Sort from highest frequency to lowest frequency
- Chart causes as a column (bar) graph, overlaid with a cumulative percentage line graph
- Identify the breakpoint in the cumulative line — the point where the curve flattens indicates you've captured the vital few
| Category | Bar | Line |
|---|---|---|
| Light Spray | 30 | 30 |
| Runs | 22 | 52 |
| Drips | 13 | 65 |
| Blister | 11 | 76 |
| Splatter | 9 | 85 |
| Bad Paint | 7 | 92 |
| Overspray | 5 | 97 |
| Other | 3 | 100 |
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.
Relationship details
| From | Relationship | To |
|---|---|---|
| Defect A — 40 | leads to | Defect B — 25 |
| Defect B — 25 | leads to | Defect C — 15 |
| Defect C — 15 | leads to | Defect D — 10 |
| Defect D — 10 | leads to | Defect E — 10 |
| 40% | leads to | 65% |
| 65% | leads to | 80% |
| 80% | leads to | 90% |
| 90% | leads to | 100% |
| 80% | leads to | 80% Threshold |
| Defect Categories → | leads to | Defect A — 40 |
| Frequency | leads to | Defect A — 40 |
| Cumulative % | leads to | 100% |
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 |
- 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:
- Observation and testing are essential to ensure requirements for quality are met — but testing alone does not guarantee zero defects.
- Testing validates functionality but does not necessarily identify all potential defects in a product.
- Quality is a continuous improvement process, not a single gate or milestone.
- 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
Relationship details
| From | Relationship | To |
|---|---|---|
| Leadership Commitment | leads to | Education & Training — for All Staff |
| Education & Training — for All Staff | leads to | Cross-Functional — Collaboration |
| Cross-Functional — Collaboration | leads to | Process Improvement — (PDCA Cycle) |
| Process Improvement — (PDCA Cycle) | leads to | Measurement & — Feedback |
| Measurement & — Feedback | leads to | Customer — Satisfaction |
| Customer — Satisfaction | Continuous Loop | Leadership 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.
