Regent MBA Specialisation in Project Management Notes

The Regent Business School MBA Specialisation in Project Management equips candidates with advanced tools for planning, executing, monitoring, and closing projects under real-world constraints such as time, cost, scope, risk, and stakeholder expectations. These exam notes are written in a South African study style—aligned to what you are likely to encounter in assessment scenarios and common curricula themes such as project governance, PMBOK®-aligned processes, scheduling and cost control, and change and risk management. The guide also mirrors the way many students prepare for UNISA-style and CUT-style exam questions: structured answers, stepwise reasoning, and applied examples rather than theory-only responses.

This is part of a collection categorized as “Regent Business School Project Management Qualification Notes.” It is designed for exam preparation, assignment support, and revision across the core specialisation competencies.

Section 1: Project Management Foundations for MBA-Level Specialisation (Regent Context + Core Concepts Often Tested)

At MBA level, “Project Management Foundations” usually does not mean repeating basic definitions. Examiners expect you to distinguish between projects and operations, understand project lifecycle logic, and demonstrate competence in governance, stakeholder management, and professional ethics. Many exam questions also test whether you can translate PM theory into decisions—e.g., how governance structures affect risk, how stakeholder engagement changes scope outcomes, or how early planning reduces rework later.

Projects vs Operations (and Why MBA Questions Care)

A project is a temporary endeavour with a defined start and end, producing a unique product, service, or result. An operation is ongoing and repetitive (e.g., customer support desk, monthly payroll runs). MBA exam questions frequently ask you to identify whether a scenario describes a project or operational work, then explain why that classification matters.

Key distinctions:

Uniqueness: Projects produce something not produced before in exactly the same way.
Temporal boundaries: Projects have a timeline and deliverable milestones.
Constraints: Scope, time, cost, and quality must be managed.
Uncertainty: Projects have higher variability and risk than operations.
Change in team composition: Roles often shift across phases.

Example scenario (common exam style):
A municipality implements a new integrated billing system across departments. The work begins at contract signing and ends at system handover with a specific go-live date, but the billing operations continue after go-live. This is a project because the implementation is unique and bounded in time.

Why it matters for governance and controls:

In operations, performance control focuses on stability (SLA compliance, throughput, defect rates).
In projects, performance control must handle change requests, shifting baselines, and milestone-based accountability.

Project Lifecycle and Phase Logic

A project lifecycle describes the series of phases from initiation to closure. Common phase patterns include:

Initiation
Planning
Execution/Implementation
Monitoring and Controlling
Closing

Some projects follow a predictive (waterfall), iterative, or hybrid approach. At MBA level, the question is often not “which method is best?” but “how do you justify the chosen approach using constraints and risk?”

Predictive vs Agile vs Hybrid (MBA-appropriate answer structure)

Predictive (Waterfall) is appropriate when:

Requirements are relatively stable.
You can define scope clearly early.
Regulatory or contract conditions require document-heavy assurance.

Agile/Iterative is appropriate when:

Requirements are evolving.
Frequent feedback reduces uncertainty.
Deliverables can be broken into increments.

Hybrid is common in large organisations because:

Governance and budgeting often remain predictive,
while delivery uses iterative increments.

Counter-argument often expected by markers:
Students who say “Agile is always best” lose marks. In regulated environments (e.g., financial services, health systems), the governance needs evidence and traceability. Agile may still be used, but within controlled compliance processes.

The PMBOK® Process Thinking (How to Answer Without Being Overly Technical)

Most Regent-style assessments expect understanding of process grouping rather than memorisation. A strong exam answer often uses the logic of planning (baseline creation), execution (work performance), and monitoring & controlling (performance measurement and corrective actions).

A practical framing:

Planning processes: develop plans and baselines for scope, schedule, cost, quality, communications, risk.
Executing processes: coordinate people/resources, perform the work.
Monitoring & controlling processes: track performance vs baselines, manage changes, control risk, verify deliverables.
Closing processes: finalise acceptance, release resources, archive lessons learned.

Governance: The Hidden Marker for High Scores

At MBA level, project governance is often the difference between a pass and a distinction. Governance answers often score highly when you:

Identify governance structures (sponsor, steering committee, PMO, project board).
Explain their responsibilities (approval, oversight, escalation, accountability).
Link governance to risk and performance outcomes.

Common governance mechanisms

Project charter approval by the sponsor/steering committee.
Stage-gate reviews (decision points between phases).
Change control board (CCB) for scope/time/cost changes.
Status reporting standards and cadence.
Escalation pathways for issues beyond the PM’s authority.

Example:
If a project faces cost overruns and scope creep, governance should determine:

whether the baseline can be renegotiated,
whether the change is approved (and under what trade-offs),
whether risk response plans are updated.

Without governance, you get informal approvals, delayed escalation, and inconsistent decision-making—typically leading to disputes and failed delivery.

Stakeholder Management: From “List Stakeholders” to “Manage Influence”

A strong answer should show you can manage stakeholder influence and engagement using a strategy. Many exam questions test:

how to identify stakeholders,
how to assess their power/interest,
how to tailor communication and engagement plans.

Stakeholder identification tools (typical MBA study content)

Power/interest grid (high power/high interest: manage closely).
Influence/impact mapping (who can block vs who can enable).
Stakeholder register (name, role, expectations, influence, communication needs).

Example of a stakeholder management plan (applied)

Project: Implement a digital document management system in a hospital.

Stakeholders:

Hospital CEO (high power, high interest)
IT department (high power, medium interest)
Doctors (medium power, high interest because of usability)
Nurses (medium power, high interest)
Union representatives (medium/high power due to policy and labour relations)
Patients (low power but high impact on service quality)

Engagement strategy:

CEO: monthly executive dashboards + decision briefs.
Doctors: usability workshops and pilot feedback loops.
Nurses: targeted training, “super-user” support, quick reference guides.
Unions: early consultation, clear data handling policies, change management support.

Why this matters: If nurses resist adoption, the system may technically be delivered but operational value fails—an exam marker will reward recognising that stakeholder engagement is not “soft skills”; it is risk management.

Ethics and Professional Responsibility in Project Leadership

MBA-level project management also includes professional responsibility: integrity, transparency, confidentiality, and avoiding conflicts of interest.

Common exam prompts:

“What ethical issues might arise during procurement?”
“How should the PM handle misinformation in status reports?”

A high-scoring answer often mentions:

accurate reporting (no masking of delays/risks),
conflict declarations (e.g., if a PM’s relative bids for work),
fair procurement processes,
compliance with contract and organisational policies.

Section 2: Project Planning, Baselines, and Scheduling/Course-Work Skills (UNISA/CUT-Style Exam Applications)

This section focuses on the planning and baseline logic that shows up in exam questions and assignments. Many South African students prepare using modules like UNISA’s project management papers (commonly taught in distance learning formats) and similar applied course structures from institutions such as Cape Peninsula University of Technology (CPUT), Central University of Technology (CUT), and other business faculties. Even when module codes differ, the exam pattern is consistent: candidates must create coherent baselines, explain schedule/cost trade-offs, and justify how planning reduces uncertainty.

To make the guide practical, each concept includes exam-ready steps and examples.

The Project Management Plan and Baselines

A project management plan is the integrated set of subsidiary plans and baselines. Typical components include:

Scope management plan
Schedule management plan
Cost management plan
Quality management plan
Resource management plan
Communication management plan
Risk management plan
Procurement management plan
Change management approach

At MBA level, you should be able to explain what is meant by a baseline:

Scope baseline: the approved scope statement and WBS.
Schedule baseline: planned start/finish dates for activities and milestones.
Cost baseline: budget approved by the controlling authority.

Exam tip (conceptual clarity):
A baseline is not a guess. It is an agreed reference point for performance measurement.

Work Breakdown Structure (WBS): The Foundation of Control

The WBS decomposes the project deliverables into smaller components. For scoring, you should show:

a logical decomposition approach,
consistent numbering,
mapping WBS elements to deliverables,
integration with schedule and cost estimates.

WBS example (applied)

Project: Build a small solar energy system for a community centre.

Deliverable breakdown (example):
1.0 Project management and governance
2.0 Site survey and design
3.0 Procurement of solar components
4.0 Installation
5.0 Testing and commissioning
6.0 Training and handover
7.0 Close-out and documentation

You can then break 4.0 installation further:
4.1 Mounting structures
4.2 Electrical cabling
4.3 Inverter installation
4.4 System integration

In exams, markers reward logical decomposition and clarity in how WBS supports cost/schedule control.

Estimating Methods (and How to Defend Your Choice)

Cost and duration estimation are common high-mark questions. Candidates often lose marks by stating methods without justifying when to use them.

At MBA level, you may be asked to choose between:

Analogous estimating (use historical similar projects),
Parametric estimating (use statistical relationship, e.g., cost per square metre),
Bottom-up estimating (sum detailed activity estimates),
Three-point estimating (optimistic, most likely, pessimistic).

Example: Choosing estimation for a training rollout

If an NGO has delivered similar training before, analogous estimating may be reasonable early. But if the training includes a new module and new delivery channels (e.g., WhatsApp-based coaching + face-to-face workshops), bottom-up or three-point methods are stronger because uncertainty is higher.

Scheduling: Critical Path, Float, and Trade-offs

A schedule is more than a list of tasks—it is a logic network with dependencies, criticality, and resource impacts. In exams, you may encounter statements like “the project is late because of a delay in Activity B” and must identify whether Activity B is on the critical path.

Critical Path Method (CPM) essentials

To compute critical path you need:

activity durations,
dependencies (FS, SS, etc.),
earliest start/finish,
latest start/finish,
slack/float.

Critical path: activities with zero (or near-zero) float.

Example calculation (simple but exam-aligned)

Consider a mini-project:

A: 2 days (start)
B: 3 days (after A)
C: 4 days (after B)
D: 2 days (after A)
E: 1 day (after D)

Total paths:

Path 1: A(2) + B(3) + C(4) = 9 days
Path 2: A(2) + D(2) + E(1) = 5 days

Critical path is Path 1 (activities A, B, C). If B slips by 1 day, the project finish shifts (unless mitigation changes dependencies).

Resource Loading vs Schedule Compression

Projects at MBA level often involve resource constraints. You may be asked to explain:

resource loading effects,
schedule compression methods (crashing vs fast tracking),
consequences for cost and risk.

Crashing vs fast tracking

Crashing: reduce duration by adding resources (usually increases cost).
Fast tracking: perform activities in parallel that were originally sequential (increases risk due to rework/overlap).

Exam-quality answer structure:

Describe the technique.
Explain the trade-off (cost vs risk).
Give mitigation steps.
Provide an example.

Example (fast tracking in software delivery)

If requirements and design are usually sequential, fast tracking might begin detailed design while requirements are still being validated. This can speed delivery but risks:

changing designs later,
rework,
integration instability.

Mitigation:

set decision thresholds,
limit parallel work to stable requirements,
maintain strong change control.

Cost Baseline and Cost Control

Cost planning and cost control are closely linked. A typical MBA scenario might ask you what to do when actual costs exceed budget and schedule slips.

Core ideas:

Planned Value (PV): value of planned work by a time.
Earned Value (EV): value of completed work.
Actual Cost (AC): cost actually incurred.

From these:

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

Even if your course uses a slightly different notation, the logic remains: compare planned vs earned vs actual.

Example using consistent numbers

Assume by week 6:

PV = R 600,000 (planned work expected)
EV = R 450,000 (work actually completed)
AC = R 520,000 (actual spend)

Then:

SV = 450,000 − 600,000 = −R 150,000 (behind schedule)
CV = 450,000 − 520,000 = −R 70,000 (over budget)
CPI = 450,000 / 520,000 ≈ 0.865
SPI = 450,000 / 600,000 = 0.75

Interpretation for exam marking:

CPI < 1 implies inefficiency (spending too much per unit of progress).
SPI < 1 implies slow progress.

Correct action would include:

analyzing root causes,
updating forecasts,
addressing resource issues,
managing changes and risks.

Quality Planning and Assurance (Often Overlooked)

At MBA level, quality is not only “inspection.” It includes:

quality planning (defining quality requirements and metrics),
quality assurance (auditing processes for compliance),
quality control (inspecting outputs).

Example: Construction project quality

If the deliverable is a building extension:

quality requirements might include concrete strength specifications,
assurance involves process audits of concrete batching and curing,
control involves testing samples and inspecting surfaces.

In exams, if you only mention “inspect at the end,” you often lose marks. High-scoring answers mention prevention and process assurance.

Section 3: Risk, Procurement, and Change Control—Decision-Making Under Uncertainty (Aligned to Regent MBA Explanations)

MBA-level specialisation requires risk management and procurement competence because most large failures occur due to unresolved uncertainty, poor contracting strategy, and unmanaged change. This section builds a structured risk process and shows how procurement and change control integrate with risk and governance.

Risk Management: From Identification to Response (and How to Score in Exams)

Risk management is not a single event. A standard process includes:

Plan risk management
Identify risks
Perform qualitative analysis
Perform quantitative analysis (when needed)
Plan risk responses
Implement responses
Monitor risks

At exam level, you must show not just lists of risks, but how you evaluate and respond.

Qualitative Risk Analysis: Probability × Impact Logic

Common qualitative method:

define a probability scale (e.g., Low/Med/High),
define an impact scale (e.g., cost/time/quality),
compute a risk rating (often probability × impact).

Example risk register entry (exam-friendly)

Risk: “Supplier delays delivery of inverter components.”

Probability: High (0.7)
Impact: Medium to High (cost overrun + schedule slip)
Response: contingency plan, dual-source supplier, expediting, penalty clauses

High scoring includes:

who owns the risk,
triggers and thresholds,
response time.

Quantitative Risk Analysis: Expected Monetary Value (EMV)

Quantitative analysis is used when you need numerical estimates to compare options. A widely used method is EMV:

EMV = Σ (Probability of outcome × Monetary value of outcome)

Example: decision between two procurement strategies

Strategy A:

30% chance of no delay (no extra cost)
70% chance of delay costing R 200,000 extra

EMV_A = 0.30×0 + 0.70×200,000 = R 140,000

Strategy B:

80% chance of no delay (extra cost R 80,000 for guaranteed delivery)
20% chance of delay costing additional R 50,000 (but guaranteed delivery reduces probability)

Let’s interpret carefully for consistency:

Under Strategy B, you pay a fixed premium of R 80,000 regardless.
If delay occurs, add R 50,000 extra.

Outcomes:

80%: extra = 80,000
20%: extra = 80,000 + 50,000 = 130,000

EMV_B = 0.80×80,000 + 0.20×130,000
= 64,000 + 26,000
= R 90,000

Decision logic: Strategy B has lower EMV, so it is the economically preferred option based on quantified risk.

Risk Response Strategies: Avoid, Mitigate, Transfer, Accept

Examiners like you to explain response type and link it to risk mechanism.

Avoid: change plan to remove risk cause.
Mitigate: reduce probability and/or impact.
Transfer: shift impact to third party (insurance, guarantees, contract terms).
Accept: acknowledge risk with no proactive action, but set contingency reserves.

Example: transfer vs mitigate in procurement

Risk: “Contractor fails to complete electrical installation on time.”

Mitigate: create detailed technical specifications, enforce milestones, quality checks.
Transfer: include liquidated damages in contract or performance bonds.

A balanced answer explains both are not mutually exclusive.

Contingency Reserves vs Contingency Planning

A common confusion: reserves are not a substitute for response planning.

Contingency reserve: budget set aside for known-unknown risks.
Management reserve: for unforeseen risks beyond identified risk register.

At MBA level, you should mention how governance uses these reserves:

CCB or steering committee approves use,
PM must justify spend and update baselines if required.

Monitoring and Controlling Risks: Triggers and Replanning

Risk monitoring includes:

checking whether triggers occurred,
tracking risk register updates,
monitoring risk exposure trends.

Example of a trigger-based escalation

Trigger: “If supplier lead time exceeds 5 working days beyond promised date.”
Action:

notify procurement manager,
activate expediting clause,
reorder critical components from alternate supplier,
update schedule baseline if mitigation changes completion dates.

Procurement Management: Contract Strategy as Risk Control

Procurement is a major risk lever. Procurement failure can create schedule slippage, quality defects, cost overrun, and disputes.

At MBA level, procurement topics include:

make-or-buy decisions,
procurement planning,
source selection,
contract administration.

Make-or-Buy Decision (Applied)

A make-or-buy analysis compares:

internal cost and capability,
external vendor cost and time,
risk of outsourcing,
strategic considerations.

Example: manufacturing vs outsourcing a component

If a company lacks capacity to produce a component for a fixed delivery date:

buying may reduce timeline risk,
but increases vendor dependency risk.

A strong exam answer includes both cost and schedule risk.

Contract Types (How They Affect Project Outcomes)

Common contract categories:

Fixed-price: buyer pays fixed amount; risk shifts to seller for scope/delivery uncertainty.
Cost-plus: seller reimbursed for allowable costs; buyer bears more cost risk.
Time-and-materials: pay for time and materials; requires tight monitoring.

In exams, you may be asked to recommend the contract type based on uncertainty:

For uncertain scope, fixed-price may lead to disputes; cost-plus or T&M with clear governance may be safer.
For stable requirements, fixed-price provides cost predictability.

Change Control: The Interface Between Scope and Risk

Change control is the mechanism to ensure that:

requested changes are evaluated for cost/time/scope/quality impacts,
approved changes update baselines,
rejected changes are documented to prevent “shadow scope.”

Change control process (stepwise for exam marks)

Change request submitted (documented form)
Impact assessment (scope/schedule/cost/quality/risk)
Review by CCB / governance body
Decision: approve/reject/hold/modify
Update baselines if approved
Communicate changes to stakeholders
Track implementation and validate results

Example: minor change that becomes major risk

A contractor requests a “small material substitution” because of availability. The substitution seems minor but affects:

supplier lead time,
compliance with standards,
integration with existing components.

If the change bypasses formal control:

quality risks increase,
rework happens,
total project cost increases.

A high-scoring exam response states that “minor change requests” should still go through impact assessment because they can change risk exposure.

Integrating Risk + Procurement + Change Control (MBA exam strength)

A top MBA answer shows you can integrate processes.

Example integration:

A supplier risk emerges (lead time risk).
You consider procurement mitigation (dual sourcing, expediting).
That triggers a change request to adjust schedule and possibly cost baselines.
Governance approves the change if it reduces overall risk exposure.

This integrated logic often differentiates an A-grade answer from a generic one.

Section 4: Execution Management, Stakeholder Communication, and Performance Reporting (What Exams Test at “Application” Level)

This section focuses on executing work, managing communications, and reporting performance. Many exam questions test how a PM should lead execution when uncertainty exists, and how to maintain stakeholder trust through transparent reporting.

Project Execution: Coordinating People and Resources

Execution is where plans become reality. Key execution responsibilities include:

directing and managing project work,
ensuring quality deliverables are produced,
managing stakeholder engagement,
implementing approved changes,
acquiring and managing resources.

At MBA level, exam questions often include scenarios like:

“The team is behind schedule but stakeholders are pressuring for frequent updates.”
“Quality defects are occurring and work must be paused.”
“A stakeholder is threatening escalation due to poor communication.”

A strong answer demonstrates structured leadership:

verify facts,
analyse root causes,
implement corrective actions,
communicate with agreed cadence.

Communication Management: Cadence, Audience, and Content

Communication is not one-size-fits-all. A communication plan defines:

what information is shared,
with whom,
how often,
format (email, report, dashboard, meeting),
escalation thresholds.

Example: Communication plan for an executive steering committee

Cadence:

weekly: PM team internal
biweekly: project managers + technical leads
monthly: steering committee report

Content for steering committee:

progress against milestones,
cost and schedule variance (e.g., EV/PV/AC),
top risks and responses,
change requests submitted and outcomes,
decisions required by governance.

Exam-style answer: “Who needs what?”

Executives: decisions, risk exposure trends, budget forecast.
Technical leads: quality metrics, defect logs, technical constraints.
End users: training plan, adoption timeline, operational readiness.

When communication is wrong, stakeholder trust fails—even if work is technically progressing.

Performance Reporting: Dashboards and Narrative Logic

Performance reporting uses data plus narrative.

A high-mark approach includes:

quantitative indicators (schedule variance, cost variance),
qualitative assessment (“progress is delayed due to supplier constraints”),
corrective actions and future forecast.

Example narrative report logic

If EV < PV and AC > EV:

say you are behind schedule and over budget,
identify cause (e.g., supplier delay),
propose action (expedite, reallocate resources),
forecast new completion date and budget estimate.

Monitoring and Controlling: Preventing “Surprises”

Monitoring and controlling includes:

tracking progress,
measuring performance vs baselines,
managing change,
controlling quality,
addressing corrective actions.

A common exam scenario includes late discovery of risk. The high-scoring answer says:

monitoring should include triggers,
risk owners update risk register,
early warning indicators allow faster corrective action.

Quality During Execution: Managing Defects and Acceptance

During execution, “quality control” and “quality assurance” must work together.

Quality control: inspect deliverables and test outcomes.
Quality assurance: audit processes to ensure work is being done correctly.

Example: software project quality acceptance testing

If a user story must meet acceptance criteria:

the team runs unit tests,
integration tests verify interoperability,
UAT confirms business needs.

If defects are found:

log defects,
perform root cause analysis,
decide whether to fix immediately or schedule fix in next iteration based on severity and risk.

Stakeholder Engagement in Execution: Managing Resistance

Stakeholders may resist due to fear of change, resource impact, or unclear benefits. Execution management should include engagement actions:

training, coaching, communication,
clarifying benefits and responsibilities,
resolving issues promptly.

Example: resistance from operational staff

A factory adopts a new maintenance system. Operational staff may resist if:

training is delayed,
system steps are too complex,
workload increases temporarily.

Corrective actions:

conduct early training,
simplify workflows with user feedback,
add “super-users” for support during go-live.

Exams often reward answers that recognise resistance is operational risk, not a communication failure only.

Change Requests During Execution: Controlling “Scope Creep”

Scope creep is a frequent exam scenario. It occurs when incremental changes add up without formal approval.

A high-scoring scope creep answer includes:

how to define “change” vs “normal progress,”
how to evaluate and document impacts,
how to use CCB decisions to enforce boundaries.

Example: scope creep in event management

A client requests additional branding elements each week. Without control:

schedule slips,
costs rise,
quality becomes inconsistent.

Solution:

treat each request as change request,
evaluate impact on budget and completion dates,
approve only those aligned with project objectives and budget allowances.

Integrating Lessons Learned into Execution

Lessons learned should not wait for project closure. At MBA level, you should mention:

capturing lessons during milestones,
adjusting planning templates and processes,
training team members based on past mistakes.

Section 5: Project Leadership, Strategy Alignment, and Capstone-Style Exam Answers (Governance, Ethics, and Forecasting)

This final section consolidates leadership, strategy alignment, and capstone-level exam skills. Many Regent MBA assessments resemble scenario-based questions: candidates must recommend an approach, explain decision impacts, and link project outcomes to organisational strategy. This section also focuses on forecasting performance and managing closure responsibly.

Strategy Alignment: Why Projects Fail Even When “On Paper” Delivery Happens

A project can be delivered “on time” yet fail strategically if:

benefits are not realised,
stakeholders do not adopt deliverables,
scope delivers features but not outcomes.

At MBA level, you must articulate the logic model:

inputs (resources),
outputs (deliverables),
outcomes (benefits).

Example: digital system implemented but not adopted

A bank introduces an online loan application system. Technical delivery is completed. However:

customers cannot complete steps due to usability issues,
staff bypass the system and continue manual processing.

Therefore, outcome (faster processing and reduced cost) fails. Exam answers should recognise this as a project management deficiency in stakeholder engagement, quality acceptance, and operational readiness planning.

Benefits Management: From Delivery to Value

Benefits management involves:

defining benefits and metrics,
establishing baseline measurements,
ensuring post-project ownership,
monitoring benefit realisation.

Example benefits metrics (exam-ready)

reduction in loan processing time from X days to Y days,
reduction in cost per application,
increase in customer satisfaction scores.

If you define these metrics in planning, you can later demonstrate success beyond deliverable completion.

Forecasting: Updating Estimates and EAC Logic

Forecasting typically appears in exam questions asking:

“What is the expected completion cost and time given current variances?”

Using earned value forecasting (one common approach):

Estimate at Completion (EAC) = BAC / CPI (when performance continues similarly)
Estimate to Complete (ETC) = EAC − AC
Estimate at Completion schedule often uses SPI-based adjustments.

Consistent example using earlier EV numbers

From Section 3 example:

PV = R 600,000 at week 6
EV = R 450,000
AC = R 520,000
CPI ≈ 0.865
SPI = 0.75

Assume Budget at Completion (BAC) is R 1,200,000.
Then:

EAC = BAC / CPI = 1,200,000 / 0.865 ≈ R 1,387,283

ETC = EAC − AC ≈ 1,387,283 − 520,000 = R 867,283

This forecast supports decision-making:

whether to approve change requests,
whether to renegotiate scope,
whether to apply corrective actions to improve CPI/SPI.

Leadership in Complex Projects: Motivating Under Constraints

Leadership at MBA level is expected to address:

team dynamics,
conflict management,
decision-making under pressure.

Example: conflict between project team and procurement

Procurement wants to choose a cheaper vendor, while project delivery team argues for higher quality and faster lead times.

A high-scoring PM answer:

Clarify objectives (time, quality, cost, compliance).
Use risk analysis to compare options (EMV and qualitative impacts).
Present governance decision options.
Agree procurement selection criteria (scoring matrix, weighted evaluation).

This demonstrates that leadership is structured and evidence-based.

Ethics and Transparency in Status Reporting

Exam scenarios often include a temptation to “manage perceptions.” Ethical leadership insists on:

truthful reporting of schedule risk,
not hiding red flags,
documenting decision rationales.

If stakeholders later discover inaccuracies, governance confidence collapses, increasing escalation frequency and undermining change control.

Project Closure: Closing the Loop Properly

Closure is not administrative; it ensures acceptance, documentation, and learning.

Closure activities include:

finalising deliverables,
obtaining formal acceptance,
releasing resources,
updating final performance metrics,
archiving contracts and project records,
conducting lessons learned workshop.

Example: lessons learned that changes future governance

In one project, repeated delays occurred because supplier lead times were not verified early. Lessons learned result in:

revised procurement planning,
supplier due diligence requirements,
earlier trigger thresholds.

Future projects then avoid recurring risk.

Capstone-Style Exam Answer Template (Use in Scenario Questions)

When writing exam answers, a structured template increases marks. Use this pattern for scenario-based prompts:

Restate the problem (1–2 sentences)
Identify key constraints (scope/time/cost/quality/risk/stakeholders)
Analyse root causes (what likely caused the issue)
Propose options (at least 2, with trade-offs)
Recommend the best option using criteria
Explain governance actions (CCB/steering committee)
Define next steps (who does what by when)
Mention monitoring and controls (KPIs, triggers, reporting cadence)
Conclude with benefits/outcomes and risk reduction

Example capstone scenario (integrated response)

Scenario:
A project to implement a document management system in a healthcare organisation is behind schedule by 3 weeks. EV indicates slow progress and AC indicates cost overrun. A major risk has emerged: the main vendor’s delivery time has stretched due to supply constraints. Stakeholders are demanding an immediate solution and threatening contract termination unless progress is accelerated.

A strong answer would:

quantify schedule/cost variances (using EV/PV/AC logic),
identify risk triggers and update the risk register,
propose procurement mitigations (expedite, dual-source, contract clause enforcement),
submit change requests if schedule baselines must change,
recommend an integrated plan with governance approvals.

It would also communicate:

executive dashboard summary,
stakeholder-specific messaging (clinicians, IT, management),
a forecast update (EAC) based on CPI/SPI.

South African Study Relevance: How to Align Answers to Common University Expectations

South African students preparing for MBA and project management modules often follow similar assessment behaviours across institutions such as UNISA (distance learning, scenario-based assignments, concept application) and CUT (practical management framing and structured answers). Even when module codes differ, the marking rubric tends to reward:

clear definitions,
logically sequenced steps,
diagrams or frameworks (even described in text),
applied examples and justification,
professional tone and structured arguments,
governance and stakeholder focus.

In Regent MBA specialisation examinations, you should expect that theoretical accuracy must be paired with applied leadership and decision-making—particularly around governance, risk, change control, and benefits realisation.

Final Consolidation: High-Mark Themes to Practise

To prepare effectively, practise answers that consistently cover:

Baselines (scope/schedule/cost) and how changes affect them
Scheduling logic (critical path, float, compression trade-offs)
Cost control with performance metrics (EV/PV/AC, CPI/SPI)
Risk management with probability/impact logic and EMV when required
Procurement strategy and contract type trade-offs
Change control and enforcement against scope creep
Communication management (cadence, audience, decision content)
Governance (steering committee, stage-gates, escalation)
Ethics (truthful reporting, conflict management)
Closure and lessons learned (acceptance + knowledge transfer)

Quick Reference Summary (Exam Memory Aid)

Area	What Examiners Look For	High-Scoring Deliverable
Governance	Who decides and how escalation works	Stage-gate/CCB explanation linked to risk
Planning	Baselines + WBS logic	Clear scope decomposition + integrated schedule/cost
Scheduling	Dependencies + critical path	Critical path identification + mitigation actions
Cost Control	EV/PV/AC interpretation	CPI/SPI with actionable corrective steps
Risk	Identification + response + triggers	Risk register quality with owners and actions
Procurement	Contract strategy + risk transfer	Recommendation justified with uncertainty logic
Change Control	Approval workflow + impact assessment	CCB decision steps + baseline update logic
Communication	Cadence + audience fit	Steering committee dashboard narrative
Leadership & Ethics	Transparency and decision accountability	Ethical status reporting + structured conflict resolution
Closure	Acceptance + learning	Lessons learned actions that improve future projects

Closing Notes

Regent MBA Specialisation in Project Management demands a mature, decision-focused approach: not only knowing frameworks, but applying governance, baselines, risk logic, procurement strategy, and change control to drive outcomes and benefits. With scenario-based practice—using the integrated logic shown across these sections—you can produce exam answers that are structured, evidence-based, and aligned to how marks are typically awarded in South African project management modules.