Advanced Diploma in Business Studies (Project Management) NMU Notes: Project Management Theory, Tools, and Practice for Passing

The Advanced Diploma in Business Studies (Project Management) at Nelson Mandela University (NMU) is assessed through a mix of project planning competence, practical application of project management tools, and the ability to justify decisions using recognized frameworks. These exam notes consolidate essential concepts—scope, scheduling, cost, risk, quality, procurement, stakeholder management, and project governance—into an integrated “what you must do” guide. The notes are written in a South African university exam style, with structured steps, worked examples, and common assessment patterns aligned to business studies project management modules.

This guide is part of the Nelson Mandela University (NMU) Project Management Study Resources collection and focuses specifically on the types of topics and outputs that typically appear in NMU project management assessments.

NMU Advanced Diploma in Business Studies (Project Management): Core Project Management Frameworks and Exam-Ready Planning

Advanced Diploma project management assessments commonly test whether you can:

1. define project purpose and measurable outcomes,
2. build a credible plan (scope + schedule + budget),
3. manage risk and stakeholder expectations, and
4. apply monitoring and control to ensure delivery.

Unlike “intro” project management, the Advanced Diploma expects manager-level reasoning: you should be able to justify tool choice (e.g., why a risk register rather than a list), demonstrate trade-offs (time vs cost), and connect project governance to performance reporting.

1) Project vs Program vs Operations (and why examiners care)

A recurring exam question asks you to distinguish between project, program, and operations, then use the distinctions to support a decision.

• Project: a temporary endeavor with a defined start and end, producing a unique outcome.
• Program: a group of related projects managed in a coordinated way to achieve strategic benefits.
• Operations: ongoing, repetitive processes that deliver steady outputs (e.g., monthly payroll, ongoing maintenance).

Exam tactic: When asked “Is this a project or operations?”, answer with:

1. Uniqueness: Is the output new or one-off?
2. Time boundary: Is there a clear deadline or end state?
3. Discontinuity: Does work stop or shift after delivery?
4. Resource change: Are resources assembled specifically for this initiative?

Example scenario: A municipality launches a “five-month ward-based water quality awareness campaign” using a temporary team and ends after campaign delivery. This is a project, not operations, because outputs (campaign materials, events) are unique and the effort is bounded in time.

2) Project Life Cycle: Initiation → Planning → Execution → Monitoring & Control → Closing

NMU-style assessments frequently require that you map activities to life-cycle phases.

A typical structure:

1. Initiation

   • Identify problem/opportunity
   • Draft project charter
   • Assign initial stakeholders
   • High-level feasibility

2. Planning

   • Scope definition and WBS
   • Schedule (activities, estimates, sequencing)
   • Budget and resource planning
   • Risk plan (risk identification + analysis approach)
   • Quality plan
   • Communication plan
   • Procurement plan (if external goods/services are needed)

3. Execution

   • Resource mobilization
   • Implement planned work
   • Manage deliverables and team performance

4. Monitoring & Control

   • Track actuals vs baselines
   • Manage changes (scope/time/cost)
   • Monitor risk responses
   • Earned value (if your module includes it)

5. Closing

   • Deliver final outputs
   • Lessons learned
   • Formal acceptance
   • Post-project evaluation and documentation

Why it matters: In exams, a common mark-loss pattern is answering “what” instead of “when” and “how”. A strong answer labels work items to phases and explains controls.

3) Project Governance and Management Information

Advanced Diploma assessments often include governance: who approves what, how decisions are recorded, and how performance is reported.

Governance elements:

• Project sponsor: funds and authorizes direction.
• Project manager: accountable for plan and delivery.
• Steering committee / project board: strategic oversight and major decisions.
• Project steering cadence: e.g., monthly meetings or milestone reviews.
• Change control board (CCB): approves changes impacting baselines.

Exam-ready governance statement:
“Governance ensures that deviations from baselines are detected early, reviewed with relevant stakeholders, and either corrected or formally approved through change control.”

4) The Project Charter (what should be inside)

A project charter is usually tested because it provides the formal mandate.

Your charter typically includes:

• Purpose / business need
• Objectives (SMART where possible)
• High-level scope
• High-level schedule
• High-level budget range
• Assumptions and constraints
• High-level risks
• Stakeholders
• Authority level and approval process
• Success criteria and acceptance approach

Mini-example (structure):

• Purpose: reduce student enrollment drop-offs by improving registration support.
• Objectives: launch an online help desk within 8 weeks; achieve ≥90% customer satisfaction in surveys by end of term.
• Scope: process mapping, system configuration, training, and communication materials; exclude replacement of the core student information system.
• Success criteria: acceptance by Registrar’s office; usage metrics exceed target.

5) Decomposition and WBS: the backbone of planning marks

Exams love the Work Breakdown Structure (WBS) because it shows whether you can decompose deliverables into manageable work packages.

A simple WBS rule:

• Build from deliverables down to work packages
• Work packages should be small enough to estimate cost and duration
• Each work package should have a clear owner and acceptance criteria

Common marking scheme logic:

• Correct hierarchy (Level 1 deliverables → Level 2 sub-deliverables → Level 3 work packages)
• Consistency with scope
• Completeness (everything in scope is included)
• Clarity and specificity

Example WBS for a training program project:

• 1. Project management deliverables
  • 1.1 Charter and planning
  • 1.2 Reporting and steering meetings
• 2. Training content
  • 2.1 Needs analysis report
  • 2.2 Slide deck development
  • 2.3 Assessment materials
• 3. Training delivery
  • 3.1 Participant recruitment and invitations
  • 3.2 Training sessions (Module 1–3)
  • 3.3 Feedback and evaluation

Advanced Diploma expectation: link WBS to the schedule and budget (even if simplified in exams).

6) Stakeholders: mapping influence and expectations

A frequent assessment component is stakeholder analysis.

Core tools you may be asked to apply:

• Power/interest grid
• Stakeholder register
• Engagement strategy (inform, consult, manage closely, monitor)

Exam-friendly stakeholder register fields:

• Name/role
• Interest in the project
• Influence/power level
• Expected requirements
• Communication needs
• Engagement actions
• Current sentiment (supportive/neutral/resistant)

Example stakeholder set:

• Project sponsor (high power, high interest)
• Department head (high power, medium interest)
• Users/participants (low power, high interest)
• Vendor (medium power, medium interest)

Why it matters: In exams, stakeholder management isn’t “communication only.” It includes managing conflict, ensuring requirements are captured, and anticipating how decisions affect different parties.

Project Scope, Scheduling, Costing, and Monitoring: How to Build a Defensible Plan (with Worked Examples)

This section trains you to answer “calculate, justify, and control.” Many NMU assessments require numerical reasoning, even if not full quantitative modelling. You must show assumptions, steps, and correct interpretation of results.

1) Scope Management: requirements, deliverables, and change control

a) Define scope and boundaries

You must differentiate:

• Product scope (features/functions of the output)
• Project scope (work needed to deliver the product)

Exam answer formula:

• Start with deliverables
• State inclusions and exclusions
• Mention constraints/assumptions
• Identify acceptance criteria

b) Requirements and acceptance criteria

Requirements are what stakeholders need. Acceptance criteria define what “done” means.

Example: online student support help desk

• Requirement: “students must be able to log tickets”
• Acceptance criterion: ticket submission works in a live pilot with ≥95% successful submissions and response acknowledgement within 24 hours.

c) Scope verification vs scope validation (often confused)

• Scope verification: confirm deliverables meet requirements (quality-focused).
• Scope validation: confirm deliverables achieve intended outcome (customer/business focused).

Counterpoint (common confusion):
“Validation” is not just “testing.” Validation asks whether the solution is fit for use and delivers intended benefits.

2) Time Management: sequencing, estimation, and critical thinking beyond “dates”

You may be tested on scheduling methods like:

• Precedence diagrams
• Critical Path Method (CPM)
• Gantt charts
• Buffer planning (if covered)
• Float/Slack interpretation

a) Activity sequencing and precedence logic

Activities depend on each other. Examples of dependency types:

• Finish-to-start (FS): predecessor must finish before successor starts.
• Start-to-start (SS): successor starts when predecessor starts.
• Finish-to-finish (FF): predecessor must finish when successor finishes.

b) Worked scheduling example (CPM-style)

Suppose a project has the following activities and durations:

Activity	Predecessor(s)	Duration (days)
A: Initiate	—	2
B: Draft plan	A	4
C: Stakeholder workshop	A	3
D: Finalize scope	B, C	2
E: Prepare budget	B	3
F: Approvals	D, E	1

Step 1: Earliest Start (ES) and Earliest Finish (EF)

• A: ES 0, EF 2
• B: ES 2, EF 6
• C: ES 2, EF 5
• D: ES max(B EF, C EF)= max(6,5)=6, EF 8
• E: ES 6, EF 9
• F: ES max(D EF, E EF)= max(8,9)=9, EF 10

Project duration = 10 days.

Step 2: Identify critical path
The critical path is the sequence that determines the project duration:

• A (2) → B (4) → E (3) → F (1) = 2+4+3+1 = 10 days
  But verify whether D also contributes: A→B→D→F gives 2+4+2+1=9 days, so it’s not critical because E finishes later.

Answer interpretation:
“The critical path is A–B–E–F, therefore any delay in B, E, or the dependency into F will affect total duration.”

c) Slack (float) and exam interpretation

Even if slack isn’t asked explicitly, examiners reward understanding. For non-critical activities like C→D path, delay may be absorbed depending on how it affects successors.

3) Cost Management: budgeting, costing structure, and cost breakdown

Cost management in exams often appears as:

• Build a simple budget from activity costs
• Distinguish direct vs indirect costs
• Identify cost drivers and estimation approaches (analogous, parametric, bottom-up)

a) Direct and indirect costs

• Direct costs: resources tied directly to specific work (e.g., contractor hours for deliverable production).
• Indirect costs: overhead (e.g., admin staff not assigned only to one task).

Example statement:
“In the budget, direct costs are derived from work packages in the WBS, while indirect costs represent organizational overhead allocated to the project.”

b) Worked costing example (aligning WBS and schedule)

Assume activities from the schedule example above have these estimated costs:

Activity	Duration (days)	Cost per day (ZAR)	Estimated Cost (ZAR)
A	2	1,500	3,000
B	4	2,000	8,000
C	3	1,200	3,600
D	2	2,500	5,000
E	3	2,200	6,600
F	1	3,000	3,000

Total Direct Cost = 3,000 + 8,000 + 3,600 + 5,000 + 6,600 + 3,000 = 29,200 ZAR.

Add contingency (10% for known unknowns):

• Contingency = 29,200 × 10% = 2,920 ZAR
• Total Budget at Completion (BAC) estimate = 29,200 + 2,920 = 32,120 ZAR

Exam note: Be explicit about what contingency covers. If risk responses are planned separately, contingency is for residual uncertainties after risk actions.

4) Monitoring and Control: baselines, variance, and corrective action

Advanced Diploma level exams tend to include control concepts, even if in simplified form.

a) Baseline types

• Scope baseline: WBS + scope statement
• Schedule baseline: time plan
• Cost baseline: budget breakdown and total BAC

b) Variance analysis (interpretation-focused)

Example: if by week 4 you planned to complete 50% of work but achieved 40% progress, you may have:

• schedule variance (delayed)
• cost variance (overspent or under-spent depending on what was actually done)

c) Earned Value Management (EVM) essentials (if included in your module)

If EVM is part of your assessment content, you’ll typically compute:

• PV (Planned Value): budgeted cost of work scheduled
• EV (Earned Value): budgeted cost of work performed
• AC (Actual Cost): actual cost incurred
• CV (Cost Variance) = EV − AC
• SV (Schedule Variance) = EV − PV
• CPI (Cost Performance Index) = EV / AC
• SPI (Schedule Performance Index) = EV / PV

Worked EVM example
Assume a project with BAC 32,120 ZAR and an assessment at the end of week 4:

• Planned progress = 50% → PV = 0.50 × 32,120 = 16,060 ZAR
• Earned progress = 40% → EV = 0.40 × 32,120 = 12,848 ZAR
• Actual cost incurred = 14,500 ZAR → AC = 14,500

Compute:

• CV = EV − AC = 12,848 − 14,500 = −1,652 ZAR (over budget)
• SV = EV − PV = 12,848 − 16,060 = −3,212 ZAR (behind schedule)
• CPI = EV / AC = 12,848 / 14,500 ≈ 0.89
• SPI = EV / PV = 12,848 / 16,060 ≈ 0.80

Interpretation for an exam:

• CPI < 1 means cost efficiency is poor (spending more than earned).
• SPI < 1 means schedule efficiency is poor (less work completed than planned).
• Corrective action: re-baseline carefully, adjust resourcing, and escalate risks affecting pace (e.g., procurement delays, stakeholder approval delays).

d) Change control and corrective vs preventive action

When variances occur:

• Corrective action: fix current performance issue (e.g., add resources)
• Preventive action: prevent recurrence (e.g., improve estimation, tighten approvals lead time)

In exams, strong answers show that not all variance needs immediate “stop work”—you decide after analysis.

5) Quality Management: ensuring “fit for purpose” delivery

Quality in project management isn’t just inspection. It includes:

• quality planning
• quality assurance
• quality control
• quality standards/criteria

a) Quality assurance vs quality control

• Quality assurance: processes to prevent defects (system-level).
• Quality control: inspecting/testing outcomes to confirm standards (product-level).

b) Quality tools (typical exam items)

• Checklists
• Inspection and testing
• Statistical sampling (if covered)
• Root cause analysis (e.g., 5 Whys, fishbone diagrams)

Exam-ready quality statement:
“Quality control confirms deliverables meet acceptance criteria, while quality assurance improves process capability to reduce recurring errors.”

Risk, Procurement, Communication, and Stakeholder Engagement: Managing Uncertainty Like a Project Manager

At Advanced Diploma level, marks often go to students who can explain uncertainty handling. Risks, procurement, and communication are interlinked: risks affect supplier performance, stakeholders affect approval speed, and communication errors create scope creep.

1) Risk Management: identification to response control

a) Risk fundamentals: threats and opportunities

A risk is an uncertain event that, if it occurs, affects objectives.

• Threat: negative impact (e.g., vendor delay).
• Opportunity: positive impact (e.g., additional funding).

A common exam risk register includes:

• Risk ID
• Description
• Category (schedule, cost, scope, quality, stakeholder, external)
• Probability (P)
• Impact (I)
• Risk rating (P×I or scoring model)
• Response strategy (avoid/mitigate/transfer/accept for threats; exploit/share/enhance for opportunities)
• Owner
• Contingency plan
• Triggers (what indicates the risk is becoming active)
• Status and residual risk

b) Probability-impact scoring example

Use a 1–5 scale for probability and impact, where:

• Rating = P × I
• 1–5 low
• 6–10 medium
• 11–25 high

Example risk register snippet

• Risk R1: Vendor procurement delay

  • P=4, I=4 → rating 16 (High)
  • Response: Mitigate (prequalify suppliers, dual sourcing options), Transfer (where contract allows penalty clauses), Contingency (buffer time 2 weeks)

• Risk R2: Stakeholder approval delays

  • P=3, I=3 → rating 9 (Medium)
  • Response: Mitigate (agree approval SLA with steering committee), Escalation path

c) Worked consequence planning (time buffer logic)

If vendor delivery is on the critical path, even small delays affect duration.

Suppose:

• Critical path affects total duration of 10 days (from earlier schedule example)
• Contingency buffer allocated: 2 days
• If vendor delay occurs of 1 day, project may still finish on original timeline if buffer absorbs it.
• If delay becomes 3 days, buffer isn’t enough; you must perform corrective action:
  1. compress non-critical tasks
  2. re-sequence work
  3. add resources
  4. negotiate scope trade-offs

2) Risk responses: choosing the right strategy

a) Threat strategies

• Avoid: eliminate cause (change requirement or method).
• Mitigate: reduce probability/impact (improve planning, controls).
• Transfer: shift impact to a third party (insurance, vendor contract terms).
• Accept: do nothing proactive beyond contingency and monitoring.

b) Opportunity strategies

• Exploit: ensure opportunity happens (secure early commitments).
• Enhance: improve probability/impact (extra marketing or partner support).
• Share: partner to benefit.
• Accept: allow it and respond if it occurs.

Exam “best answer” pattern:
Always connect response choice to the risk type and criticality (critical path, budget baseline, acceptance criteria).

3) Procurement Management: buying goods/services to support delivery

Procurement issues appear frequently in project management assessments because they link to schedule delays and cost escalations.

a) Procurement types and contract considerations

Depending on complexity:

• simple purchase orders
• framework agreements
• competitive bidding (tendering)
• service-level agreements (SLAs)

Common contract levers in exams:

• delivery timelines
• acceptance criteria
• performance penalties/bonuses
• payment milestones
• escalation clauses
• change order rules

b) Procurement plan components

• procurement need and justification
• procurement method (competitive/negotiated)
• timeline
• supplier evaluation criteria
• contract structure
• risk allocation (what belongs with vendor vs project)

c) Worked procurement risk example tied to a budget

Assume you allocate:

• Estimated cost of vendor deliverable (Activity E, “Prepare budget” in the earlier plan context is internal; let’s use vendor external deliverable as an example):
  • Suppose an external vendor contract is 6,600 ZAR equivalent cost
• If procurement delay causes rework due to missed timeline, you might incur:
  • additional quality inspection cost 1,200 ZAR
  • additional administrative cost 600 ZAR

Total additional cost if rework occurs = 1,800 ZAR.

Now, if contingency is 2,920 ZAR, the rework is within contingency but reduces remaining risk coverage. This is the kind of reasoning examiners reward: procurement risk impacts cost baseline and must be managed via contingency and change control.

4) Communication Management: communication plans that prevent scope creep

Communication failure is a leading cause of project problems in real assessments. Examiners often ask:

• who communicates with whom,
• what information is sent,
• how often,
• through which channel,
• and how issues escalate.

a) Communication plan fields

• stakeholder group
• communication objective
• message content (what)
• channel (email, meetings, dashboards)
• frequency
• owner (who prepares)
• audience (who receives)
• response/feedback mechanism

b) Example communication plan (simple)

• Steering committee meeting: monthly
• Project status report: weekly (to internal management)
• Stakeholder workshops: at milestones (e.g., before final scope approval)
• Risk review: bi-weekly for high-risk projects
• Procurement updates: fortnightly during supplier onboarding

c) Stakeholder communication and “approval bottlenecks”

If stakeholders delay decisions, schedule suffers. You should:

• implement SLAs for approvals where possible
• track decision logs
• escalate delays with evidence: impact on baselines and outcomes

Exam line to use:
“Communication is not merely reporting progress; it is a control mechanism that ensures timely decisions and alignment with acceptance criteria.”

5) Stakeholder Engagement: managing conflict and building buy-in

Stakeholder engagement strategies often fall into:

• informing (one-way communication)
• consulting (two-way feedback)
• involving (shared decision-making)
• collaborating (co-create solutions)
• empowering (stakeholders influence outcome)

Conflict example:
A department head demands scope expansion (additional training modules), but the project charter scope excludes that. A strong answer:

1. references scope baseline and charter
2. explains impact on schedule/budget
3. proposes options:
   • formal change request with CCB approval
   • implement additional modules as Phase 2 after baseline delivery
   • negotiate trade-offs (reduce another activity)
4. communicates the decision and update baselines if approved

This demonstrates both stakeholder management and change control competence.

Integrated Project Case Study for NMU Advanced Diploma: Building a Full Plan, Risk Register, Budget, and Control Strategy

The most exam-effective way to prepare is to practice building an integrated plan end-to-end. NMU Advanced Diploma assessments frequently require you to apply multiple concepts in one scenario. Below is a full case study with worked components that you can adapt in your answers.

Case Study: “Student Registration Support Enhancement Project” at a South African Higher Education Institution

A university experiences delays and confusion during student registration periods. The Registrar’s office reports increased queries at the help desks and a rise in incomplete registrations. The institution wants a temporary project that improves the student registration experience by implementing a structured help desk process, producing user guides, and training staff.

Project charter summary (for the case)

• Project objective: Improve registration support and reduce incomplete registration incidents through a structured help desk and training.
• Duration: 10 weeks (you may simplify to months in exams, but we keep weeks for detail).
• High-level deliverables:
  1. Help desk ticketing process and workflow
  2. User guides (online and print)
  3. Staff training (frontline staff)
  4. Monitoring and evaluation report with acceptance and lessons learned

Stakeholders (consistent across the case)

• Project sponsor: Registrar’s office (high power, high interest)
• Project manager: you (responsible for delivery)
• Steering committee: Faculty administration and student services leadership
• Help desk staff: frontline team (medium power, high interest)
• IT support team: technical enablement (medium power, medium interest)
• Students (end users): low power, high interest
• Vendor (if used): training materials supplier (optional)

1) Scope definition and WBS for the case

a) Scope inclusions and exclusions

In scope:

• process mapping of help desk workflow
• ticket categories and escalation rules
• design and production of user guides
• scheduling and delivering staff training
• collecting feedback and producing evaluation report

Out of scope (explicit exclusions):

• replacing the core student information system
• redesigning the entire admissions policy framework

Acceptance criteria examples:

• Help desk workflow approved by Registrar’s office.
• User guides published at least 2 weeks before registration peak.
• Staff training completed with ≥90% attendance and positive feedback ≥4/5 average rating.
• Evaluation report accepted by steering committee.

b) WBS (deliverable-based)

You can present it in hierarchical form:

1. Project management deliverables

   • 1.1 Project charter and planning
   • 1.2 Weekly progress reporting
   • 1.3 Steering committee documentation

2. Help desk workflow and ticketing

   • 2.1 Requirements workshop (Registrar + help desk staff)
   • 2.2 Ticket categories and SLAs
   • 2.3 Escalation workflow
   • 2.4 Pilot testing

3. User guides production

   • 3.1 Content development (scripts, FAQs)
   • 3.2 Design and layout
   • 3.3 Print production and upload

4. Staff training

   • 4.1 Training needs analysis
   • 4.2 Training material finalization
   • 4.3 Training delivery sessions
   • 4.4 Post-training evaluation

5. Monitoring, evaluation, and closing

   • 5.1 Data capture plan
   • 5.2 Performance analysis report
   • 5.3 Lessons learned and closure

2) Schedule building (exam-friendly precedence logic)

You can avoid overly complex modelling by showing sequencing and critical thinking.

A simplified precedence structure (assume 10 weeks):

1. Charter and planning (Weeks 1–2)
2. Workflow requirements workshop (Week 2)
3. Ticket categories and SLAs (Weeks 3–4)
4. Pilot testing (Week 5)
5. User guide content development (Weeks 3–5)
6. Design and print/upload (Weeks 5–7)
7. Training needs analysis and material finalization (Weeks 6–8)
8. Training sessions (Weeks 8–9)
9. Evaluation report (Week 10)
10. Closing and acceptance (end of Week 10)

Critical path logic:
If pilot testing reveals workflow problems late, it delays training and/or guide finalization. In exams, show you understand this by describing dependencies (e.g., user guide accuracy depends on finalized workflow).

3) Budgeting for the case (with consistent numbers and totals)

To practice numeric exam questions, build a budget baseline using activity cost estimates.

Assume these cost items (direct costs):

Cost Item	Description	Estimated Cost (ZAR)
1	Project management labor (PM time for planning & reporting)	18,000
2	Workshop and facilitation costs	6,000
3	User guide design & production	12,500
4	Training delivery costs (materials + trainer time)	14,000
5	Pilot testing and data capture setup	4,500
6	Printing and distribution	6,500

Total direct cost = 18,000 + 6,000 + 12,500 + 14,000 + 4,500 + 6,500
= 61,500 ZAR

Add contingency at 10% (for residual uncertainties):

• Contingency = 61,500 × 10% = 6,150 ZAR

Budget at Completion (BAC) = 61,500 + 6,150 = 67,650 ZAR

This BAC is the consistent base you would use in any EVM-style variance analysis question.

4) Risk register for the case (worked example with response actions)

Below is a structured risk register snippet you can adapt.

Risk scoring model: Probability (P) 1–5 and Impact (I) 1–5; rating = P×I.

Risk ID	Risk Description	P	I	Rating	Category	Proposed Response	Owner	Trigger
R1	Approval delays by Registrar’s office	4	4	16	Stakeholder	Mitigate: approval SLA + weekly tracking; Escalate to sponsor	PM	No approval after 5 working days
R2	Staff training attendance lower than required	3	3	9	Quality/Scope	Mitigate: schedule sessions early + reminder comms; Accept with extra session if needed	HR/Training lead	Attendance <80% in first session
R3	IT enablement issues for workflow pilot	3	4	12	Schedule/Quality	Avoid/Mitigate: pre-pilot tests with IT; reserve IT resources; contingency	IT lead	Pilot not operational by Week 5
R4	User guides contain outdated information due to late workflow changes	4	3	12	Scope/Quality	Mitigate: freeze content after pilot; change control for guide edits	Content lead	Workflow changed within 2 weeks of publishing
R5	Budget underestimation (cost escalation)	2	4	8	Cost	Mitigate: vendor price checks; manage procurement; contingency	Finance liaison	Costs exceed 90% of estimate at mid-project

Why this register scores marks:

• It includes triggers, not just actions.
• It assigns owners.
• It uses a consistent scoring approach.
• It links to both schedule and quality.

5) Monitoring and control plan for the case

a) Baselines

• Scope baseline: WBS + scope statement and acceptance criteria
• Schedule baseline: 10-week plan with milestone dates
• Cost baseline: BAC = 67,650 ZAR and cost breakdown

b) Control mechanisms

• Weekly status reports (progress, issues, risks)
• Steering committee monthly review
• Change request and CCB approval process
• Quality checks: pilot test results and training feedback summaries
• Procurement performance monitoring (if external supplier used)

c) Example earned value reasoning (light EVM)

Assume mid-project at end of Week 5:

• Planned completion of 50% of deliverables
• Earned completion: 45% (pilot slightly delayed)
• Actual spending: 35,000 ZAR by Week 5

Compute:

• PV = 50% × 67,650 = 33,825 ZAR
• EV = 45% × 67,650 = 30,442.5 ZAR
• AC = 35,000 ZAR

Variances:

• CV = EV − AC = 30,442.5 − 35,000 = −4,557.5 ZAR
• SV = EV − PV = 30,442.5 − 33,825 = −3,382.5 ZAR

Interpretation:

• negative CV indicates cost overrun relative to earned value (spending more than planned for the work delivered).
• negative SV indicates behind schedule.

Corrective action options (show judgement):

1. If delays are driven by stakeholder approvals (R1), prioritize escalation and SLA enforcement.
2. If costs are driven by pilot rework (R4), freeze content after pilot and reduce rework through change control.
3. If schedule risk is critical, adjust staffing within budget contingency.

d) Change control example

If Registrar’s office requests additional training modules not in scope:

• Raise a change request:
  • impact on schedule (training sessions require extra week)
  • impact on cost (add estimated 8,000 ZAR)
  • impact on quality (risk of insufficient time for content review)
• CCB decides:
  • approve as Phase 2
  • or accept revised scope with baseline update

In an exam answer, your marks improve if you show you would not blindly accept scope creep.

6) Lessons learned and closing deliverables (often overlooked)

Closing isn’t merely “finish”. It includes:

• formal acceptance by sponsor/steering committee
• final report and documentation
• archive project records
• lessons learned workshop
• performance and benefit evaluation plan

A strong closing section in an exam answer will mention:

• what went well (e.g., pilot helped reduce training mistakes)
• what failed (e.g., delayed approvals affected guide freeze)
• what to improve next time (e.g., earlier scheduling of approvals and clearer SLA)

NMU-Oriented Exam Preparation Strategy: Answering Common Questions, Writing in Mark-Scoring Format, and Applying Tools Correctly

This final section ensures you can convert knowledge into marks. NMU (and many South African university) examiners reward structured responses, correct terminology, applied calculations, and evidence of coherent reasoning. The goal here is to give you a repeatable exam template and practice patterns aligned to the way Business Studies project management assignments are typically assessed.

1) How to structure answers (the “claim–evidence–implication” method)

When you face a theoretical or scenario question, use:

1. Claim: define or state the recommended approach.
2. Evidence: reference tool/framework (WBS, risk register, baseline, EVM, communication plan).
3. Implication: explain effect on time/cost/scope/quality or stakeholder alignment.

Example:
Question: “Explain how risk management supports project objectives.”

• Claim: risk management reduces negative impact on schedule and cost.
• Evidence: risk register with probability/impact scoring, response ownership, triggers.
• Implication: earlier detection allows corrective actions before critical path is affected.

This method stops your answer from being purely descriptive.

2) Common question types and how to score high

a) “Discuss” questions

Examples:

• “Discuss scope management in project management.”
• “Discuss stakeholder engagement strategies.”

High-mark approach:

• start with definitions
• list processes/steps
• link to a scenario
• give one example of a tool (e.g., WBS, stakeholder register, change control log)

Avoid only listing definitions without linking to practical decision-making.

b) “Explain the difference between…” questions

Examples:

• “Differentiate between validation and verification.”
• “Differentiate between quality assurance and quality control.”

High-mark approach:

• use a short table or bullet comparison
• include the “why” in one sentence

c) Calculation questions

Examples:

• EVM calculation (PV, EV, AC, CV, SV, CPI, SPI)
• budget totals and contingency
• critical path duration from a precedence diagram

High-mark approach:

• show formulas
• substitute values clearly
• present final numeric result with units (ZAR, days)
• interpret results (what it means)

Examiners often award method marks even if the final answer is incorrect.

3) “Critical path” and scheduling reasoning: how to write without getting lost

A frequent mistake: students calculate some earliest starts but never say what it means.

A high-scoring written pattern:

1. calculate ES/EF for each activity
2. identify longest dependency chain (critical path)
3. state total duration
4. say which activities have no slack (critical)
5. mention management action: protect critical activities and monitor buffers

In short: always include interpretation.

4) Risk answers that earn marks: beyond listing risks

Examiners typically expect:

• risk identification (threats/opportunities)
• scoring or at least qualitative evaluation
• risk owner
• response strategy
• triggers
• monitoring plan

Low-mark approach: “There is a risk of delays; we will manage it.”
High-mark approach: specify probability/impact, show response selection, name owner and trigger.

5) Communication and stakeholder questions: demonstrate control, not only messaging

If asked “How should communication be managed?”, show:

• who receives what
• frequency and channels
• how communication supports decision-making
• how issues are escalated

Add a stakeholder engagement angle: different stakeholders need different engagement levels.

6) Procurement and contract questions: show risk allocation thinking

If procurement appears, don’t just describe procurement stages. Add:

• vendor selection criteria
• contract terms that protect schedule/quality
• how vendor performance is monitored
• how procurement risks are reflected in the risk register

7) A reusable NMU-style mini template for scenario answers

When you get a scenario, use a structured mini-template like:

1. Project objective and deliverables (1–2 sentences)
2. Scope inclusions/exclusions (bullets)
3. WBS summary (deliverable hierarchy)
4. Schedule approach (key milestones and dependencies; critical path explanation if required)
5. Budget and contingency (totals with arithmetic)
6. Risk register (at least 5 risks; include scoring or qualitative ranking; response + owner + trigger)
7. Monitoring and control (baselines + how variance is managed; change control)
8. Communication and stakeholder engagement (communication plan + engagement strategy)
9. Closing deliverables (acceptance + lessons learned)

This template aligns well with how project management is assessed: breadth plus defensible depth.

8) Terminology you must use correctly (to avoid mark loss)

Use these terms consistently:

• Baseline (scope/schedule/cost)
• Change control (CCB; scope creep management)
• Acceptance criteria (not just “done”)
• Verification vs validation
• Quality assurance vs quality control
• Threat vs opportunity
• Probability/impact scoring
• Critical path and float/slack
• Corrective vs preventive action

9) Two exam practice outlines (write them quickly under timed conditions)

Practice Outline 1: “Explain risk management and provide a risk register”

Include:

• risk register fields
• scoring model
• at least 5 risks with response strategies
• triggers and owners
• monitoring and control

Practice Outline 2: “Build a budget and explain variance using EVM”

Include:

• BAC and contingency math
• PV/EV/AC definitions
• calculation steps
• CV/SV/CPI/SPI and interpretation
• corrective actions

Practical Summary: What to Memorize and What to Apply in NMU Project Management Exams

1. Always define scope clearly (include/exclude) and use acceptance criteria.
2. Build a credible WBS and connect it to schedule and cost.
3. Use scheduling reasoning: dependencies → earliest finishes → critical path.
4. Use budget arithmetic correctly: direct cost totals + contingency to get BAC.
5. Use monitoring logic: compare actual vs baselines; interpret variance and recommend corrective actions.
6. Risk registers must include scoring, owners, response strategies, and triggers.
7. Stakeholder management should show engagement strategy + communication plan + escalation/decision pathways.
8. Procurement is more than “buying”: it’s risk allocation and performance monitoring.
9. Quality is both process and product: QA vs QC.
10. In exams, structure answers: claim–evidence–implication.

These notes support consistent exam performance in Advanced Diploma in Business Studies (Project Management) NMU Notes assessments by integrating frameworks, applied reasoning, and calculation practice into a single coherent study guide.