UFS Business School Programme in Project Management (PPM) Complete Notes

The UFS Business School Programme in Project Management (PPM) is a structured pathway designed to build practical and academic competence in planning, executing, monitoring, and closing projects. These complete exam notes consolidate core project management concepts, tools, and applied techniques commonly assessed in South African university contexts. You’ll find a strong focus on the way project management is typically examined in programmes aligned to UFS and comparable qualifications such as UNISA, CUT, and other local universities’ project-oriented modules.

This set is written in an exam-ready style: definitions are paired with “how to apply,” processes include step-by-step logic, and common pitfalls are addressed with realistic scenarios. Where helpful, the notes include example mini-cases, sample calculations, and decision frameworks—so you can translate theory into answers under time pressure.

Section 1: Understanding the UFS Business School PPM Programme & Core Project Management Foundations

What “Programme in Project Management (PPM)” Usually Assumes in South African University Exams

In many South African university settings, project management is tested at a blend of:

Conceptual understanding (definitions, principles, frameworks)
Process competence (what happens first/next; what outputs are produced)
Application (using tools like the logframe, WBS, risk registers, or earned value)
Professional judgement (trade-offs: time vs cost, risk vs opportunity, scope vs budget)

The UFS Business School PPM programme typically expects you to demonstrate both project thinking and management thinking: you must be able to describe what a project manager does, but also show how they do it using structured methods.

In exams, your marks usually depend on whether you can:

Name and define key terms (e.g., project, programme, portfolio, scope, stakeholder)
Apply a method to a scenario (e.g., create a schedule logic using dependencies)
Justify a decision (e.g., why a particular risk response fits)
Produce outputs (e.g., a risk register row, a WBS level, a simple cashflow model)

Project vs Programme vs Portfolio (Common Exam Differentiation)

A recurring question pattern in project management modules (including those aligned to UFS Business School and similar SA programmes) is to distinguish between:

Project: A temporary endeavour with a defined start and end, created to produce a unique output.
Programme: A group of related projects managed in a coordinated way to achieve outcomes and benefits.
Portfolio: A collection of projects and/or programmes managed to meet strategic objectives.

Exam tip: When asked to define differences, don’t only write definitions—link them to management implications:

Projects are managed for specific deliverables.
Programmes are managed for benefits/outcomes.
Portfolios are managed for strategic alignment and resource balancing.

Mini-scenario (typical exam style)

A municipality invests in:

a water pipeline upgrade (one project),
a leak detection system rollout (second project),
and a training campaign for maintenance teams (third project).

If these are coordinated to deliver broader water reliability improvement, they form a programme. If the municipality also funds unrelated infrastructure priorities (roads, housing, sanitation) and chooses investments strategically, that wider selection is the portfolio.

The Project Life Cycle: From Initiation to Closure

Most exam questions expect you to know that projects typically move through phases such as:

Initiation: establish need, feasibility, business case, appoint the project manager, identify stakeholders.
Planning: define scope, create WBS, schedule, cost estimates, risk planning, procurement strategy.
Execution: perform work, coordinate resources, manage communications, implement plans.
Monitoring & Controlling: track performance, manage changes, mitigate risks, correct variances.
Closing: deliver outputs, hand over, review lessons learned, close contracts.

A valuable exam approach is to phrase answers using outputs:

Initiation produces the business case, project charter (or equivalent).
Planning produces a project management plan, scope baseline, schedule baseline, cost baseline, risk register, communication plan.
Monitoring/controlling produces status reports, change requests, and variance analyses.
Closing produces acceptance documentation and a lessons learned report.

The Triple Constraint and Why It Fails as a “Single-Lens” Model

The classic triple constraint:

Scope
Time
Cost

is often taught early, and it is useful—but exams increasingly expect you to go beyond it. Many PPM questions involve:

Quality (does the output meet standards?)
Risk (what could disrupt the constraint balance?)
Stakeholders (acceptance, expectations, influence)

A modern way to answer is:

The triple constraint determines core feasibility, but quality, risk, and stakeholder satisfaction are also critical success factors.

Example: scope creep under fixed time and cost

If a company schedules a system implementation for 3 months at a fixed budget, and the client adds features every week (“just small changes”), the project may:

finish late,
or ship only partial functionality,
or exceed cost,
and likely reduce quality (bugs, rework).

Your answer should show causal logic: scope changes drive effort changes, which drive schedule and cost variances.

Stakeholders and Stakeholder Management

Most PPM exam content includes stakeholder analysis because project outcomes often depend on who supports the project.

You should know:

Stakeholder: any individual or group impacted by the project or who can influence its outcome.
Stakeholder identification: map internal/external stakeholders.
Stakeholder analysis: power/interest grid, influence–impact, or salience.
Stakeholder engagement: plan communication, manage resistance, build support.

Power/Interest Grid (how to apply in answers)

Typically classify into:

High power / High interest: closely manage, keep satisfied.
High power / Low interest: keep informed, minimal effort.
Low power / High interest: keep engaged, provide adequate communication.
Low power / Low interest: monitor, avoid over-communication.

In exams, you can score by explicitly stating:

what communication method fits each class (workshops, emails, reports),
and what key message matters to each class (benefits, compliance, cost control).

Project Governance: Decision Rights and Accountability

South African university projects often ask about governance because real projects require authority structures. Governance includes:

Steering committee or project board,
approval gates (e.g., approve charter, approve baseline),
roles and responsibilities (project manager, sponsor, team, procurement, functional managers).

A strong exam answer explains:

who has final decision authority for changes,
how escalation works when the project manager can’t resolve an issue,
and how reporting cadence supports governance.

Knowledge Check (Exam-Style)

You should be able to answer quickly:

Distinguish project vs programme vs portfolio.
List typical project phases and the main outputs from each.
Explain why the triple constraint needs extension (quality, risk, stakeholder satisfaction).
Use the power/interest grid to propose communication strategies.

Section 2: Project Planning Tools—WBS, Scheduling, Costing, Scope Control, and Baselines

Defining Scope: Requirements, Deliverables, and Boundaries

Scope planning is central to project success—and it is heavily examined. Scope includes:

Product scope: features and functions of the delivered output.
Project scope: the work required to deliver the product.

You must also differentiate:

Requirements (what must be true or delivered),
Deliverables (tangible outputs),
Assumptions and constraints (things you believe/limits you must respect).

Common exam trap: confusing requirements with deliverables

Example:

Requirement: “The system shall allow user authentication.”
Deliverable: “Authentication module delivered and tested.”

An exam-grade answer shows you understand that deliverables are evidence of completed requirements.

Work Breakdown Structure (WBS): The Backbone of Planning

A WBS breaks down project work into manageable components. The key logic:

Start with the final deliverable (level 1).
Decompose into major deliverables (level 2).
Continue to work packages (often level 3–5).

Work packages should be:

small enough to estimate duration and cost,
assignable to a responsible person or team,
trackable for progress.

Example WBS snippet (conceptual)

Project: “Build a small training facility”

1.0 Pre-Construction
- 1.1 Design approvals
- 1.2 Permits and compliance
2.0 Construction
- 2.1 Site preparation
- 2.2 Building works
- 2.3 Electrical installation
3.0 Fit-Out
- 3.1 Furniture installation
- 3.2 IT and network
4.0 Commissioning & Handover
- 4.1 Testing and commissioning
- 4.2 Training users
- 4.3 Handover documentation

In exams, you may be given a scenario and asked to propose a WBS or critique one. A strong critique checks:

Are work packages measurable?
Are dependencies plausible?
Are responsibilities clear?
Does the WBS cover all deliverables (and only deliverables)?

Estimating Methods: From Expert Judgement to Quantitative Tools

Exams often ask about estimation and uncertainty. Common estimate types:

Analogous estimation: use historical data from similar work.
Parametric estimation: use statistical relationships (e.g., cost per meter, cost per unit).
Bottom-up estimation: estimate work packages and sum them.
Three-point estimation (PERT-like): best, most likely, worst to compute expected values.

Three-point estimation mini-example

Suppose a work package has:

Best (O) = 4 days
Most likely (M) = 6 days
Worst (P) = 10 days

Expected duration (using a PERT-style formula) often:

TE = (O + 4M + P) / 6
TE = (4 + 4×6 + 10) / 6 = (4 + 24 + 10) / 6 = 38/6 ≈ 6.33 days

An exam-friendly answer then discusses:

risk implications: “long tails” create schedule risk,
need for contingency reserves or buffers.

Scheduling: Dependencies, Critical Path, and Milestones

Scheduling is where many exams test your ability to structure logic. Core scheduling concepts include:

Activities derived from WBS work packages,
Dependencies (Finish-to-Start, Start-to-Start, etc.),
Milestones (time points with no duration, representing meaningful progress),
Critical path (sequence that determines project duration).

Dependency logic (example)

If Activity B depends on Activity A:

Start of B can’t occur until A finishes.
That’s a Finish-to-Start (FS) dependency.

In exams, you may be asked:

identify which activities lie on the critical path,
explain what happens to the critical path if a duration changes.

Backward vs Forward Scheduling

Planning questions may ask about:

forward scheduling (start from project start date),
backward scheduling (start from a due date and work backward).

Backward scheduling is useful when:

the project must finish by a fixed deadline (e.g., event date).

Baselines: Scope, Schedule, Cost Baselines

A baseline is a reference plan approved at a point in time. For PPM contexts, you should understand:

Scope baseline: approved scope statement and WBS.
Schedule baseline: planned start/finish dates for activities.
Cost baseline: budget assigned to work packages/activities over time.

The exam emphasis is typically on change control:

variances must be measured against baselines,
changes require approval,
approved changes update baselines (or produce a revised baseline).

Cost Estimation and Budgeting

Cost includes:

labour,
materials,
equipment,
subcontractor costs,
overheads (sometimes),
contingency and management reserves.

Cost baseline logic

A common exam calculation is:

estimate cost for work packages,
sum to get activity cost,
aggregate to get totals per phase or reporting period,
build the time-phased cost profile.

Cashflow vs Budget (Important Distinction)

Students sometimes confuse:

Budget (total amount allocated),
Cashflow (timing of actual payments).

In project management, cashflow timing matters because:

procurement might require deposits,
retention payments might occur at handover,
supplier terms affect liquidity.

If an exam question provides a budget and asks for a cashflow plan, you should:

schedule major procurement payment milestones,
align cash outflows to expected activity timing.

Change Control: Managing Scope Creep and Variance

A rigorous exam answer includes:

Change request submission,
impact assessment (cost, time, scope, risk),
review by appropriate authority (project steering committee/sponsor),
decision and communication,
update of baselines and documentation.

Example: change request impact assessment

If a client asks for additional reports:

Scope increases → more development/testing.
Schedule likely extends or forces resource reallocation.
Costs increase → higher budget or reallocation from contingency.
Quality might be at risk if deadlines remain fixed.

Your answer gains marks when you explicitly discuss options:

accept the change and adjust schedule,
accept the change and adjust budget,
keep schedule/budget by reducing other scope,
reject the change or propose a phased approach.

Quality Planning and Acceptance Criteria (Often Exam-Linked)

Quality in project management often appears as:

quality planning (how quality will be achieved),
quality assurance (systematic activities),
quality control (inspection/testing).

Acceptance criteria are measurable standards for deliverables. In exams, if acceptance criteria aren’t defined:

you risk disputes at handover,
and rework becomes likely.

Knowledge Check (Exam-Style)

Explain WBS and why work packages matter.
Compute a three-point estimate using a PERT-style formula.
Use dependency logic to identify schedule implications.
Explain baseline and change control in 5–7 linked steps.

Section 3: Risk Management, Procurement/Contracting, Communication & Stakeholder Engagement in PPM Exams

Risk Management Overview: From Identification to Response

Risk management is a structured cycle:

Plan risk management (how risk will be done: templates, cadence).
Identify risks (sources, events, causes).
Analyse risks (qualitative and/or quantitative).
Plan responses (avoid, mitigate, transfer, accept; exploit, enhance, share, reject).
Implement responses.
Monitor and control risks.

An exam-ready answer should include both risk and uncertainty, showing that not all risks are predictable, but they are still managed.

Risk Register: The Tool You’re Expected to Use

A risk register typically includes:

Risk ID
Description (cause-event-effect)
Category (technical, schedule, cost, stakeholder, external, compliance)
Probability and impact scores
Risk rating (or priority)
Response strategy
Owner
Triggers (early warning indicators)
Contingency action and timeframe

Example risk register rows (typical format)

Risk ID	Risk description	Category	Probability	Impact	Rating	Response	Owner	Trigger
R1	Supplier delays materials	Procurement/schedule	High	High	9	Mitigate: dual sourcing; expedite logistics	Procurement Manager	Delivery missed by 3 days
R2	Stakeholder requirements keep changing	Stakeholder/scope	Medium	High	6	Mitigate: formal change control; workshops	PM	2+ new requests without change approval
R3	Regulatory approval takes longer than expected	Compliance/external	Low	High	4	Transfer/mitigate: use specialist consultant	Compliance Officer	No feedback within 10 working days

Even if your exam doesn’t ask for a full table, including owner and triggers often differentiates top answers.

Qualitative Risk Analysis: Probability–Impact Matrix

A probability–impact matrix helps prioritize. Common scales:

Probability: Low/Medium/High (or 1–5)
Impact: Low/Medium/High (or 1–5)

Risk rating often equals:

probability score × impact score

Counter-argument / Limitations

Qualitative matrices can be subjective. High-scoring risks may not always be the most likely to occur in practice. In exams, when asked about limitations, you can state:

results depend on assessor judgement,
matrix doesn’t capture correlation or interdependencies well,
quantitative analysis may be needed for high-cost, high-uncertainty risks.

Quantitative Risk Analysis: When Complexity Increases

Quantitative techniques may include:

expected monetary value (EMV),
scenario analysis,
simulation (Monte Carlo),
sensitivity analysis.

In most basic exams, qualitative may be sufficient, but some questions include EMV:

EMV = Probability × Impact (with costs usually in currency units).

EMV mini-example

If a risk can cause:

additional cost of R 200,000 with probability 20%,
EMV = 0.2 × 200,000 = R 40,000

Then you can compare:

EMV of risk,
against cost to mitigate.

Response Strategies: Avoid, Mitigate, Transfer, Accept

A strong exam answer describes what each strategy means and when it fits.

Avoid: change plan to remove risk cause.
Mitigate: reduce probability and/or impact.
Transfer: shift impact to third party (insurance, fixed-price contracts).
Accept: no action now; manage via contingency if it occurs.

Example response mapping

Risk: “Network installation delayed”
- Mitigate: schedule vendor checks early, create buffer
- Transfer: contract penalties for late delivery
- Accept: only if delay cost is low and buffer exists

Risk Triggers and Monitoring

Exams like “monitoring” questions. Triggers are signals:

delivery missed by a threshold,
stakeholder approvals not obtained within defined time,
procurement cost variance exceeding tolerance.

In your answer, show you understand that:

monitoring is not passive,
it triggers pre-planned response actions.

Procurement and Contracting in Project Management

Why Procurement is Examined in PPM

Projects require goods/services; procurement introduces:

supplier risk,
contract compliance,
timeline and cashflow effects,
quality variations.

Procurement Planning Concepts

Procurement planning includes:

make-or-buy decisions,
procurement approach (competitive bidding, negotiated contracts),
contract type selection.

Contract Types and Their Implications

Common contract types:

Fixed-price: supplier bears most cost overruns.
Cost-reimbursable: buyer reimburses eligible costs plus fee; buyer bears cost risk.
Time and materials: payment based on time and materials used.
Unit price: pay per unit delivered.

In exams, you may be asked which contract type reduces which risks. A general principle:

fixed-price contracts shift cost risk to suppliers,
cost-reimbursable shifts risk back to buyer,
unit price is helpful when quantities can be measured.

Example decision logic

If scope is stable and requirements are clear:

fixed-price may work.
If scope is uncertain:
cost-reimbursable or time/materials can be safer (but requires strong controls).

Procurement Process Steps (Exam-Style Sequence)

Typical flow:

Define procurement need.
Determine procurement method.
Prepare specification and terms.
Invite bids/quotes.
Evaluate bids using criteria.
Award contract.
Manage contract performance (deliverables, quality, changes).
Close procurement contract.

Your marks can increase if you include:

evaluation criteria (price, quality, delivery capability, past performance),
how you handle bids that are non-compliant.

Communication and Stakeholder Engagement

Communication Planning

Communication planning determines:

who needs what information,
frequency and format,
responsibility for sending information,
escalation procedures.

A complete answer lists typical outputs:

communication plan,
meeting schedules (status meetings, steering committee),
reporting templates (progress report, risk report).

Project Reporting Cadence

Common cadences:

daily/weekly for work teams,
biweekly/monthly for steering committee,
ad hoc for major risks or decisions.

Your answer should connect cadence with decision needs:

steering committee needs enough information to decide on changes and budget issues.

Managing Conflict and Resistance

Stakeholder engagement isn’t only “communication”; it includes influence management.
Common sources of resistance:

fear of change,
unclear benefits,
perceived loss of power/resources,
poor communication quality.

In exams, you can improve answers by proposing engagement tools:

workshops,
co-design sessions,
training,
feedback loops,
phased rollouts.

Worked Example: Integrated Risk + Procurement + Communication

Scenario: A manufacturing firm plans a new packaging line installation. Delivery depends on a specialised machinery supplier.

Risks:

supplier delay,
installation contractor availability,
regulatory safety sign-off.

Actions:

Mitigate supplier delay: dual sourcing option (or backup supplier shortlist) and early purchase order triggers.
Control contractor risk: include availability and penalties in contract terms.
Reduce compliance delays: hire a compliance specialist and schedule safety inspections early.
Communication: weekly supplier status and installation plan updates; monthly steering committee risk review.

In exams, the mark-winning move is integrating:

response strategy,
owner,
trigger,
and communication plan.

Knowledge Check (Exam-Style)

Describe steps in risk management cycle.
Explain what should appear in a risk register.
Choose response strategies (avoid/mitigate/transfer/accept) with justification.
Match contract types to uncertainty levels in scope.

Section 4: Earned Value Management, Monitoring & Controlling, Change Impact, and Performance Measurement

Monitoring and Controlling: The Management Loop

Monitoring & controlling compares actual performance to planned baselines. The core idea:

measure performance,
identify variance,
analyze cause,
recommend corrective/preventive action,
update stakeholders and governance decisions.

A strong exam answer uses a “loop” narrative:

collect data (progress, costs, delivered work),
compute performance metrics,
interpret variances and trends,
decide actions,
implement and communicate.

Variance Types: Schedule, Cost, Scope

In project exams, you might need to describe:

schedule variance: activity progress slower/faster than planned.
cost variance: spending higher/lower than planned for the work performed.
scope variance: deliverables changed without approved change control.

Scope variance often triggers cost and schedule variance too, because scope changes increase work and complexity.

Earned Value Management (EVM): Measuring Work Done vs Money Spent

EVM uses three key values:

PV (Planned Value): what you planned to spend for the work scheduled by a date.
EV (Earned Value): what you planned to earn (value) for the work actually completed by that date.
AC (Actual Cost): what you actually spent for the completed work.

From these, you calculate:

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

Percentages/indices:

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

Interpretation guide (exam-safe)

If EV > PV → ahead of schedule (SV positive; SPI > 1)
If EV < PV → behind schedule (SV negative; SPI < 1)
If EV > AC → under budget (CV positive; CPI > 1)
If EV < AC → over budget (CV negative; CPI < 1)

Example EVM Calculation (Common Exam Task)

Suppose by week 6:

PV = R 500,000 (planned)
EV = R 420,000 (earned)
AC = R 460,000 (actual)

Compute:

SV = EV − PV = 420,000 − 500,000 = −R 80,000
CV = EV − AC = 420,000 − 460,000 = −R 40,000
SPI = EV / PV = 420,000 / 500,000 = 0.84
CPI = EV / AC = 420,000 / 460,000 ≈ 0.91

Interpretation:

schedule is behind (SPI 0.84),
cost performance is also weak (CPI 0.91).

Forecasting with EVM: EAC and ETC (Exams Often Test Forecasts)

Common forecast formulas include:

Estimate at Completion (EAC)
Two simplified approaches:
- If performance continues as current cost efficiency: EAC = BAC / CPI
- If variance is expected to be unusual only: EAC = AC + (BAC − EV) (varies by assumed model)
Estimate to Complete (ETC)
ETC = EAC − AC

To use these, you must have:

BAC (Budget at Completion)—the total approved budget.

Forecast mini-example

Assume:

BAC = R 1,200,000
AC = R 460,000
CPI = 0.91
Then:
EAC = BAC / CPI = 1,200,000 / 0.91 ≈ R 1,318,681
ETC = EAC − AC ≈ 1,318,681 − 460,000 = R 858,681

A top exam answer then links forecast to action:

if EAC exceeds budget by about R 118,681, propose corrective actions (re-scheduling, supplier escalation, scope trade-offs).

Performance Reporting: Dashboards and Trend Analysis

EVM isn’t only about single-date metrics. Trend matters:

CPI and SPI trend upward or downward,
variances persist or improve,
risks are materialising.

In an exam scenario, if CPI decreases over time, your narrative should state:

cost overrun is continuing,
corrective actions may be needed: tighten estimates, replan schedule, review procurement.

Managing Changes Using Performance Data

EVM connects to change control:

if EV/AC indicates work is more expensive, you may seek approval for:
- revised budget,
- change in procurement method,
- scope reprioritisation.

However, an exam-grade answer should caution:

performance variance is not automatically a justification to approve all changes.
Governance should ask:
were baseline assumptions wrong,
can the issue be corrected without scope reduction or additional budget,
is there contractual leverage (claim, penalty, renegotiation)?

Corrective vs Preventive Action

Corrective action: fix what has already gone wrong.
Preventive action: reduce likelihood of future problems.

In exams, you can gain marks by giving examples:

Corrective: rework a faulty deliverable, allocate extra technicians to catch up.
Preventive: improve test procedures, update risk triggers, train contractors.

Scope Control and Measuring Deliverables

Monitoring scope requires:

verifying deliverables against acceptance criteria,
tracking approved changes,
preventing “unapproved work” that creates hidden scope.

A common exam phrase: “scope control includes managing changes and verifying deliverables.” You should mention both:

verify outputs,
control changes.

Worked Case: Using EVM plus Change Control

A project has:

BAC = R 1,200,000
At week 6:
PV = R 500,000
EV = R 420,000
AC = R 460,000

You forecast EAC ≈ R 1,318,681 (as earlier). The sponsor asks whether to:

approve additional budget (additional R 118,681),
reduce scope to bring EAC down,
adjust schedule and resource plan to improve CPI.

A top answer would:

propose analysis on root cause (why CPI is < 1),
state which options are likely to reduce costs,
link the option to governance and stakeholder impact.

Knowledge Check (Exam-Style)

Define PV, EV, AC and compute SV, CV, SPI, CPI.
Interpret CPI/SPI values in plain language.
Use CPI to forecast EAC and explain management implication.
Distinguish corrective vs preventive action.

Section 5: Integration, Leadership, Ethics, PM in Real Context, and Exam-Ready Answer Construction (UFS-Style Coverage)

Project Integration Management: Connecting All Knowledge Areas

Integration management ensures the project “works as a system.” Typical integration processes include:

developing a project charter,
developing the project management plan,
directing and managing project work,
monitoring and controlling project work,
performing integrated change control,
closing the project.

In exams, integration questions often ask:

how planning outputs connect to controlling outputs,
where decisions are made,
and how changes are handled across scope, time, cost, risk, and procurement.

Integrated Change Control: The “Decision Hub”

Integrated change control ensures changes are:

reviewed for impacts across the whole project,
documented and approved,
communicated.

An exam-ready response includes:

Receive change request.
Assess impacts (scope, schedule, cost, quality, risk).
Evaluate alternatives.
Decide approval/rejection.
Update baselines and documents.
Communicate decision and implement.

Example: integrated impacts of a stakeholder request

Stakeholder requests an additional training module.

Impacts:

scope increases (more content),
schedule increases (development and delivery time),
cost increases (materials, facilitator time),
risk changes (training delivery schedule dependencies),
procurement may need extra subcontracting.

An excellent answer uses a mini “impact matrix” approach:

list each affected area and what changes you expect.

Leadership and Team Management in Project Context

Many PPM questions include leadership and team dynamics:

project managers may be in a leadership role without formal authority over functional staff,
motivation and performance depend on trust, clarity, and recognition.

Key leadership themes:

team formation and development,
conflict handling,
performance management,
coaching and facilitation,
communication discipline.

Example conflict scenario (exam style)

Two subcontractors disagree on installation sequence. The project manager should:

clarify dependency logic (what must happen first),
assess risk of rework,
update schedule and procurement coordination,
document agreement.

Your answer should show:

you aren’t only mediating emotions,
you’re restoring system logic.

Ethics and Professional Responsibility

South African university assessments in business and management often include ethical reasoning in applied contexts. In project management ethics, consider:

transparency (accurate reporting),
fairness (procurement integrity),
compliance (regulatory adherence),
respect for people (not exploiting labour or hiding safety issues).

An exam answer can mention:

conflicts of interest,
misrepresentation of progress data,
misuse of budget or resources.

Even when ethics is not explicitly asked, ethical language strengthens professional credibility in long-form answers.

Exam-Ready Framework for Constructing High-Scoring Answers

Since PPM exam questions are often scenario-based, you need a repeatable structure.

A powerful template (for many long questions):

Define / clarify the key concept asked.
Select the most relevant framework/tool.
Apply to the scenario with specific steps.
Justify (why this is the best tool/approach).
Mention outputs (what documents or artifacts result).
Close with expected outcomes (how it reduces risk/variance).

Example: how to answer “Explain risk response strategies”

Step-by-step approach:

Avoid/Mitigate/Transfer/Accept definitions.
Provide when each strategy fits (based on probability and impact).
Give a scenario-specific mapping (e.g., supplier delay → mitigate/transfer).
Mention ownership and triggers.
Provide monitoring actions.

This structure ensures that even if your calculations are imperfect, your conceptual framework still secures partial marks.

Case Study Practice: A Full Integrated PPM Scenario

To consolidate concepts without repeating prior sections, consider a full case you can use for exam preparation.

Scenario: “Community Health Outreach Project”

A non-profit organisation runs a 12-week community health outreach initiative:

Build and equip a mobile outreach station.
Train volunteer teams.
Run screening sessions and collect data.
Produce a final report for donors.

Key challenges:

procurement of equipment with variable delivery times,
stakeholder scheduling (schools and clinics),
risk of data quality and reporting delays,
sponsor expectation of a final deliverable by week 12.

Step 1: Planning outputs (scope, schedule, cost)

Define deliverables:
- outreach station operational,
- volunteer training completed,
- screening sessions conducted,
- final donor report accepted.
Build a WBS:
- procurement,
- installation setup,
- training,
- screening operations,
- reporting and handover.
Create schedule logic:
- procurement must precede setup,
- setup must precede training,
- training precedes outreach sessions.

Step 2: Baselines and change control

Approve scope baseline (WBS) and schedule baseline (milestones at weeks 4, 8, 12).
Approve cost baseline including a contingency for procurement delays.
Establish change control: any new donor reporting requirement must be approved by sponsor before it affects scope or schedule.

Step 3: Risk register creation (integrated)

Risks might include:

equipment delay (procurement),
volunteer absenteeism (people),
partner site cancellations (stakeholders),
data entry errors (quality).

Responses:

equipment delay: dual-source option and early ordering trigger,
volunteer absenteeism: standby volunteers,
site cancellations: reserve partner lists,
data errors: validate data forms and review process.

Step 4: Monitoring & EVM (performance control)

At week 6, you measure:

PV (planned work progress for weeks 1–6),
EV (earned value for completed work),
AC (actual spend).

If EV < PV and AC > EV, it indicates:

schedule behind and cost overrun.
You then decide:
corrective action (catch-up),
preventive action (reduce recurrence),
and consider change control if necessary.

Step 5: Communication and stakeholder engagement

Weekly operational meeting (implementation team).
Biweekly sponsor update (risk and milestone progress).
Rapid escalation if milestones at weeks 8 or 12 are threatened.

Linking UFS Programme Expectations with Exam Practice

A common theme in local university project management assessments is that students must show:

structured thinking,
correct terminology,
and applied reasoning to realistic constraints (budget, stakeholder needs, compliance).

In the UFS Business School Programme in Project Management (PPM) context, exam questions often reward students who can:

connect planning outputs to control mechanisms,
show that changes are governed,
and explain risk and procurement impacts on performance outcomes.

If you consistently incorporate:

baselines,
risk register with owners and triggers,
change control steps,
and performance measurement (qualitative and/or EVM),
you will be well-positioned for exam success.

Final Exam-Style Checklists

Core Definitions You Must Memorise (Quick Recall)

Project vs programme vs portfolio
Triple constraint + quality/risk/stakeholder extensions
WBS and work packages
Baselines and change control
Risk register, probability, impact, triggers, risk owner
PV, EV, AC; SPI, CPI; EAC

Common Calculations (Practice Before the Exam)

Three-point estimate: (O + 4M + P) / 6
EVM: SV, CV, SPI, CPI
Forecast: EAC = BAC / CPI (when that assumption is used)

Common “Top Answer” Behaviours

Use scenario language (not only generic definitions).
Provide justification (why this tool/response).
Include outputs (what document or artifact results).
Add governance/approval logic (who decides changes).

Knowledge Check (Exam-Style)

Describe integrated change control as an end-to-end process.
Explain how a stakeholder request can affect scope, schedule, cost, risk, and procurement.
Use a structured template to answer a risk response question.
Connect monitoring metrics to corrective action decisions.

Summary of What This PPM Notes Package Covers

These complete exam notes provide a full, integrated overview of the UFS Business School Programme in Project Management (PPM) learning focus areas: foundational project concepts; planning with WBS, scheduling logic, cost estimation, and baselines; risk management with risk registers and response strategies; procurement/contracting basics tied to uncertainty; performance measurement with EVM and forecasting; and integration through change control, governance, leadership, and ethics. The notes are designed to help you produce consistent, high-quality answers in South African university exam conditions—where clarity, application, and structured reasoning are rewarded most strongly.