Postgraduate Diploma in Project Management (Regent) Exam Packs: A Comprehensive Study Guide (with UNISA/MNG/CUT-Style Practice)

The Postgraduate Diploma in Project Management (Regent) exam packs are typically built around the same core competencies assessed across South African project management programmes: planning and scope definition, risk and cost control, procurement and contract management, stakeholder engagement, monitoring and evaluation (M&E), and professional governance. This study guide is designed to help you prepare for exam-style questions by translating commonly tested frameworks into practical, mark-allocation-friendly answers—using the kind of structure and course-aligned language you will recognise from South African university study packs (including UNISA-style modules such as PJM (Project Management)-related content and MNG / PDM-type corporate management disciplines, as well as CUT’s process-and-assessment approach).

Because “Regent Business School Project Management Qualification Notes” form part of a larger collection, this guide focuses on what you need for exam packs: how to answer, what to include, how to apply theory to scenarios, and how to avoid the common marks-lost mistakes.

1) Understanding the Regent Postgraduate Diploma Exam Pack Format (and How South African Universities Typically Assess Project Management)

A strong exam pack strategy starts with understanding how South African universities (and professional diplomas like Regent’s) assess project management. Even when module codes differ (e.g., UNISA MNG/PJM-related modules or CUT business management-style applied assessments), the underlying assessment logic is consistent: students are expected to demonstrate not only knowledge of tools (like WBS, CPM/PERT, risk registers, earned value), but also the ability to apply them in a scenario, justify decisions, and show governance thinking.

1.1 What “exam packs” usually contain (and what markers look for)

In many Regent-style exam packs, you will find a combination of:

Short theory questions (define concepts, distinguish between terms, describe frameworks)
Problem-solving questions (calculations: budgets, earned value metrics, schedule interpretation)
Case-based scenario questions (stakeholders, procurement approach, risk response, M&E design)
Essay/structured responses (explain a process and justify choices)

Markers typically reward answers that:

Use clear headings and logical sequencing (especially for process questions).
Link every tool back to project objectives (time, cost, quality, scope, benefits, and governance).
Include justification, not just description (e.g., “we choose X because…”).
Show assumptions when the question provides insufficient data.
Include appropriate terminology (scope baseline, change control, risk response, stakeholder register, dependency mapping, etc.).

If you’ve prepared using UNISA-style guidance, the emphasis often matches what UNISA lecturers commonly require: a balance between theory and applied reasoning. CUT assessments often push similar applied competence: you don’t just list steps—you demonstrate how the steps work in a real situation.

1.2 Exam pack topics you must master for postgraduate-level marks

Even if the exact wording differs, most project management postgraduate exams test the same “backbone competencies”:

Project initiation and scope definition
- Problem statement, objectives, success criteria, deliverables
- Stakeholder identification and analysis
- High-level requirements and acceptance criteria
Planning and scheduling
- Work Breakdown Structure (WBS)
- Resource and cost estimation
- Network scheduling (Critical Path Method—CPM, or PERT)
Risk, procurement, and contract fundamentals
- Risk identification, analysis, and response planning
- Risk registers, mitigation vs contingency
- Procurement planning and contract types
Monitoring & controlling
- Change control, governance, reporting
- Earned Value Management (EVM) metrics when numerical questions appear
Quality, communication, and M&E
- Quality planning and quality assurance
- Communication plans and escalation procedures
- Monitoring indicators and evaluation logic

Your goal in an exam pack isn’t memorisation—it’s recognition + structured application.

1.3 A “mark-allocation” answer template that fits most Regent-type questions

For most scenario questions, use a consistent template. For example:

Identify the key issue(s) in the scenario (one or two sentences).
State the relevant project management concept/tool.
Apply the tool to the scenario with at least two concrete elements (e.g., stakeholders, risks, activities, budgets).
Justify why your choice is best for constraints described in the scenario.
Conclude with what outcomes you expect (e.g., reduced schedule variance, improved compliance, safer delivery).

Example mini-structure:

Issue: “The project is behind schedule because procurement is delayed and risk was not managed.”
Tool: “Use risk response planning + change control + procurement schedule integration.”
Apply: “Add procurement risk to the risk register, specify triggers and contingency procurement channels, update schedule dependencies.”
Justify: “This reduces the probability of procurement failure and creates a clear escalation path.”
Outcome: “Improves schedule performance and supports governance reporting.”

That kind of structured answer is typically what exam packs reward.

1.4 Common South African exam traps (and how to avoid them)

Below are frequent mistakes students make in Regent/UNISA/CUT-aligned assessment patterns:

Only defining terms without connecting to the question’s scenario
Fix: Add “What it means for this case is…” and include at least one applied detail.
Using tools without explaining inputs/outputs
Fix: For a WBS question, mention deliverables and how the WBS drives scheduling and estimating.
Confusing risk vs issue
Fix: Define risk as “uncertain event that may occur”; issue is “current problem requiring action.”
Assuming change control is just “approval”
Fix: Explain impact assessment, documentation, approvals, communication, and baseline updates.
EVM arithmetic errors
Fix: Write down formulas first, then substitute numbers carefully.
Procurement answers that ignore governance/compliance
Fix: Mention procurement planning, contract management, and performance reporting.

The exam pack advantage comes from consistently showing that you can manage projects as systems—not as disconnected topics.

2) Project Planning Mastery for Exam Packs: Scope, WBS, Scheduling, Budgeting, and Stakeholders (UNISA/MNG/CUT-Style Application)

Project planning is often the highest-weight area in project management postgraduate exams because it integrates nearly everything: scope drives deliverables; deliverables drive WBS; WBS drives schedules and cost estimates; governance and stakeholders influence approvals and change controls. This section is built to help you answer planning questions in a way that matches the structure South African universities frequently use for marks.

2.1 Defining scope and success criteria (so your exam answer “holds together”)

A postgraduate-level planning answer should clearly distinguish:

Project scope: what work will be done and what deliverables will be produced.
Product scope: the characteristics of the delivered product/service.
Project success: meeting time/cost/quality and achieving outcomes/benefits.

2.1.1 Objectives and success criteria: build them like an exam response

A good exam response includes:

Specific objectives (often SMART: Specific, Measurable, Achievable, Relevant, Time-bound).
Deliverables (tangible outputs).
Acceptance criteria (how stakeholders confirm the deliverables are complete).

Example scenario (used throughout this guide):
A municipality is implementing a 4-month “Smart Water Metering Pilot” to improve billing accuracy and reduce water losses. The project must deliver 1,000 smart meters, install the meters, integrate data collection with a billing system, train operational staff, and achieve regulatory compliance.

A strong planning answer would specify success criteria such as:

Delivery: “1,000 smart meters installed and operational by end of Month 4.”
Quality: “Billing system integration passes functional testing with at least 95% accuracy against sample readings.”
Compliance: “All meter types and installation practices meet regulatory requirements by Month 3.”
Benefits: “Billing accuracy improves, and water loss indicators reduce by a measurable baseline comparison (defined in M&E plan).”

This makes your answer consistent later when you discuss monitoring and evaluation.

2.2 Work Breakdown Structure (WBS): how to score high with structure, not just listing

Markers usually award points for the logic of your WBS:

It should be deliverable-based (not task-based only).
It should enable estimation and scheduling.
It should show hierarchy (levels).

2.2.1 Example WBS for the Smart Water Metering Pilot

A deliverable-based WBS may look like:

1.0 Project Management
- 1.1 Project initiation & governance setup
- 1.2 Risk management and reporting
- 1.3 Procurement coordination and contract management
2.0 Meter Procurement and Logistics
- 2.1 Supplier procurement and delivery tracking
- 2.2 Inventory management
3.0 Installation and Commissioning
- 3.1 Site preparation
- 3.2 Meter installation
- 3.3 Commissioning & verification testing
4.0 System Integration
- 4.1 Data collection configuration
- 4.2 Billing system integration
- 4.3 Interface testing
5.0 Training and Handover
- 5.1 Training materials and sessions
- 5.2 Operational handover and documentation
6.0 Compliance and Assurance
- 6.1 Regulatory compliance checks
- 6.2 Quality assurance audits
- 6.3 Final acceptance sign-off

2.2.2 Turning the WBS into exam-ready scheduling logic

Your answer should explicitly link WBS to:

Activity definition (each work package becomes activities)
Dependencies (installation depends on meter procurement; integration depends on installed meters and system configuration)
Resource allocation (installers, IT integrators, QA personnel)
Cost estimation (each work package has a cost element)

Even if a question does not ask for a full schedule, you should still show that you understand the chain from WBS → schedule → cost.

2.3 Scheduling: critical path thinking (CPM) without getting lost

At postgraduate level, examiners expect more than “list activities in order.” You should:

Identify dependencies,
Determine the critical path (the sequence that determines project duration),
Explain schedule risks and mitigation.

2.3.1 A simple CPM example tied to the Smart Water Metering Pilot

Assume these activity durations:

Activity	Description	Duration (weeks)	Predecessor(s)
A	Supplier delivery lead time	4	None
B	Inventory ready for install	1	A
C	Site installation (batch)	3	B
D	Meter commissioning & verification	1	C
E	Billing integration configuration	2	B
F	Interface testing & validation	1	D, E
G	Training & handover	1	F
H	Regulatory compliance checks	2	C

Project duration is determined by the path that yields the longest finish time.

Potential critical paths:

A → B → C → D → F → G
Durations: 4 + 1 + 3 + 1 + 1 + 1 = 11 weeks
A → B → C → H → (compliance impacts acceptance; assume acceptance sign-off waits until compliance checks are complete and then can be released alongside G)
Durations: 4 + 1 + 3 + 2 = 10 weeks, plus any tie-in to final acceptance.

If the acceptance and handover depends on both F and compliance completion, you must argue which finishes later. The exam-ready move is to explain that compliance checks may delay acceptance if they are on a path that overlaps with F.

2.3.2 Why critical path logic matters in exams

Exams often ask:

“Which activity delays the project the most?”
“Where should management focus resources?”
“What happens if Activity E slips by 1 week?”

If you understand critical path:

You can answer effect propagation (how a delay affects finish date),
You can justify re-planning decisions (crashing, fast-tracking, resource reallocation),
You can connect scheduling to risk management and change control.

2.4 Cost estimation and budgeting: building the cost model carefully

Cost planning is not just “add up costs.” You must consider:

Costs per work package,
Contingency vs management reserve,
Base cost baseline for monitoring.

2.4.1 Cost elements for the pilot (example categories)

For Smart Water Metering Pilot, the cost model might include:

Meters and accessories: cost of 1,000 smart meters (procurement)
Installation labour: installers and site support
IT integration: system configuration and testing
Testing and commissioning: verification tests
Training and handover: training sessions and documentation
Compliance and assurance: QA audits and regulatory checks
Project management overhead: PM, reporting, governance meetings
Contingency: for identified risks (e.g., supplier delays)
Management reserve: for unknown unknowns (not yet identified)

In an exam, even if numbers are not given, you should describe how you would separate these components.

2.4.2 Linking budgeting to Earned Value later (without confusion)

EVM requires:

Planned Value (PV): budgeted cost of work scheduled
Earned Value (EV): budgeted cost of work performed
Actual Cost (AC): actual spending

Your planning should create:

A baseline schedule (what work is planned when),
A baseline budget (what each work package is worth),
A method for measuring progress (percent complete rules).

If you haven’t built a measurement method, you risk EV miscalculation—which is a common exam trap.

2.5 Stakeholder identification and analysis: the “why” behind engagement plans

Stakeholders influence:

Scope acceptance,
Change approvals,
Compliance requirements,
Procurement constraints,
Operational handover.

2.5.1 Stakeholder register: what to include

In exam answers, include at least:

Stakeholder name/role (or organisation role),
Interest (high/medium/low),
Influence/power (high/medium/low),
Position (supportive/neutral/resistant),
Communication needs,
Engagement strategy.

2.5.2 Example stakeholder map for the pilot

For the pilot, stakeholders might include:

Municipal Project Sponsor (high power, high interest): needs governance reporting and approvals.
Regulatory Compliance Officer (high power, medium interest): requires compliance documentation by Month 3.
IT Integration Lead (medium power, high interest): focuses on integration milestones and testing readiness.
Procurement Manager (high power, high interest): drives supplier lead times and contract terms.
Operational Staff / Water Services Team (medium power, high interest): requires training and acceptance of handover documentation.
Community Representatives (low to medium power, medium interest): may influence site access and responsiveness to installation activities.

In your exam response, you should explain how engagement strategies reduce friction:

Use governance meetings for sponsor alignment,
Provide compliance evidence early to avoid last-minute rework,
Schedule training close to handover,
Ensure site access processes are coordinated.

3) Risk, Procurement, and Contract Management for Exam Packs: From Risk Register to Response Planning (with Scenario-Driven Answers)

Risk and procurement are heavily tested because they connect planning to real delivery constraints. Students often lose marks by treating risk as a generic list. At postgraduate level, you must show:

risk identification with credible drivers,
qualitative or quantitative analysis,
response selection tailored to risk type,
procurement choices aligned to schedule and governance.

3.1 Risk management: distinguishing risk categories and making it actionable

A full marks risk answer normally includes:

Identify risks (uncertainty that can affect objectives).
Analyse risks (probability and impact; qualitative categories at minimum).
Plan responses (avoid, mitigate, transfer, accept, exploit opportunities).
Assign ownership (who manages each risk).
Set triggers and monitoring (what signals mean the risk is emerging).
Create a risk register (the exam-friendly output).

3.1.1 Risk vs issue: a critical distinction

Risk: may occur (uncertain). Example: “Supplier delays meter delivery due to logistics disruptions.”
Issue: has occurred (current). Example: “The supplier missed delivery date and meters are not on site.”

In the pilot scenario:

If meters arrive late, it begins as a risk (before the delay becomes confirmed).
Once confirmed, it becomes an issue needing recovery action and change control.

3.2 Example risk register entries for the Smart Water Metering Pilot

Below is an example risk register segment (qualitative scoring). Use this pattern in exam answers even if you can’t provide exact numbers.

Risk ID	Risk description	Probability	Impact	Category	Response	Owner	Trigger / Monitoring
R1	Supplier delay of smart meters	Medium	High (schedule, cost)	Schedule/Cost	Mitigate: dual-source options; track lead times weekly; keep contingency shipping	Procurement Manager	Delivery tracking shows variance >1 week
R2	Installation team availability shortfalls	Medium	Medium	Resource	Mitigate: reserve subcontractors; cross-train install team	PM + HR Liaison	Staffing roster shows capacity <80%
R3	Billing integration incompatibility	Low-Med	High (rework)	Quality/Integration	Mitigate: interface testing plan; involve IT early; use prototype testing	IT Integration Lead	Early test failures in sandbox environment
R4	Regulatory compliance evidence delayed	Low	High	Compliance	Avoid/Mitigate: compliance plan early; review documentation before submission	Compliance Officer	Submission readiness review misses milestone by 2 weeks
R5	Training not completed before handover	Medium	Medium	Adoption	Mitigate: schedule training in final month; confirm attendance	Training Coordinator	Training attendance < target by mid-final month

In an exam pack, the strength is not the “perfect scores”—it’s the logic and the actionability of each entry.

3.3 How to justify response strategies (avoid vs mitigate vs transfer vs accept)

A common postgraduate marking scheme rewards justification. Use the following logic:

Avoid: change plan to eliminate the risk driver (best when feasible early).
Mitigate: reduce probability and/or impact.
Transfer: shift impact to another party (e.g., insurance or contract clauses), without eliminating the underlying uncertainty.
Accept: do nothing besides having contingency plans and monitoring; appropriate when risk is low or mitigation is too costly.

3.3.1 Applied justification: R1 supplier delay

Avoid: You could restructure procurement to reduce reliance on one supplier (dual-source). That’s effectively “avoid” the single-point failure.
Mitigate: Weekly lead time tracking reduces uncertainty and enables faster recovery actions.
Transfer: Contractual clauses (liquidated damages, delivery guarantees) transfer some financial consequences—but not operational dependency.
Accept: If backup logistics are too expensive, you accept some residual risk but maintain contingency shipping options and a revised installation schedule.

Your exam answer should demonstrate that you understand transfer is not a magic fix.

3.4 Risk monitoring: triggers, thresholds, and escalation

Markers like to see that you know monitoring isn’t just reviewing the register—it’s about:

triggers,
decision rules,
escalation pathways.

For the pilot:

If delivery tracking shows meter lead time variance >1 week (trigger), then:
1. Procurement Manager escalates to PM within 48 hours,
2. PM initiates a schedule update proposal,
3. Change control board assesses whether to fast-track installation after partial delivery or reorder installation batches.

This links risk monitoring to governance, which is a postgraduate requirement.

3.5 Procurement planning: aligning procurement method to constraints and risk

Procurement is not purely administrative—it shapes schedule, quality, cost, and compliance.

3.5.1 Procurement planning outputs (exam-ready)

In a planning question, mention outputs such as:

Procurement strategy,
SOW/ToR (scope of work/terms of reference),
Selection criteria,
Contract type rationale,
Delivery schedules integrated into the project master schedule,
Supplier performance metrics and acceptance criteria.

3.5.2 Procurement choices for meters and installation services

For meters (goods), options could include:

Purchase order / fixed-price contract for delivery,
Framework agreements with suppliers,
Delivery and warranty terms.

For installation services:

Time-and-materials contracts (when scope is uncertain),
Fixed-price contracts (when scope and deliverables are stable),
Hybrid contracts with performance bonuses/penalties.

In an exam, if you choose a fixed-price delivery contract for meters:

You must argue how it reduces cost uncertainty and improves budget control.
You must also discuss risk: supplier delays still affect schedule, so you need mitigation (dual-source, penalties, contingency logistics).

3.6 Contract management: what to monitor and how it ties to project control

Postgraduate exams often ask “how do you manage contract performance.” Answer with:

Contract performance reporting
- delivery timelines,
- quality acceptance tests,
- documentation compliance,
- service level adherence.
Contract change management
- how changes are requested,
- how claims and variations are assessed,
- how approved changes update baselines.
Dispute resolution mechanisms
- negotiation steps,
- escalation,
- formal dispute process.

Applied to R1:

If supplier delays, you check:
- whether it breaches contract timelines,
- whether it triggers penalties,
- whether recovery options are contractually permitted,
- whether schedule updates constitute a change requiring formal approvals.

4) Monitoring, Controlling, and Earned Value: Turning Plans into Performance (Quality, Change Control, and EVM Calculations)

After planning and risk/procurement setup, the next exam-heavy area is monitoring and controlling. Many students can describe tools, but lose marks when asked to interpret outcomes or do calculations. This section focuses on how to answer both theory and computation.

4.1 Monitoring vs controlling: the exam definition that matters

Monitoring: observe project performance against baseline; collect and analyse data.
Controlling: take action to correct variances and update plans where permitted.

A postgraduate answer should state that control is not always “stop everything.” It includes:

corrective actions,
preventive actions,
change requests,
baseline updates when justified and approved.

4.2 Change control: governance-focused answer structure

A strong change control answer includes:

Trigger for change request (what event caused the proposed change).
Change description (what exactly changes: scope, schedule, cost, quality).
Impact assessment
- schedule impact (critical path changes),
- cost impact (budget reallocation),
- quality/compliance impact,
- risk impact.
Decision process
- who approves,
- evidence required,
- record keeping.
Implementation and communication
- update baselines,
- inform stakeholders,
- monitor after implementation.

In the Smart Water Metering Pilot:

If regulatory compliance evidence arrives late (issue from R4), you may propose re-sequencing activities or additional QA reviews.
That is a change to schedule and potentially scope of assurance tasks; it requires a change request.

4.3 Quality management: assurance vs control

Postgraduate exams often ask quality in project delivery. Keep it clean:

Quality assurance (QA): processes to ensure quality is built in (systematic activities).
Quality control (QC): operational checks—testing, inspection, measurement.

For the pilot:

QA includes quality planning and QA audits aligned with compliance requirements.
QC includes commissioning verification tests and interface test results.

A high-scoring answer explains that quality is integrated into execution:

QA to reduce defects early,
QC to confirm acceptability at delivery points,
documentation for acceptance and compliance.

4.4 Earned Value Management (EVM): calculations and interpretation

EVM integrates scope, time, and cost. In exam packs, EVM questions often ask for:

PV, EV, AC,
schedule variance (SV),
cost variance (CV),
CPI (cost performance index),
SPI (schedule performance index),
forecasts: EAC (estimate at completion), sometimes ETC and VAC.

4.4.1 The key formulas (write them first)

Given at a measurement date:

PV (Planned Value) = budgeted cost of work scheduled
EV (Earned Value) = budgeted cost of work performed
AC (Actual Cost) = actual spending

Then:

SV = EV − PV
CV = EV − AC
CPI = EV / AC
SPI = EV / PV

If CPI < 1: cost overrun.
If SPI < 1: behind schedule.
If SV < 0: behind schedule.
If CV < 0: over budget.

4.4.2 Worked EVM example aligned to the pilot timeline

Suppose by the end of Week 6, the project is planned to have completed work worth a budget PV = R600,000. By that date:

Work performed corresponds to EV = R520,000 (because only part of installation and integration packages are complete).
Actual cost AC = R580,000.

Compute:

SV = EV − PV = R520,000 − R600,000 = −R80,000 (behind schedule)
CV = EV − AC = R520,000 − R580,000 = −R60,000 (over budget)
CPI = EV / AC = 520,000 / 580,000 = 0.8966… ≈ 0.90
SPI = EV / PV = 520,000 / 600,000 = 0.8666… ≈ 0.87

Interpretation for the exam answer:

The project is cost-inefficient (CPI ≈ 0.90) and schedule behind (SPI ≈ 0.87).
Management should investigate root causes:
- Are delays due to procurement (R1)?
- Are rework costs increasing due to integration issues (R3)?
- Is resourcing short (R2)?

4.4.3 Forecasting with EAC (simple approach)

A common simplified EAC approach:

If current CPI and SPI trends continue, then:
EAC ≈ BAC / CPI

Assume total BAC (Budget at Completion) for the pilot is R1,200,000. Then:

EAC ≈ 1,200,000 / 0.90 = 1,333,333 (approximately)

Variance at completion (VAC):

VAC = BAC − EAC = 1,200,000 − 1,333,333 = −R133,333
So forecast is over budget by about R133,333.

Your exam-ready commentary must connect forecast to actions:

corrective schedule action (re-baseline or resource reallocation),
cost corrective action (reduce rework, tighten procurement terms),
change control actions (approve only essential changes).

4.5 Performance reporting and dashboards: what to include

Postgraduate exams may request what to include in reporting. A strong report includes:

progress against schedule and cost (PV/EV/AC if EVM used),
milestone attainment status,
top risks and issue log (including changes since last report),
change requests status,
quality and compliance status,
decisions required from governance bodies.

For instance, in the pilot:

A monthly report to sponsor includes:
- EVM results,
- whether the compliance evidence milestone (Month 3) is on track,
- whether meter procurement variance from lead time is within trigger thresholds,
- whether training sessions have been scheduled and attendance confirmed.

This connects monitoring to decision-making.

5) Exam-Ready Scenario Writing: Integrating Governance, Stakeholders, Procurement, Risk, Quality, and M&E into One Coherent Answer (South African University-Style Case Work)

The final part of this guide focuses on exam packs as they are experienced: real questions demand coherent reasoning across multiple domains. Many students fail not because they lack knowledge, but because they produce disjointed answers—risk lists without governance, plans without stakeholder acceptance, or M&E without baseline logic. This section provides an integrated approach with “case-work” style responses you can adapt.

5.1 Building an integrated response: the five-layer method

When a scenario spans multiple requirements, use this five-layer method:

Governance & objectives layer
Who decides? What are success criteria? What baselines exist?
Scope & deliverables layer
What must be delivered, and what are acceptance criteria?
Plan layer
WBS, schedule logic, resourcing, budgeting.
Delivery controls layer
risk register, procurement strategy, quality assurance/control, change control.
Performance & benefits layer
monitoring metrics, M&E plan, reporting cadence, evaluation approach.

The result is coherent and marker-friendly.

5.2 Scenario case: “Smart Water Metering Pilot” integrated exam answer (example)

Assume the exam question:

“A municipality is implementing a Smart Water Metering Pilot. After 6 weeks, the project is behind schedule and costs are higher than planned. Regulatory evidence for compliance is at risk of being late. Provide a monitoring and controlling plan, including risk response, change control, and reporting. Use EVM principles where possible.”

5.2.1 Layer 1: governance & objectives

A high-scoring response begins with objectives and governance:

Objectives: install 1,000 smart meters and integrate billing system by Month 4; achieve compliance by Month 3; train operational staff for handover.
Success criteria: delivery, integration testing results, compliance sign-off, and defined benefits through M&E.
Governance: sponsor oversight with a change control board; compliance officer involvement for acceptance and evidence review.
Baselines: scope baseline (deliverables and acceptance criteria), schedule baseline (critical path activities), cost baseline (budget per work package).

5.2.2 Layer 2: scope & deliverables

State deliverables explicitly:

1,000 smart meters installed and operational
Commissioning and verification tests passed
Billing system integration functional with target accuracy
Training completed and operational handover documentation delivered
Compliance evidence compiled and submitted for sign-off

Then mention how these deliverables tie to acceptance.

5.2.3 Layer 3: plan—what gets adjusted under variance

Using EVM results from Section 4:

PV = R600,000
EV = R520,000
AC = R580,000
SV = −R80,000
CV = −R60,000
CPI ≈ 0.90, SPI ≈ 0.87

Interpretation:

Underperformance is both schedule and cost related.
Focus on drivers: procurement delays (R1), integration rework (R3), compliance evidence slippage (R4), resourcing shortfalls (R2).

Plan adjustments may include:

re-sequencing non-critical installation batches if compliance evidence depends on specific documentation earlier,
prioritising compliance documentation workflows earlier in the project,
fast-tracking integration configuration tasks where dependencies allow.

5.2.4 Layer 4: delivery controls—risk, procurement, quality, change control

Now connect controls:

Risk responses:

Update risk register immediately:
- escalate R1 supplier lead time risk if evidence suggests delivery is worsening,
- add or strengthen R4 compliance evidence action plan with clear submission dates.

Risk triggers and actions:

If compliance evidence milestone readiness review misses by 2 weeks, initiate a corrective change:
1. Add extra compliance documentation review sessions (resource adjustment),
2. Reassign QA evidence owners,
3. Propose schedule re-baselining if required.

Procurement controls:

review contract delivery timelines and penalties,
confirm whether expedited shipping options are contractually permissible,
ensure delivery tracking integrates into the master schedule.

Quality controls:

increase the frequency of interface testing in sandbox environment (QA process),
require commissioning verification checklists before declaring installation complete for EV progress measurement.

Change control:

implement formal change requests for:
- schedule compression (fast-tracking),
- reallocation of budget between work packages,
- scope changes (only if compliance and testing acceptance require additional tasks).

A marker-friendly change control explanation includes impact assessment on time, cost, quality, and risk.

5.2.5 Layer 5: performance & benefits—reporting and M&E

Monitoring & reporting:

weekly dashboard for PM/IT/procurement leads,
monthly report for sponsor and governance board including:
- EVM metrics (SV, CV, CPI, SPI),
- top risks and their status,
- compliance evidence progress,
- decisions required.

M&E:

establish indicators aligned to success criteria:
- installation completion rate (1,000 meters total),
- compliance evidence submission status,
- billing integration functional test pass rate (target 95% accuracy against sample readings),
- training completion (attendance and operational readiness sign-off),
- benefit metrics: billing accuracy improvements and water loss reduction vs baseline.

Even if M&E details are not numerically required in the exam question, mention indicators and evaluation timing.

5.3 How to answer “procurement and contracts” questions using the pilot logic

Many exams include a procurement/contract question. A strong approach is to:

state procurement objectives (value for money, compliance, schedule alignment),
select a contract strategy,
identify contract performance monitoring,
describe dispute/change management.

For the pilot:

meters: fixed-price delivery approach with delivery lead time clauses and acceptance tests,
installation services: performance-based fixed price where deliverables are clear (site readiness, install completion, commissioning pass).

Then show what you monitor:

delivery schedule adherence,
warranty and defect rectification timelines,
acceptance testing results,
documentation completeness for compliance sign-off.

5.4 How to answer “stakeholder management” questions at postgraduate level

Stakeholder questions often ask:

“How will you manage stakeholders to ensure project success?”
“Develop an engagement plan.”

Your integrated answer should include:

mapping of stakeholder power/interest (as in Section 2),
engagement strategies,
communication mechanisms (reporting cadence, workshops, escalation routes),
how stakeholder feedback affects scope and acceptance.

In the pilot:

sponsor: governance meetings and approvals,
compliance officer: early evidence review cycles,
operational staff: training and handover readiness,
community reps: site access planning and communication to reduce disruption.

The key is to show stakeholder engagement as a control mechanism—not just relationship management.

5.5 Exam technique: converting theory into points (and avoiding repetition)

A final exam strategy aligned with how South African exam packs are marked:

Avoid repeating the same definition in multiple sub-answers.
Use definitions only once, then apply.
When asked for a plan:
- present steps in a numbered sequence,
- include at least one example (e.g., a specific trigger, a specific risk response).
When asked for calculations:
- show the formula,
- substitute values,
- interpret results in words linked to the scenario.

This is how you turn knowledge into marks.

5.6 Practice mini-questions (with answer elements you can write under exam conditions)

Below are exam-pack style prompts and the answer components you should include.

Mini-question A (Risk register)

Prompt: “Identify five risks and propose risk responses for a municipal infrastructure project delivering by a fixed deadline.”
Answer elements to include:

Risk description with driver,
Probability/impact categories (qualitative),
Response strategy (avoid/mitigate/transfer/accept),
Owner,
Trigger and monitoring method.

Mini-question B (EVM interpretation)

Prompt: “Given PV = R800,000, EV = R700,000, AC = R900,000, interpret performance and suggest corrective actions.”
Answer elements:

SV = EV − PV = −R100,000 (behind schedule)
CV = EV − AC = −R200,000 (over budget)
CPI = EV/AC = 0.78 (approx)
SPI = EV/PV = 0.88 (approx)
Corrective actions: investigate causes; update resource plan; tighten procurement; implement change control.

Mini-question C (Change control)

Prompt: “Explain a change control process and how you would assess a scope change impacting schedule and compliance.”
Answer elements:

Change request submitted,
impact assessment on schedule/cost/quality/compliance/risk,
decision by change control board,
baseline update where approved,
communication and monitoring post-implementation.

These mini-questions show what markers expect without requiring you to invent a whole narrative.

Closing Consolidation: The Regent Exam Pack Mindset (What to Memorise vs What to Apply)

For postgraduate exams, what you memorise should be:

standard definitions you must use correctly (risk vs issue, QA vs QC, monitoring vs controlling),
core formulas (especially EVM),
structured output expectations (risk register fields, WBS logic, change control steps).

What you apply should be:

the scenario-specific logic (your chosen example project: the Smart Water Metering Pilot with 1,000 smart meters, a 4-month delivery plan, compliance-by Month 3, training and handover near completion),
the cause-and-effect reasoning (what variance likely indicates, how procurement/risk/control interventions address it),
stakeholder and governance integration (who must approve, who must provide evidence, how reporting triggers decisions).

When your answers consistently follow the planning → control → performance chain, your work aligns with how Regent Business School project management assessments typically reward postgraduate-level competence—and how South African universities commonly assess similar module outcomes.