Project Quality and Performance Management is a core competency in project management at universities in South Africa, including Durban University of Technology (DUT). These exam notes bring together quality planning, quality assurance, quality control, performance measurement, risk-linked quality improvement, and practical tools used in real project environments. The focus throughout is on how to manage “quality” (meeting requirements) alongside “performance” (time, cost, scope, outcomes), using clear metrics, audits, and feedback loops.
The notes are written for DUT-style understanding and application: you’ll see structured processes, measurable indicators, and worked scenarios that mirror typical exam questions.
1) Project Quality Management Foundations (Linking Quality to Project Performance)
Quality in a project is not just “making things right”; it is ensuring the project’s outputs meet the agreed requirements and expectations, while performance delivery (time, cost, scope, benefits) remains on track. In exam settings, the most common weakness is treating quality management as separate from schedule and cost. In practice—and in DUT-focused project management modules—the strongest answers explain the link: poor quality causes rework, delays, and budget overruns; high quality supports stable delivery and predictable performance.
1.1 Definitions and Scope: Quality vs Performance vs Grade
A clear distinction often earns marks in theory-heavy questions:
- Quality: Degree to which requirements are met. Requirements come from stakeholders, specifications, regulations, and internal standards.
- Performance: How well the project (and its outputs) meets objectives—commonly measured through schedule performance, cost performance, and scope/outcome attainment.
- Grade: Category or class reflecting technical characteristics (e.g., “economy” vs “premium” tyres). Grade is not the same as quality; you can have high grade with low quality if requirements aren’t met.
Exam-friendly framing:
- Quality answers: “Did we meet the requirements?”
- Performance answers: “Did we meet targets for cost, time, scope, and outcomes?”
1.2 Stakeholder Requirements and the Quality Baseline
In quality and performance management, the “quality requirements” must be explicit. Typical sources include:
- Contractual specifications
- Engineering drawings and standards
- Regulatory and safety requirements
- Customer/user needs
- Internal organizational processes (templates, SOPs, policies)
To measure quality, you need a quality baseline (a set of documented requirements and acceptance criteria). In a performance context, you also need:
- Schedule baseline (planned start/end dates for deliverables)
- Cost baseline (planned budgets)
- Scope baseline (work breakdown and boundaries)
Key concept: Quality management uses the baseline requirements to define what “done” means. Performance management then tracks how well delivery aligns with baselines.
1.3 Common Quality Dimensions Used in Projects
Quality requirements are often multidimensional. Common dimensions include:
- Functionality: Does the output do what it is supposed to do?
- Reliability: Does it keep working consistently over time?
- Usability: Can users operate it without excessive complexity?
- Safety: Does it meet safety standards?
- Maintainability: Is it feasible to service and repair?
- Compliance: Does it meet laws and regulations?
- Performance/efficiency: Does it meet technical performance thresholds?
In construction, for example:
- Functionality might mean “the building meets design intent.”
- Safety means compliance with building codes.
- Maintainability might mean equipment access, spare parts availability, and design for serviceability.
In IT and service projects:
- Functionality and usability are strongly weighted.
- Reliability can be defined as uptime targets.
- Compliance can include data protection and security controls.
1.4 Why Quality and Performance Are Interdependent
Poor quality almost always shows up as poor performance. Consider the typical chain:
- Requirements misunderstood or ignored
- Output built/tested incorrectly
- Defects discovered late (during integration, commissioning, or user acceptance)
- Rework activities begin
- Rework consumes schedule float and budget
- Performance metrics deteriorate (delays, cost overruns, scope pressure)
- Stakeholder trust decreases, increasing change requests and coordination costs
Conversely, quality management improves performance by:
- Reducing defect rates
- Catching issues earlier via inspections and testing
- Stabilizing production/delivery processes
- Improving predictability of delivery outcomes
Exam scenario idea: If a project reports “on budget” but poor quality leads to frequent rework, the effective cost rises and schedule slips. A high-scoring answer explicitly distinguishes:
- Planned vs effective cost
- Reported progress vs verified completion
1.5 Quality Planning Output: Quality Plan and Quality Metrics
A Quality Plan is a structured document that explains:
- What quality standards to follow
- How quality activities will be performed (assessments, inspections, testing)
- Roles and responsibilities
- Quality metrics and acceptance criteria
- Procedures for dealing with nonconformities and corrective actions
Quality metrics can include:
- Defect density (defects per component or per page)
- Rework rate (% work re-done)
- First-pass yield (% of outputs passing initial test)
- Test coverage (% requirements tested)
- On-time inspection completion (%)
In performance management, metrics often include:
- Planned Value (PV), Earned Value (EV), Actual Cost (AC)
- Schedule variance (SV = EV − PV)
- Cost variance (CV = EV − AC)
- Cost Performance Index (CPI = EV/AC)
- Schedule Performance Index (SPI = EV/PV)
Bridge concept: Quality metrics become performance drivers. For example, low first-pass yield increases rework and usually harms CPI and SPI.
2) Quality Planning, Assurance, and Control: Tools, Techniques, and Exam Answers
A strong project quality management response typically uses the structure: quality planning → quality assurance → quality control. Exams love this because it gives a clear sequence and allows you to show understanding of both processes and outputs.
2.1 Quality Planning: From Requirements to Acceptance Criteria
Quality planning converts stakeholder and technical requirements into operational criteria.
2.1.1 Translating Requirements into Measurable Criteria
The transformation step is often where candidates lose marks: they list standards but do not show measurable acceptance criteria.
A good approach:
- Identify requirement: e.g., “Road surface must meet skid resistance standard.”
- Define measurable indicator: e.g., coefficient of friction threshold.
- Specify test method: e.g., sand patch or measured friction device.
- Set acceptance threshold: e.g., friction ≥ X.
- Define frequency and sampling: e.g., sample 3 locations per 1 km.
- Set documentation requirement: e.g., test reports signed by engineer.
2.1.2 Quality Plan Components (Typical Exam List)
A Quality Plan typically includes:
- Standards and regulations to apply
- Roles: who performs reviews, inspections, and audits
- Quality control procedures: testing/verification
- Quality assurance approach: process evaluation, audits
- Sampling strategy (if not 100% inspection)
- Control of nonconforming outputs
- Continuous improvement method (corrective/preventive actions)
2.2 Quality Assurance (QA): Auditing Processes, Not Just Products
Quality assurance focuses on the system/process that produces outputs. Think of QA as asking:
- Are we following the documented procedures?
- Are controls in place to prevent defects?
- Are our process metrics improving?
QA is often done via:
- Process audits
- Compliance checks against standards/SOPs
- Management reviews
- Training and certification checks
- Supplier quality evaluations
Exam contrast:
- Quality Control: checks outputs (defect detection)
- Quality Assurance: checks how outputs are produced (defect prevention)
2.3 Quality Control (QC): Inspection, Testing, and Verification
Quality control is operational. It uses inspections and tests to confirm that outputs meet acceptance criteria.
Common QC activities include:
- Incoming inspection (materials, equipment)
- In-process inspection (at stages in delivery)
- Final inspection and verification (before acceptance)
- Performance testing (functional trials, load tests)
- Documentation review (checklists, sign-offs)
2.3.1 Inspection Types and Their Uses
Key inspection types:
- 100% inspection: checks every unit; expensive but useful for safety-critical outputs.
- Sampling inspection: checks a sample; cost-effective but requires correct sampling design.
- First article inspection: initial sample production for calibration of process.
- In-line monitoring: real-time checks during delivery.
2.3.2 Sampling and Acceptance Thresholds (Worked Example)
Suppose a manufacturing subcontractor provides 500 valve units. The project spec requires pressure testing for functionality. Full testing is costly, so a sampling approach is used.
Assume:
- Sample size: 50 units
- Acceptance rule: if more than 2 valves fail pressure tests, reject the batch
If test results show 3 failures:
- Reject the batch
- Trigger supplier corrective action and replacement
If test results show 1 failure:
- Accept with possible additional mitigation (e.g., tighten process controls)
An exam question might ask:
- “Which QC method should be used and why?”
Answer should explain trade-offs: cost vs defect risk vs safety/compliance implications.
2.4 Root Cause Analysis (RCA): The Core of Corrective Action
When nonconformities occur, corrective actions should address root causes, not symptoms.
Common RCA tools:
- 5 Whys
- Fishbone (Ishikawa) diagram
- Pareto analysis (focus on the 20% causes generating 80% issues)
- Fault tree analysis (more advanced)
2.4.1 Example: Defect in Electrical Panel Assembly
Issue: Panels fail an insulation resistance test.
Possible causes:
- Wrong wire type (material issue)
- Incorrect assembly procedure (process issue)
- Operator not trained on torque specs (people issue)
- Dust contamination from workspace (environment issue)
- Test equipment calibration drift (equipment issue)
Using 5 Whys, teams might reach:
- “Why did test fail?” → insulation resistance low
- “Why low?” → contamination on terminals
- “Why contamination?” → assembly area not cleaned between batches
- “Why not cleaned?” → cleaning SOP not enforced
- “Why SOP not enforced?” → unclear responsibility and missing checklist
Corrective action: assign responsibility, enforce checklists, and train operators.
Preventive action: add cleaning verification step into in-process QC.
2.5 Quality Audits and Verification Activities
Quality audits evaluate whether quality activities and documentation meet planned arrangements.
2.5.1 Audit Types
- Internal audits: performed by the organization
- External audits: performed by clients or certification bodies
- Supplier audits: evaluate vendor compliance and capability
Audits typically include:
- Checking documentation: quality plan, test records, inspection reports
- Interviewing personnel: verifying training and understanding
- Observing work: confirming procedures are followed
Exam tip: A high mark answer includes both audit scope (what is covered) and audit criteria (what standards are used).
2.6 Control of Nonconforming Outputs
A quality system must control outputs that do not meet requirements. Options commonly include:
- Rework to meet specs
- Repair (if permitted)
- Use-as-is (only with formal acceptance by authorized authority)
- Scrap/dispose
- Substitute with approved alternative
- Hold and investigate while root cause is determined
Important: “Use-as-is” is not automatic—it requires formal approval. Examiners expect candidates to state the need for authorization.
3) Performance Management: Metrics, Earned Value, Risk-Adjusted Monitoring, and Continuous Improvement
Performance management in projects is broader than schedule and cost. It combines measurement, reporting, forecasting, and corrective decisions so that the project can meet objectives. Quality is a component: performance systems must consider the impact of defect rates and process instability on delivery.
3.1 Performance Measurement Framework: What to Measure and Why
Performance measurement answers:
- Are we doing the work planned?
- Are we achieving the intended outputs?
- Are we using resources efficiently?
- Are we progressing toward outcomes/benefits?
Typical performance dimensions:
- Time: schedule adherence and completion forecasts
- Cost: budget use and cost efficiency
- Scope: deliverables completed vs planned
- Quality: defect trends and acceptance performance
- Risk/issue status: exposure trends and mitigation effectiveness
- Stakeholder satisfaction: feedback, sign-offs, acceptance readiness
3.2 Earned Value Management (EVM): Time and Cost with a Single Logic
EVM integrates scope, schedule, and cost. The basic variables:
- PV (Planned Value): what should have been spent for planned work
- EV (Earned Value): value of completed work
- AC (Actual Cost): actual spending
Core calculations:
- Schedule Variance (SV) = EV − PV
- Cost Variance (CV) = EV − AC
- Cost Performance Index (CPI) = EV / AC
- Schedule Performance Index (SPI) = EV / PV
- Estimate at Completion (EAC): forecast final cost
- Estimate to Complete (ETC): remaining cost
3.2.1 Worked Example: Monthly EVM Snapshot
Assume a project has these planned values and costs for a reporting month:
- PV = R 2,000,000 (planned work for the month)
- EV = R 1,600,000 (work actually completed value)
- AC = R 2,200,000 (actual cost incurred)
Compute variances:
- SV = EV − PV = 1,600,000 − 2,000,000 = −R 400,000 (behind schedule)
- CV = EV − AC = 1,600,000 − 2,200,000 = −R 600,000 (over budget)
Indices:
- CPI = EV/AC = 1,600,000 / 2,200,000 = 0.727
→ cost performance is poor; each rand spent earns only R0.727 of value - SPI = EV/PV = 1,600,000 / 2,000,000 = 0.800
→ schedule performance is below plan
A high-scoring exam answer also forecasts:
- If current performance continues, EAC might be calculated using CPI-adjusted methods.
- If issues are corrected, an alternative EAC formula might be used.
3.3 Performance Reporting: Dashboards, Status Reports, and Decision Triggers
A project’s performance management system needs consistent reporting cycles.
Common reporting artifacts:
- Weekly progress reports (work done, work planned)
- Monthly performance reports (EVM, risk status, quality metrics)
- Executive dashboards (high-level KPIs)
- Issue logs and change request summaries
- Quality control summaries (defects, inspection results)
3.3.1 Example KPI Set (Quality + Performance Together)
A balanced KPI set might include:
| Category | KPI | Target | Measurement Frequency |
|---|---|---|---|
| Schedule | SPI | ≥ 1.00 | Monthly |
| Cost | CPI | ≥ 1.00 | Monthly |
| Quality | First-pass yield | ≥ 95% | Weekly/biweekly |
| Quality | Defect density | ≤ 2 defects per 1,000 units | Monthly |
| Risk | % high risks with active mitigation | 100% | Monthly |
| Scope | Deliverables accepted (UAT/inspection) | ≥ planned count | Monthly |
Even if an exam question is theory-based, referencing integrated KPIs shows applied thinking.
3.4 Linking Quality Metrics to Performance Forecasts
A key DUT-type competency is describing feedback loops:
- If defect rates rise, rework increases.
- Rework consumes time and increases actual costs.
- Therefore, quality metrics should be included in forecasting models.
3.4.1 Scenario: Defect Spike and EVM Impacts
Assume a project’s QC shows:
- First-pass yield drops from 95% to 80%
- Rework hours increase by 30%
- Testing backlog increases because defects must be retested
Result:
- EV stagnates (less “earned” progress due to rework and delays)
- AC rises (more labor and materials for rework)
EVM signals:
- CPI decreases
- SPI declines
Corrective actions could include:
- Process audit to identify why defects increased
- Stop-the-line for specific assembly step
- Retraining on procedure
- Update SOP and checklists
- Increase sampling temporarily to protect schedule
3.5 Risk-Adjusted Performance Management
Performance cannot be managed without considering uncertainty. Risk management should feed into performance monitoring:
- High risks may threaten schedule milestones and quality acceptance.
- Mitigation effectiveness affects performance trends.
3.5.1 Example: Quality Risk with Supplier Materials
Risk: Supplier A might deliver steel with inconsistent tensile strength.
Impact:
- Potential failure in inspection
- Delays due to replacement or rework
- Increased cost due to testing and supplier claims
Controls:
- Incoming inspection increased frequency
- Supplier audit every 60 days
- Contract includes quality warranty clauses
Performance monitoring:
- Track supplier rejection rate
- Track lead time variability
- Include supplier-related quality failures in cost and schedule forecasting
3.6 Continuous Improvement: PDCA and Lessons Learned
Continuous improvement is how organizations learn and improve performance over time.
A standard framework:
- Plan: define objectives, identify problems, plan changes
- Do: implement changes in pilot or controlled environment
- Check: measure results using metrics (defects, cycle time, CPI/SPI, customer satisfaction)
- Act: standardize improvements or revise approach
3.6.1 Example: Applying PDCA to Construction Defects
Problem: recurring tiling defects leading to rework.
Plan: identify defect causes through inspections, create improved tile installation checklist.
Do: train installers and run checklist on one section of the building.
Check: compare defect rate in pilot section to baseline; measure rework hours.
Act: if improvement is confirmed, roll out checklist across all sections and update QA documentation.
An exam question might ask for:
- “Describe continuous improvement and how it ties to quality and performance.”
A strong answer references PDCA and the measurement of outcomes.
4) Integrated Management: Quality Assurance Under Constraints, Performance Trade-offs, and Change Control
In many exam scenarios, project teams are constrained by deadlines, budget limitations, stakeholder pressure, and operational realities. Integrated management is the skill of balancing quality and performance while dealing with changes, disputes, and trade-offs.
4.1 Trade-offs: Time vs Quality vs Cost (Why “Fast” Can Be Expensive)
A classic trade-off:
- Compressing schedule may reduce inspection time and increase defects.
- Increased defects lead to rework—raising costs and further delaying delivery.
A useful exam framing is to explain that:
- Short-term schedule decisions can cause long-term performance loss.
- Project managers should use data to make trade-off decisions, not assumptions.
4.1.1 Example: Overtime vs Quality Control
Scenario:
- A team insists on working overtime to meet a milestone.
- QC staffing remains the same, so inspections are late.
- Defects discovered later cannot be fixed quickly.
Result:
- Schedule appears “saved” initially, but final acceptance fails.
- Milestone slips due to retesting and rework.
An excellent answer suggests mitigation:
- Increase QC resources during critical phases
- Adjust staffing plan while protecting inspection frequency
- Define “fast-track acceptance” only if quality risk remains acceptable
4.2 Change Control as a Quality and Performance Mechanism
Change control is not only about scope; it affects quality and performance because changes can invalidate acceptance criteria and disrupt baselines.
A typical change control process includes:
- Submit change request (description, reason, affected baseline areas)
- Review and assess impact (quality, schedule, cost, risk)
- Approve/reject based on criteria (authority, contract conditions, project objectives)
- Update baselines and documentation
- Implement with traceability to ensure quality requirements still hold
4.2.1 Example: Design Change in Building Services
Change: Client requests upgraded ventilation capacity.
Quality impact:
- New specifications require testing and certification adjustments.
Performance impact: - Schedule: longer procurement for fans
- Cost: increased equipment cost
- Risk: increased integration complexity
Change control should trigger:
- Updated design documents
- Updated QA/QC testing plans
- Re-verification of acceptance tests
- Supplier lead time review
4.3 Handling Nonconformities Across Project Stages
Nonconformities should be managed differently depending on when they occur.
4.3.1 Early vs Late Nonconformities
- Early: easier to correct, cheaper, less disruption.
- Late: expensive, can require rework of finished work, can trigger contractual disputes.
An exam answer should mention:
- detection timing
- cost of change escalation
- need for early QC gates
4.4 Quality Gates and Stage Acceptance
Many projects use quality gates—formal checkpoints where deliverables must pass requirements before moving forward.
Examples of quality gates:
- Design approval gate (drawings reviewed and compliant)
- Prototype testing gate (performance verification complete)
- Construction phase gate (materials verified and workmanship acceptable)
- Commissioning gate (system performance verified)
- UAT/acceptance gate (stakeholder sign-off)
A quality gate should include:
- objective criteria
- evidence required (test reports, inspection checklists, signed sign-offs)
- responsible authority for approval
4.5 Managing Stakeholder Expectations: Quality of Deliverables vs Quality of Communication
Quality management includes:
- technical quality of outputs
- service quality of project delivery: clarity, responsiveness, transparency
Stakeholder satisfaction influences performance:
- if stakeholders lose confidence, they may request more changes or delay approvals
- if communications are poor, quality documentation may be missing, causing acceptance delays
Exam responses should treat stakeholder communications as part of the quality system:
- documented meeting outcomes
- decision logs
- traceability between requirements and acceptance criteria
4.6 Supplier and Contractor Quality Management
Projects often depend on external suppliers and contractors. Supplier quality management ensures external inputs meet requirements.
Key actions:
- supplier evaluation and prequalification
- quality requirements in contracts (specs, testing, documentation)
- supplier performance tracking
- supplier audits
- incoming inspection and acceptance sampling
- managing nonconforming supplier deliveries through NCR processes (nonconformance reports)
4.6.1 Example: Supplier Rejection Rate Trending Up
Suppose supplier rejection rate rises from:
- 2 rejects per 100 deliveries to
- 6 rejects per 100 deliveries
Performance impact:
- inventory holding increases
- schedule risks increase
- additional testing costs appear
Corrective actions:
- supplier root cause analysis request
- process change enforcement
- increased incoming inspection for a limited period
- contract remedy triggers if thresholds exceed
5) DUT-Focused Exam Application: Answering Quality & Performance Questions with Templates, Scenarios, and Mark-Routine Thinking
This final section consolidates how to approach DUT-style exam questions: structure, definitions, processes, tools, and the “mark routine” that turns content into marks. It also includes scenario practice based on common project management question patterns, including mixed quality-performance issues, EVM-style interpretation, and corrective action planning.
5.1 Building an Exam Answer Structure That Gains Marks
When a question asks for “Explain” or “Discuss,” a high-scoring answer typically uses this structure:
- Define the key term(s) (quality, assurance, control, performance)
- Differentiate related terms (quality vs performance, QA vs QC, quality vs grade)
- Describe the process (planning → assurance → control → corrective action → continuous improvement)
- Use tools/techniques (checklists, audits, RCA, EVM metrics)
- Apply to a scenario (what happens, what metrics change, what actions follow)
- Conclude with outcomes (reduced defects, improved predictability, stakeholder acceptance)
This structure prevents drifting into generic statements.
5.2 Common DUT Exam Topics and How to Frame Them
5.2.1 “Quality Plan” Questions
If asked: “Discuss the contents of a quality plan,” include:
- standards and requirements
- roles and responsibilities
- inspection/testing plan
- sampling strategy
- acceptance criteria
- nonconformance handling procedures
- records and documentation requirements
Add a scenario line:
- “For example, in a construction project, acceptance might rely on workmanship inspection checklists and test certificates.”
5.2.2 “QA vs QC” Questions
If asked: “Differentiate between quality assurance and quality control,” use:
- QA: process/system focus, audits, prevention
- QC: output focus, inspections/tests, detection
- Provide an example for each:
- QA: training verification and process audit
- QC: measurement and acceptance testing of delivered output
5.2.3 “EVM” Questions
If asked: “Explain Earned Value Management,” include:
- PV, EV, AC definitions
- key indices: CPI and SPI
- variances: SV and CV
- interpretation: what positive/negative indicates
- how it supports performance decisions
Add a short arithmetic example (like the one in Section 3.2) to show competence.
5.3 Scenario Practice 1: IT System Development with Quality Failures
Scenario: A university project is developing a student portal. The project reports it is “on track” because tasks are completed, but user acceptance testing shows frequent defects and the project is at risk of missing its final release date.
Quality evidence:
- First-pass yield drops below target
- Defect density increases
- Testing backlog grows
Performance consequence:
- More retesting increases actual cost (AC rises)
- Earned value may stagnate because “work completed” is not actually accepted until defects are corrected
Required exam answer elements:
- Explain QA vs QC in this context
- Provide corrective actions linked to root causes
- Link quality metrics to performance forecasts (CPI/SPI trend logic)
A strong response might specify:
- QA: audit development process (requirements traceability, coding standards, code reviews, testing procedures)
- QC: run structured testing gates (unit testing completeness, integration test coverage, regression testing)
- RCA: 5 Whys on defect clusters (requirements ambiguity, missing automated tests, code review gaps)
- Corrective action: add mandatory code review checklist, enforce test coverage requirements, adjust sprint definition-of-done
- Performance link: reduced defect rates improve EV realization at acceptance gates, stabilizing CPI/SPI
5.4 Scenario Practice 2: Construction Project with Late Nonconformities
Scenario: A road rehabilitation project discovers major workmanship nonconformities at a late stage—during final inspection and commissioning.
Quality implication:
- Nonconformities are expensive because the work has already been completed and partially covered.
- Acceptance may be delayed due to retesting and rework.
Performance implication:
- Schedule slips due to rework and retest cycles
- Budget increases due to repair costs and extended overheads
Expected exam answer:
- Explain the benefits of earlier quality gates (design approval, in-process inspections)
- Propose corrective actions:
- rework plan with revised QC checkpoints
- root cause analysis to prevent recurrence (e.g., training gaps, material quality variability)
- supplier engagement if materials were a contributing cause
- Propose preventive actions:
- update QC plan to increase sampling where risk is higher
- enforce checklists and hold points before cover-up stages
- ensure documentation readiness to avoid acceptance delays
5.5 Scenario Practice 3: Supplier Quality Drift and Project Forecast Changes
Scenario: A project uses a subcontractor to provide a key component. Over the past two months:
- rejection rate increases
- lead times extend
- inspection failures become more frequent
Quality metrics:
- incoming inspection failure rate up
- first-pass yield down in downstream work
Performance management:
- PV may remain unchanged because planned schedule assumes reliable deliveries
- EV is delayed because completed work is not accepted without correct components
- AC rises due to expediting, retesting, and replacements
Exam answer should:
- Show how supplier quality issues affect EV realization
- Propose corrective actions (supplier corrective action request, audit, contract remedies)
- Propose performance adjustments:
- update schedule assumptions
- revise procurement plan and buffer strategy
- adjust risk register and mitigation plan
5.6 “Mark Routine” Checklist for Quality & Performance Questions
Use the following checklist when writing exam answers:
Definitions (must include at least two key definitions)
- Quality: degree to which requirements are met
- Performance: achievement against objectives (time/cost/scope/outcomes)
- Grade (optional but high value): category/class not equal to quality
Differentiations (at least one differentiation)
- QA vs QC
- Quality vs performance
- Early vs late nonconformities
Processes (show the workflow)
- Quality planning
- QA (system/process audits)
- QC (inspection/testing)
- Nonconformance control
- Corrective/preventive action
- Continuous improvement (PDCA)
Tools and metrics (show at least two)
- Quality metrics: defect density, first-pass yield
- RCA tools: 5 Whys, fishbone
- Performance: EVM PV/EV/AC, CPI/SPI
- Risk: risk register linkage to performance forecasting
Application (must connect to a scenario)
- “Because defects increased, rework increased → AC rises → CPI drops → schedule slips → SPI declines.”
This checklist is aligned with how exam markers award marks: clarity + structure + application.
5.7 Conclusion: What a High-Scoring DUT-Level Answer Looks Like
A high-scoring answer on Project Quality and Performance Management (DUT) is not just a list of definitions. It demonstrates:
- a clear distinction between quality, QA, QC, and performance
- a full workflow from planning to corrective action
- quantitative thinking through quality metrics and performance indices
- integrated decision-making using risk, change control, and quality gates
Ultimately, project quality and performance management is about ensuring deliverables meet requirements and that delivery remains predictable and efficient—so stakeholders receive accepted outputs on time and within cost, with reduced defect recurrence and stronger trust in project governance.
