NWU IOPD 514 Project Management Exam Notes & Study Guide (Unisa/CUT-Style, Practical Focus)

NWU IOPD 514 (Project Management) exam preparation needs more than memorising definitions—it requires disciplined application of project frameworks such as scope, schedule, cost, risk, quality, procurement, and stakeholder management. These notes are written in a South African exam-friendly style, aligned with what students typically study for modules like NMNG / MNG-coded management and project management courses at universities such as UNISA and CUT, while keeping the focus tightly on NWU IOPD 514. Use them as a revision guide: learn the theory, then practise short exam-style answers using the process steps, formulas, and worked scenarios included below.

1) Understanding IOPD 514: Project Management Foundations, Frameworks, and Exam-Answer Structure (NWU)

A strong IOPD 514 start is to master what a “project” is, how project management differs from operations, and how the main bodies of knowledge organise the work. In South African project management exams, lecturers often reward students who:

1. define key concepts crisply,
2. link concepts to the project phases, and
3. show an integrated approach rather than isolated definitions.

1.1 What counts as a project (vs. operations)

Project: a temporary endeavour to create a unique product, service, or result. “Temporary” does not mean short; it means there is a defined start and finish. “Unique” means it is not repetitive like day-to-day production.

Operations: ongoing, repetitive activities intended to produce the same outputs continuously.

Exam-ready comparison (write in a paragraph):

• Projects have a defined lifecycle (initiation → planning → execution → monitoring & controlling → closure).
• Operations have continuous work with ongoing improvement, but no fixed end date.
• Projects typically have higher uncertainty, requiring more risk planning.
• Project success is measured by meeting constraints (scope/time/cost/quality) and stakeholder expectations.

1.2 Project management knowledge areas (the backbone of answers)

In many South African syllabi, including modules similar in structure to NWU IOPD 514, project management is organised into areas that appear in almost every exam question:

1. Integration management (how everything fits together)
2. Scope management
3. Schedule / time management
4. Cost management
5. Quality management
6. Resource management
7. Communications management
8. Risk management
9. Procurement management
10. Stakeholder management

A typical exam marker expects you to use these as headings or sub-points, even if the question is open-ended.

1.3 The project lifecycle and phase activities

A project lifecycle is not the same as a process group; it describes the sequence of phases the project passes through (e.g., feasibility, design, construction, commissioning).

Common lifecycle structure (general but exam-friendly):

• Initiation: identify problem/opportunity, justify project, appoint PM (project manager), draft high-level business case.
• Planning: detail scope, WBS, schedule, budget, risk plan, quality plan, communication plan, procurement plan.
• Execution: do the work (deliverables), manage people/resources, implement plans.
• Monitoring & Controlling: track progress, manage changes, measure performance, update forecasts.
• Closure: handover deliverables, close contracts, conduct lessons learned.

Key point to remember for integration:
Monitoring & controlling is not only at the end; it runs throughout execution.

1.4 Typical exam question formats (and how to structure responses)

South African project management exams frequently include:

• Short questions: define and give one example.
• Medium scenario questions: apply concepts to a case with constraints.
• Longer essays: “Discuss” or “Explain” with a framework and steps.

High-scoring structure for scenario questions:

1. Restate the problem in 1–2 sentences (show you understood the scenario).
2. Identify relevant knowledge areas (e.g., scope, schedule, risk, stakeholders).
3. Apply steps/processes (what would you do first? then next?).
4. Justify why (tie back to success criteria and constraints).
5. Mention deliverables (e.g., WBS, risk register, change request form).
6. Conclude with outcomes (what will improve if you follow your plan).

1.5 Process groups vs. knowledge areas: common confusion

A frequent student error is to mix the two:

• Process groups = where work happens (Initiating, Planning, Executing, Monitoring & Controlling, Closing).
• Knowledge areas = what topic is being managed (Scope, Time, Cost, etc.).

Correct integration example:

• In Planning (process group) you do Scope planning, create WBS, develop schedule and cost estimates.
• In Monitoring & Controlling you compare actual vs. planned, manage changes, track risk.

If the exam asks “Explain schedule management”, you should mention both:

• the schedule management processes (planning/controlling), and
• how those processes occur across process groups.

2) Scope, Work Breakdown Structure (WBS), Scheduling, and Costing for NWU IOPD 514 (Practical Calculations)

Many IOPD 514 exam questions focus on how to structure work (scope), plan it (WBS/schedule), and budget it (cost estimation and control). These are highly teachable topics—marks often depend on whether you can show a clear logic chain.

2.1 Scope management: defining scope clearly

Scope management ensures the project includes all the work required—and only the work required—to complete the project successfully.

A strong answer includes:

• Collect requirements (what stakeholders need)
• Define scope (what the project will deliver)
• Create WBS (break down scope into manageable work packages)
• Validate scope (formal acceptance of deliverables)
• Control scope (manage changes)

Exam tip:
A common mark-loser is unclear deliverables. Good scope answers list:

• deliverables,
• acceptance criteria,
• boundaries/exclusions.

2.2 Requirements vs. scope: avoid a common mistake

• Requirements describe needs and expectations.
• Scope is the set of deliverables and the work to produce them.

For example:

• Requirement: “The website must support multilingual content.”
• Scope statement: “Deliverable includes database schema, content management module, and translation workflow.”

2.3 WBS (Work Breakdown Structure): how it earns marks

A WBS decomposes deliverables into work packages at a level where cost/schedule can be estimated and controlled.

WBS rules you can write in exams

• Start from the final deliverable and break down progressively.
• Use mutually exclusive breakdowns (no overlap).
• Use a consistent numbering system (e.g., 1.0, 1.1, 1.1.1).
• Ensure work packages have measurable outcomes.

Example WBS for a “Library Renovation Project” (illustrative)

Project deliverable: Renovate student library reading area.

A partial WBS:

• 1.0 Project Management
  • 1.1 Initiation and approvals
  • 1.2 Reporting and governance
• 2.0 Design and Documentation
  • 2.1 Architectural design
  • 2.2 Engineering sign-off
  • 2.3 Procurement specification
• 3.0 Renovation Works
  • 3.1 Site preparation
  • 3.2 Demolition
  • 3.3 Partitioning and ceilings
  • 3.4 Electrical and lighting
  • 3.5 Flooring and finishing
• 4.0 Commissioning and Handover
  • 4.1 Inspection and compliance
  • 4.2 Training and handover
  • 4.3 Close-out documentation

Even if the exam question does not ask you to create a full WBS, markers expect to see the principle of decomposition.

2.4 Scope baseline and change control

A scope baseline typically includes:

• scope statement,
• WBS,
• WBS dictionary (optional but often referenced).

When scope changes, you must:

1. Raise a change request
2. Assess impact on schedule/cost/quality
3. Approve/reject via appropriate authority (e.g., steering committee)
4. Update baselines and communicate changes

Scenario mini-example (how to answer):
If a client adds “extra wall shelving” late, you should:

• clarify what “extra” means (size, location, material),
• assess schedule impact (installation affects final flooring/inspection),
• update budget,
• adjust procurement and resources,
• obtain formal approval before execution.

2.5 Scheduling: Gantt charts, milestones, and critical path thinking

Schedule management typically includes:

• define activities,
• sequence activities,
• estimate activity durations,
• develop schedule,
• control schedule.

2.5.1 Gantt chart basics (good for exam drawings)

A Gantt chart shows:

• activities on the vertical axis,
• time periods on the horizontal axis,
• bars indicating duration and overlaps.

Use it for:

• communicating plan to stakeholders,
• showing constraints and dependencies.

2.5.2 Milestones (exam-friendly)

Milestones are significant events with zero duration, such as:

• “Design approved”
• “Site handover”
• “Inspection passed”
• “Training completed”

Milestones simplify progress reporting.

2.6 Critical Path Method (CPM): the logic behind “critical”

While different courses approach CPM differently, the exam usually tests whether you understand:

• dependencies,
• earliest start (ES),
• earliest finish (EF),
• latest start (LS),
• float/slack,
• critical path.

Simple worked CPM-style example

Assume a small project has the following activities and durations:

• A: 2 days (no predecessor)
• B: 4 days (depends on A)
• C: 3 days (depends on A)
• D: 2 days (depends on B and C)

Forward pass:

• A: ES 0 → EF 2
• B: ES 2 → EF 6
• C: ES 2 → EF 5
• D: depends on B and C → ES = max(6, 5) = 6 → EF = 8

Project duration = EF of final activity = 8 days.

Backward pass (conceptual):

• D latest finish (LF) = 8
• D latest start = 8 − 2 = 6
• B latest finish = 6
  • B latest start = 6 − 4 = 2
• C latest finish = 6
  • C latest start = 6 − 3 = 3
• A is predecessor to B and C:
  • A latest start must satisfy both → max of constraints; conceptually this gives float for whichever branch is shorter.

In the final answer, if C finishes earlier (EF 5 vs B EF 6), then C has some slack; B and D are “critical” for maintaining duration.

How to write it in an exam:
State the project duration and explain critical path = the longest dependency chain controlling end date.

2.7 Cost management: estimation and budgeting

Cost management includes:

• estimate costs,
• determine budget,
• control costs.

2.7.1 Cost estimation methods (what lecturers like)

You may be expected to distinguish:

• Analogous estimation: use historical similar projects (faster, less precise).
• Parametric estimation: use statistical relationships (e.g., cost per m²).
• Bottom-up estimation: estimate each work package and sum (more accurate).
• Three-point estimates (often PERT): optimistic, most likely, pessimistic to estimate expected duration or cost.

Example: parametric estimation (write clearly)

If electrical installation costs are R 1,200 per light fitting, and you estimate 50 fittings, then:

• Electrical cost = 50 × 1,200 = R 60,000

If you later find you need 55 fittings:

• Revised electrical cost = 55 × 1,200 = R 66,000
• Cost variance from estimate = R 6,000 increase

2.7.2 Budget vs. estimate

• Estimate: expected cost for planning.
• Budget: allocated funds baseline (often broken down by time and deliverables).

2.8 Cost control basics: tracking actuals against plan

Common exam concepts:

• cost baseline
• cost variance (CV)
• earned value (EV), planned value (PV), actual cost (AC)

Even if your module does not heavily emphasise Earned Value Management (EVM) calculations, many IOPD 514 exam questions still expect:

• how to interpret variance,
• how to forecast using performance indices.

3) Earned Value Management (EVM), Risk, Quality, and Stakeholder Management: Applying the “Control” Skills (NWU)

This section targets the most “application-heavy” exam areas. In South African project management modules, students often struggle because they know definitions but cannot compute or interpret outcomes. The goal here is to provide: (1) EVM calculation competence, (2) risk register logic, and (3) stakeholder and quality planning that ties back to success.

3.1 Earned Value Management (EVM): PV, EV, AC, and variance

EVM compares:

• Planned Value (PV): what the project planned to accomplish by a given date.
• Earned Value (EV): what work was actually accomplished measured in value terms.
• Actual Cost (AC): what it actually cost to do that work.

From these:

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

Interpretation:

• CV < 0 → over budget
• CV > 0 → under budget
• SV < 0 → behind schedule
• SV > 0 → ahead of schedule

Optionally (often included):

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

Worked EVM scenario (use this as a template)

A project is assessed after 6 weeks.

Given:

• PV = R 200,000 (planned work)
• EV = R 170,000 (earned work)
• AC = R 220,000 (actual cost)

Compute:

• CV = EV − AC = 170,000 − 220,000 = −R 50,000
• SV = EV − PV = 170,000 − 200,000 = −R 30,000
• CPI = EV / AC = 170,000 / 220,000 = 0.773
• SPI = EV / PV = 170,000 / 200,000 = 0.85

Interpretation to write:

• The project is over budget (negative CV).
• It is also behind schedule (negative SV).
• CPI 0.773 means the project is getting only 77.3% of the value for each rand spent.
• SPI 0.85 means performance is at 85% of planned schedule progress.

Forecasting: BAC, EAC (common exam logic)

You might also need:

• BAC = Budget at Completion (total planned budget)
• If you have BAC and performance indices, you can forecast EAC.

A common simplified formula:

• EAC = BAC / CPI
• (Alternative: use SPI if schedule issues dominate; sometimes: EAC = AC + (BAC − EV) / CPI, but keep consistent with your module’s approach.)

Assume:

• BAC = R 1,000,000
  Then:
• EAC = 1,000,000 / 0.773 ≈ R 1,294,200

Interpretation:

• If performance continues, total project cost may rise to approximately R 1.294 million, indicating escalation risk.

3.2 Risk management: risk registers, probability-impact, and response planning

Risk management includes:

• identify risks,
• analyse risks (qualitative or quantitative),
• plan responses,
• implement responses,
• monitor and control risks.

3.2.1 Qualitative risk analysis: the expected “risk matrix”

You often classify risks using:

• likelihood (e.g., Low/Medium/High),
• impact (e.g., Low/Medium/High).

A typical exam answer includes:

• a risk rating (e.g., “High likelihood + High impact = high priority”),
• justification,
• and response strategy.

3.2.2 Risk responses: avoid, mitigate, transfer, accept

For threats (negative risks):

• Avoid: eliminate the threat by changing plan.
• Mitigate: reduce probability and/or impact.
• Transfer: shift impact to a third party (insurance, contract clauses).
• Accept: no action now; create contingency and monitoring.

For opportunities (positive risks):

• Exploit, enhance, share, accept.

Worked example: risk register entries (write like an exam)

Assume a contractor managing a campus IT upgrade faces:

1. Risk: Supplier delays for servers

   • Likelihood: High
   • Impact: High
   • Response: Mitigate (backup suppliers, expedite shipping), Transfer (liquidated damages clauses), and create contingency.

2. Risk: Cybersecurity vulnerabilities discovered late

   • Likelihood: Medium
   • Impact: High
   • Response: Mitigate (security testing early), Avoid (architecture review before procurement), Accept (if time-limited) with contingency.

Your risk register should include:

• description,
• probability/impact,
• owner,
• triggers,
• response actions,
• contingency and assumptions.

3.3 Risk monitoring and triggers: “when to act”

High marks often come from including triggers such as:

• “If lead time exceeds 2 weeks beyond estimate, trigger escalation with supplier.”
• “If defect rate exceeds X per 100 tests, re-run regression and halt deployment.”

Even simple thresholds show exam markers that you understand control.

3.4 Quality management: planning for “fit for use”

Quality is about ensuring deliverables meet requirements and fitness for use. Quality management includes:

• plan quality,
• manage quality assurance,
• perform quality control.

3.4.1 Quality assurance vs quality control

• Quality assurance (QA): processes that ensure the quality system is correct (prevention).
• Quality control (QC): inspection/testing of outputs (detection).

A strong exam answer contrasts:

• QA reduces defects by improving processes (e.g., standard checklists, training).
• QC ensures deliverables meet acceptance criteria (e.g., test results, inspections).

Example: construction and inspections

For a renovation:

• QA: follow method statements, train workers, use approved materials.
• QC: measure dimensions, inspect installation, test electrical compliance.

3.5 Stakeholder management: mapping power/interest and communication plans

Stakeholder management focuses on:

• identifying stakeholders,
• planning engagement,
• managing engagement,
• monitoring overall stakeholder relationships.

3.5.1 Stakeholder mapping (power vs interest)

Common categories:

• High power, high interest: manage closely.
• High power, low interest: keep satisfied.
• Low power, high interest: keep informed.
• Low power, low interest: monitor.

Example for a university project

Stakeholders could include:

• Project sponsor (high power, high interest)
• Faculty management (high power, medium interest)
• Student representative council (medium power, high interest)
• Maintenance staff (medium power, medium interest)
• External contractor (high power, low-to-medium interest depending on contract terms)

3.5.2 Communications plan essentials

A communications plan should specify:

• audience,
• information type (status reports, risk updates),
• frequency,
• channel (email, meetings),
• owner (who sends),
• format (dashboard, report template).

In exam scenario questions, if the project is behind schedule and stakeholders are upset, you can propose:

• daily stand-ups with contractor,
• weekly steering committee reporting,
• targeted issue escalation within 24 hours for critical risks.

4) Procurement, Contract Management, Change Control, and Professional Ethics in Projects (NWU)

Many learners focus on technical planning but lose marks on procurement, contract governance, and change control. In IOPD 514, these topics often connect to real-world issues: supplier performance, delays, scope creep, contract disputes, and governance. This section addresses those with exam-ready frameworks and scenario responses.

4.1 Procurement management: buying goods/services for the project

Procurement management includes:

• plan procurement,
• conduct procurements,
• control procurements,
• close procurements.

Key planning decisions to mention

• Make-or-buy analysis (use internal resources or purchase externally).
• Procurement strategy (competitive tendering, negotiation, preferred suppliers).
• Contract type (fixed-price, cost-reimbursable, time-and-materials).
• Evaluation criteria (price, quality, delivery time, capability).

4.2 Contract types and why they matter

A brief exam-ready description:

• Fixed-price (lump sum)
  Supplier bears more risk; buyer expects clear scope and specifications.

• Time-and-materials
  Used when scope is uncertain; buyer pays for time and materials at agreed rates.

• Cost-reimbursable
  Buyer reimburses allowable costs; often includes incentives and controls. Requires strong oversight to prevent overspend.

Scenario example: “scope uncertainty”

If the project scope is still evolving (e.g., design not final), fixed-price may be risky. Time-and-materials or cost-reimbursable may be more appropriate, accompanied by tighter change control and milestone-based payment.

4.3 Procurement documents and evaluation

Typical procurement documents:

• Statement of Work (SOW)
• Terms of reference
• Technical specifications
• Contract conditions
• Delivery timelines
• Pricing schedule
• Bid evaluation form

A strong exam answer should include:

• evaluation criteria and weights,
• how you ensure fairness and compliance with policies.

4.4 Contract management: performance tracking and claims

Contract management involves:

• managing deliverables,
• tracking performance (quality, schedule),
• handling non-conformance,
• processing variations and claims.

In exams, you might be asked: “What should the PM do if the contractor delivers late?”

Exam answer logic:

1. Check contract milestones and deliverable acceptance criteria.
2. Confirm whether delay is due to contractor control or external causes (e.g., utilities).
3. Require an updated recovery plan (schedule baseline updates only after approval).
4. Apply contract mechanisms (extensions of time, liquidated damages—if applicable).
5. Document everything (audit trail).

4.5 Change control: integrated change management

Change control is an integrated process—because a change in scope affects schedule and costs, possibly also quality and risk.

Change control steps (write as numbered steps)

1. Receive request (change request form)
2. Log it into change register
3. Assess impact:
   • scope implications
   • schedule impact (activities/durations)
   • cost impact (estimates, budget changes)
   • quality impact (acceptance criteria)
   • risk implications
4. Evaluate alternatives (do we reduce scope elsewhere? extend schedule? negotiate cost?)
5. Decide (approval/rejection)
6. Implement approved changes
7. Update baselines and communicate to stakeholders

4.6 Scope creep: prevention and response

Scope creep is incremental expansion of scope without corresponding adjustments to time/cost/effort.

Prevention strategies:

• clear scope baseline and WBS,
• strict requirement change process,
• stakeholder engagement to clarify needs early,
• regular scope validation meetings.

Response strategies:

• negotiate trade-offs (e.g., “If we add Feature X, we must remove Feature Y or extend timeline.”)
• formalise approvals (no verbal “yes” without documented change).

4.7 Professional ethics and governance in project management

In South African university programs, ethics is often assessed indirectly: students should show that governance and integrity matter.

Exam-ready ethical points:

• transparency in reporting (no hiding negative variance),
• fairness in procurement (no conflicts of interest),
• confidentiality of bid and project information,
• accountability for project decisions,
• compliance with university/public procurement policies (in principle).

A good exam answer to an ethics scenario includes:

• steps to report irregularities,
• documenting decisions and evidence,
• consulting relevant governance structures.

4.8 Worked example: change impact with cost/time trade-offs

Scenario:

• Original plan: 8-week project, budget R 1,000,000.
• New requirement: additional security gate installation increases scope.
• Assessment shows it adds +2 weeks but increases cost by R 150,000.
• Stakeholders propose alternative: reduce interior finishing scope to keep schedule.

Alternative assessment:

• If finishing is reduced, schedule returns to 8 weeks but cost increases only by R 90,000 (because labour hours are reduced but security work remains).

How to answer:

• compare options,
• recommend based on constraints and acceptance criteria,
• ensure the approval process is used,
• update baselines accordingly.

Keep numbers consistent in your response:

• Option 1 end date: 10 weeks, budget R 1,150,000
• Option 2 end date: 8 weeks, budget R 1,090,000

5) Integrated Project Planning and Exam Practice: Building a Complete Management Plan, Using Case Studies, and Answering Like a Top Student (NWU)

The final section consolidates what examiners want most: integrated thinking. Rather than separate “scope essay”, “risk essay”, and “quality essay”, you must show how a project management plan connects everything. This is where you can gain substantial marks by writing a coherent project approach that addresses multiple constraints simultaneously.

5.1 The integrated project management plan: what it must contain

A practical management plan includes (mapped to knowledge areas):

• Project charter: purpose, objectives, high-level scope, sponsor authority.
• Scope baseline: scope statement, WBS, WBS dictionary (optional).
• Schedule baseline: activities, durations, milestones, dependencies.
• Cost baseline: budget allocation over the timeline.
• Quality plan: QA/QC methods, acceptance criteria, standards.
• Resource plan: roles, responsibilities, staffing schedule.
• Communications plan: meeting cadence, reporting formats.
• Risk management plan: risk register, thresholds, response strategies.
• Procurement plan: contract strategy, procurement schedule.
• Stakeholder engagement plan: communication and management approach.

In an exam scenario, you can mention these as a checklist.

5.2 Mini-case study (composite university scenario) and integrated response

Case: A North-West University campus department approves an IOPD 514-type project: upgrading a departmental learning management system and training staff. The project must be completed before the start of the academic semester to avoid disruption.

Assume these baseline constraints (use consistently):

• Scheduled duration: 10 weeks
• Budget at completion (BAC): R 500,000
• Deliverables:
  1. System configuration and integration (Deliverable 1)
  2. Data migration (Deliverable 2)
  3. Security testing and compliance sign-off (Deliverable 3)
  4. Staff training and handover documentation (Deliverable 4)

Common exam question: “Describe how you would manage scope, schedule, cost, risk, quality, and stakeholders.”

A top response connects deliverables to WBS, schedule milestones, cost budgeting, and control.

5.3 Scope plan application to the case

Step 1: Define scope and deliverables
Write deliverables in scope terms:

• Deliverable 1: LMS configuration includes role-based access, course templates, and integration with authentication.
• Deliverable 2: Data migration includes extraction, cleaning, migration scripts, and verification.
• Deliverable 3: Security testing includes vulnerability scan, penetration test report, remediation retest, and sign-off.
• Deliverable 4: Training includes workshops, user guides, and handover documentation.

Step 2: Build a WBS (partial example)

• 1.0 Project Management
• 2.0 Requirements & Design
• 3.0 LMS Configuration
• 4.0 Data Migration
• 5.0 Security Testing & Compliance
• 6.0 Training & Handover
• 7.0 Procurement/Support (if external testing contractor used)

Even a partial WBS signals exam competence.

Step 3: Scope acceptance
Define “acceptance” criteria, such as:

• configuration approved by departmental IT lead,
• migration validation pass rate,
• security sign-off documented,
• training attendance and competency evaluation completed.

5.4 Schedule plan application with milestones

Create milestones aligned to deliverables:

• Week 2: Requirements and design approved
• Week 4: Configuration complete
• Week 6: Data migration completed and validated
• Week 8: Security testing completed and remediation retest passed
• Week 10: Training completed and project closure documentation signed off

In your answer, explain dependencies:

• security testing depends on configuration and migration availability,
• training depends on security sign-off and final system readiness.

5.5 Cost plan application (and how to justify estimates)

Allocate budget across work packages (example allocation that sums to R 500,000):

Work Package	Budget (R)
Project Management (1.0)	80,000
Requirements & Design (2.0)	60,000
LMS Configuration (3.0)	140,000
Data Migration (4.0)	90,000
Security Testing & Compliance (5.0)	80,000
Training & Handover (6.0)	50,000
Total	500,000

This table is intentionally simple and complete:

• The total equals R 500,000.
• Your exam answer can reference this allocation as a budget breakdown.

If the exam asks for cost control approach:

• compare PV/EV/AC weekly or at key milestones,
• forecast EAC when CPI drops.

5.6 Risk management application to the case (with triggers)

Identify 4–6 high priority risks:

1. Risk: Data migration errors increase rework

   • Likelihood: Medium
   • Impact: High
   • Response: Mitigate (use test migrations, run reconciliation checks)
   • Trigger: “If error rate exceeds 2% during trial migration, halt production migration and rerun data cleaning.”

2. Risk: Security compliance sign-off delayed

   • Likelihood: Medium
   • Impact: High
   • Response: Avoid/Mitigate (engage compliance early, draft test scripts early)
   • Trigger: “If remediation cycle exceeds 1 round by Week 7, escalate to sponsor and adjust scope for retest timing.”

3. Risk: Key SME unavailable for sign-off

   • Likelihood: Low-Medium
   • Impact: Medium
   • Response: Accept/Mitigate (backup reviewers, scheduling buffer)
   • Trigger: “If no sign-off by assigned SLA date, trigger escalation and interim approval.”

4. Risk: Training adoption low (stakeholders resist change)

   • Likelihood: Medium
   • Impact: Medium
   • Response: Mitigate (communication plan, champions, Q&A sessions)
   • Trigger: “If post-training assessment < 70%, schedule additional sessions.”

Your goal is to show the risk register is not just a list; it includes owners and triggers.

5.7 Quality plan application to the case

Define QA/QC activities:

• QA:

  • standard configuration templates,
  • peer review of configuration changes,
  • documented development and change procedures.

• QC:

  • acceptance testing checklist per deliverable,
  • data migration reconciliation report,
  • security test evidence packages.

Acceptance criteria examples:

• Migration: “100% courses migrated, with reconciliation of student counts.”
• Security: “Signed vulnerability remediation report and final test summary.”

5.8 Stakeholder engagement plan for the case

Map stakeholders:

• Sponsor (campus manager or head of department): high power, high interest
• IT lead: high power, high interest
• Compliance/security officer: high power, medium-high interest
• Staff users: medium power, high interest
• Students: low power directly, but high interest indirectly (minimise disruption)

Communications plan (sample):

• Weekly steering meeting (sponsor + IT lead): progress, risks, decisions
• Bi-weekly technical working session: configuration and migration status
• Training communications: schedule announcements, user guides before go-live
• Escalation channel: 24–48 hour response for critical issues affecting Week 10 handover

5.9 Earned Value control integrated into the case

Assume after Week 5 (midpoint), the project has:

• PV = R 250,000 (planned value by Week 5 out of 10 weeks)
• EV = R 215,000 (earned value based on completed deliverables)
• AC = R 260,000 (actual spend)

Compute:

• CV = EV − AC = 215,000 − 260,000 = −R 45,000
• SV = EV − PV = 215,000 − 250,000 = −R 35,000
• CPI = EV / AC = 215,000 / 260,000 ≈ 0.827
• SPI = EV / PV = 215,000 / 250,000 = 0.86

Interpretation for your answer:

• Over budget and behind schedule.
• The reason must be investigated: Are we spending more due to rework? Is migration causing delays?

Corrective action options:

• update the schedule with realistic durations,
• revise estimates for remaining work packages,
• implement recovery plan,
• consider change control if scope must change.

Forecasting:

• BAC = R 500,000
• EAC = BAC / CPI = 500,000 / 0.827 ≈ R 604,200

State the forecast as part of monitoring & controlling:

• “If performance continues, total cost may reach approximately R 604,200, exceeding budget by about R 104,200.”

5.10 Contract and procurement integration: using supplier support carefully

If the project uses an external security testing contractor:

• procure through a competitive process or preferred supplier list (as per policy),
• set contract deliverables: test plan, scan report, penetration test report, remediation guidance, retest results,
• include timeline clauses aligned to the Week 8 milestone.

If delays occur:

• contract management includes documenting causes, negotiating extensions, and enforcing quality deliverables (not just time).

5.11 Exam-writing practice: model answer skeletons

Below are exam-ready skeletons you can practise. They are not filler; they demonstrate how to hit marks by addressing the question requirements explicitly.

Skeleton A: “Discuss scope management” (scenario-based)

1. Define scope management and why it matters.
2. Explain the scope management processes (requirements → define scope → WBS → validate → control).
3. Provide a scenario application:
   • show deliverables,
   • propose WBS breakdown,
   • describe acceptance criteria,
   • outline change control steps.
4. Conclude with how scope control protects time and cost.

Skeleton B: “Explain EVM and interpret variances”

1. Define PV/EV/AC and equations for CV and SV.
2. Compute values using provided data.
3. Interpret signs (positive/negative).
4. Mention indices (CPI/SPI).
5. Provide a corrective action plan and forecasting approach.

Skeleton C: “Identify risks and propose responses”

1. Explain risk register purpose.
2. List at least 4 risks with probability/impact and owner.
3. Specify response strategy (avoid/mitigate/transfer/accept).
4. Add triggers and contingency actions.
5. Explain monitoring approach.

Skeleton D: “Write a procurement plan”

1. Decide what to buy and why (make-or-buy).
2. Choose procurement method and contract type.
3. Define evaluation criteria.
4. Plan performance monitoring and contract closure steps.
5. Link procurement decisions to schedule milestones.

5.12 South Africa exam relevance: integrating course vocabulary like Unisa/CUT management modules

South African project management teaching often overlaps with general management modules. Students frequently take exams in modules that use comparable exam language such as:

• “discuss”
• “justify”
• “evaluate alternatives”
• “apply to a scenario”
• “explain processes”
• “outline deliverables”

Even when a module is specific—like NWU IOPD 514—lecturers typically reward consistent academic style used in other institutions’ management/programme modules (for example, UNISA and CUT management and project-related courses commonly use frameworks and applied discussion). Therefore:

• Use the same core project management vocabulary consistently.
• Write structured, process-based answers.
• Include deliverables (risk register, communication plan, WBS, baselines).
• Use worked computations only where the exam provides numbers or expects them.

This integrated style is especially helpful in essay questions because you show both conceptual understanding and practical application.

Conclusion: What to Practise for NWU IOPD 514

To score highly in NWU IOPD 514 Project Management, practise four layers repeatedly:

1. Framework accuracy (process groups and knowledge areas).
2. Scope clarity (WBS, deliverables, acceptance criteria, change control).
3. Control calculations (especially EVM: PV/EV/AC, CV/SV, CPI/SPI, forecasting).
4. Integrated scenarios (risk register with triggers, quality QA/QC evidence, procurement governance, stakeholder engagement).

Mastering these layers turns definitions into marks.