Advanced Diploma in Project Management (CUT) Course Material — Exam Notes & Study Guide (NGP0000 / PMP / Proj Planning)

The Advanced Diploma in Project Management offered through the Central University of Technology (CUT) is built for learners who must demonstrate both planning discipline and professional project leadership. These notes translate typical CUT project management course material—including the kinds of work you see in South African university modules—into exam-ready explanations, frameworks, worked examples, and scenario practice. The guide is designed to help you answer “what”, “why”, and “how” questions with the same clarity you’d use in CUT assignments, online tests, and final examinations.

1. CUT Advanced Diploma in Project Management: Module Structure, Learning Outcomes & How Exams Test You

CUT’s Advanced Diploma in Project Management (and closely related diplomas/advanced certificates in project management) generally focuses on the practical application of project concepts: scope, scheduling, risk, cost, procurement, stakeholder management, quality, and governance. Across South African institutions, especially in the project management cluster, exam tasks usually require you to:

• Define a concept accurately (e.g., “stakeholder register”, “WBS”, “EVM”)
• Apply the concept to a scenario (e.g., “build a risk register from a case”)
• Justify decisions using project management logic (e.g., “why update schedule baselines”)
• Analyse trade-offs (e.g., “fast-tracking vs crashing and cost implications”)
• Evaluate compliance and professional standards (e.g., governance, ethics, reporting)

Even when module codes differ between universities and qualification versions, exam styles remain consistent. CUT learners are often tested on core knowledge areas aligned with recognized project management bodies (such as PMI-style knowledge areas) and with project governance practices.

1.1 Typical CUT-focused learning outcomes you must be able to demonstrate

In most CUT project management offerings at advanced diploma level, learning outcomes are built around demonstrable competence. In exam answers, you should show competence through structure:

1. Concept clarity
   Explain the concept and its purpose in project delivery.
2. Process steps
   Break the process into steps (inputs → tools & techniques → outputs).
3. Application
   Apply the concept to an example: a construction project, IT rollout, facility upgrade, or community programme.
4. Risk & control
   Explain how control is achieved: monitoring metrics, change control, reporting cadence, audit points.
5. Professional alignment
   Relate to governance and ethical practice: procurement fairness, stakeholder inclusion, documentation discipline.

If you structure your responses in that order, your marks usually improve because examiners can locate the required elements.

1.2 How exam questions are commonly phrased in project management modules

South African university exams (including CUT) frequently use a few recognizable question patterns:

• Short definition questions
  “Define WBS.” “What is a stakeholder register?”
• Structured explain-and-justify questions
  “Explain how risk response planning links to monitoring.”
• Scenario tasks
  “Given a project with delays, calculate schedule impact and propose corrective actions.”
• Framework construction
  “Draft a risk register table for the provided scenario.”
• Critical evaluation
  “Discuss why poor change control causes cost overruns.”
• Calculations
  “Calculate EAC using given BAC, AC, CV, and CPI,” etc.

A common issue: learners can define terms but cannot apply them. The cure is practice with scenarios and consistent use of process logic.

1.3 Key terminology you should standardize in your answers

To perform well, you must use consistent terms correctly. Below is a “terminology anchor list” that you can reuse across exam answers.

• Project: Temporary endeavour with a defined beginning and end, producing a unique deliverable.
• Programme: Grouping of projects managed together to deliver outcomes.
• Portfolio: Collection of programmes/projects managed to align with strategy.
• Deliverable: Tangible/verify-able output.
• Milestone: Significant event marking progress.
• Scope: Work included/excluded; product scope and project scope.
• WBS (Work Breakdown Structure): Hierarchical decomposition of project work.
• Activity: Work package scheduled and assigned to resources.
• Baseline: Approved plan (scope baseline, cost baseline, schedule baseline).
• Change Control: Process to evaluate, approve/reject, and implement changes.
• Risk: Uncertain event that, if it occurs, affects objectives.
• Issue: Known problem already happening (risk becomes issue when it occurs).
• EVM (Earned Value Management): Technique integrating scope, schedule, and cost.
• KPI/KRI: Measures for performance and risk monitoring.
• Stakeholder register: A tool listing stakeholders and engagement needs.
• Governance: Policies and decision structures ensuring accountability.

Examiners reward precision. If you define “risk” as a “known issue” or “issue” as a “potential risk,” you often lose marks.

1.4 Building high-scoring exam answers: the “CUT approach” template

A reliable response template for scenario-based questions:

1. Restate the problem in 2–3 lines using case details.
2. Identify key management area (scope, cost, schedule, risk, procurement, quality, stakeholders).
3. List assumptions if the question implies missing information (but do not invent facts).
4. Use the correct framework/process:
   • For risk: identify, analyse, plan responses, implement, monitor.
   • For schedule: sequence, estimate durations, develop schedule, control schedule.
   • For cost: estimate costs, budget, control costs.
5. Propose actions with reasoning (not just “do X”).
6. Conclude with expected benefit (e.g., improved predictability, reduced variance, stronger stakeholder alignment).
7. Add evidence: short calculation, mini-table, or example deliverable.

This structure is especially helpful in advanced diploma-level exams because questions often mix theory with application.

1.5 South African university relevance: aligning with common CUT/project management course content

South African students often cross-check content with similar modules in other universities. In Unisa-style and other South African project management programmes, you typically see elements like:

• Project planning and scheduling
• Budgeting and cost control
• Risk management
• Procurement and contract management
• Quality management
• Stakeholder management and governance
• Project monitoring and evaluation

CUT learners may see different module codes, but the exam logic and learning expectations match these content clusters. Your answers should therefore mirror what those modules test: practical correctness + structured reasoning.

2. Project Planning & Scope Control in CUT Projects: WBS, Scheduling Logic, Change Control, and Baselines

Project planning is where many marks are earned quickly—because you can show discipline. Planning is not “making a timetable”; it is establishing a baseline, defining scope, and ensuring that future control is possible. Advanced diploma-level assessments typically expect you to understand the logic chain from scope definition to schedule development and then to control mechanisms.

2.1 Scope management fundamentals: from charter to requirements to WBS

A strong answer begins with the scope chain:

• Project Charter / Initiation
  Establishes why the project exists, high-level objectives, and high-level scope boundaries.
• Requirements / Scope definition
  Determines what needs to be delivered and acceptance criteria.
• WBS creation
  Decomposes deliverables into manageable work packages.
• Scope verification & acceptance
  Confirms deliverables meet requirements.
• Scope control / change control
  Prevents uncontrolled “scope creep.”

Case-style example: Community Library Upgrade (mini-scenario)

Imagine a project to upgrade a community library:

• Deliverables: refurbished reading room, updated shelving, computer terminals, accessibility improvements.
• Constraints: must be completed before the winter school term.
• Key stakeholders: library committee, local municipality, IT provider, contractors, learners.

In scope planning, you would convert that into a WBS structure:

1. 1.0 Project Management
   • 1.1 Governance & reporting
   • 1.2 Project controls (scope, schedule, cost)
2. 2.0 Facilities Upgrade
   • 2.1 Reading room refurbishments
   • 2.2 Accessibility improvements
3. 3.0 Technology & Terminals
   • 3.1 Hardware procurement
   • 3.2 Installation and testing
4. 4.0 Shelving & Fit-out
   • 4.1 Shelves delivery and assembly
5. 5.0 Commissioning & Handover
   • 5.1 System testing
   • 5.2 Final inspections and handover documentation

Your WBS should not be “too high-level” (otherwise it can’t drive schedule and cost estimates). But it also should not be extremely detailed where planning becomes impossible.

2.2 Decomposition rules: how examiners expect your WBS to be structured

A good WBS in exam answers often follows decomposition logic:

• Start with major deliverables.
• Decompose down into work packages that can be:
  • scheduled,
  • assigned to responsible parties,
  • estimated for cost,
  • monitored for completion.

Common WBS decomposition mistakes (and how to avoid them)

• Mistake 1: Mixing deliverables and activities
  WBS should represent work required to produce deliverables; activities live in the schedule, not in the WBS headings.
• Mistake 2: No clear “work package” boundaries
  If a work package is too broad, it becomes impossible to track progress and cost.
• Mistake 3: Forgetting management and control work
  Exams sometimes include surprises: you lose marks if you omit governance tasks, reporting cadence, or quality assurance.

2.3 Activity definition & sequencing: logic that makes a schedule believable

After WBS, you define activities. For scheduling you need logic:

• Activity sequencing (what must happen before what)
• Logical relationships:
  • Finish-to-Start (FS) — simplest dependency
  • Start-to-Start (SS)
  • Finish-to-Finish (FF)
  • Start-to-Finish (SF) (rare; examiners may still expect you know it)

Worked scheduling micro-example

Suppose the library upgrade has:

• A1: Remove old shelving (2 days)
• A2: Install new shelving (3 days) depends on A1 (FS)
• A3: Order shelving (5 days) can start immediately (no dependency)
• A4: Fit computers (2 days) depends on A2 and A3 delivery

You’d show dependencies clearly:

• A1 → A2 (FS)
• A3 independent start
• A2 and A3 → A4 (FS)

Even if the exam question doesn’t require a full network diagram, it usually rewards correct dependency reasoning.

2.4 Estimating durations: deterministic vs range-based thinking

In advanced project management, duration estimation is rarely “one single truth.” Exams may include questions about uncertainty:

• Deterministic estimates (single number)
• Three-point estimates (optimistic, most likely, pessimistic)
• Range estimates and probabilistic scheduling concepts

If a question provides only one duration per activity, you apply it directly. If it provides three values, you should apply expected value logic (common in PERT-style thinking).

Example: Three-point estimate

If an activity has:

• Optimistic (a) = 2 days
• Most likely (m) = 4 days
• Pessimistic (b) = 8 days

Expected duration (commonly used PERT approximation):
[
t_e = \frac{a + 4m + b}{6} = \frac{2 + 16 + 8}{6} = \frac{26}{6} \approx 4.33 \text{ days}
]

Your exam answer should mention assumptions: that uncertainty is captured using optimistic/most likely/pessimistic and that duration variance informs risk planning.

2.5 Developing the schedule & using baselines

A schedule baseline typically includes:

• activity list
• durations
• dependencies
• critical path (if applicable)
• start/finish dates
• milestones

A schedule baseline is crucial because control depends on comparison against the baseline.

Critical path concept: why it matters

The critical path is the longest path through the network logic that determines minimum project duration. Any delay on critical path activities delays the project finish date unless recovery actions occur.

In exam scenario questions, you must:

• identify which activities are likely on the critical path,
• explain why delays matter more there than on non-critical paths,
• propose schedule recovery actions (re-sequence, add resources, review dependencies, fast-track).

2.6 Baseline management: controlling scope and schedule changes

Advanced diploma-level questions often test your understanding that baselines are not “recommendations.” A baseline is an approved plan that can only change through controlled change management.

Change Control Process (exam-ready steps)

A typical change control process includes:

1. Change request submitted
   (written, includes description and reason)
2. Impact analysis
   scope, schedule, cost, quality, risk implications
3. Review by relevant authority
   project manager + steering committee + functional stakeholders as required
4. Decision: approve or reject
   or approve with modifications
5. Update baselines (if approved)
   scope baseline, schedule baseline, cost baseline
6. Communicate changes
   update stakeholders and project documentation
7. Implement and verify
   ensure changes delivered as approved

Counter-argument exam move: “Why not just update informally?”

If the question asks “why not informally update the schedule,” you respond:

• Informal updates break the audit trail and governance.
• They reduce predictability and accountability.
• They make variance analysis impossible (you can’t compare to baseline).
• They can create conflicts with contract terms and procurement documentation.

2.7 Scope creep: diagnosing and controlling it

Scope creep usually occurs when:

• requirements are added informally,
• approvals are missing,
• stakeholders assume changes are “part of the deal,”
• documentation is weak,
• acceptance criteria are unclear.

In exam answers, always link scope creep to control tools:

• maintain requirements traceability (if taught in module)
• maintain a change log
• require impact assessment for every change
• align with procurement and contract terms
• confirm acceptance through defined sign-offs

2.8 Integration: how planning decisions affect cost and risk

Finally, planning is integrated. Poor scope planning causes:

• rework (quality risk)
• missed milestones (schedule risk)
• increased cost (cost overrun)

Therefore, advanced exam answers must show integration:

• WBS drives cost estimates and budgeting.
• Activity logic drives schedule and resource planning.
• Baselines drive control and reporting.
• Risk identification often starts from scope and assumptions.

3. Risk, Quality, and Procurement/Contracts in CUT-style Advanced Assessments: Registers, Response Strategies, EVM-lite, and Governance

Advanced Diploma project management exams often combine multiple knowledge areas in one scenario. A frequent pattern is: “The project is late and over budget; propose risk and quality responses, and recommend procurement adjustments.” This section builds the integrated toolkit you need.

3.1 Risk management cycle: identify → analyse → plan → implement → monitor

An exam-ready risk management answer should follow the cycle:

1. Risk identification
   • sources: scope uncertainty, market conditions, supplier capacity, technical complexity, regulatory issues.
   • methods: brainstorming, interviews, checklists, SWOT, lessons learned.
2. Qualitative analysis
   • likelihood and impact (often rated High/Medium/Low or a numeric scale).
3. Quantitative analysis (if asked or data available)
   • expected monetary value (EMV), simulation, decision trees.
4. Risk response planning
   • strategies: avoid, mitigate, transfer, accept; for positive risks: exploit, enhance, share.
5. Risk register creation
   • fields: risk description, cause, event, probability, impact, score, owner, response strategy, contingency plan, triggers.
6. Implementation
   • assign resources to risk response actions.
7. Monitoring and control
   • track risk indicators (KRIs), review changes, update risk register.

3.2 Risk register: a complete exam table structure (with realistic entries)

Below is an exam-style risk register you can adapt. Use it to practice answer writing.

Risk ID	Risk event (what might happen)	Cause/driver	Likelihood (1-5)	Impact (1-5)	Score	Owner	Response strategy	Triggers/Indicators	Contingency
R1	Supplier delays cause materials late	Procurement lead times underestimated	4	4	16	Procurement Manager	Mitigate (expedite orders) + Mitigation with alternate supplier	Late confirmation from supplier; order not shipped by week 2	Use alternate supplier or local buy
R2	Scope changes from stakeholders	Requirements not frozen	3	3	9	Project Manager	Avoid (requirements baseline) + Mitigate via change control	New requirements submitted outside change process	Approve only with formal impact assessment
R3	Rework due to quality defects	Incomplete inspection plan	3	5	15	QA Lead	Mitigate (QA plan, inspections)	Defect rate rising at acceptance tests	Re-inspect and replace affected components

Scores are typically computed as Likelihood × Impact. This structure aligns with many CUT exam expectations because it shows both planning and control.

3.3 Response strategies: when to choose avoid vs mitigate vs transfer vs accept

Learners often list strategies without matching them to the nature of risk. High marks require alignment:

• Avoid: eliminate the cause or stop the activity.
  Example: if regulatory approval is impossible within schedule, redesign scope to remove a regulated deliverable.
• Mitigate: reduce probability/impact.
  Example: mitigate supplier delay by multi-sourcing and early order placement.
• Transfer: shift impact to another party (e.g., insurance, contract clauses).
  Example: transfer construction risk to contractor via performance guarantees (but note: you still manage contract performance).
• Accept: no active changes; plan contingency.
  Example: minor risks with low score; document and monitor.

Counter-argument you should know: “Transfer is not offloading”

In procurement, transferring risk via contract does not remove the need for:

• vendor management,
• contract oversight,
• claims administration,
• performance measurement.

In exams, a brief statement like “risk is transferred but not eliminated; the project remains accountable for outcomes” often boosts quality.

3.4 Quality management in projects: quality planning and control

Quality management in advanced diploma project management typically includes:

• Quality planning: define quality standards, acceptance criteria, and methods.
• Quality assurance: systematic activities to ensure standards are followed.
• Quality control: operational techniques to measure deliverables and correct defects.

In a library upgrade scenario, quality might include:

• accessibility compliance (ramps, signage, door clearances)
• electrical safety checks for computers
• workmanship standards for refurbishments
• usability testing for terminals

Example: quality control plan snippet

For a “fit computer terminals” activity:

• Inspection points: pre-install wiring check, post-install functional test.
• Acceptance criteria:
  • terminals boot within a defined time,
  • peripherals function,
  • cable management meets safety standard,
  • documentation delivered (manuals, warranty cards).
• Method: test scripts, checklist-based inspections, sign-off by QA lead and IT provider.

3.5 Procurement and contracts: request, evaluate, contract manage

Procurement in project management is not just buying; it is controlling supplier contribution to project outcomes.

Common procurement questions in exams include:

• difference between purchasing and procurement planning
• procurement strategy selection
• tendering and contract types
• contract management and performance reporting

Procurement planning steps (exam-friendly)

1. Identify what to procure based on WBS and scope.
2. Decide procurement approach:
   • single vendor vs multiple vendors,
   • competitive bidding vs framework agreements,
   • buy vs make.
3. Define contract terms:
   • deliverables, timelines, quality standards,
   • payment terms (milestone-based vs time-based),
   • penalties/bonuses (if applicable),
   • acceptance criteria and handover documentation.
4. Conduct evaluation:
   • price, quality capability, delivery track record, compliance requirements.
5. Award and contract signing.
6. Manage supplier performance:
   • progress reports,
   • site inspections,
   • defect management,
   • variations and claims handling.

3.6 Contracts: common clause areas that appear in scenario answers

Even if your course does not list contract law in detail, exams often reward awareness of key clauses:

• Scope of work / deliverables
• Performance standards
• Delivery schedule and milestones
• Liquidated damages / penalties (if taught)
• Change management and variation procedures
• Warranty and maintenance
• Acceptance testing and sign-off
• Payment terms
• Dispute resolution
• Termination conditions
• Confidentiality and data protection (where relevant)

In a scenario where delays occur due to supplier issues, you should refer back to:

• contract milestones,
• supplier obligations,
• variation approval,
• claims process.

3.7 EVM-lite: connecting risk/quality problems to cost and schedule variance

While full EVM calculations might appear in other sections, advanced diploma exams often expect conceptual understanding—sometimes with calculations.

Key EVM-lite metrics:

• BAC (Budget at Completion): total budget baseline.
• PV (Planned Value): planned work value by a date.
• EV (Earned Value): value of work actually performed.
• AC (Actual Cost): actual cost incurred.

Performance:

• Schedule Variance (SV) = EV − PV
• Cost Variance (CV) = EV − AC
• CPI (Cost Performance Index) = EV / AC
• SPI (Schedule Performance Index) = EV / PV

Mini calculation example

Assume:

• BAC = R 1 000 000
• PV = R 400 000 (planned by now)
• EV = R 320 000 (earned work)
• AC = R 380 000 (actual spent)

Compute:

• SV = EV − PV = 320 000 − 400 000 = −R 80 000 (behind schedule)
• CV = EV − AC = 320 000 − 380 000 = −R 60 000 (over budget)
• CPI = EV / AC = 320 000 / 380 000 ≈ 0.84

Interpretation in exam terms:

• CPI < 1 indicates cost inefficiency.
• SV negative indicates delayed progress.

Then link to risk/quality:

• delays might be driven by supplier risk,
• overrun might be driven by rework (quality defects).

3.8 Governance and ethics: why procurement failures matter in exams

South African project management assessments commonly expect you to mention governance issues such as:

• transparency,
• accountability,
• documentation,
• conflict of interest avoidance,
• fair procurement processes,
• contract compliance.

If a scenario implies irregular procurement or poor vendor evaluation, you must connect governance to outcomes:

• non-compliance causes delays,
• disputes and claims become more likely,
• project credibility suffers.

A strong exam answer includes a line like: “Governance ensures decisions are auditable and defensible; this reduces disputes and stabilizes delivery.”

4. Stakeholder Management, Communications, Reporting & Monitoring/Evaluation for CUT Project Success

Project management at advanced diploma level includes managing people and information. Many failing answers in scenario questions ignore human factors or communication governance. In CUT-style assessments, stakeholder management and communication are tested both as theory and as practical response to “conflict, delays, and poor visibility.”

4.1 Stakeholder identification and analysis: building a map that drives action

Exams typically ask you to:

• identify stakeholders,
• assess their interest and influence,
• determine engagement strategy.

A common approach uses a power/interest grid:

• High power / high interest: manage closely, keep informed, involve actively.
• High power / low interest: keep satisfied, brief regularly.
• Low power / high interest: keep informed, collaborate.
• Low power / low interest: monitor with minimal effort.

Example: stakeholder list for the library upgrade

• Library committee: high power / high interest
• Local municipality: high power / medium interest
• IT provider: medium power / high interest (depends on scope)
• Learners and parents: low power / high interest (beneficiaries)
• Contractors: medium/high power / medium interest
• Government accessibility inspector: high power / low interest (periodic compliance gatekeeping)

A strong exam response uses this to justify engagement plans.

4.2 Stakeholder engagement plans: from registers to communication methods

A stakeholder engagement plan typically contains:

• stakeholder name/role
• needs and expectations
• influence level
• communication frequency
• communication method (meetings, emails, reports, workshops)
• owner (who communicates)
• purpose (inform, consult, involve, collaborate, empower)
• risk: stakeholder resistance likelihood
• escalation triggers

Communication matrix example (mini)

Stakeholder	Need/expectation	Frequency	Method	Owner	Purpose
Library committee	Timely completion before term	Weekly	Progress meeting + dashboard	Project Manager	Involve & manage expectations
Municipality	Compliance & approvals	Bi-weekly + ad hoc	Formal reports	PMO/PM	Satisfy & ensure approvals
IT provider	Installation schedule & acceptance	Weekly	Calls + acceptance checklist	Technical Lead	Collaborate
Accessibility inspector	Compliance gate at end	Per milestone	Inspection appointment	QA Lead	Inform & verify

In exams, you don’t need the full universe of stakeholders, but you do need to show that you understand who needs what and when.

4.3 Communications management: reporting cadence and meeting discipline

Communications are not just sending updates—they are designed to support decisions.

A practical communications model includes:

• Project kickoff communications (roles, responsibilities, governance).
• Routine status reports (progress, issues, risks, decisions required).
• Progress meetings:
  • weekly operational (execution status),
  • monthly steering committee (governance, decisions, escalations).
• Change notification communications (approved changes only).
• Issue escalation mechanism (time-bound and documented).

What examiners like to see

• A clear reporting cadence (weekly/monthly)
• Named roles for reporting (PM, QA lead, procurement manager)
• Inclusion of decisions required section
• A structured format: status, risks, issues, changes, next steps

If you include those headings in your answer, you usually appear well prepared.

4.4 Monitoring and evaluation (M&E): distinguishing monitoring vs evaluation

Advanced diploma exams may use terms loosely, so you must define them.

• Monitoring: ongoing measurement of progress against plan.
  Focus: are we on track?
• Evaluation: assessment of performance/outcomes at specific points.
  Focus: did we achieve intended benefits? why/why not?

In a library upgrade project:

• Monitoring: check construction schedule, procurement lead times, defect rates.
• Evaluation: assess user satisfaction post-launch, accessibility compliance verification, learning usage outcomes.

4.5 Performance measurement: KPIs for project delivery and quality outcomes

Exams often ask “what KPIs would you use.” Answer with both:

• delivery KPIs (schedule, cost, scope)
• quality KPIs (defects, acceptance pass rate)
• stakeholder KPIs (approval turnaround, satisfaction)
• risk KPIs (risk closure rate, KRI trends)

KPI examples (for library upgrade)

• Schedule:
  • % of milestones achieved on time
  • average days of slippage on critical activities
• Cost:
  • CPI and cost variance
  • forecast at completion
• Quality:
  • defect density per work package
  • number of rework cycles
  • acceptance sign-off rate at inspections
• Stakeholders:
  • stakeholder approval turnaround time
  • number of stakeholder escalations per month
• Risk:
  • risks closed as planned
  • KRIs that cross thresholds

4.6 Issue management: from identification to resolution and learning

Learners sometimes confuse risks and issues. In exam answers:

• Risk: uncertain; may or may not happen.
• Issue: occurred; requires action now.

Issue log fields typically include:

• issue description
• root cause (if known)
• impact (schedule/cost/quality)
• owner
• corrective action
• target date
• status (open/in progress/closed)
• verification method

Scenario-based example: recurring rework

If inspections show repeated defects in computer installations:

• treat as an issue (happening now),
• perform root cause analysis,
• update quality plan and technical checklist,
• potentially revise supplier performance expectations.

Then reflect learning into future projects:

• capture lessons learned,
• update templates, training, and QA procedures.

4.7 Forecasting: when reality diverges from baselines

Forecasting appears in many advanced diploma assessments as “what do you do when you see variance?”

Core steps:

1. Determine current performance (SV/CV, progress achieved).
2. Identify root causes:
   • scope change?
   • supplier delay?
   • rework?
   • resource constraints?
3. Update forecast:
   • EAC estimate (if taught)
   • revised completion date (if schedule impacts)
4. Recommend corrective actions:
   • schedule recovery plan
   • cost control plan
   • risk response updates
5. Communicate forecast to stakeholders and governance structures.

In your exam answer, ensure the actions are linked to the variance cause. “Over budget” alone is not enough; you must say why and then propose the response.

5. Integrative Project Management Practice for CUT Exams: Workflows, Calculations, Mini-Case Strategy, and “How to Answer” Under Time Pressure

This final section consolidates your skills into exam practice. It includes an integrated mini-case, a set of “likely exam tasks” and how to respond, and guidance on time management and answer style. The goal is to convert knowledge into a method you can apply in any CUT project management exam scenario.

5.1 Integrated mini-case: “Clinic IT & Facilities Modernisation” scenario

Use this mini-case to practice how different course material clusters connect.

Project: Clinic IT & Facilities Modernisation
Purpose: Improve service delivery via new computer terminals, updated infrastructure, and better patient record management processes.
Constraints: Must be completed before a clinic accreditation visit in October 2026.
Budget baseline (BAC): R 1 000 000
Planned progress date: end of August 2026
By end of August 2026, the project has:

• PV (Planned Value): R 400 000
• EV (Earned Value): R 320 000
• AC (Actual Cost): R 380 000

Additional scenario information:

• Supplier confirmed delivery for computer hardware two weeks late (risk event materialised).
• Rework required: one component installed incorrectly and had to be replaced.
• Stakeholder concern: clinic management is unhappy about unclear communication and expects daily status updates.

Your tasks in an exam-like style might include:

• Identify risks/issues and propose actions
• Recommend schedule and procurement responses
• Explain stakeholder communication plan
• Interpret the EVM-lite metrics and propose corrective actions
• Suggest quality control adjustments

5.2 EVM-lite interpretation: compute and explain in exam language

Using the values:

• SV = EV − PV = 320 000 − 400 000 = −R 80 000
• CV = EV − AC = 320 000 − 380 000 = −R 60 000
• CPI = EV / AC = 320 000 / 380 000 ≈ 0.84

Interpretation:

• Schedule variance negative: the project is behind plan.
• Cost variance negative: the project is spending more than the earned value—inefficient cost performance.
• CPI below 1: every rand spent is producing less value than planned.

Now link interpretation to scenario causes:

• supplier delay drives schedule slippage;
• rework drives increased actual cost.

Corrective action should therefore target both:

• schedule recovery,
• cost containment and quality prevention.

5.3 Schedule recovery strategies: fast-track, crashing, and logic revalidation

In exam scenarios, schedule recovery typically includes a mix of:

• Fast-tracking: overlapping activities that were originally sequential.
  • Example: start cabling slightly earlier while waiting for final shelving completion, if dependencies allow.
• Crashing: adding resources to critical activities to reduce duration.
  • Example: add technicians to installation/testing, within contractual and resource feasibility limits.
• Logic revalidation: check if dependencies are correct.
  • Often delays occur due to unrealistic dependencies.

Your answer should include caution:

• fast-tracking may increase risk and rework (quality cost).
• crashing increases cost and must be balanced with budget impact.

This is where advanced exam answers differ: you don’t just propose the action; you discuss trade-offs.

5.4 Procurement response: manage supplier delay and contract options

Supplier delay is now an issue/risk realised. Procurement response options include:

1. Expedite and recovery plan with supplier
   • request accelerated delivery,
   • confirm revised delivery dates,
   • agree on penalties/claims if contract allows.
2. Alternate sourcing
   • if critical components are time-sensitive,
   • confirm compatibility and warranties.
3. Contract variation control
   • ensure changes are documented and approved through governance.

A high-quality exam answer includes:

• evidence that procurement decisions consider contract terms,
• supplier performance monitoring (delivery confirmations, acceptance testing plan).

5.5 Quality response: reduce rework by strengthening QA and verification

Rework from incorrect installation becomes a quality issue. Quality actions:

• Update the installation checklist and acceptance criteria.
• Add inspection points:
  • before closing/installing components permanently,
  • after installation but before handing over.
• Conduct root cause analysis:
  • training gap?
  • ambiguous instructions?
  • tool/part mismatch?
• Implement corrective and preventive action:
  • training,
  • documentation,
  • revised method statement.

In exams, mentioning “preventive actions” and “inspection points” demonstrates advanced quality thinking.

5.6 Stakeholder communication plan: fix expectations and reduce conflict

Stakeholders expect daily updates; but daily reporting may not be sustainable or necessary. Advanced answers propose a tiered communication approach:

• Daily updates for leadership and escalation items (short format)
• Weekly detailed status report for governance and execution
• Monthly evaluation against objectives

For clinic management:

• Provide a daily “traffic-light” summary:
  • schedule status,
  • cost status,
  • top risks/issues,
  • decisions needed.

For governance:

• provide weekly narrative report with:
  • progress vs baseline,
  • risks updated,
  • issues with actions and owners.

This approach manages stakeholder concerns while preserving efficiency and avoiding information overload.

5.7 Risk-to-issue transformation: show control thinking

The supplier delay risk materialised—now it is an issue requiring active correction. In your exam answer, you should explicitly state:

• Risk R1 (supplier delay) → became issue “hardware delivery delay”
• Response must now include:
  • assignment of owner,
  • revised action plan,
  • updated schedule and baseline implications,
  • procurement actions and escalation.

This transformation often earns marks because it shows correct project control thinking.

5.8 How to answer common CUT exam tasks: ready-to-use templates

Task A: “Build a risk register from the scenario”

Use this structure:

1. Identify at least 3 risks and explain cause + event.
2. Provide likelihood and impact ratings (use a clear scale).
3. Compute a score (Likelihood × Impact).
4. Assign an owner.
5. Provide response strategy and triggers.

Task B: “Explain change control and its value”

Must include:

• steps in process,
• baseline update principles,
• why documentation matters,
• impact analysis: scope/schedule/cost.

Task C: “Interpret EVM metrics and recommend actions”

Must include:

• compute SV, CV, CPI if asked,
• interpret results,
• connect to root cause,
• propose corrective actions.

Task D: “Design stakeholder engagement”

Must include:

• stakeholder list,
• power/interest logic,
• communication method and frequency,
• owner.

5.9 Time management in a 2–3 hour CUT exam: a practical schedule

A typical exam may include a mix of theory and calculations. A realistic time plan:

• 10–15 minutes: read questions, highlight key requirements, identify which frameworks/calculations are required.
• 60–75 minutes: answer longer scenario parts (risk, stakeholder plan, change control, procurement actions).
• 25–35 minutes: calculations and interpretation (EVM-lite, scoring).
• 20–30 minutes: revise, check consistency of numbers, ensure each part contains required headings (definitions, steps, justification).

Consistency checks that help you avoid losing marks:

• Are all scores computed correctly and consistent?
• Did you use the same dates and budget values across answers?
• Did you match actions to causes?

5.10 Consistency checklist: numbers, dates, and assumptions

Because your exam answer is graded, inconsistency can cost marks. Use a quick checklist while writing:

• Budget values: BAC stays constant unless change control is discussed.
• EVM values: PV/EV/AC must match what was given.
• Scores: Likelihood × Impact must be computed identically across table and text.
• Dates: anchor your schedule logic to the scenario time horizon (e.g., “by end of August” and “accreditation visit in October 2026”).
• Terminology: risk vs issue must be correct.

5.11 Short “exam bank” answers you can adapt

Below are concise statement patterns you can use in longer answers.

• On WBS:
  “A WBS decomposes project scope into deliverables and work packages, enabling accurate estimation, scheduling, and control.”

• On baseline:
  “A baseline is the approved plan used for performance measurement; changes require formal change control to maintain traceability and governance.”

• On risk vs issue:
  “Risk is uncertain and may occur; an issue has occurred and requires corrective action and tracking through an issue log.”

• On EVM interpretation:
  “Negative SV indicates behind schedule progress, while negative CV and CPI below 1 indicate cost inefficiency relative to earned work.”

• On stakeholder engagement:
  “Engagement should be tailored to influence and interest levels, with communication frequency and method set to manage expectations and enable decisions.”

5.12 Final integrated practice: a sample answer outline for the mini-case

If the exam asks you to “respond to the scenario,” a high-scoring outline is:

1. EVM summary
   • compute SV, CV, CPI; state meanings.
2. Root cause analysis
   • supplier delay → schedule impact; rework → cost impact.
3. Risk/issue management
   • transform risks into issues; update risk register.
4. Schedule recovery plan
   • consider fast-tracking or crashing on critical activities; revise logic.
5. Procurement actions
   • contract review, expedite, possible alternate sourcing; documentation.
6. Quality corrective action
   • QA inspections, root cause analysis, preventive actions.
7. Stakeholder communication plan
   • tiered reporting; traffic-light daily; weekly detailed governance.

That outline directly maps to the knowledge areas CUT exams commonly test—scope/schedule control, risk/quality control, procurement governance, and stakeholder communication.

Closing note embedded in practice (not a warning):

The strongest performance in an Advanced Diploma in Project Management (CUT) Course Material exam comes from writing structured answers that show process thinking and decision reasoning—supported by correct calculations, scenario-driven justification, and consistent use of project governance concepts.