Project Quality Assurance & Control is one of the most practical parts of the PMP-style knowledge base: it answers how a project team prevents quality problems (Assurance) and detects/corrects defects (Control). In the context of the Wits (University of the Witwatersrand) PMP-aligned learning pathway—where candidates are expected to apply PMBOK®-consistent concepts to real South African project environments—quality becomes a measurable management discipline rather than a “final inspection” activity. These notes consolidate the core Wits PMP exam themes: planning quality, performing quality assurance and control, managing continuous improvement, and understanding quality cost trade-offs.
This guide is written for learners often searching for Wits PMP-aligned notes and related qualification content, including Wits Business School Project Management pathways. It also aligns with the style of exam preparation seen in South African project management modules (for example, problem-based learning in Wits and Unisa-type study approaches), while staying anchored to PMP-recognizable terminology.
Wits PMP Quality Management Foundations: From Planning to Control
Quality management on PMP-style courses usually begins with a simple question: What does “good” mean for this project? The answer must be traceable, measurable, and agreed upon by stakeholders. In Wits PMP contexts, candidates are often assessed not only on definitions but also on the logic chain—how outputs from quality planning feed into quality assurance and quality control, and how findings lead to corrective actions.
Key Concepts: Quality vs. Grade (and Why PMP Exams Test It)
PMP exam questions commonly distinguish quality from grade:
- Quality: the degree to which a set of inherent characteristics meets requirements.
- Grade: category or rank used when different requirements are intended for different uses of the same product/service.
Why it matters in practice (South African projects):
A contractor might offer “standard” and “premium” lighting packages. The grade differs, but quality is still judged against the agreed specifications for each grade (e.g., luminous flux, durability, compliance with wiring standards). If stakeholders accept “premium” grade but the lamps fail early, quality is the issue—not grade.
Quality Planning Inputs and Outputs (What You Must Be Able to Write From Memory)
On a PMP-aligned syllabus, the quality planning process typically draws from:
Inputs commonly emphasized
- Project management plan (including scope and schedule baselines)
- Stakeholder register and stakeholder engagement plan
- Requirements documentation (including product requirements and quality standards)
- Enterprise environmental factors (EEFs)
- Organizational process assets (OPAs)
Outputs
- Quality management plan
- Quality metrics and checklists
- Process improvement plan
- Sometimes: quality baseline (or a similar artifact depending on the framing used in your course)
Quality Management Plan: What It Should Contain
A robust quality management plan should describe, at minimum:
- Quality standards to be used (internal and external)
- How quality will be measured (metrics)
- Roles and responsibilities (who performs what)
- Quality assurance activities (planned audits/reviews, process evaluations)
- Quality control activities (inspections, testing, reviews)
- Quality cost approach (prevention/appraisal/failure costs)
- Continuous improvement approach (how lessons learned and changes are handled)
Typical exam pattern: A question describes a team creating inspection forms and test procedures but does not clearly document the auditing system. The exam expects you to recognize that those items relate more strongly to control, while the assurance and process review structure belong in the quality management plan.
Quality Metrics: Make Requirements Measurable
When requirements are vague, quality becomes subjective and disputes become common. PMP-style learning encourages converting requirements into metrics such as:
- % compliance with specification dimensions
- Test pass/fail rates
- Mean time between failures (MTBF)
- Turnaround time (TAT) for deliverables
- Density of rework (e.g., hours per 100 units)
Example scenario (construction/engineering in SA):
A road maintenance project specifies “good asphalt quality.” To measure quality, convert that into metrics:
- Asphalt temperature within a specified range during laying
- Compaction targets (e.g., % relative compaction)
- Thickness tolerance in mm
- Core sample strength outcomes (lab results)
Then, the team can plan both:
- Assurance: verify that compaction procedure and equipment calibration processes are correct
- Control: test core samples and compaction results against thresholds
Process Quality vs. Product Quality
A deep exam theme is that quality problems can stem from:
- Process issues (e.g., incorrect calibration routine, missing training)
- Product issues (e.g., defective output)
PMP-style reasoning expects you to ask: Is the project’s process preventing defects, or are we only catching them after they occur? This is why quality assurance is often described as prevention-oriented, while quality control is detection-oriented.
The Quality Cost Model: Prevention, Appraisal, Internal Failure, External Failure
A widely taught model (and often discussed in PMP courses) categorizes quality costs:
- Prevention costs: planning, training, process documentation, audits to prevent defects
- Appraisal costs: inspections, testing, reviews to detect defects
- Internal failure costs: scrap, rework, retesting before delivery
- External failure costs: warranty claims, penalties, reputation damage after delivery
Why PMP exams love this:
They ask you to choose the action that reduces total cost, not only the short-term detection costs.
Counter-intuitive but important:
Spending more on prevention (e.g., training, robust SOPs, calibration system checks) can reduce appraisal and failure costs, lowering total costs.
Common South African Project Drivers That Make Quality Management Critical
In many South African public and private projects, quality is pressured by:
- procurement delays leading to compressed timelines
- supplier variability (materials and subcontractors)
- fluctuating skills availability (training gaps)
- compliance requirements across local standards and contractual specifications
These pressures create conditions where poor quality becomes expensive quickly. That’s why Wits PMP-aligned candidates are taught to treat quality as a lifecycle management discipline—not as a final stage.
Case Example: IT Infrastructure Rollout with Incomplete Requirements
Consider a project to implement new customer-facing systems at a company in South Africa. If stakeholders only specify “the system must be reliable” without metrics, the team might still do unit testing and a final acceptance test.
- That is control, but the absence of quality planning leads to disputes: reliability thresholds were never defined.
- Quality assurance might have asked earlier: What is the acceptable outage duration? What is the maximum allowable defect escape rate?
In a PMP-exam logic chain, the best correction is usually: create measurable requirements and define quality standards/metrics in the quality management plan, then align control procedures to those metrics.
Quality Assurance in PMP: Audits, Process Reviews, and Continuous Improvement
Quality assurance (QA) focuses on improving processes so that the project can produce deliverables that meet requirements. In PMP-aligned learning (including Wits PMP exam preparation), QA is often tested through questions that contrast QA vs. QC, or that ask which activity belongs to assurance: audits, process improvement planning, and evaluation of compliance with quality standards.
What Quality Assurance Really Does (Prevention and System Improvement)
QA includes planned and systematic activities to ensure the project’s processes are adequate. Examples include:
- Process audits (e.g., verifying that documented procedures are followed)
- Quality audits (checking compliance to agreed standards)
- Management reviews of quality performance
- Assessment of improvement initiatives
Exam framing you should recognize instantly:
If the scenario says “verify the process is followed” or “audit the quality management system,” that is quality assurance. If the scenario says “inspect/test the deliverable,” that is quality control.
QA Outputs: How Assurance Creates Action
QA activities can produce:
- recommendations for change
- corrective or preventive actions
- updates to process documentation
- updates to lessons learned (or refinement of process improvement plan)
- improvements to training and governance
Key PMP linkage:
QA findings must flow through integrated change control or the project’s corrective action system where appropriate. The project doesn’t just “audit for audit’s sake”—it uses findings to improve.
Corrective vs Preventive Actions (and How to Distinguish Them)
A common PMP logic trap is confusing corrective and preventive actions.
- Corrective actions: address causes of discovered nonconformities (fix the problem)
- Preventive actions: address causes of potential nonconformities (stop the problem before it occurs)
Example (QA audit):
An audit finds that test equipment calibration records are missing for certain batches of work. That finding causes:
- a corrective action: fix missing records, recalibrate equipment, retest affected deliverables if required
Preventive action might include:
- requiring automated calibration reminders
- training the responsible technician
- updating the SOP to ensure calibration records are attached before work proceeds
Quality Assurance Tools and Techniques
Depending on the course framing, QA uses tools such as:
- Quality audits
- Process analysis / root cause analysis (especially when metrics show recurring patterns)
- Benchmarking (comparing processes with best practice or internal historical data)
- Cause-and-effect diagrams and other root cause tools (often more associated with corrective action)
- Flowcharts / process mapping to understand failure points
Even when these tools are taught under a broader “quality” umbrella, the exam question generally wants you to categorize the activity as assurance vs control.
Role of Stakeholders in QA
Quality assurance is not only a technical function. Stakeholders influence QA because:
- stakeholder requirements define “fitness for purpose”
- governance bodies may request assurance evidence for compliance
- users can provide feedback on whether the product meets operational expectations
In Wits PMP-style environments, candidates often see case studies where business stakeholders demand proof that quality processes are working, not just that deliverables “seem fine.” This emphasizes audits, governance reports, and evidence-based assurance.
Example Case Study: Water Treatment Plant Upgrade
Situation: A municipality embarks on a water treatment plant upgrade. Multiple subcontractors handle electrical works, mechanical components, and civil construction.
Quality assurance activities
- The project quality team audits subcontractor processes:
- installation procedures for electrical panels
- welding certification procedures
- materials traceability documentation
- The team runs management reviews after key milestones:
- completion of panel installation
- completion of pipeline welding
How assurance prevents failures
- If audits show welding certifications are inconsistent, the project team can correct processes before pipeline segments are closed in.
- This prevents rework that would otherwise require cutting open installed sections—far more expensive and risky.
Exam-ready takeaway:
QA in this case is prevention. Even if QC later tests weld strength, the real value is that QA ensures the process that produces welds is correct and compliant.
Example Case Study: Training and Process Standardization in an HR System Rollout
Situation: A company deploys a new HR platform. Data migration fails intermittently due to inconsistent mapping.
QA activity
- QA audits the data migration process:
- confirm whether mapping templates exist
- verify that data mapping reviews occur
- check version control on mapping configurations
Preventive improvement
- standardize the mapping template
- require peer review before migration runs
- add checkpoints for data validation logic
In PMP reasoning: the deliverable (migrated data) will be controlled, but QA ensures the process used for migration is reliable and repeatable.
Continuous Improvement: Beyond “Fixing Defects”
PMP-quality assurance is strongly linked to continuous improvement. The logic chain is:
- measure quality performance
- analyze trends and root causes
- improve processes
- update standards and procedures
- institutionalize learning through lessons learned and process assets
Important nuance:
Continuous improvement is not a random brainstorming session. It must be grounded in evidence (metrics, audit findings, trends) and produce specific improvements.
Common Exam Traps in Quality Assurance Questions
- Calling QC as QA
- Example trap: “Inspect deliverables to confirm compliance” → that’s QC, not QA.
- Ignoring documented processes
- If a scenario says procedures exist but are not followed, QA focuses on compliance with process, not only whether the final output passes tests.
- Skipping preventive actions
- If the scenario indicates repeated small errors, preventive improvements are expected rather than only corrective fixes.
Quality Control in PMP: Inspection, Testing, Sampling, and Defect Management
While QA ensures that processes are right, quality control (QC) ensures that the output is right. QC is the operational side: inspecting, testing, and verifying deliverables against requirements and standards. In Wits PMP exam notes, QC is where many candidates lose marks because they do not apply sampling/inspection logic correctly, or they confuse control results with assurance activities.
What Quality Control Produces (Deliverable-Focused Evidence)
QC produces:
- acceptance decisions (pass/fail, meet/not meet)
- verified deliverable measurements
- test results and inspection reports
- records of nonconformities
- recommendations for rework or repair
- updates to documentation, such as test logs and quality control records
PMP exam logic:
If a question asks what the team does to confirm whether work outputs comply, it is QC.
Quality Control Activities: Inspections and Testing
QC includes:
- inspections: evaluating deliverables (e.g., visual inspection, dimensional checks)
- testing: performance testing (e.g., functional tests, load tests)
- review: formal review of deliverables against criteria
- sampling: testing only a subset when full inspection is impractical
Sampling Concepts That Regularly Appear in Exam Questions
A PMP learner should know key reasons sampling is used:
- full inspection can be cost-prohibitive
- time constraints limit full verification
- deliverables may be too numerous to test completely
However, sampling requires careful planning:
- defined sampling criteria
- statistical rationale (where used)
- clear acceptance thresholds
Exam-style reasoning example:
If a scenario says “the team will test 10 units from a batch of 1,000 using a predetermined sampling plan,” that indicates structured QC with acceptance logic. If the team instead “picks a few random units without criteria,” it may weaken the quality decision evidence.
Inspection Techniques: What “Inspection” Can Mean
Inspection can be:
- visual (surface defects, workmanship)
- dimensional (tolerances, measurement checks)
- documentation-based (ensuring required records exist, traceability is complete)
- functional (observing behavior against requirements)
QC often depends on:
- calibrated equipment
- trained inspectors
- controlled testing environments
Defect Management: Nonconformities and Rework
When QC finds issues, the project must decide:
- whether defects require repair, rework, or replacement
- whether re-testing/verification is required
- whether the defect impacts acceptance or requires escalation
PMP exam questions commonly expect the sequence:
- identify nonconformity
- document findings
- perform root cause analysis (sometimes led by QA but can support QC)
- implement corrective actions
- verify fixes (re-test)
- update acceptance decisions and records
Quality Control and Integration with Change Control
QC findings may cause:
- corrective actions
- preventive actions
- sometimes change requests if requirements or designs must be altered
Exam logic:
QC results alone do not automatically change scope, schedule, or design. Quality findings must follow the project’s governance process (e.g., corrective action system or integrated change control) depending on the magnitude and nature of the finding.
Tools and Techniques for Quality Control
Common QC tools/techniques include:
- checklists and inspection sheets
- control charts (when statistical process control is taught)
- histograms (distribution of defects)
- Pareto analysis (80/20 defect categories)
- test documentation and results tracking
- sampling plans
Even when not all these tools are required for a specific exam, being able to classify them as QC tools helps avoid confusion with QA.
Control Charts (Conceptual Understanding for PMP-Style Scenarios)
Control charts help monitor process variation. If a process begins to produce outputs outside control limits, the process may require investigation.
Practical interpretation for exam reasoning
- If results fluctuate within control limits → process is stable
- If results exceed control limits or show non-random patterns → process is not stable
The PMP exam typically tests whether you interpret chart signals as process control decisions.
A Concrete Case Study: Manufacturing Component Procurement
Situation: A project procures mechanical components from a supplier. Delivery quality has been inconsistent.
Quality control plan
- incoming inspection of components upon delivery
- sampling plan defined by criticality
- dimension checks and performance tests
QC outcomes
- If defects are found:
- quarantine affected items
- request corrective action from supplier
- re-inspect after corrective measures
- assess whether defects affect project deliverables and acceptance
Quality assurance linkage
- QA might audit the supplier’s manufacturing and inspection processes to prevent recurrence, not just accept/reject batch products.
A Concrete Case Study: Software Development Defects
Situation: A project is building a web service. QC includes:
- unit testing
- integration testing
- system testing
- defect tracking and severity classification
QC verification steps
- execute test cases
- record pass/fail results
- triage defects based on severity and impact
- apply fixes
- regression test to confirm the fix didn’t break other functionality
PMP exam reasoning:
When the question highlights testing, defect discovery, and verification of deliverables, it is quality control.
Acceptance Criteria: The Foundation for QC Decisions
QC decisions rely on acceptance criteria, which must be derived from:
- requirements and specifications
- quality standards
- contract requirements
- stakeholder expectations for readiness
If acceptance criteria are missing or vague, QC becomes subjective. That is why Wits PMP-aligned material emphasizes the strong link between quality planning and quality control: metrics and acceptance thresholds are not optional.
Quality Control Records: Evidence Matters
QC creates records such as:
- inspection reports
- test results
- nonconformity reports
- sign-offs
- traceability evidence
Why it matters:
In real audits or claims, the project must show evidence of diligence. QC records can be critical for contract compliance and for learning.
Common QC Exam Traps
- Treating QC results as QA evidence
- Passing tests for one batch does not mean the process is controlled; QA addresses process.
- Skipping re-testing
- Fixes must be verified; otherwise “corrected” defects may reappear.
- Mixing acceptance with control
- QC determines compliance; acceptance decisions follow the governance/contractual steps.
Putting It Together: Quality Management Strategy, Metrics, Costs, and Exam-Grade Scenarios
This section synthesizes the two halves—QA and QC—into an integrated quality management strategy. Wits PMP-style exam questions often present a scenario with multiple activities occurring concurrently, and you must classify each activity correctly and choose the best overall approach.
The Integrated View: Quality Planning → QA → QC → Corrective/Preventive Action
A consistent mental model:
- Quality planning
- define standards, metrics, roles, QA/QC methods
- Quality assurance
- ensure processes produce compliant outputs
- Quality control
- inspect/test deliverables to verify compliance
- Nonconformities
- document and analyze causes
- Corrective and preventive actions
- fix what is wrong and prevent recurrence
- Continuous improvement
- institutionalize improvements into OPAs and lessons learned
Exam emphasis:
If the scenario lacks measurable standards early, your likely best option is to strengthen quality planning—not to increase inspections without addressing the root.
Quality Metrics and Quality Baselines
A strong exam answer often mentions:
- quality metrics aligned to requirements
- quality baseline (or equivalent measurement reference)
- targets for acceptable performance
- reporting frequency and thresholds for escalation
Example metrics
- defect density per module
- percentage rework hours
- inspection pass rates
- customer satisfaction score (for service projects)
- number of critical nonconformities per milestone
A Sample Quality Metrics Table (Exam-Style)
The following example shows how metrics could be documented in a quality management plan (illustrative, but the structure matches PMP learning expectations):
| Metric | Measurement Method | Target | Escalation Threshold |
|---|---|---|---|
| Defect density | defects per function point | ≤ 0.8 | > 1.0 sustained 2 iterations |
| Test pass rate | % test cases passed | ≥ 95% | < 90% in a release cycle |
| Rework effort | hours rework per sprint | ≤ 12 hrs | > 18 hrs in two sprints |
| Critical nonconformities | count per milestone | ≤ 1 | ≥ 2 at a milestone gate |
How this connects to QA vs QC
- QC uses the measurement method and results to accept/reject deliverables.
- QA uses trends and audit evidence to improve processes causing those results.
Quality Costs: Interpreting Trade-offs for Exam Questions
Quality is not free. PMP-oriented study emphasizes quality cost categories and the decision logic:
- If failure costs (internal/external) rise, prevention and appraisal must be reviewed.
- If appraisal costs rise but failures remain, QA might reveal process issues (not just improve testing).
Practical reasoning example
- A team increases inspections (appraisal) but still finds the same defect type.
- That suggests deeper process problems (QA should investigate training, SOPs, and root causes), not only more inspections.
Root Cause Analysis: Linking QC Findings to QA Improvements
When QC finds defects, root cause analysis can be used to determine whether the cause is:
- process-related (QA focuses here)
- product design-related (could require change control)
- supplier quality-related (supplier corrective action; plus QA audits of supplier processes)
Root cause analysis tools often include:
- 5 Whys
- fishbone (Ishikawa) diagrams
- Pareto analysis to prioritize defect categories
Even though these tools appear under broader quality learning, the exam expects you to apply them in the correct workflow: QC finds → analysis identifies cause → corrective/preventive actions improve processes → verify.
Scenario Set 1 (Construction / Engineering / Compliance)
Scenario A:
A team builds a facility and uses inspection checklists weekly. QC identifies a repeating weld defect pattern. The team immediately reworks the welds but never checks why the welding process is failing.
Best interpretation
- QC is being performed (inspections, defect discovery, rework)
- QA is not sufficiently applied (process audit and preventive actions missing)
Best improvement
- perform a QA process audit of welding procedure compliance, equipment calibration, and training
- apply preventive actions: retrain welders, adjust process controls, enforce calibration records before work starts
Exam logic:
If the question asks what activity should be added to prevent recurrence, the answer points to QA and preventive actions.
Scenario B:
A project audits supplier documentation and verifies traceability for materials before installation.
Interpretation
- This is QA because it checks compliance of processes and systems producing outputs (materials traceability process), not only testing installed components.
Scenario Set 2 (IT / Digital Systems)
Scenario C:
A software team reviews requirements, sets measurable acceptance criteria, defines testing metrics, and runs scheduled process audits on coding standards and peer review practices.
Interpretation
- This is heavily QA-related (process governance and audits)
- The testing that follows is QC
Scenario D:
The team tests every release using automated unit/integration tests and manual acceptance testing, logging defects and deciding accept/reject per sprint release criteria.
Interpretation
- This is QC-focused (testing and acceptance decisions)
- If defects are recurring because of missing peer reviews, QA would need to address the process.
Scenario Set 3 (Service Delivery / Customer-Facing)
Scenario E:
A call center project monitors average call handling time, complaint rate, and re-contact rate. When trends worsen, the team audits training materials and call scripts.
Interpretation
- monitoring and measurement: both QA and QC can use metrics, but:
- audits of training materials and call script processes strongly align with QA
- service-level inspections (e.g., recorded call spot checks) are QC
Exam logic:
Choosing QA vs QC often depends on whether the activity targets process systems or output verification.
South African University-Exam Focus: Wits PMP & How to Answer Quality Questions Like an Exam Candidate
This final section consolidates exam strategy and emphasizes common question styles used in South African university assessments for project management-adjacent modules. Because many learners searching for “Wits PMP course notes” also study alongside Unisa and other South African coursework, the emphasis is on structured answer logic: define, classify, apply to scenario, and choose the best action.
How South African PMP Candidates Often Get Quality Questions Wrong
Common patterns:
- Over-using “testing” as the answer
- Testing is QC, but many scenarios ask about prevention or process compliance.
- Ignoring evidence and records
- PMP-quality is evidence-driven. If you don’t mention records, acceptance criteria, or documented outputs, your answer may be graded as incomplete.
- Not linking QA findings to corrective/preventive action
- QA and QC must lead to action, not only identification.
- Not tying metrics to requirements
- Quality without measurable standards collapses into opinion.
A “Classifier” Framework for QA vs QC (Fast Exam Reasoning)
When you read a scenario, ask three questions in order:
- Is the action about verifying deliverables?
- If yes → Quality Control
- Is the action about verifying processes/systems?
- If yes → Quality Assurance
- Does the question ask what to do to prevent recurrence?
- If yes → Preventive action (often driven by QA)
This classifier reduces guesswork.
Quality Answer Template (Useful for Written Exams and Online Assessments)
A good PMP-aligned written response often includes:
- Label the activity (QA or QC) with one sentence.
- State the purpose (prevention vs inspection/verification).
- Mention a concrete method/tool (audit, checklist, test, sampling plan, control chart).
- Connect to output evidence (records, reports, acceptance decisions).
- Describe the action response (corrective/preventive actions; retest; change control).
Example of a concise exam-grade answer style
- “The activity is quality control because it verifies the deliverable against acceptance criteria through testing/inspection; findings will be documented as nonconformities and corrective actions will be followed by re-testing and acceptance decision updates.”
Example Exam Question 1 (Conceptual)
Question (typical framing):
A project team performs weekly inspections of completed work items and issues defect reports. What is the most appropriate classification of this activity?
High-scoring reasoning
- Inspections of completed items → deliverable verification → Quality Control
Best answer choice
- “Quality Control (QC), using inspections/checklists and defect reporting.”
Example Exam Question 2 (Scenario: Prevention)
Question framing:
A quality audit reveals that the calibration process for test equipment is not being followed, leading to inconsistent test results. The team decides to standardize calibration routines, add automated reminders, and train technicians.
Classification
- audit of calibration process and standardization → Quality Assurance
- emphasis on preventing inconsistent results → preventive actions
Example Exam Question 3 (Sampling vs Full Inspection)
Question framing:
A batch contains 10,000 items. Full inspection is too expensive, so the team plans to inspect 500 items using a predetermined sampling plan with defined acceptance criteria.
Classification
- testing/inspection of deliverables → Quality Control
Why the sampling plan matters
- it provides structured and defensible acceptance criteria; random pick without plan weakens evidence quality.
Building Complexity: When Both QA and QC Are Needed
Sometimes scenarios contain both. For example:
- team audits supplier processes (QA)
- team also inspects incoming materials (QC)
Exam strategy
- Do not pick only one if question asks which activities are being performed. Instead, classify both and explain which role each plays.
Continuous Improvement in Exam Answers: What to Say and What Not to Say
High-quality answers should:
- mention using metrics/trends and audit findings
- identify root causes
- improve processes and institutionalize changes
- update lessons learned and process assets
Avoid generic answers like “we will improve quality” without showing mechanism (metrics, audit evidence, root cause analysis, actions).
Quality and Project Performance: How to Link Quality to Cost/Schedule
PMP-aligned study emphasizes that quality affects:
- rework cost
- schedule slippage (rework causes delays)
- risk exposure (defects can become major issues)
- stakeholder satisfaction (especially for service projects)
Exam logic connection
- Better quality planning and QA prevention reduce internal failure costs.
- Better QC early reduces external failures after delivery.
- Over-reliance on QC late increases rework and schedule impact.
Practical Links to Wits PMP Course Style Learning
Wits PMP learners are typically assessed with scenario reasoning and process classification. Quality management content is therefore learned as:
- definitions
- workflow
- classification into QA/QC
- evidence and corrective action loops
That’s why these notes emphasize decision logic and not only definitions.
Consolidated Checklist for Exam Day
Use this quick reference when solving quality questions:
Quality Assurance (QA)
- audits/process reviews
- prevention and improvement of processes
- verifies system compliance
Quality Control (QC)
- inspection/testing/reviews of deliverables
- acceptance decisions and defect identification
- uses metrics, sampling plans, test results
Always include in the best answers
- acceptance criteria or standards
- documented evidence/records
- corrective and/or preventive action response
- re-verification (re-testing or re-inspection) when fixes occur
Summary of Core Exam Takeaways
Project Quality Assurance & Control (Wits PMP course-aligned notes) boils down to a disciplined quality lifecycle:
- Quality Planning defines standards, metrics, roles, and the QA/QC approach.
- Quality Assurance ensures processes are capable and compliant through audits and process reviews—preventing defects.
- Quality Control inspects/tests deliverables against acceptance criteria—detecting defects and enabling acceptance decisions.
- Quality Cost Thinking explains why prevention and appraisal can reduce internal/external failure costs.
- Corrective and Preventive Actions close the loop from findings to process improvement.
- Continuous Improvement uses trends, root causes, and lessons learned to refine organizational process assets.
These notes provide the exam-grade reasoning you need: recognize whether a scenario describes process verification (QA) or deliverable verification (QC), connect findings to corrective/preventive actions, and ensure your answers reflect evidence-based quality management rather than “final inspection” thinking.
