Rhodes University PGDip in Enterprise Management (PGDip EM) – Project Management Notes

Rhodes University’s PGDip in Enterprise Management (PGDip EM) is designed to strengthen practical management capability—particularly through applied assignments that mirror real enterprise environments. In the Project Management component, candidates are expected to manage projects using structured planning, stakeholder engagement, risk thinking, and disciplined execution. These exam notes consolidate the core concepts, frameworks, and exam-ready problem-solving approaches typically tested in South African university assessments, with emphasis on what matters for marks: clear structure, correct terminology, and coherent justification.

The notes below are written specifically for study within the broader category of “Rhodes University Project Management & Leadership Notes”, focusing on project management for enterprise contexts as used in postgraduate management modules.

1) Project Management Foundations for Enterprise Management Students

Project management at postgraduate level is not merely about “doing tasks in order.” It is about creating predictable outcomes in environments where constraints (time, cost, quality, scope, risk, and stakeholder expectations) compete. In the PGDip EM context, your lecturer typically expects you to connect project methods to business value: why the project exists, what success means for the enterprise, and how management decisions affect delivery.

What Makes a “Project” in a Business Context?

A project is a temporary endeavour undertaken to create a unique result—while an operation is ongoing and repetitive. In an enterprise, many initiatives begin as projects:

Launching a new product line
Implementing an ERP system
Building a small distribution warehouse
Designing a new customer service process
Establishing a compliance programme (e.g., internal controls)

A common exam-style question asks you to differentiate projects from operations. Your answer should include:

Temporary (has a beginning and end)
Unique deliverable (not routine work)
Constraints (scope, time, cost, quality)
Cross-functional coordination (resources from different departments)

A typical enterprise example: Suppose a retail group needs to upgrade its inventory tracking process. The upgrade might be a project with a target go-live date, a defined scope (software configuration + staff training + data migration), and measurable success criteria (reduced stockouts, improved stock accuracy). After the upgrade, daily inventory operations continue—those are business-as-usual.

The Project Life Cycle: Concept-to-Closure Thinking

The project life cycle gives structure from idea to closure. Examiners often want you to show you understand that life cycles include decision gates, not only implementation phases.

A pragmatic life cycle for exam responses:

Initiation
Planning
Execution (Implementation)
Monitoring & Controlling
Closing

Key exam-ready principles:

Uncertainty is highest early, so planning is iterative.
Cost of changes is lowest early (before heavy implementation).
Risk exposure typically decreases as the project progresses (though new risks appear).

Initiation: From Need to Project Charter

Initiation answers:

Why is this project needed?
What opportunity or problem does it address?
Who authorises it?

In enterprise management assignments, initiation usually leads to a Project Charter. A strong charter typically includes:

Project purpose and justification
High-level scope
Stakeholders (initial identification)
High-level risks
Milestones
Budget range (even if approximate early)
Authority and responsibilities

The “Triple Constraint” and the Enterprise Triangle

Many students memorise the triple constraint: scope, time, cost. At postgraduate level, you should expand it to include quality and often risk and resources.

A useful way to explain it in exams:

Scope: what work is included
Time: how long it takes
Cost: total expenditure
Quality: fitness for purpose and acceptance criteria
Risk: likelihood and impact of events that affect delivery
Resources: availability of people, skills, and materials

Then link it to management decisions: if scope increases, either time or cost must increase, or quality must be adjusted (often not acceptable), or risks increase.

Roles and Governance: Who Decides?

Project management requires clear roles. Typical structures include:

Project Sponsor: provides funding and strategic alignment
Project Manager: coordinates planning and delivery
Project Team: performs work packages
Steering Committee (or project board): monitors strategic progress, resolves major decisions
Functional Managers: supply resources and manage line responsibilities
Stakeholders: influenced by or involved in the project

Exam tip: If a question asks “What is governance?” you can answer that governance is about how decisions are made, how accountability works, and how performance is monitored.

The Project Management Knowledge Areas (PGDip EM Relevance)

Even if your module uses a specific framework (often aligned to PMBOK-style thinking), exam expectations usually include:

Integration management (coordinating all aspects)
Scope management (defining and controlling what is included)
Schedule management (planning and tracking time)
Cost management (budgeting and cost control)
Quality management (ensuring deliverables meet requirements)
Resource management (staffing and team development)
Communications management (information flows)
Risk management (identification, analysis, response)
Procurement management (acquiring external goods/services)
Stakeholder management (engaging parties appropriately)

In enterprise management, you must also emphasise business outcomes:

measurable value delivered
adoption by users/customers
benefits realised post-launch

Project Success Criteria: Deliverable vs Business Value

Exams often test whether you can articulate:

Iron triangle success: deliver within scope/time/cost
Stakeholder success: satisfaction and acceptance
Business success: benefits realised (revenue, efficiency, reduced errors, improved compliance)

A project can “succeed” by meeting schedule and budget but still fail business value if users do not adopt the change. Therefore, your answers should include a benefits perspective.

Example: ERP Implementation “On Time” but Still Fails

Imagine an ERP system is delivered on schedule and within budget. However:

Data migration was incomplete
Training sessions were too short
Business processes were not redesigned

The system technically works, but users revert to spreadsheets. Business value is not realised because adoption is weak.

Your exam response should connect these dots: project management must include change readiness, training, communications, and stakeholder engagement—elements that support business benefits.

2) Project Planning: Scope, Schedule, Budget, and Quality

Planning transforms project intent into execution-ready structure. In a PGDip EM exam context, you often receive scenarios requiring you to outline processes, produce clear documents (WBS, risk register, schedule logic), and justify choices.

Scope Management: Defining Work Clearly

Scope management includes:

Collecting requirements
Defining scope (boundaries)
Creating WBS (breakdown into manageable components)
Validating scope (acceptance)
Controlling scope (changes)

Requirements vs Deliverables

A common confusion: requirements are what stakeholders need; deliverables are what the project produces.

Example:

Requirement: “The reporting dashboard must show monthly sales by region.”
Deliverable: “Dashboard module configured with data feeds + user access + testing evidence.”

In exams, if you use correct terminology—requirements, scope, deliverables—you typically gain marks for clarity.

Work Breakdown Structure (WBS): The Backbone for Planning

A WBS decomposes the project deliverables into smaller components until work packages are manageable.

A simple WBS approach:

Level 1: Project deliverables
Level 2: Major components
Level 3: Work packages
Level 4: Activities (sometimes integrated into scheduling)

Practical WBS Example for an Enterprise Project

Consider a project: “Implement a Customer Feedback System”.

A reasonable WBS (illustrative):

WBS Level	Component	Example Work Packages
1	Feedback System	Configure survey tools, integrate email/SMS, establish dashboards
2.1	Survey Design	Define questions, pilot testing, language review
2.2	Integration	Set up SMS/email triggers, data pipeline mapping
2.3	Dashboard & Reporting	Build dashboard views, define reporting schedule
2.4	Training & Adoption	Train customer service agents, adoption KPI tracking

Your exam response should explain:

Why WBS is created (to make planning feasible)
How it supports schedule and cost estimation
How it improves change control

Scope Baseline and Change Control

Once scope is defined, it becomes a baseline. Change control ensures:

Changes are requested formally
Impact is assessed (time/cost/quality/risk)
Approval is obtained before work proceeds

A strong exam answer describes a change control workflow:

Change request submitted
Impact analysis by project manager (often with technical leads)
Review by steering committee / sponsor if major
Approval or rejection
Update baselines (scope, schedule, costs)
Communicate decision to stakeholders

Schedule Planning: From Activities to Critical Thinking

Schedule management covers:

Activity definition
Sequencing
Estimating durations
Developing schedule
Controlling schedule

Activity Definition and Sequencing

In exam scenarios, you might be asked to outline steps for building a schedule. The key is to mention dependencies:

Finish-to-Start (FS): next activity starts after previous finishes
Start-to-Start (SS): next starts when previous starts
Finish-to-Finish (FF): next finishes when previous finishes
Start-to-Finish (SF): rare in practice, but conceptually possible

Estimating Duration: Deterministic vs Probabilistic Thinking

Many university exams accept rule-of-thumb methods:

Expert judgement
Historical data
Three-point estimation (optimistic, most likely, pessimistic)

At postgraduate level, showing you understand uncertainty helps:

If tasks depend on procurement lead times, durations are less certain.
If tasks are technical and well-defined, estimates can be tighter.

Critical Path Method (CPM): Exam-Relevant Scheduling Logic

CPM determines which sequence of activities drives the project end date. You need to demonstrate:

compute earliest start/finish times
compute latest start/finish times
identify activities with zero slack (critical activities)

Even if the exam does not require full numerical calculations, you should describe the concept clearly.

Example Logic (Without Full Numbers)

If Activity A must finish before Activity B and B is on the longest chain, delaying A delays B and delays the project end date. Critical activities are those where delays directly affect completion.

Cost Management: Budgeting with Structure

Cost management includes:

estimating costs
determining budget
controlling costs
forecasting performance

A typical exam structure:

Estimate cost for each work package/activity
Aggregate into budgets per phase
Create a cost baseline
Monitor actuals and variances
Forecast at completion

Cost Types: Direct, Indirect, Fixed, Variable

Students often lose marks by only saying “costs.” Distinguish:

Direct costs: labour, materials directly tied to deliverables
Indirect costs: overhead, facilities, administration
Fixed costs: stable regardless of output in the short term
Variable costs: change with activity level (e.g., consumables)

Earned Value Management (EVM): Why It Appears in Exams

EVM integrates scope, schedule, and cost by using:

PV (Planned Value): what should have been done by a date
EV (Earned Value): what has been done measured in budget terms
AC (Actual Cost): what it actually cost

Common EVM metrics:

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

Exam tip: If you are given numbers, compute systematically and interpret meaning in words.

Example: Interpret EVM Results in Enterprise Terms

Suppose:

PV = R500,000
EV = R420,000
AC = R450,000

Then:

SV = EV − PV = R420,000 − R500,000 = −R80,000 (behind schedule)
CV = EV − AC = R420,000 − R450,000 = −R30,000 (over budget)

Interpretation:

Work produced is less than planned by value.
It also cost more than planned for the work achieved.
Management actions: investigate causes (resource delays? rework? supplier issues) and adjust forecasts.

Quality Planning: Acceptance Criteria and Prevention

Quality management is not only inspection; it is prevention and process control.

Key exam concepts:

Quality planning: decide how to meet requirements
Quality assurance: audit processes to ensure compliance
Quality control: inspect results/deliverables

Acceptance Criteria

A deliverable should have acceptance criteria. Example:

“Dashboard must load within 3 seconds for standard datasets.”
“Reports must match source data within ±1% tolerance.”
“User training attendance records and assessment scores meet minimum thresholds.”

Quality planning is tied to stakeholder satisfaction and risk reduction.

Planning Outputs: Documents Examiners Love to See

Common outputs:

Project charter
Project management plan (integration of subsidiary plans)
WBS and WBS dictionary
Schedule baseline
Cost baseline
Risk register
Quality management plan
Communications plan
Stakeholder register

In exams, if asked “What should be in a project plan?” you can mention these and relate them to project control.

3) Risk, Stakeholders, and Communications: Managing Uncertainty in Enterprises

Projects rarely fail solely because planning is poor; they fail because risks materialise, stakeholders react, information flows break down, and decisions are delayed. In PGDip EM, the examiner expects you to demonstrate structured risk management and credible stakeholder engagement.

Risk Management: Identification to Response

Risk management typically includes:

Risk identification
Qualitative analysis (probability and impact categories)
Quantitative analysis (optional/advanced)
Risk response planning
Risk monitoring and control

Risk Identification Techniques

Common techniques to mention:

expert interviews
brainstorming
document review (contracts, specs, past projects)
checklists
assumption analysis
SWOT-like thinking (strengths and weaknesses can be sources of risk)

Building a Risk Register

A risk register often has columns:

risk description
category (technical, schedule, cost, stakeholder, external)
probability
impact
score (e.g., P×I)
response strategy
owner
trigger conditions
contingency plans

Exam tip: Show ownership. Every risk should have a named responsible person/role.

Risk Response Strategies

Four classical response strategies:

Avoid: eliminate the threat
Mitigate: reduce probability/impact
Transfer: shift risk to another party (e.g., insurance, contract)
Accept: acknowledge risk and plan contingency

Also mention:

Exploit (for opportunities)
Enhance
Share
Accept

Enterprise Example: Procurement Risk

A project depends on a vendor delivering equipment by a fixed date. Risks include:

delayed delivery due to shipping delays
quality issues on arrival
vendor capacity constraints

Responses:

Avoid: choose a local supplier with shorter lead times
Mitigate: place early order + negotiate delivery windows
Transfer: include penalty clauses in contract
Accept: keep contingency time and budget for expedited shipping

Opportunity Management: Positive Risks Matter Too

In enterprise projects, opportunities are just as important:

Adoption of a new tool accelerates process improvements
Partner organisations can reduce delivery cost
Media attention increases customer uptake

Opportunity response:

create plans to capture value if conditions occur
assign owners for opportunity tracking
integrate into schedule as “value tasks” where feasible

Risk Triggers and Contingency Planning

A common weakness in student answers is describing a risk without trigger conditions. Strong answers include triggers such as:

“If vendor delivery slips by more than 5 business days, activate expedited shipping plan.”
“If stakeholder feedback shows repeated confusion during pilot testing, trigger additional training sessions.”
“If defect rate exceeds threshold in early testing, pause rollout and conduct root-cause analysis.”

Stakeholder Management: Mapping Influence vs Interest

Stakeholders include anyone impacted by the project or who can influence it:

internal users
managers
suppliers
regulatory bodies
unions (in some enterprise contexts)
customers (direct or indirect)

Stakeholder Analysis Tools

Common classification:

Power/Interest grid
salience model (power, legitimacy, urgency)
RACI matrix (Responsible, Accountable, Consulted, Informed)

In exams, you should state how analysis helps:

prioritise engagement
tailor communication strategies
reduce resistance and misinformation

Engagement Strategies by Stakeholder Category

A practical approach:

High power, high interest: close manage, frequent meetings, co-decision
High power, low interest: keep satisfied, concise updates
Low power, high interest: keep informed, involve in feedback loops
Low power, low interest: monitor, minimal communication

Example: Resistance from Operational Staff

In an enterprise implementing a new process, operational staff may resist due to fear of job impact or extra workload. Stakeholder engagement strategies:

communicate benefits (e.g., fewer errors, less rework)
show how the new system reduces manual work
involve them in pilot testing
provide training and support
address concerns through structured feedback

If an exam asks “How do you handle resistance?” a strong answer includes prevention (communications, involvement), correction (training, adjustments), and escalation (sponsor intervention for policy issues).

Communications Management: Information as a Project Deliverable

Communications are not “messages”; they are planned information flows.

Elements:

communication requirements
frequency and channels
message content tailored to stakeholder needs
reporting formats
escalation paths

Communication Plan Essentials

A communications plan often specifies:

stakeholder group
information needed
frequency (weekly, monthly, milestone-based)
channel (email, meetings, dashboards)
owner (project manager, sponsor, team lead)
purpose (inform, consult, decide)

Project Reporting: What to Put in a Status Report

A typical status report includes:

progress against schedule baseline
progress against scope (what was completed / what remains)
cost performance (actual vs budget)
risk status (new risks, changes in rating)
quality status (defects, acceptance tests)
issues/decisions required
next milestones

Exam tip: If asked to explain “What is the difference between an issue and a risk?”

Risk: potential future event (uncertain)
Issue: current problem requiring action

Example: Communications Failure and Its Consequences

Scenario:

Vendor sends technical changes.
Project manager assumes the team received the notice.
Users test the deliverable based on the old configuration.

Result:

rework
schedule slip
increased cost
stakeholder frustration

Lesson: communications planning must ensure the correct information reaches the correct people at the correct time with version control.

Monitoring Stakeholder Engagement

Stakeholder engagement is dynamic. You should monitor:

sentiment (supportive/resistant)
participation level
risks related to stakeholder behaviour
changes in stakeholder power or priorities

An exam answer should state that engagement strategies are revisited as project context evolves.

4) Project Implementation, Monitoring & Control: Delivering Under Pressure

Implementation is where plans meet reality. Monitoring and controlling ensures deviations are detected early, analysed, and corrected. This section emphasises decision-making, performance measurement, change control, and leadership behaviours.

Executing Projects: Turning Plans into Action

Execution involves:

managing people
managing resources
implementing the planned work
coordinating approvals and deliverables
maintaining quality and compliance
performing project communications

In enterprise projects, execution typically includes:

procurement activities
technical development and configuration
training and change management activities
rollout planning and go-live readiness

Managing the Project Team

Key team management practices:

clarify roles and responsibilities
manage workloads
develop competencies (training)
handle conflict and team dynamics
maintain motivation and accountability

A strong exam response connects team performance to schedule reliability. If a team is over-allocated or lacking skills, tasks slip and quality defects increase.

Monitoring & Controlling: Detecting Variance Early

Monitoring ensures work is tracked continuously; controlling ensures corrective action is taken.

Core control actions:

compare actual vs planned performance
analyse variance causes
recommend corrective or preventive actions
update baselines if changes are approved
document lessons learnt

Integration of Control: Change Management at Scale

Because projects are interdependent, a change in one area affects others. For example:

a schedule change affects cost and staffing
a scope change affects quality and risk
new stakeholder requirements affect acceptance criteria

Thus, integrated change control ensures decisions consider full project impacts.

Performance Dashboards and Metrics

Exams often ask for which metrics to track. Provide examples:

Schedule:

% complete by work package
milestone attainment
critical path changes

Cost:

budget burn rate
forecast at completion
cost variance (AC vs EV, if using EVM)

Quality:

defect density
test pass rates
number of rejected deliverables
audit findings

Risk:

changes in probability/impact
emerging risks
risk response effectiveness

Using EVM to Manage: Practical Interpretation

If you compute EVM metrics, the key is to interpret:

CPI < 1: cost inefficiency—spend is higher than earned progress
SPI < 1: schedule inefficiency—progress is behind plan
Trends: persistent variance means forecast changes needed

A management response could include:

adjust staffing levels
renegotiate scope priorities
accelerate tasks (crashing/fast-tracking—though with trade-offs)
re-baseline with sponsor approval if warranted

Corrective vs Preventive Actions

Students often confuse these. Clarify:

Corrective actions: fix performance already deviating (after a problem occurs)
Preventive actions: prevent potential future problems (before deviations happen)

Example:

Corrective: a defect discovered in testing leads to rework.
Preventive: increase test coverage before release to avoid similar defects.

Issue Management: Escalation and Decisions

Issues are current obstacles. Strong issue management:

logs issues with owners
sets resolution deadlines
escalates when blocked by sponsor decisions or policy constraints
tracks resolution evidence

An exam may ask: “How would you handle an issue requiring executive decision?”
Answer with:

document issue impact (time, cost, quality)
propose options with trade-offs
request decision
implement approved resolution and communicate

Fast-Tracking, Crashing, and Their Risks

In advanced schedule control, two classic techniques:

Fast-tracking: performing activities in parallel that were normally sequential
Crashing: adding resources to shorten duration (overtime, additional staff)

Both can increase risk and cost. In enterprise management, you must justify them:

if a regulatory deadline is fixed, time compression may be necessary
if quality risk rises, additional testing or rework budget must be included

Quality Control During Execution: Gatekeeping Deliverables

Quality control includes:

inspections and tests
review of deliverables against acceptance criteria
configuration/version management
documentation for audits

Example: In a compliance-related project, quality gates could include:

sign-off by compliance officer
evidence of risk assessments
training records
audit trails

Change Requests During Implementation

Most projects experience changes. The exam expects you to manage them:

record change request
determine impact on scope/time/cost/quality/risk
consult relevant stakeholders
obtain approvals based on severity and governance
update baselines accordingly
communicate changes clearly

If you do not control changes, “scope creep” can destroy schedule and cost forecasts.

Leadership and Professional Responsibility

Project managers influence outcomes through:

stakeholder trust
decision quality
fairness and transparency
escalation discipline
ethical conduct

Postgraduate-level answers should demonstrate judgement, not just process. For instance:

do not hide bad news—communicate early with options
protect the project from uncontrolled changes
balance technical needs with stakeholder expectations

Case Scenario: Implementation Failure Avoidance

Consider a project to implement a new procurement system. During execution:

users complain about usability
the system meets technical requirements but adoption is low
managers request changes that were not planned

A project manager should:

treat “adoption” as a quality and stakeholder acceptance issue
use user feedback sessions
prioritise changes based on scope governance
update training materials and possibly user journeys
manage expectations through communications

This scenario links execution with stakeholder engagement and quality acceptance criteria.

5) Project Closure, Benefits Realisation, and Exam-Ready Framework Answers

Project closure is where many marks are lost. Students often end at “deliverables completed,” but a complete project management answer includes formal closure, knowledge transfer, performance evaluation, and benefits realisation.

What Closure Includes

Closure activities typically include:

Verify deliverables are complete and accepted
Hand over to operations or product owners
Close contracts and settle procurement items
Finalise documentation (lessons learnt, final reports)
Release resources
Conduct post-project evaluation (success vs targets)

An exam question may ask: “Explain project closure and its importance.” Your answer should highlight:

accountability
risk reduction after handover
continuity of operations
organisational learning

Administrative Closure vs Project Closure

Administrative closure refers to:

signing completion documents
closing out procurement
updating systems and records

Project closure includes:

confirming acceptance criteria
ensuring knowledge is transferred
evaluating whether project objectives were achieved

If a project is “technically completed” but not operationally stable, operational readiness must still be assessed.

Benefits Realisation: The Enterprise Management Lens

Postgraduate enterprise management expects you to think beyond completion. Benefits can include:

cost savings (reduced manual work)
revenue growth (improved customer experience)
risk reduction (compliance and fewer incidents)
productivity improvements (faster processes)
service quality (reduced defects and better response times)

Benefits realisation usually occurs:

during adoption and rollout
post go-live as processes stabilise

Example: Customer Service Process Improvement

A project implements a workflow system. Deliverables are installed. However, benefits only occur if:

staff actually use the workflow
escalation rules are followed
reporting is used for improvement cycles

Thus, closure must include operational adoption support and measurement of KPIs.

Post-Implementation Review and Lessons Learnt

A strong closure includes:

what went well
what did not go well
root causes of issues
recommendations for future projects

Lessons learnt should not only describe events but explain:

why they happened
what decision framework could have improved outcomes
what changes to templates/processes would prevent recurrence

Project Success Evaluation: Multi-Dimensional Scoring

Success evaluation can use:

schedule performance (milestones achieved)
cost performance (actual vs budget)
quality performance (acceptance and defect rates)
stakeholder satisfaction (feedback)
benefits realisation (operational metrics)

Example: Multi-Criteria Success Table (Illustrative)

Dimension	Target	Result	Interpretation
Schedule	Milestone by 30 June	Achieved 5 July	Slightly late
Budget	Within R2,000,000	Within budget	Cost controlled
Quality	Acceptance sign-off	Achieved	Deliverables meet requirements
Stakeholders	Positive satisfaction feedback	Mixed	Adoption challenges
Benefits	Reduce process time by 20% by month 3	Only 10%	Benefits delayed

If you include such analysis in an exam, ensure the logic is coherent and explain actions needed to address adoption and benefits delays.

Common Exam Question Patterns and How to Answer

University exam questions often fit recurring forms. Below are the patterns and exam-ready response frameworks.

Pattern 1: “Explain the difference between risk and issue”

Answer structure:

Define risk (uncertain future event)
Define issue (current problem)
Provide example for each
Mention management response: risk planning vs issue resolution

Pattern 2: “Describe how you would manage scope creep”

Answer structure:

Scope baseline importance
Change control workflow
Requirements traceability (if relevant)
Stakeholder communication and approval gates
Monitoring scope with WBS and acceptance criteria

Pattern 3: “Build a project schedule conceptually”

Answer structure:

Define activities from WBS
Determine dependencies
Estimate durations
Apply sequencing to build schedule
Identify critical path
Plan monitoring and controls

Pattern 4: “Use EVM to interpret performance”

Answer structure:

Write given values (PV, EV, AC)
Compute SV, CV, SPI, CPI
Interpret (ahead/behind, under/over budget)
Recommend management actions (corrective steps)

Pattern 5: “Stakeholder engagement plan”

Answer structure:

Identify stakeholders
Determine power/interest classification
Define engagement strategies per group
Create communications plan (frequency/channel)
Monitor engagement and update plan

A Full Integrated Mini-Case for Revision

To consolidate learning, consider a coherent enterprise mini-case that ties together planning, risk, stakeholder management, execution control, and closure. Use this as a mental “template” for exam scenarios.

Mini-Case: School-to-Enterprise Training Programme System

An enterprise partner needs to launch a digital management system to coordinate training sessions for youth development. The project includes:

user registration
scheduling training sessions
capturing assessments
reporting outcomes to the enterprise partner
training for staff and volunteer coordinators

Initiation outputs:

project charter: objective to improve scheduling accuracy and reporting timeliness
success criteria: system acceptance by staff, stable reporting by month end

Planning outputs:

WBS: modules for registration, scheduling, assessments, reporting, training
schedule baseline: milestones for configuration, pilot testing, staff training, go-live
cost baseline: internal labour + external hosting and support costs
quality plan: test cases and acceptance thresholds (e.g., correct scheduling rules, report accuracy)

Risk and stakeholder management:

risks: delayed hosting setup; data privacy concerns; low adoption
stakeholder engagement: enterprise partner high power/high interest; volunteer coordinators high interest/low power
communications: weekly status updates to sponsor; daily pilot issue tracking for team during pilot

Execution and control:

implement configuration and integrate data
monitor defects and user feedback
manage change requests using integrated change control
use issue log to track blockers and escalate decisions

Closure and benefits:

verify deliverables meet acceptance criteria
handover to operations and ensure training completion
conduct post-implementation review and measure outcomes: improved scheduling accuracy and reporting timeliness

In an exam, if you write this integrated logic with clear headings and correct terminology, you demonstrate comprehensive competence.

Practical Study Checklist for PGDip EM Project Management Exams

Use this checklist to structure your revision and your exam responses:

Define key terms precisely (project, stakeholder, risk, issue, baseline)
Use correct frameworks (WBS, change control, EVM logic, stakeholder power/interest)
Provide structured answers with headings and steps
Include examples (mini scenarios showing how the concept works)
Interpret results (not just computations)
Recommend actions aligned to the problem and governance
Close the project properly (acceptance, handover, lessons learnt, benefits)

Alignment with South African PGDip/Management Exam Style

South African university project management assessments often expect:

formal tone and structured responses
scenario-based application of concepts
correct use of project documentation terms
coherent reasoning (why a method is appropriate)

In that style, the strongest answers usually:

begin with definitions or context
proceed in logical step order (initiate → plan → execute → monitor/control → close)
include at least one concrete example
demonstrate management judgement for trade-offs and uncertainties

Conclusion: Building Exam-Ready Project Management Competence for Rhodes PGDip EM

Rhodes University’s PGDip in Enterprise Management builds project capability that serves enterprise outcomes: alignment to business value, disciplined planning, structured uncertainty management, stakeholder engagement, and reliable delivery. To excel in project management exams, you must present answers that are both methodologically correct and scenario-aware—showing how decisions affect time, cost, quality, risk, and adoption.

If you can consistently structure your responses around life cycle phases, use the key artefacts (charter, WBS, baselines, risk register, communications plan), and interpret performance (especially EVM when numbers are provided), you will demonstrate the competence required at postgraduate level and score strongly on applied questions.