UNISA PUB3705 Public Project Management Exam Notes: Study Guide (SA Government Focus)

Public project management is the practical discipline of planning, organizing, leading, and controlling projects to deliver public value—on time, within budget, and with appropriate governance and risk management. UNISA’s PUB3705 (Public Project Management) is designed to help learners apply structured project management methods in public sector contexts, where stakeholders are diverse, compliance requirements are strict, and outcomes are measured in social impact as much as in financial performance. These exam notes focus on the core concepts, frameworks, and exam-ready problem-solving approaches typically assessed in PUB3705, with a strong South African government focus for public administration learners.

1) Public Project Management Foundations (PUB3705 Concepts, Governance, and Project Life Cycle)

What makes “public” project management different?

In private sector projects, success is often defined primarily by profitability, competitive advantage, and shareholder value. In the public sector, success must be defined by public value: improved services, equitable access, compliance with legal and policy requirements, accountability, and measurable outcomes for communities.

Key differences you should be able to explain in an exam:

Multiple accountability lines: to political leadership, to communities, to oversight bodies (e.g., Auditor-General), and to internal audit.
Stakeholder complexity: beneficiaries, community structures, labour unions, regulators, service providers, traditional leadership (where relevant), and national/provincial/municipal departments.
Governance and compliance: procurement legislation (e.g., Preferential Procurement Policy Framework Act—PPPFA), public finance management rules, and transparency requirements.
Risk posture: higher scrutiny; reputational and legal risk weigh heavily.
Outcome measurement: the benefits might be social, developmental, and long-term—not only immediate financial returns.

Core definitions and exam-friendly distinctions

A strong start in PUB3705 is to define and differentiate concepts correctly:

Project: a temporary endeavour with a defined start and end, undertaken to create a unique product, service, or result.
Program: a group of related projects managed in a coordinated way to achieve broader outcomes.
Portfolio: a collection of projects/programs managed to align with strategic objectives.
Public project: a project initiated by a public institution (national/provincial/municipal department, SOE, agency) to deliver public services or infrastructure, funded through public resources and governed by public sector rules.

Common exam trap: confusing process and project. Processes (e.g., procurement cycle) are ongoing; projects are time-bound with unique outputs (e.g., building a specific clinic, implementing a digital permit system by a set date).

Public project governance: why it matters

Governance is the system of roles, rules, and decision rights that ensure projects serve public interest, remain compliant, and receive the oversight needed for accountability.

In exam questions, governance often appears as:

Who approves the business case?
Who authorizes budget releases?
Who approves changes to scope?
Who monitors performance?
What are the escalation and reporting lines?

A typical public governance structure includes:

Accounting Officer / Accounting Authority: final responsibility for public funds and accountability.
Project Sponsor: ensures alignment to strategy and secures resources.
Steering Committee: strategic oversight and major decision-making (scope, cost, schedule changes, major risks).
Project Manager: day-to-day management and delivery.
Project Management Office (PMO): supports project controls, standards, reporting, and coordination across projects.
Internal Audit / Risk Committee: independent assurance and risk monitoring.
Audit and oversight bodies: retrospective evaluation (e.g., compliance with audit requirements, performance information).

Project life cycle in the public sector

While project life cycles vary by institution, exam answers generally expect a standard structure:

Initiation / Concept
- Identify problem or opportunity.
- Stakeholder analysis.
- Preliminary feasibility, options assessment.
- Draft business case and project charter.
Planning
- Detailed scope definition (deliverables, acceptance criteria).
- Work Breakdown Structure (WBS).
- Schedule development.
- Cost estimation and budget planning.
- Risk and procurement planning.
- Quality plan and communication plan.
Execution / Implementation
- Resource mobilization.
- Procurement execution.
- Managing contractors/suppliers.
- Monitoring progress and managing changes.
Monitoring and Controlling
- Track performance vs plan (cost, schedule, scope).
- Risk reviews and mitigation actions.
- Reporting dashboards for governance.
Closing / Handover
- Final acceptance tests.
- Lessons learned.
- Financial closure and audits.
- Operational handover and benefits tracking.

Public sector nuance: closing can be prolonged due to compliance documentation, variations/claims, and audits. Many learners lose marks by not discussing closing properly—be sure to include acceptance, documentation, and benefits evaluation.

The project charter and business case (what examiners look for)

Project Charter (often in initiation):

Purpose and background.
Objectives and expected outcomes.
High-level scope and boundaries.
Roles and responsibilities.
High-level schedule and budget range.
Stakeholder list and initial stakeholder needs.
Governance arrangements and reporting lines.

Business Case (often the “why approve?” document):

Problem statement and strategic alignment.
Options considered (do nothing, low-cost alternatives, full solution).
Costs (capex/opex if relevant), benefits, feasibility.
Risks and mitigations.
Value for money rationale.
Recommendation and approval request.

Exam tip: when a question asks “justify a project,” the expected answer uses business case logic: strategic alignment + feasibility + value for money + risk management + accountability.

Stakeholder management in public projects

Stakeholder management is central in public projects because service delivery affects many groups.

Stakeholder identification (practical approach)

Use a structured approach:

Create a list of parties impacted by the project.
Determine interests/needs and power/influence.
Identify likely positions (support, neutral, resist).
Plan engagement strategies (inform/consult/involve/empower).

Engagement strategies (common exam formats)

Inform: provide information (newsletters, public notices).
Consult: gather feedback (public hearings, workshops).
Involve: work with stakeholders to incorporate input.
Collaborate/Empower: joint decision-making or co-creation where appropriate.

Public sector constraints and “success criteria”

A public project can fail even if it technically builds what was planned, because it may fail governance, compliance, or stakeholder expectations.

Success criteria typically include:

Deliverables completed and accepted (quality).
Achieved schedule milestones (time).
Stayed within budget or within authorized thresholds (cost).
Compliance with procurement and financial rules.
Stakeholder satisfaction and service readiness.
Benefits realized (or measurable progress).

2) Planning for Delivery: Scope, Work Breakdown, Scheduling, Costing, and Procurement Strategy

Defining scope correctly: from problem to deliverables

Scope planning is one of the most tested areas because weak scope definition causes most public project failures: scope creep, poorly defined acceptance criteria, and disputes with contractors.

A reliable scope structure for exam answers

Use three layers:

Project objectives: what you want to achieve (outcomes).
Deliverables: what you will produce (outputs).
Activities/tasks: how you will produce deliverables.

Example exam framing you can adapt:

Objective: Improve access to primary healthcare services in Ward X.
Deliverables: renovated clinic facility, equipped consultation rooms, functional IT system, trained staff, operational guidelines.
Activities: design, procurement, construction, installation, training, system configuration, handover.

Scope boundaries and assumptions

Always include:

What is in scope (e.g., construction and equipment supply).
What is out of scope (e.g., staffing beyond initial training, separate medical staffing recruitment).
Assumptions (e.g., land availability, municipal approvals).
Constraints (e.g., budget ceiling, procurement lead times).

Work Breakdown Structure (WBS): the mechanics

A WBS decomposes the project into manageable components so planning, estimating, monitoring, and reporting can be performed.

How to build a WBS in an exam

Start with major deliverables.
Break each deliverable into work packages.
Break work packages into tasks.
Assign coding or numbering for reporting.

Use consistent levels. For example:

1.0 Clinic Renovation
- 1.1 Architectural works
  - 1.1.1 Demolition
  - 1.1.2 Building works
  - 1.1.3 Finishes
- 1.2 Electrical works
  - 1.2.1 Cabling
  - 1.2.2 Fixtures and installation
- 1.3 Plumbing works
- 1.4 Medical equipment installation
- 1.5 Commissioning and handover

What examiners want:

WBS must reflect deliverables.
Work packages must be identifiable and estimable.
Tasks should be measurable for progress tracking.

Scheduling: milestones, critical path logic, and dependencies

In public projects, schedules must account for lead times: procurement approvals, bid evaluation, contract signing, mobilization, and inspections.

Schedule fundamentals

Milestone: a significant event (e.g., “construction completed,” “facility handed over”).
Dependency: one task requires completion of another (e.g., procurement of electrical equipment depends on finalized electrical design).
Constraints: fixed dates (e.g., service delivery windows, compliance deadlines).

Exam-ready steps to develop a schedule

Identify tasks from WBS.
Determine logical sequence and dependencies.
Estimate durations and resource assumptions.
Create a network diagram (or logic-based ordering).
Calculate early and late start/finish (if using critical path).
Identify critical path tasks and buffer/float.
Develop baseline schedule and approval steps.

Even if the exam does not require full critical path calculation, you should explain:

how you would identify critical tasks,
how delays affect overall completion,
why schedule baseline matters for controlling variations.

Cost management: estimation, budgeting, and cost control

Public project cost management includes ensuring costs are estimated realistically, budgets are authorized properly, and variances are managed with governance controls.

Cost estimation methods (typical PUB3705 expectations)

Analogous estimation: based on similar past projects.
Parametric estimation: uses statistical relationships (e.g., cost per square meter for construction).
Bottom-up estimating: estimate each work package then aggregate.
Three-point estimating: optimistic, most likely, pessimistic values (useful for uncertain tasks).

Example numerical logic (consistent and exam-friendly)

Suppose a work package (e.g., installation of electrical panels) has three duration estimates:

Optimistic = 4 days
Most likely = 6 days
Pessimistic = 10 days

Using a simple PERT approach for expected duration:
[
T_e = \frac{O + 4M + P}{6} = \frac{4 + 4(6) + 10}{6} = \frac{4 + 24 + 10}{6} = \frac{38}{6} \approx 6.33 \text{ days}
]

This expected duration is then used in scheduling and cost estimation where daily cost rates or resource rates are applied.

Budgeting and baseline

A budget baseline typically includes:

Total budget by work package or phase.
Contingency for identified risks.
Provision for escalation if relevant.
Funding release schedule (important in public contexts with phased funding).

Procurement planning: aligning contracts with project needs

Public projects heavily depend on procurement: wrong procurement method, poor specifications, or weak contract management leads to delays and disputes.

Procurement considerations in a public project

Determine what must be procured (goods, services, works).
Specify requirements precisely to reduce ambiguity and variation risk.
Decide procurement method based on:
- market availability,
- complexity,
- value thresholds (institution policy and legal framework),
- urgency and fairness/competition principles.
Plan procurement lead times:
- advertising/tendering,
- bid evaluation,
- approvals,
- contract signing and mobilization.

Contract types and exam logic

While your module may not require deep legal analysis, it’s important to differentiate typical contractual approaches:

Lump sum: fixed total price; requires detailed scope/specifications.
Unit price: pay for quantities; useful where quantities vary.
Time and materials: flexible but risk of cost overrun if not controlled.

Exam scenario tip:

If scope is uncertain, avoid a purely lump sum approach without strong remeasurement mechanisms.

Quality planning: getting “right first time”

Quality in public projects is not only “construction quality,” but also process compliance and service usability.

Quality planning elements include:

Quality objectives and acceptance criteria.
Quality assurance vs quality control distinction:
- Quality assurance: process/system to ensure quality.
- Quality control: inspections/tests to verify.
Quality audits and checklists.
Standards alignment (technical standards, occupational health and safety where relevant).

Risk planning: integrate with schedule and budget

A risk plan should not be generic. It must connect risk responses to:

schedule buffers,
contingency budget,
procurement strategies,
communication and mitigation responsibilities.

A typical risk response plan includes:

risk event,
probability and impact assessment,
risk owner,
response strategy (avoid, mitigate, transfer, accept),
trigger indicators,
contingency actions.

3) Monitoring, Controlling, and Managing Changes: Performance Measurement, Risk, and Governance Reporting

Why monitoring and controlling are central to project success

Many public project failures aren’t due to poor initial planning alone; they occur when:

governance oversight is weak,
risks are not escalated,
change requests are not controlled,
reporting is delayed or incomplete,
contract management issues are ignored.

Monitoring is about tracking; controlling is about taking corrective action.

Performance measurement: cost, schedule, and scope controls

Baselines and variances

You need to compare actual performance to baseline:

scope baseline (what is approved),
schedule baseline (planned timeline),
cost baseline (approved budget).

Variances include:

schedule variance (late/early),
cost variance (over/under),
scope variance (scope creep).

In exam questions, when asked “what would you do next,” your answer should include:

Identify the variance and quantify it.
Analyse root causes.
Propose corrective actions.
Submit recommendations through governance processes.
Update baselines if changes are approved.

Earned Value Management (EVM): exam-relevant essentials

If PUB3705 includes EVM topics, examiners typically test conceptual understanding and basic calculations. EVM compares:

Planned Value (PV): value of work scheduled by a certain date.
Earned Value (EV): value of work actually completed.
Actual Cost (AC): cost actually incurred for the work completed.

From these, compute:

Schedule Variance (SV) = EV − PV
Cost Variance (CV) = EV − AC

And performance indices:

Schedule Performance Index (SPI) = EV / PV
Cost Performance Index (CPI) = EV / AC

Example for exam practice (consistent numbers)

Assume by Day 60:

PV = R 600 000
EV = R 540 000
AC = R 610 000

Compute:

SV = 540 000 − 600 000 = −R 60 000 (behind schedule)
CV = 540 000 − 610 000 = −R 70 000 (over budget)
SPI = 540 000 / 600 000 = 0.90
CPI = 540 000 / 610 000 ≈ 0.89

Interpretation:

SPI < 1: schedule performance is below plan.
CPI < 1: cost efficiency is below plan.

A high-mark exam answer adds:

what corrective actions are possible (resource reallocation, revise sequence, renegotiate contract deliverables where appropriate),
and how you would document governance escalation.

Managing change: change control systems

Change management in public projects is critical due to:

contractor claims and variations,
evolving stakeholder requirements,
compliance changes,
funding adjustments.

Change control process (typical exam sequence)

Receive change request (from sponsor/contractor/stakeholder).
Log and assess the change:
- impact on scope, schedule, cost, quality, risks, procurement.
Evaluate alternatives and recommend:
- accept, reject, defer, or revise.
Submit for approval to the change authority (often steering committee/sponsor/Accounting Authority).
Implement approved change:
- update documents, baselines, communicate stakeholders.
Close change:
- ensure revised acceptance criteria and update benefits tracking.

Common pitfalls

Approving changes informally (“verbal instructions”) without a documented process.
Updating schedule without updating cost baseline.
Ignoring procurement implications (change may require new procurement steps).

Risk monitoring and response execution

A risk register is a living document. Monitoring involves:

tracking risk triggers (early warning signs),
reviewing status periodically (weekly/monthly/at stage gates),
updating probability/impact and risk response effectiveness.

Risk response review example

If “delay in procurement approvals” has:

probability reduced due to early liaison with procurement office,
then:
update probability,
consider reducing contingency if governance allows.

Conversely, if approvals become slower than expected, increase probability and trigger escalation.

Contract management and stakeholder communication

Public projects often depend on contractors and service providers. Effective control includes:

progress reporting from contractors,
inspection and acceptance testing,
managing variations and claims,
ensuring contractor compliance with quality and safety requirements.

Communication plan elements:

what information to report,
to whom,
how often,
which format (dashboard, written report, steering committee minutes).

Exam scenario tip:
If asked for “reporting mechanisms,” include both:

operational reporting (weekly progress),
governance reporting (monthly steering committee update),
risk escalation (immediate escalation for high risks).

Governance reporting: what should appear in a typical project status report

A strong status report generally includes:

progress against milestones,
deliverables completed vs planned,
cost summary vs baseline,
schedule summary and critical path changes,
top risks and mitigation progress,
issues requiring decisions,
decisions taken by steering committee,
upcoming procurement and major activities,
compliance and quality checks,
next period plan.

A public project status report is not only numbers; it must demonstrate accountability and action.

4) Project Appraisal, Feasibility, Value for Money, and Benefits Management in Public Projects

Project appraisal: choosing the right project and the right option

In public sector contexts, appraisal is the gatekeeping mechanism that determines which projects to start and how to justify them.

What appraisal typically includes

Need assessment (what problem exists and who is affected).
Strategic alignment (how the project supports departmental/national priorities).
Demand analysis and beneficiaries.
Options analysis:
- do-nothing,
- low-cost alternative,
- full solution with different designs or implementation models.
Feasibility:
- technical feasibility,
- financial feasibility,
- institutional capacity feasibility,
- legal feasibility.
Risk assessment.
Value for money comparison.

Financial feasibility vs broader public value

Exams sometimes test that financial feasibility alone is insufficient in public administration:

A project can be financially costly but justified by essential service delivery (e.g., emergency infrastructure or health services).
Benefits may include:
- increased access,
- reduced travel time,
- improved health outcomes,
- reduced service interruptions,
- better compliance with regulations.

Value for Money (VfM): how to explain it clearly

Value for Money is a public management principle emphasizing that the project’s benefits justify its costs, considering both:

economy (minimize cost of inputs),
efficiency (optimize use of resources),
effectiveness (achieve intended outcomes).

A VfM explanation should include:

how alternatives compare,
what outcomes are improved,
how risks are managed,
how performance will be measured and verified.

Benefits management: from outputs to outcomes

A common exam question is to distinguish:

Outputs: what the project delivers (e.g., renovated clinic, deployed system).
Outcomes: what changes for beneficiaries and service performance (e.g., improved clinic turnaround time, reduced patient waiting time).

Benefits management involves:

Define benefits and link to project objectives.
Identify benefit owners and responsibilities.
Select KPIs (key performance indicators).
Plan measurement baseline and target values.
Track benefits post-implementation.

Example benefits logic (clinics)

Output: renovated clinic building.
Outcome: improved patient throughput and reduced waiting times.
KPIs:
- average waiting time (minutes),
- number of patients served per day,
- availability of medical equipment,
- percentage of patients treated within defined service standards.

Monitoring benefits vs completing the project

A public project may “close” administratively when construction is complete, but benefits realization continues after handover.

Exam-ready phrasing:

project close-out confirms acceptance and readiness,
benefits review evaluates whether outcomes occur (often during operational phase, e.g., 3–12 months after completion).

Stage gates and approval points

Appraisal results in decisions. Many public projects follow stage gates:

Gate 1: approve concept and business case direction.
Gate 2: approve detailed design and procurement strategy.
Gate 3: approve execution plan and contract award.
Gate 4: approve commissioning and handover.
Gate 5: benefits evaluation.

Your exam answer should show:

what documents are required at each gate,
who approves,
what evidence is expected.

Feasibility: technical, institutional, and compliance readiness

Feasibility is not only engineering or system development; it includes institutional readiness:

Can the department operate and maintain the deliverables after handover?
Are there trained staff and maintenance contracts?
Do procurement and supply chain systems support ongoing operations?
Are there compliance constraints (environmental approvals, safety compliance)?

Risk-adjusted appraisal: accounting for uncertainties

A strong public appraisal includes:

explicit risk analysis,
use of contingency budgets,
scenarios (best case/expected/worst case).

Risk-adjusted reasoning helps justify why:

schedule buffers exist,
contingency is allocated,
procurement method is chosen.

5) Exam-Ready Applied Practice: Problem-Solving in PUB3705 (Scenarios, Calculations, and Governance Decisions)

How to approach PUB3705 scenario questions

Most PUB3705 exam questions are scenario-based: you’re given a public project context and asked to:

identify issues,
propose corrective actions,
draft management plans (e.g., risk register entries, change control steps),
justify a decision (e.g., why a certain governance approach is needed),
compute basic performance metrics (sometimes EVM, sometimes cost/schedule variance),
explain how to manage stakeholders and compliance.

A practical method for high marks:

Read for the “action verb”: “explain,” “justify,” “recommend,” “calculate,” “outline,” “propose.”
Identify the decision context: initiation, planning, execution, or closure.
Pick the correct framework: WBS, risk management, change control, governance reporting, benefits logic, appraisal.
Use structured answer formatting: headings, numbered steps, bullet lists.
Use consistent terminology: scope baseline, schedule baseline, risk register, steering committee, sponsor, Accounting Officer.
Tie actions to governance and accountability: public projects require approval pathways.

Scenario 1: Clinic renovation with procurement delays and scope drift

Given: A provincial clinic renovation project aims to complete in 12 months with a budget baseline of R 12 000 000. During execution, procurement approvals delayed electrical components by 6 weeks. Meanwhile, stakeholders requested additional medical storage cabinets and an upgrade to finishes.

Tasks (exam-style) might include:

Identify issues and risks.
Recommend change control actions.
Propose corrective actions for schedule and cost control.
Suggest stakeholder engagement actions.

Step-by-step solution logic

Identify issues
- Delay: procurement approvals (schedule risk realized).
- Scope drift: extra cabinets and finishes (scope change without formal approval).
- Potential cost impact: additional materials, labour, and potential rework.
Update the risk register and escalate
- Confirm whether procurement delay was already in risk register.
- If not or if probability/impact changed, update it.
- Escalate to steering committee if it threatens milestone dates.
Apply change control
- Log change requests for storage cabinets and finish upgrades.
- Assess impact on:
  - scope baseline,
  - schedule baseline (installation and rework),
  - cost baseline (material and labour),
  - quality (standards),
  - procurement (new or amended orders),
  - risks (additional delay, contractor claims).
Corrective actions for schedule
- Fast-track non-dependent tasks (e.g., site preparation, plumbing works) where possible.
- Re-sequence activities so that work not dependent on delayed electrical components continues.
- Consider schedule compression only if quality and compliance remain feasible.
Corrective actions for cost
- Identify cost drivers:
  - overtime,
  - rework,
  - contract variations.
- Seek approvals for contingency use only for approved risk response or authorized changes.
- Prevent unauthorized spending.

Governance reporting content for this scenario

A status report should highlight:

milestone slippage due to electrical procurement delay,
progress against renovation deliverables,
estimated cost impact compared to R 12 000 000 baseline,
list of change requests submitted and whether approved,
top updated risks and mitigation actions.

Scenario 2: Calculating cost and schedule performance using EVM

Given: By Day 60, the baseline planned budget for the work scheduled is R 600 000 (PV). The planned value for completed work is R 540 000 (EV). Actual expenditure for the completed work is R 610 000 (AC).

Required:

Calculate SV, CV, SPI, CPI.
Interpret results.
Recommend actions.

Calculations (consistent with PUB3705 approach)

SV = EV − PV = R 540 000 − R 600 000 = −R 60 000
CV = EV − AC = R 540 000 − R 610 000 = −R 70 000
SPI = EV / PV = R 540 000 / R 600 000 = 0.90
CPI = EV / AC = R 540 000 / R 610 000 ≈ 0.89

Interpretation

SPI of 0.90 means less work has been achieved than planned by Day 60 (behind schedule).
CPI of 0.89 means the project is spending more per unit of work value than planned (over budget).

Recommendations (must be governance-aligned)

Conduct root cause analysis:
- schedule: dependencies, contractor performance, procurement delays?
- cost: overtime, rework, inefficient resource allocation?
Update forecasts (e.g., estimate EAC and TCPI conceptually).
Propose corrective actions:
- reallocate resources,
- renegotiate deliverable timelines,
- approve contingency use if justified by risk response,
- enforce change control for scope drift.

Scenario 3: Benefits plan and KPI definition for digital service delivery

Given: A municipality plans a digital permitting system project. The project delivers a system (output), but the exam expects you to show how you manage benefits (outcomes).

Task:

Propose 5 KPIs and define baselines and targets (you may use illustrative numbers if the question allows).

Example KPIs and structure (how to write it well)

Use an outcome focus:

Average permit processing time
- Baseline: 14 days
- Target: 7 days after go-live
Percentage of permits processed within SLA
- Baseline: 55%
- Target: 85%
User adoption rate
- Baseline: 0% digital usage (baseline time)
- Target: 60% of applications submitted digitally within 6 months
System availability
- Baseline: not applicable (new system)
- Target: 99.5% monthly uptime
Customer satisfaction
- Baseline: 60/100 (survey)
- Target: 80/100

Even if the exam uses different numbers, the structure matters:

KPI definition,
measurement method,
baseline,
target,
data source,
frequency.

Benefits ownership and post-project tracking

Assign benefit ownership:

project manager supports implementation,
operations manager owns service performance,
IT support owns uptime,
customer relations owns satisfaction metrics.

Include benefits review timing:

initial benefits review at 3 months post handover,
final measurement at 12 months.

Scenario 4: Handling a change request from a contractor claim

Given: A contractor requests a change due to unforeseen ground conditions. The request adds 4 weeks and R 250 000 to costs. The contract requires documentation and approval for variations.

Task:

Outline how to handle the change request responsibly.

A high-mark change control answer should include:

Log and review
- register variation request,
- ensure technical justification is attached.
Impact assessment
- cost impact (R 250 000),
- schedule impact (+4 weeks),
- scope impact (what deliverable changes),
- quality and safety implications.
Verify and validate
- independent assessment (engineer/technical committee),
- check whether conditions were predictable and if contingency should apply.
Procurement and contract compliance
- determine whether new procurement is required,
- ensure approvals follow public governance processes.
Decision and communication
- propose accept/reject/adjust options,
- communicate decision through steering committee and contract officer.
Update baselines and forecasts
- update schedule baseline if approved,
- update cost baseline or use contingency according to approved approach.

Scenario 5: Risk escalation and stakeholder resistance

Given: During a community water supply project, community members resist relocation because of misunderstanding. This creates protest risk and threatens compliance with construction access routes.

Task:

Propose risk response and stakeholder engagement plan.

Risk response approach

Identify risk category: stakeholder resistance leading to schedule disruption.
Assign risk owner: project manager with community liaison lead.
Response strategies:
- Mitigate: community engagement sessions and transparent communication.
- Avoid: adjust construction access routes if feasible.
- Transfer: not possible for stakeholder sentiment; keep mitigation internal.
- Accept: only if minimal impact and alternative access exists.

Stakeholder engagement actions

Inform: explain project purpose, timelines, and relocation arrangements.
Consult: workshops with community representatives.
Involve: co-design temporary access solutions and grievance mechanisms.
Empower: involve local committees in monitoring and reporting.

Governance escalation

If protests threaten safety or compliance:

escalate immediately to sponsor/steering committee,
coordinate with relevant public safety/community liaison bodies,
ensure decisions are documented.

Quick exam checklist (what to include in nearly every answer)

When you are unsure, use this checklist to structure your response:

Identify stage (initiation/planning/execution/closure).
State relevant concept (scope baseline, risk register, change control, benefits plan).
Use a framework: steps, categories, or headings.
Link to governance: steering committee/sponsor/Accounting Officer approval.
Include practical actions: corrective action, monitoring mechanism, documentation.
Provide calculations where required and interpret results clearly.
Avoid generic answers: anchor recommendations in the scenario.

Closing Consolidation: Master Themes You Must Be Able to Explain Clearly in PUB3705

Master theme 1: Accountability and governance are delivery tools, not bureaucracy

In public projects, governance ensures decisions are traceable, risks are managed transparently, and funds are used responsibly. The exam rewards answers that:

show who decides,
show what evidence is needed,
explain how reporting triggers corrective action.

Master theme 2: Scope control prevents cost and time collapse

Most public project cost overruns and schedule delays relate to unclear scope, poor acceptance criteria, or weak change control. A strong exam answer shows:

scope baseline discipline,
formal change requests and impact assessments,
acceptance criteria and quality assurance.

Master theme 3: Monitoring and controlling must connect to action

Monitoring reports are not the goal; controlling actions are. Strong answers:

quantify variances,
interpret meaning (e.g., SPI/CPI),
propose specific corrective measures,
escalate to the right governance structure.

Master theme 4: Benefits management is part of the project, not only the operational phase

Public value is measured through outcomes. High marks come from:

output-to-outcome mapping,
KPI definition with baseline and target,
post-handover benefits tracking.

Final Exam-Ready Summary of Key Terms (for fast revision)

Project: temporary endeavour with unique output/result.
Business case: justification for project approval (strategic alignment, feasibility, VfM, risks).
Project charter: authorization and high-level project direction.
WBS: decomposition of deliverables into manageable work packages.
Schedule baseline: approved timeline against which progress is measured.
Cost baseline: approved budget baseline for variance tracking.
Risk register: updated list of risks, owners, probabilities/impacts, responses, triggers.
Change control: formal process to assess and approve changes.
EVM: PV, EV, AC → SV, CV, SPI, CPI for performance interpretation.
Benefits management: measuring outcomes and public value after implementation.

If you want, I can also generate mock PUB3705 exam questions with memo-style answers (including scenario-based EVM, risk register entries, and change control proposals) using South African public sector contexts.