MBA with Project Management Focus Area – Core Concepts Study Guide (USB & Stellenbosch Business School: MBA Project Management)

An MBA with a Project Management focus area demands more than knowing project terminology—it requires decision-making discipline, measurable outcomes, and the ability to manage stakeholders, risks, scope, schedule, and cost under real organisational constraints. This study guide consolidates core concepts that are commonly assessed in Project Management pathways aligned with Stellenbosch Business School (USB) and typical MBA/PM modules. It is written for exam readiness, with frameworks, models, and applied examples that mirror how South African universities—including USB—test understanding in assignments and examinations.

1) Project Management Foundations for the MBA (USB-aligned core)

Understanding “a project” vs “work,” “programme,” and “portfolio”

In MBA-level project management, the first concept you must be able to articulate is the distinction between different ways organisations organise change:

• Operations / business as usual: repetitive work that maintains current service levels (e.g., payroll processing).
• Project: a temporary endeavour with a defined start/end date and a specific outcome (e.g., implementing a new ERP system).
• Programme: a group of related projects managed together to achieve outcomes/benefits that individual projects cannot deliver alone (e.g., “Digital Transformation Programme”).
• Portfolio: a set of projects/programmes managed to align with strategic objectives and resource constraints (e.g., prioritising IT, HR transformation, and capex projects in one investment view).

For exam purposes, you should be able to respond to a classic question like: “Why does portfolio management matter if we already have project scheduling and risk registers?” The answer is strategic governance: projects often compete for shared resources (budget, people, vendor capacity), and portfolio decisions determine which work is funded and which is stopped or deferred.

The core “iron triangle” (scope–schedule–cost) and why MBA problems are rarely pure

Many introductory courses teach the triple constraint: scope, time, and cost. MBA project management extends this by including stakeholder satisfaction, quality, and benefits realisation.

A useful way to remember the relationship is:

• Increasing scope typically requires additional cost and/or longer time.
• Shortening time typically increases cost (e.g., overtime, fast-track contracting, added resources).
• Reducing cost often threatens scope and/or quality.

However, MBA questions frequently include a fourth factor: quality/performance (delivering the intended capability). For example:

• A construction project may meet schedule and cost but deliver below spec, triggering rework, claims, and reputational damage.
• An IT rollout may go live on time but with poor usability or data integrity, reducing adoption and thus benefits.

Project life cycle: from idea to closure (and lessons learned)

Project life cycles vary by industry, but exams commonly test whether you understand typical stages:

1. Initiation: define the problem/opportunity, identify stakeholders, draft business case.
2. Planning: create scope statement, schedule, cost baseline, risk plan, procurement plan.
3. Execution: perform work packages, manage quality, coordinate people and vendors.
4. Monitoring & controlling: compare actuals vs baselines, manage changes, track risks.
5. Closing: formal acceptance, final reporting, transfer to operations, lessons learned.

A high-mark answer explains that risks and uncertainty are highest early; therefore, early-stage decisions have disproportionate long-term impact. You should also emphasise that project closure is not merely “finishing tasks”—it includes acceptance, documentation, and benefit handover.

Stakeholder management as a core MBA competency

Where traditional project management focuses on delivering outputs, MBA-level project management focuses on outcomes and political realities. Stakeholder management includes:

• identifying stakeholders and their influence/interest
• understanding what they care about (e.g., compliance, cost control, job security, customer service)
• planning engagement and communication
• handling resistance and change impact

Common frameworks you should know:

• Power/Interest Grid: classify stakeholders into “manage closely,” “keep satisfied,” “keep informed,” etc.
• Salience Model (power, legitimacy, urgency): helps explain why some stakeholders dominate conversations.
• Engagement plan: tailored communications for different stakeholder groups.

Example (South African context, typical exam style):
A logistics company plans to implement route optimisation software. Stakeholders include operations managers, drivers, compliance officers, IT security, and customers. Even if the technical plan is perfect, failure to engage drivers may lead to low adoption and incomplete benefits (e.g., routes not used, exceptions handled manually).

Governance and organisational structures: who decides and who delivers?

In MBA examinations, “governance” is often the differentiator between passing and failing answers. It’s not only a legal concept—it’s a decision system.

Key governance elements:

• Project sponsor: usually accountable for business case and benefits.
• Project manager: responsible for delivery planning/execution within authority limits.
• Steering committee: oversight, approvals, escalations, and re-prioritisation decisions.
• PMO (Project Management Office): standards, templates, reporting, and sometimes resource coordination.

In South Africa, you may see governance referenced in procurement, compliance, and tender-driven environments. You should therefore be comfortable discussing how governance affects:

• change approvals (who can approve scope changes?)
• risk escalation (what triggers executive review?)
• procurement method selection (who approves contract type and spend?)

Case mini-scenario: ERP implementation—where projects fail despite good planning

Consider a hypothetical ERP project in a mid-sized manufacturing firm. The project plan includes training sessions, cutover activities, and data migration. Yet the project struggles. Typical root causes you should mention:

• Inaccurate scope: initial requirements omit key costing rules; late additions create rework.
• Weak stakeholder engagement: finance staff disagree on chart of accounts mapping but are brought in late.
• Poor change control: users create workarounds during testing; these become entrenched before go-live.
• Underestimated integration risks: interfaces with existing inventory systems require additional testing cycles.
• Benefits not owned: sponsor assumes cost reductions will happen automatically, but operations leaders don’t adopt new processes.

This scenario sets up later sections on scope, schedule, cost, risk, and benefits realisation. The key exam takeaway is that “project management” is not just planning—it’s controlling change, managing people, and protecting outcomes.

2) Scope, Schedule, Cost, and Quality—Planning for measurable control (USB-aligned)

Scope management: turning strategy into a controlled work definition

Scope management ensures that the project delivers the defined requirements and excludes non-required work.

Core artefacts include:

• Project charter / business case: why the project exists.
• Scope statement: high-level boundaries and deliverables.
• Work Breakdown Structure (WBS): a hierarchical decomposition of deliverables into manageable work packages.
• Requirements documentation: functional/non-functional requirements.
• Acceptance criteria: how deliverables are validated.

A common exam question: “How does a WBS improve control?”
You should answer: it makes work visible, enables estimating at the work-package level, supports scheduling and cost estimation, and allows change control to trace impacts.

WBS example: building a customer portal

A WBS might include major deliverables:

1. Project management and governance
2. UX/UI design
3. Front-end development
4. Back-end services
5. Security and compliance
6. Testing and user acceptance
7. Deployment and handover

Each deliverable is decomposed further until work packages can be estimated and assigned. For instance:

• Testing and user acceptance
  • create test scripts
  • execute functional tests
  • execute integration tests
  • manage UAT sign-off

Scope creep vs justified change

Scope creep is unwanted expansion without controlled approval. Exam markers expect you to describe how to prevent it using:

• a clear scope baseline
• a formal change control process
• impact assessment (schedule/cost/quality)
• stakeholder approvals for changes

Schedule management: critical thinking beyond “dates”

Schedule management includes building a schedule model, sequencing activities, and controlling progress. In MBA questions, the schedule is not just a Gantt chart—it’s a decision tool.

Main elements:

• Activity definition: identify specific actions needed.
• Sequencing: determine logical dependencies.
• Estimating durations: based on resources and complexity.
• Developing schedule: network diagram or critical path method.
• Schedule baseline: approved plan for performance measurement.
• Tracking progress: monitor actuals and forecasts.

Critical path concept (exam-friendly explanation)

If tasks have dependencies, some tasks form the critical path—meaning delays on those tasks are likely to delay project completion (assuming other paths have float/relief).

In an ERP example:

• Data migration depends on finalised mapping rules.
• Testing depends on successful migration.
• Training depends on completed system configuration.

If mapping rules slip, then migration slips, testing slips, and go-live date is threatened.

Cost management: baseline, estimation, and forecast discipline

Cost management is about budgeting and controlling expenditure relative to plans.

Key concepts:

• Cost estimate: predicted costs by category (labour, materials, equipment, vendors).
• Cost baseline: approved budget (often including contingency).
• Contingency vs management reserve:
  • contingency: planned for identified risks and uncertainty within scope
  • management reserve: for unknown-unknown events or broader project-level uncertainty
• Earned Value Management (EVM): integrates scope, time, and cost performance (discussed in more depth later).

Practical cost breakdown example

Suppose a 6-month project with three cost categories:

Cost Category	Budget (ZAR)	Notes
Internal labour	3,600,000	PM + engineers + QA
Vendor / contractors	2,400,000	Development and specialised testing
Infrastructure & licences	1,000,000	Cloud services + security tooling
Total budget	7,000,000	Baseline for performance

If the project is forecast to spend 7,700,000 by month 6, the forecast indicates a cost overrun relative to the baseline.

Quality management: prevent defects, manage expectations

Quality in project management includes conformance to requirements and fitness for use.

Quality-related elements:

• Quality plan: defines what quality standards apply and how they will be measured.
• Quality assurance (process quality): improving processes to prevent defects.
• Quality control (product quality): inspections, tests, acceptance sampling.
• Defect management: severity, root cause analysis, corrective actions.

MBA exams often ask: “Why is quality management not the same as testing?”
A strong answer says: testing finds defects; quality assurance prevents them through process improvements (e.g., coding standards, review gates, test automation strategy). Testing is only one method.

Integrated change control: scope/schedule/cost/quality are inseparable

MBA-level competence is integration. You must demonstrate how change impacts:

• deliverables and scope boundaries
• schedule activities and critical path
• cost estimates and contingency consumption
• quality standards (rework, defect rates)
• risks and stakeholder expectations

A typical change control process:

1. Request submitted (what changed and why?)
2. Log the change and assess impact
3. Estimate changes to schedule and cost
4. Evaluate quality implications
5. Identify risk implications
6. Obtain approvals
7. Update baselines and communicate

Mini case: “Fast-track” decision and hidden consequences

A bank’s project to deliver a regulatory reporting upgrade is threatened by an external deadline. The sponsor requests a fast-track schedule.

Possible implications:

• parallel task execution increases rework risk
• vendors may charge premium rates
• testing cycles may compress, increasing defects
• training and documentation may be delayed, reducing adoption
• stakeholder satisfaction may drop if users face system instability

An exam-worthy answer explains that fast-tracking is a strategic trade-off: sometimes it is correct, but it must be backed by:

• updated schedule and cost baselines
• revised risk register (including higher risk of integration defects)
• enhanced quality assurance measures
• realistic acceptance testing and deployment windows

3) Risk, Procurement, and Contract Management—Managing uncertainty and external dependencies

Risk management: structured thinking under uncertainty

Risk management is essential in MBA project management because projects involve uncertainty in scope, schedule, cost, technology, and stakeholders.

Core risk management cycle:

1. Plan risk management: define methodology, roles, timing.
2. Identify risks: what could happen?
3. Perform qualitative analysis: prioritise risks by probability and impact.
4. Perform quantitative analysis: estimate numerical risk impacts (where relevant).
5. Plan responses: avoid, mitigate, transfer, accept.
6. Implement responses
7. Monitor and control risks: track triggers and residual risks.

Risk register structure (what exam markers look for)

A risk register typically includes:

• risk ID and description
• categories (technical, schedule, cost, vendor, stakeholder, compliance)
• probability and impact rating
• risk score (if using scoring)
• risk owner
• response strategy
• triggers and early warning signs
• contingency plan
• status and review date

Qualitative vs quantitative risk analysis

• Qualitative analysis: uses scoring, ranks priorities, and helps focus attention.
• Quantitative analysis: uses numeric techniques like expected monetary value (EMV) or simulation (e.g., Monte Carlo).

MBA exams may not require advanced mathematics but do require you to understand when quantitative analysis is appropriate. For example:

• Quantitative analysis is useful for major budget impacts or high uncertainty.
• Qualitative analysis may suffice when data is scarce or decisions must be made quickly.

Risk response strategies: avoid, mitigate, transfer, accept

Make sure you can articulate differences.

• Avoid: change plan to eliminate threat (e.g., switch technology).
• Mitigate: reduce probability/impact (e.g., additional testing).
• Transfer: shift impact to a third party (e.g., insurance, fixed-price contracts).
• Accept: acknowledge and have contingency (e.g., reserve funds).

Example: cybersecurity risk for a customer portal

• Threat: data breach due to misconfiguration.
• Avoid: remove risky component—if feasible.
• Mitigate: implement secure configuration, penetration testing, monitoring.
• Transfer: vendor contract requiring compliance and liability coverage; cyber insurance.
• Accept: only if residual risk is within tolerance and mitigation is in place, with incident response plan.

Managing risk tolerance and escalation

Risk tolerance is how much risk the organisation can bear. MBA tasks often require you to justify why certain risks must be escalated to executives.

Common escalation triggers:

• risk score above threshold
• high probability of schedule slip beyond tolerance
• vendor performance degradation
• regulatory compliance risk with legal exposure

Procurement management: acquiring goods and services effectively

Procurement management is about obtaining external resources with appropriate governance. It includes:

• procurement planning (what to buy, when, how)
• solicitation planning (tender documents, RFP)
• vendor selection (evaluation criteria)
• contract administration (deliverables, SLAs, change clauses)
• contract closure

Contract types and their implications

A strong exam answer connects contract type to risk allocation:

• Fixed-price: vendor bears cost overrun risk; project benefits when scope is stable; higher risk if requirements change.
• Time-and-materials: project bears labour/material cost; vendor bears less risk; can be appropriate when scope is uncertain but requires tight monitoring.
• Cost-plus: cost reimbursed plus fee; risk largely sits with client unless strong controls exist.

In procurement-heavy environments, you should also reference:

• evaluation criteria (technical capability, price, delivery time, experience, compliance)
• must-have compliance requirements (e.g., tax clearance, B-BBEE documentation in South Africa contexts—be consistent and avoid inventing metrics).

Vendor performance and SLA management

Even after selection, procurement success depends on contract administration.

Key mechanisms:

• deliverable acceptance criteria
• progress reporting and meeting cadence
• service levels (uptime, response time)
• penalties and service credits
• escalation procedures
• change control alignment between contract and project baselines

Case mini-scenario: outsourced implementation with late delivery risk

A telecommunications firm outsources a software component to a vendor. The project’s schedule assumes 8 weeks for development and 2 weeks for integration testing.

Risk register entry:

• risk: vendor delivers late
• cause: underestimation of complexity due to undocumented API behaviour
• probability: medium-high
• impact: project go-live delay

Response plan:

• mitigation: require weekly demos, add acceptance milestones, conduct API discovery early
• transfer: include contract clause for liquidated damages (if feasible)
• acceptance: build contingency of 1 week in integration testing

In an MBA exam answer, you must emphasise that risk responses must be realistic and implementable. A “transfer” response that is legally weak or operationally difficult is not credible.

Procurement ethics and compliance: governance is part of project management

MBA-level procurement includes ethical procurement and compliance discipline.

A high-grade approach:

• ensure transparent selection criteria
• prevent conflict of interest
• document decisions
• manage approvals and spend within policy

Even when exam questions are scenario-based, the best answers incorporate governance—because procurement is frequently where projects face audit scrutiny.

4) Earned Value Management, Monitoring & Controlling, and Performance Reporting

Monitoring & controlling: measuring progress that matters

Monitoring and controlling compare actual performance against baselines to determine variance and forecast outcomes.

Core outputs:

• variance analysis (schedule variance, cost variance)
• change requests identification
• risk updates
• performance reports for stakeholders

In MBA assessments, “reporting” is a competency: you must present numbers with interpretations and decisions, not only describe activity status.

Baselines: what “good control” depends on

A baseline is an approved plan against which performance is measured:

• Scope baseline
• Cost baseline
• Schedule baseline

Without baselines, you can’t credibly measure variance. MBA exams often test this reasoning: if baselines are frequently changed without control, the project appears “stable” in charts but is actually losing control.

Earned Value Management (EVM): integrating scope, time, cost

EVM uses three core concepts:

• PV (Planned Value): planned cost for work scheduled by a certain date.
• EV (Earned Value): planned cost for the work actually completed by that date (based on budgeted cost of completed work).
• AC (Actual Cost): actual cost spent for the completed work.

From these, you compute:

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

EVM then supports forecasting:

• Estimate at Completion (EAC): forecast total project cost.
• Estimate to Complete (ETC): forecast cost remaining.
• Variance at Completion (VAC): forecast total variance.

Numerical example (exam-ready)

Assume by week 10:

• PV = 4,000,000 ZAR (planned expenditure for scheduled work)
• EV = 3,600,000 ZAR (value of completed work)
• AC = 4,200,000 ZAR (actual spent)

Compute:

• CV = EV – AC = 3,600,000 – 4,200,000 = -600,000 ZAR (cost overrun on earned work)
• SV = EV – PV = 3,600,000 – 4,000,000 = -400,000 ZAR (behind schedule)
• CPI = EV / AC = 3,600,000 / 4,200,000 = 0.857
• SPI = EV / PV = 3,600,000 / 4,000,000 = 0.9

Interpretation:

• CPI < 1: costs are higher than planned for work accomplished.
• SPI < 1: progress is slower than planned.

A high-scoring answer explains what decisions might follow: reduce scope, re-sequence activities, adjust resourcing, tighten change control, or renegotiate vendor terms depending on root causes.

Interpreting EVM correctly: avoid common pitfalls

Common mistakes you should avoid in exam answers:

• Using EV incorrectly: EV should reflect earned work, not “percentage complete” based on opinions.
• Ignoring reasons behind variance: EVM numbers must translate into drivers (e.g., poor estimation, procurement delays, rework).
• Not updating baselines with change control: baselines represent approved scope and schedule.

If the exam scenario includes a late requirement change that was approved, you should state that EV computations and baselines must reflect the updated approved scope (or you must clarify whether calculations are based on original or revised baselines).

Reporting and dashboards: making performance actionable

MBA reporting includes both financial and operational indicators:

• EVM metrics (CPI, SPI)
• schedule forecasts (finish date prediction)
• risk status (high/medium/low)
• quality metrics (defect rate, acceptance status)
• procurement status (vendor deliverables met/missed)

A robust reporting approach is “numbers + narrative + recommendation”:

1. what happened (variance)
2. why it happened (root cause)
3. what will happen if nothing changes (forecast)
4. what should be decided now (recommendation)

Change control in monitoring: closing the loop

Monitoring & controlling drives change control. A well-structured control loop:

1. detect variance (e.g., schedule slippage)
2. diagnose cause (e.g., design not approved; vendor delay)
3. propose corrective actions (e.g., add resources, restructure tasks)
4. if scope/schedule/cost baselines are impacted, submit change requests
5. update baselines after approvals
6. communicate to stakeholders

Mini case: performance degradation due to quality rework

A healthcare project is delivered under budget initially. EVM shows CPI around 1.05 but SPI starts to drop after month 2. The root cause is rework: tests find defects in a critical integration component. The defect rate doubles compared to earlier sprints.

An MBA-level response:

• quantify impact: rework consumes schedule and increases AC
• link quality to schedule: rework delays acceptance and downstream activities
• recommend corrective actions:
  • strengthen quality assurance (review gates, test coverage)
  • update risk register (integration defect risk)
  • adjust procurement/contract terms if vendor deliverables cause defects

This case connects quality management (Section 2) to control and forecasting (this section).

5) Benefits Realisation, Agile/Hybrid Approaches, and Strategic Leadership in PM (USB & MBA focus)

From outputs to outcomes: benefits realisation management (BRM)

Many MBA project management questions focus on whether the project achieved business value—not merely whether it was delivered on time. Benefits realisation is the practice of ensuring outcomes are tracked and achieved.

Benefits types:

• Tangible financial benefits: cost reduction, revenue increase.
• Operational benefits: cycle time reduction, defect reduction.
• Compliance benefits: reduced regulatory risk.
• Customer benefits: improved satisfaction, reduced churn.
• People/process benefits: adoption of new workflows.

Benefits realisation typically includes:

• defining benefit statements and owners
• establishing baseline performance metrics
• setting benefit measurement plans
• tracking benefits post go-live (not just during delivery)

Example: measuring benefits for a process automation project

Suppose an insurance company implements automation to reduce manual document processing. Benefits might include:

• baseline: 10,000 documents processed per month with average 6 days turnaround
• after go-live target: 12,000 documents per month and 4 days turnaround
• measurement cadence: monthly until targets are stable for 3 months

In a real exam scenario, you should be able to argue:

• why benefits may lag go-live (training ramp-up, process stabilisation)
• why adoption matters (users must follow new workflow)
• why internal resistance can reduce benefits

Agile and hybrid approaches in MBA project management

Many MBA students associate project management only with predictive/plan-driven methods. However, modern environments require flexibility.

Predictive (waterfall-like) vs adaptive (agile-like)

• Predictive: detailed planning early, changes controlled; good when requirements are stable.
• Adaptive: iterative delivery, frequent feedback; good when requirements evolve.

Hybrid approaches combine structured governance with iterative delivery—commonly used in enterprise projects.

Agile terms you should know conceptually (without needing code-level depth):

• backlog and prioritisation
• sprints/iterations
• incremental delivery
• retrospectives (continuous improvement)
• stakeholder feedback loops

Agile governance: how to align iteration with executive oversight

MBA-level leadership requires explaining how agile can still be controlled.

• Use a release plan or roadmap rather than one fixed delivery date.
• Maintain a change governance layer: prioritize changes into backlog with business case justification.
• Keep quality gates and acceptance criteria.
• Track progress using appropriate metrics (velocity, burn-down/burn-up, cycle time) while maintaining financial governance.

Risk management in agile projects

Agile reduces certain risks through early delivery and feedback, but introduces other risks:

• scope volatility can increase if product ownership is weak
• technical debt can accumulate
• stakeholder misalignment can cause rework across iterations

Therefore, risk management remains essential:

• define risk categories for agile (stakeholder alignment, delivery dependencies, integration risk)
• monitor early indicators (failed sprint goals, increasing defects, missed demos)

Stakeholder leadership: managing power, legitimacy, urgency

Returning to stakeholder management, MBA projects require leadership through conflict and uncertainty.

Tools for leadership:

• stakeholder mapping and engagement planning
• escalation pathways
• negotiation and expectation management
• sponsor alignment and decision-making clarity

A high-mark exam answer often includes:

• how the project manager engages the sponsor/senior leadership
• how the PM communicates trade-offs (schedule vs cost vs quality)
• how decisions are recorded and enforced

A full case synthesis: digital transformation programme with multiple projects

Consider an organisation launching a Digital Transformation Programme consisting of three projects:

1. Project A: customer portal (software development)
2. Project B: CRM integration (systems integration)
3. Project C: process redesign and training (change and adoption)

Programme-level benefits:

• reduced call centre workload
• faster customer onboarding
• improved customer retention

A typical exam question might ask: “How do project management concepts differ between the programme and the individual project?”

A strong answer differentiates:

• Project A focuses on deliverables and technical quality for the portal.
• Project B focuses on integration stability, data governance, and interface testing.
• Project C focuses on adoption, training effectiveness, and process compliance.
• Programme governance ensures shared dependencies (e.g., data standards) and benefit tracking across all projects.

Managing portfolio constraints: prioritisation and resource allocation

At portfolio level, not all projects can get full resources simultaneously. A portfolio review may lead to:

• deferral of one project
• reduction in scope for another
• increased resources for critical projects
• stop/go decisions based on strategic alignment

MBA exam answers should emphasise:

• how portfolio decisions influence project risk
• how resource scarcity causes schedule/cost variance
• why benefits alignment reduces “zombie projects”

Counter-arguments and trade-offs: what not to assume

To score highly, include nuanced counter-arguments.

Counter-argument 1: “EVM is enough to manage projects.”

Response: EVM is a performance measurement technique, not a complete project management system. It can be undermined by poor baseline integrity, inaccurate EV methods, or uncorrected root causes. You still need stakeholder management, quality, and risk response execution.

Counter-argument 2: “Agile means no planning.”

Response: Agile doesn’t remove planning; it changes planning granularity. Roadmaps, release planning, and continuous risk assessment remain crucial. MBA-level governance still requires cost and benefit oversight.

Counter-argument 3: “Fast-tracking always works.”

Response: Fast-tracking often increases integration and defect risks. It can be valid when deadlines are external and risks are mitigated, but it must be supported by realistic testing, quality gates, and updated financial forecasts.

Exam-style checklist: what to include in a top answer

When a scenario is presented in an MBA PM exam, top answers usually include:

• problem framing: what business need is being met?
• scope definition: what deliverables are included/excluded?
• plan structure: how work is organised (WBS), sequenced (dependencies), and estimated (cost categories)?
• risk response: key risks, response strategy, triggers.
• procurement/vendor management: selection criteria, contract implications, SLAs.
• control and reporting: baseline vs actual, variance interpretation (including EVM if provided).
• change control: how approvals and baselines are managed.
• benefits realisation: measurement plan, owners, post-go-live tracking.
• leadership and stakeholder engagement: who influences decisions, how resistance is handled.

Aligning with common South African MBA/PM assessment themes

South African university assessments in MBA and project management often emphasise:

• structured reasoning and justification
• applied calculations (especially around budgeting, scheduling logic, and sometimes EVM-style performance)
• governance and stakeholder narratives
• realistic operational constraints (vendor capacity, compliance, adoption, training)

At Stellenbosch Business School (USB)—within a project management focused MBA—students are typically evaluated on their ability to integrate management concepts with practical project delivery thinking. This study guide therefore focuses on the “core concepts” that repeatedly appear across exam questions: governance, integrated planning, risk and procurement, performance measurement, and benefits realisation.

Quick practice scenario (with expected elements)

Use the following as an exam simulation for synthesis:

Scenario: A retail group plans an e-commerce platform upgrade before the November sales period. Delivery is threatened by a vendor integration risk and internal staff resistance to new order-processing workflows. The sponsor demands “minimum disruption” to existing operations.

What a high-mark answer must cover:

1. Define scope boundaries (what is in/out for upgrade vs separate enhancements).
2. Build a schedule that accounts for integration dependencies and sales-period cutover constraints.
3. Estimate cost categories and include a contingency for identified risks.
4. Identify top risks:
   • vendor API/integration behaviour
   • operational disruption during cutover
   • low adoption due to resistance
5. Plan responses:
   • early integration testing, milestone-based vendor reporting
   • staged cutover / pilot in a limited region
   • training plan and change communications, appoint process owners
6. Set quality acceptance criteria (performance, security checks, transaction success rate).
7. Use monitoring & controlling:
   • variance analysis and updated forecast
   • change control if scope/cost/schedule baselines are impacted
8. Plan benefits realisation:
   • adoption metrics and customer experience metrics post-launch

This scenario integrates the full guide into a single decision-focused narrative—exactly how MBA project management answers are evaluated.

Final consolidation: the “core concepts map” for rapid revision

Use this condensed mapping for last-minute recall:

• Foundations: project vs operations; sponsor/PM/steering; stakeholder power/interest.
• Planning control: scope via WBS; schedule via dependencies/critical path; cost via baselines/contingency; quality via assurance + control.
• Uncertainty management: risk identification → analysis → response → triggers → monitoring.
• External delivery: procurement planning; contract type risk allocation; SLA and vendor performance governance.
• Performance measurement: monitoring vs baselines; EVM metrics (PV/EV/AC); interpret CPI/SPI and forecast EAC.
• Strategic value: benefits realisation (baseline, owners, post go-live measurement); agile/hybrid governance; leadership for adoption.

References for further study (non-exhaustive, conceptual)

This guide is aligned with internationally used project management concepts commonly taught in MBA and advanced project management contexts, including the integration of scope/schedule/cost/quality, governance, risk management, procurement, performance measurement, and benefits realisation.

• Project Management Institute (PMI): foundational terminology and performance measurement concepts (e.g., EVM fundamentals).
• General agile and governance literature for hybrid delivery models.
• University-level MBA and project management materials used in South African business schools and executive programmes, including USB project leadership and delivery frameworks.