WPM201 – Project Management (NMU BCom Module) Study Guide

WPM201 (Project Management) is a foundational BCom module that equips you with practical tools and exam-ready theory for planning, scheduling, controlling, and closing projects. This study guide is designed to match the kind of work you’ll typically be assessed on in South African university courses—especially where projects, time/cost trade-offs, risk, procurement, and stakeholder management are central. You’ll find structured explanations, worked examples, and exam-focused “how to answer” guidance grounded in standard project management frameworks used across South African commerce programs (including the style commonly expected in BCom project management modules).

1) Project Management Foundations for WPM201 (NMU BCom)

Project management in WPM201 is usually assessed through scenarios: you’re given a business context and expected to identify project phases, justify methods, and apply tools such as scope statements, work breakdown structures (WBS), Gantt charts, critical path analysis, and basic risk/quality approaches. Even when the module references particular frameworks (e.g., PMI-style concepts), exam questions typically test whether you understand the logic behind each tool and can apply it coherently.

1.1 What a project is (and what it is not)

A project is a temporary endeavor undertaken to create a unique product, service, or result. The key features you must remember for exams:

Temporary: it has a start and end (even if the end is not perfectly known).
Unique: not routine production; it delivers something new or distinct.
Resourced and constrained: it uses budgets, people, time, equipment, and must meet requirements.

By contrast, operations are ongoing and repetitive. A manufacturing line producing the same product daily is operational work; building a new production facility is a project.

Exam-style distinction technique:
If the question mentions deliverables, start/end dates, budgets, and a distinct output, you can treat it as a project.

Common exam scenario:
A company runs a “customer satisfaction survey” every year (operations). But designing and launching a new digital survey platform for the first time within a defined timeline (project). If you see “first time,” “roll out,” and “within X months,” that’s your cue.

1.2 Project stakeholders and the project environment

Projects almost always involve multiple stakeholders with competing interests. Stakeholder understanding in WPM201 commonly appears in questions on communication planning, resistance management, and role assignment.

Typical stakeholder categories:

Sponsor: funds and supports the project; typically ensures governance and escalations.
Project manager: coordinates resources, plans, risk response, reporting.
Customers / end users: define requirements and accept deliverables.
Functional managers: provide staff and may influence priorities.
Team members: perform work packages and report progress.
Suppliers / contractors: deliver materials, services, or subprojects.
Regulators / compliance bodies: require legal approvals and adherence to standards.
Project governance (committees, steering committees): reviews progress and approves major changes.

Why this matters:
If you ignore stakeholders, you may create plans that look good on paper but fail due to approvals, procurement delays, or user adoption problems. WPM201 assessments often reward answers that explicitly connect stakeholder actions to schedule/cost outcomes.

1.3 The life cycle: initiation, planning, execution, monitoring & controlling, closing

Most exam questions are anchored in the project life cycle. A common structure you should be able to describe:

Initiation
- Identify the problem/opportunity
- Draft a project charter
- Define high-level scope, objectives, and stakeholders
Planning
- Develop scope management plan, schedule, cost estimates, quality plan
- Build WBS and define activities
- Prepare risk register and communication plan
Execution
- Acquire resources and perform work
- Manage communications and stakeholder engagement
Monitoring and controlling
- Track progress against baseline (scope/schedule/cost)
- Control changes
- Manage risks as they materialize
Closing
- Confirm acceptance, complete documentation
- Perform lessons learned
- Transition deliverables to operations

Exam tip:
When asked “Explain the phases,” you should not just list them—explain what documentation or outputs typically exist in each phase (charter, schedule baseline, risk register, acceptance/hand-over).

1.4 The triple constraint (scope–time–cost) and trade-offs

A foundational concept in project management exams is the “triple constraint”:

Scope: what is delivered
Time: how long it takes
Cost: what it costs
(Often also affected: quality, but in exams quality is usually treated as part of fulfilling scope)

A frequent WPM201 scenario: management requests schedule compression, but that affects cost or scope.

Worked logic example:
If an upgrade must be finished in 8 weeks instead of 10, you may:

Add overtime (cost increases),
Add staff (cost increases, and coordination overhead increases),
Reduce scope (scope decreases—deliverable may not fully meet requirements).

Why marks are awarded:
Good answers mention which constraint changes and the likely second-order effects.

1.5 Project objectives and SMART thinking

Project objectives need clarity. Many courses emphasize objectives that are:

Specific
Measurable
Achievable
Relevant
Time-bound

Example for a marketing project (not just “do marketing”):

“Launch a new customer loyalty program website and campaign within 12 weeks, achieving at least 5,000 sign-ups by week 12.”

If the question asks you to formulate objectives, exam markers expect measurable outputs and a time horizon.

1.6 Governance, project success criteria, and “success is not just finishing”

WPM201 may ask you to define what “success” means. Success could mean:

Delivering within time and budget,
Meeting scope/quality requirements,
Achieving benefits (e.g., cost savings, revenue uplift, improved service),
Stakeholder satisfaction,
Compliance and sustainable handover to operations.

Counter-argument to watch for:
A project can be “on time and on budget” but fail in benefits delivery (e.g., end users reject the system). Conversely, a project may exceed schedule slightly but deliver major business value and high user adoption.

For exam answers, it’s ideal to show you understand both.

1.7 Common project documents and outputs in WPM201

You should be able to explain, at a basic level, what each document is and why it exists:

Project charter: authorizes the project, high-level objectives, roles
Project management plan: integrates subsidiary plans (schedule/cost/quality/risk)
Scope statement: describes deliverables and boundaries
WBS: decomposes deliverables into work packages
Schedule (baseline): planned dates for activities
Cost baseline: budget approved for comparison
Risk register: identified risks, probability/impact, responses
Quality plan: standards, assurance/control activities
Communication plan: who gets what info, when, and how
Change log: records approved/unapproved changes
Acceptance/hand-over documentation: closure and transition to operations

2) Scope, WBS, Scheduling, and Cost Control (Core Exam Tools)

In WPM201, scope and schedule questions are very common. Many exam scripts expect that you can translate requirements into a structured plan using a WBS and then build a schedule using logical sequencing. Cost control may be tested either via basic estimating or via variance-style interpretation.

2.1 Defining and controlling scope

Scope in project management includes all work required to deliver the specified product/service. Scope control is about preventing uncontrolled additions (“scope creep”).

Key scope components:

Scope statement: what the project will deliver and constraints
Deliverables: tangible outputs (e.g., “Training completed,” “Website launched”)
Inclusions vs exclusions: what’s explicitly out of scope reduces misunderstandings
Acceptance criteria: measurable requirements for “done”

Exam-ready phrasing:
When asked about scope creep, explain it as “unplanned expansions of scope without corresponding increases in time/cost.”

2.2 Work Breakdown Structure (WBS): meaning and exam application

A WBS decomposes deliverables into smaller, manageable work components called work packages. In exams, you may be asked to:

Create a WBS from a short scenario,
Convert WBS levels into a schedule,
Explain why WBS supports cost estimation and control.

Good WBS characteristics:

Oriented to deliverables (not just activities),
Hierarchical (Level 1 → Level 2 → work packages),
Each work package is measurable and assignable.

Example WBS (scenario: “Implement an Accounting System”)

Level 1: Accounting System Implementation

Level 2.1: Requirements & Documentation
- 1.1 Business requirements workshop
- 1.2 Process mapping (as-is and to-be)
Level 2.2: System Configuration
- 2.1 Chart of accounts setup
- 2.2 Roles and permissions configuration
Level 2.3: Data Migration
- 3.1 Data cleaning and validation
- 3.2 Import historical transactions
Level 2.4: Testing & Training
- 4.1 User acceptance testing (UAT)
- 4.2 End-user training sessions
Level 2.5: Go-Live & Closure
- 5.1 Cutover support
- 5.2 Handover documentation and sign-off

You’d then map each work package to activities and durations in the schedule.

2.3 Activity definition and sequencing (logic matters more than memorization)

After WBS, project managers define activities required to complete work packages and determine their sequence using dependency logic:

Finish-to-Start (FS): successor can start only after predecessor finishes.
Start-to-Start (SS): successor starts when predecessor starts (overlap allowed).
Finish-to-Finish (FF): successor finishes when predecessor finishes.

In many WPM201 exam questions, the simplest correct approach is to assume FS dependencies unless the question states overlap or other relationships.

Dependency indicators to look for in scenarios:

“Must approve before procurement”
“Data must be cleaned before migration”
“Training after system is configured”

2.4 Building a schedule: Gantt charts and baseline scheduling

A Gantt chart is a visual timeline showing tasks and durations across calendar time. It’s often used in practical project management and in teaching.

Common Gantt question types:

Identify which tasks occur concurrently,
Determine the start and end dates based on dependencies,
Explain why a baseline is necessary for monitoring.

Baseline concept:
Once planning is approved, the schedule becomes the baseline. During execution, actual progress is compared to baseline to compute variances.

2.5 Critical Path Method (CPM): computing duration and critical tasks

CPM identifies the longest path through the project network that determines the minimum completion time. Tasks on the critical path have zero float (delay directly affects finish date).

2.5.1 Step-by-step CPM approach (exam method)

A structured exam method:

Create a network diagram (or list dependencies).
Determine earliest start (ES) and earliest finish (EF):
- EF = ES + duration
- ES of an activity depends on the maximum EF of its predecessors.
Determine latest finish (LF) and latest start (LS):
- LF depends on the minimum LS of its successors.
- LS = LF − duration
Compute float/slack:
- Float = LS − ES = LF − EF
Identify the critical path: activities with float = 0.

2.5.2 Worked CPM example (with consistent numbers)

Scenario: A small office building project has the following activities and dependencies.

Activity	Duration (days)	Predecessors
A: Site prep	5	—
B: Foundations	8	A
C: Walls	6	B
D: Roofing	4	C
E: Electrical rough-in	7	B
F: Plaster & paint	3	C
G: Install fixtures	2	D, F, E

Step 1: Earliest times

A: ES=0 → EF=0+5=5
B: depends on A → ES=5 → EF=5+8=13
C: depends on B → ES=13 → EF=13+6=19
D: depends on C → ES=19 → EF=19+4=23
E: depends on B → ES=13 → EF=13+7=20
F: depends on C → ES=19 → EF=19+3=22
G: depends on D, F, E.
- ES = max(EF of D, F, E) = max(23, 22, 20) = 23
- EF = 23 + 2 = 25

So the project finishes in 25 days.

Step 2: Latest times
Work backwards from project completion time 25.

G: LF=25 → LS=25−2=23
D: successor G → D LF = LS of G = 23 → D EF = D duration 4 → LS = 23−4=19
- So D EF=19+4=23 (consistent)
F: successor G → F LF = 23 → F LS=23−3=20
- F EF=20+3=23, but earlier EF for F was 22; note: latest values can be later than earliest if float exists.
E: successor G → E LF = 23 → E LS=23−7=16
- E EF=16+7=23, earlier EF was 20, so float exists.
C: successors D and F
- C LF = min( D LS, F LS ) = min(19, 20) = 19
- C LS = 19−6=13
- C float = LS−ES = 13−13=0 (critical)
B: successors C and E
- B LF = min( C LS, E LS ) = min(13, 16) = 13
- B LS = 13−8=5
- B float = 5−5=0 (critical)
A: successor B → A LF = B LS = 5 → A LS=5−5=0
- A float =0−0=0 (critical)

Critical path: A → B → C → D → G
Total duration = 5 + 8 + 6 + 4 + 2 = 25 days.

Exam marking expectations:

If you show a correct ES/EF and float calculation, you’ll generally earn strong marks even if the network diagram isn’t drawn perfectly.
If the question asks for “shortest time,” you give the computed 25 days and identify critical activities.

2.6 Schedule compression: crashing basics (and exam trade-offs)

WPM201 may test crashing: reducing the duration of critical activities at additional cost.

A basic crashing logic you should remember:

Identify critical path.
Determine which critical activities can be shortened (usually by paying for extra resources).
For each candidate crash option:
- Compute new duration and new finish time
- Compute incremental cost
Choose the combination that achieves target completion time at minimum added cost (if asked).

Important:
Non-critical activities typically can be shortened without affecting project duration unless constraints and dependencies change. Many exam questions expect you to focus on critical activities.

2.7 Cost estimation fundamentals and cost baseline logic

Cost planning uses:

Analogous estimation (using similar past projects),
Parametric estimation (using statistical relationships),
Bottom-up estimation (sum of work package estimates),
Three-point estimates (where uncertain durations/costs exist).

WPM201 exam questions may give you a budget and ask for interpretation (e.g., variance, forecast, or affordability).

Baseline reminder:
A cost baseline is the approved budget used to measure performance. Costs are tracked as actuals vs planned.

3) Risk Management, Quality, and Stakeholder Communication

WPM201 commonly assesses risk and quality either as stand-alone theory questions or integrated into project scenarios. You’ll typically be expected to identify risks, assess them with probability/impact thinking, and recommend responses. Communication and stakeholder engagement often appear as “what should you do and why” questions.

3.1 Understanding risk: threat vs opportunity

In project management:

Risk is an uncertain event that, if it occurs, has a positive or negative effect.
A threat is negative (e.g., supplier delays).
An opportunity is positive (e.g., early availability of materials).

A strong exam answer explicitly distinguishes these and links them to response strategies.

3.2 Risk identification: where risks come from

Common risk sources in real project scenarios:

Scope risk: unclear requirements, scope creep.
Schedule risk: dependency delays, unrealistic estimates.
Cost risk: price fluctuations, currency risk, labor cost escalation.
Resource risk: skills shortage, staff turnover.
Procurement risk: vendor reliability, contract disputes.
Technical risk: system integration failures, performance issues.
Legal/compliance risk: regulatory approvals delay.
Stakeholder risk: resistance, changing stakeholder expectations.

Exam tactic:
When the question gives a scenario, list risks that are directly supported by scenario facts. Avoid generic risks like “risk of failure” unless elaborated.

3.3 Qualitative and quantitative risk analysis (what to do and how)

Qualitative risk analysis uses probability/impact categories (e.g., Low/Medium/High). You may be asked to create a risk matrix and prioritize.

Quantitative risk analysis may involve numerical techniques (expected monetary value, simulation). For typical BCom exams, qualitative analysis and risk matrix often dominate.

3.3.1 Example qualitative risk matrix

Use a simple 3×3 matrix:

Probability: Low, Medium, High
Impact: Low, Medium, High

Example risks for a “New Payroll System” project:

Risk 1: Data migration errors (P=High, I=High)
Risk 2: Vendor delayed integration (P=Medium, I=High)
Risk 3: User training attendance low (P=Medium, I=Medium)
Risk 4: Minor UI change request (P=Low, I=Low)

If asked to “prioritize,” you focus on High-High and High-medium combinations.

3.4 Risk response planning: avoid, mitigate, transfer, accept

WPM201 answers should show you know the standard response strategies:

Avoid: eliminate threat cause
Example: refine requirements early to avoid scope errors.
Mitigate: reduce probability and/or impact
Example: add data validation and rehearsal migrations.
Transfer: shift impact to a third party
Example: insurance, fixed-price contracts, performance guarantees.
Accept: acknowledge and prepare contingency
Example: keep buffer time; no active prevention.

For each risk, a strong answer includes:

Trigger/early warning signs (when to react)
Response action
Owner (who monitors/acts)
Contingency plan (what to do if it happens)

3.5 Worked risk scenario: turning a risk register into actions

Scenario: A municipal tender awarded to implement an e-permitting platform. The project team identifies these risks:

Supplier delays in delivering servers
Policy changes affecting permit categories
Cybersecurity vulnerabilities discovered late in testing
Budget constraints reducing number of testers

Recommended response plan (exam-ready):

Supplier delays (Threat)
- Mitigate: dual sourcing plan; negotiate delivery milestones
- Transfer: include liquidated damages in contract (if applicable)
- Contingency: prepare local staging environment using temporary hardware
Policy changes (Threat + scope risk)
- Avoid (partially): confirm policy draft status with stakeholders early
- Mitigate: implement configuration-based categories rather than hard-coded changes
- Contingency: establish change control procedure with decision thresholds
Cybersecurity vulnerabilities (Threat)
- Mitigate: security testing earlier; threat modeling during design
- Accept (for low-risk findings): prioritize remediation backlog with severity scoring
- Owner: security lead + vendor security team
Budget constraints (Threat)
- Mitigate: prioritize testing activities; use risk-based testing
- Transfer: if outsourcing testers, use fixed deliverables and performance checks
- Contingency: extend UAT schedule while keeping critical functionality first

Why this scoring improves marks:
Your answer moves beyond “mitigate” to show a plausible operational response and a contingency.

3.6 Quality management in project management

Quality in projects refers to meeting requirements and fitness for purpose. WPM201 may test quality planning and quality control concepts.

3.6.1 Quality assurance vs quality control

Quality assurance (QA): processes to prevent defects (systematic audits, standards)
Quality control (QC): activities to check outcomes (testing, inspections)

Example for an information system project:

QA: use coding standards, peer reviews, test plan templates
QC: perform unit testing, integration testing, UAT, and acceptance verification

3.7 Quality metrics and standards (how to respond in an exam)

If a scenario includes “requirements,” “performance,” or “compliance,” you should link to quality measures such as:

Acceptance criteria (measurable)
Test coverage
Defect rate thresholds
Response time targets (e.g., “page loads under 2 seconds”)
Compliance with relevant regulations or standards

A strong exam answer also connects quality to stakeholder trust and reduced rework costs.

3.8 Stakeholder communication and engagement

Communication planning includes:

What information is communicated
Who receives it
When it is communicated
How it is communicated (reports, meetings, dashboards)

Common communication deliverables:

Weekly status report
Risk updates
Change control notices
Steering committee presentations
Meeting minutes and action tracking

Engagement tools:

Stakeholder mapping (influence vs interest)
Tailored engagement strategies
Managing expectations through transparency and reporting

Exam technique:
When asked “How do you manage stakeholders,” don’t only list communication channels. Explain how communication reduces uncertainty and supports decision-making (e.g., approvals, resource releases, conflict resolution).

4) Project Costing, Budgeting, Procurement, and Performance Measurement

This section connects planning to financial control and delivery mechanics like procurement. Many WPM201 assessments blend conceptual understanding with quantitative reasoning.

4.1 From cost estimates to budgeting

Cost management includes:

Estimating costs,
Determining budget,
Controlling costs.

A project budget typically includes:

Direct labour
Materials/resources
Subcontractor costs
Equipment rental
Overheads allocated (as per institutional method)
Contingency reserve (for risks)
Management reserve (for unknown unknowns; sometimes simplified in BCom exams)

Exam-ready structure:
If a question asks you to build a budget, break it down by WBS work packages or activity categories.

4.2 Procurement management: basics and why it matters in schedules

Procurement involves acquiring goods/services from outside providers. Procurement risks often show up as:

delayed delivery,
contract disputes,
quality issues,
payment delays.

In scheduling, procurement is usually external and can be a critical path driver.

Typical procurement stages:

Identify what to procure
Prepare specifications and requirements
Select suppliers (tendering / quoting)
Negotiate and contract
Order and deliver
Inspect/accept
Pay and close contract

Exam scenario approach:
If a scenario mentions tender processes or supplier selection timelines, don’t assume procurement is instant. Include procurement as a time-consuming activity and link it to schedule dependencies.

4.3 Contract types (conceptual differentiation)

While exams may not demand deep legal knowledge, it helps to understand common procurement contract logic:

Fixed-price: payment fixed; contractor bears cost risk (but may charge for risk).
Cost-reimbursable: payer reimburses eligible costs plus fee; payer bears cost risk.
Time and materials: based on rate and usage; often used when scope is uncertain.

How to use this in exam answers:
If scope is uncertain, fixed-price can be risky for contractor; time-and-materials can reduce contractor risk but requires stronger oversight.

4.4 Change control: linking scope changes to cost/schedule impacts

Change management is a major exam theme. If scope changes, it affects:

schedule (longer/shorter task durations),
costs (more resources/materials),
quality (new requirements),
stakeholder approvals.

Change control workflow (exam-friendly):

Request submitted (description of change)
Impact analysis (scope/time/cost/quality)
Review by change control board/steering committee
Decision (approve/reject/modify)
Update baselines and communicate

4.5 Performance measurement: comparing plan vs actual

WPM201 often uses baseline comparisons rather than complex earned value calculations. Still, you should understand the logic:

Planned value (PV): what you planned to do by a date
Actual cost (AC): what it actually cost
Earned value (EV) (if used): what work was actually completed in terms of budget value

If your module uses earned value, you may be asked to interpret or compute:

Schedule variance (SV = EV − PV)
Cost variance (CV = EV − AC)

Even if earned value is not heavily emphasized, exam questions often test whether you can reason from planned vs actual progress and costs.

4.6 A worked performance measurement example (consistent numbers)

Scenario: By week 6:

Planned value (PV) = R300,000 (planned work value completed)
Earned value (EV) = R240,000 (actual work completed value)
Actual cost (AC) = R260,000 (cost spent)

Compute:

SV = EV − PV = 240,000 − 300,000 = −R60,000
Interpretation: behind schedule.
CV = EV − AC = 240,000 − 260,000 = −R20,000
Interpretation: over budget.

If asked, you’d state both: schedule variance negative and cost variance negative.

4.7 Cost forecasting and variance interpretation

When variances exist, project managers forecast future performance:

If cost variance is negative (over budget), estimate whether to adjust resources or require corrective action.
If schedule variance is negative (behind schedule), assess whether to crash or re-plan.

Exam caution:
Avoid vague statements like “we will monitor.” Provide a plausible action:

re-sequence activities,
add resources to critical tasks,
revise procurement timeline,
improve quality processes to reduce rework.

4.8 Practical mini-case: integrating scope, schedule, and cost

Mini-case: A retail company launches a mobile app.

Scope includes: app development, testing, launch marketing campaign.
Schedule: 10 weeks planned.
Budget: R1,200,000 with contingency R100,000.
At week 5, the app is only at 40% (instead of planned 50%).
Testing has uncovered 12 critical defects, causing rework.

What you should do in an exam answer:

Identify schedule variance (behind plan).
Identify cost impact (rework adds costs).
Recommend corrective action:
- triage defects by severity,
- ensure requirements stability (change control),
- allocate additional testers on critical path items (if budget allows),
- decide whether contingency is used (and document justification).
Communicate with stakeholders:
- sponsor update,
- change control submission if scope/time changes are needed.

Even without exact computations, an exam-grade response connects cause → effect → corrective plan.

5) Exam-Ready Project Planning, Risk/Quality Integration, and Answering Strategies (NMU-style readiness)

This final section consolidates everything into exam performance: how to structure answers, how to apply frameworks consistently, and how to avoid common mistakes. It also provides multiple scenario templates you can adapt in WPM201 tests.

5.1 How to structure an exam response in project management

A typical WPM201 exam question may ask you to:

“Explain and apply”
“Discuss and justify”
“Analyse a scenario”
“Calculate and interpret”
“Recommend”

A high-scoring answer usually has these elements:

Directly address the command verb
- Explain: define + give reasons + example
- Discuss: provide multiple factors + evaluation
- Analyse: identify issues + impacts + relationships
- Recommend: propose action + justify with logic
- Calculate: show steps and interpretation
Use framework logic
- scope → WBS → schedule → cost → risk/quality → communication → control → close
Link tool to purpose
- Don’t just “create a WBS.” Explain how it helps estimation and monitoring.
Provide scenario-specific details
- Use facts from the question (delivery deadlines, stakeholders, dependencies).
Include interpretation
- For numbers, explain what positive/negative variance means.

5.2 Common mistakes that lose marks

Listing theory without applying to the scenario
Markers reward application.
Building a schedule but ignoring dependencies
If activity B depends on A, you must show it.
Confusing critical path logic
Critical path is the longest route determining project duration; float = 0 activities are critical.
Ignoring scope/quality when proposing time changes
Crashing should be linked to cost and quality risks.
Risk responses that are only vague
“Mitigate risk” without describing how/when/owner/contingency often loses marks.

5.3 Scenario templates you can reuse (without repeating exact wording)

Template A: “Plan a project” answer scaffold

Initiation outputs: charter, stakeholders, objectives
Planning outputs: scope statement, WBS, schedule baseline, cost baseline
Quality plan: QA/QC approach and acceptance criteria
Risk plan: risk register + prioritized risks + response strategy
Communication plan: reporting frequency and stakeholder engagement
Monitoring and control: how you track progress and manage changes
Closing: acceptance, handover, lessons learned

Template B: “Risk register + responses” scaffold

For each risk:

description (threat/opportunity)
probability and impact rating (qualitative)
priority (e.g., High-High)
response strategy (avoid/mitigate/transfer/accept)
trigger/early warning
contingency plan
risk owner

Template C: “Schedule question” scaffold (CPM or Gantt)

list activities and durations
show dependencies
compute ES/EF (and LS/LF if CPM)
determine float
identify critical path and minimum project duration
interpret the result (what tasks matter)

5.4 How to answer CPM questions without overcomplicating

If the exam expects CPM, show:

a table of ES/EF and optionally LS/LF,
float computation,
identification of critical tasks.

If a network diagram is not required, tables are acceptable—just be consistent and compute from the dependencies given.

Consistency rule:
If your ES/EF produces a final project duration of 25 days, your later LS/LF and critical path total must also align with 25.

5.5 Integrated case practice: turning theory into a full plan

Consider the following exam-style scenario you might see in WPM201:

Scenario: A business wants to launch an internship program for unemployed graduates. The project must run within 10 weeks and meet these deliverables:

Internship program guidelines and contracts drafted
Recruitment and selection of 50 interns
Orientation training delivered
Matching interns to 10 host departments
Monitoring and final reporting

Assume:

Scope includes delivering the program components above.
Stakeholders: sponsor (HR director), project manager, host departments, applicants/interns, recruitment supplier.

5.5.1 Build a WBS (example)

Level 1: Internship Program Launch
- 1.1 Draft guidelines and contracts
  - workshop with HR/legal
  - draft policy documents
  - contract template sign-off
- 1.2 Recruit and select 50 interns
  - advertise positions
  - screen applications
  - conduct interviews
  - verify eligibility
  - select 50 interns
- 1.3 Deliver orientation training
  - develop training materials
  - schedule orientation sessions
  - deliver orientation
  - attendance verification
- 1.4 Match interns to 10 host departments
  - collect host department needs
  - allocate interns
  - confirm placements
- 1.5 Monitoring and final reporting
  - weekly check-ins setup
  - mid-point review
  - final report drafting
  - stakeholder presentation

This WBS shows deliverables are decomposed into manageable packages.

5.5.2 Schedule reasoning (no need for full CPM unless asked)

Contract sign-off must precede recruiting (dependency).
Orientation cannot start until intern selection is complete.
Matching to departments requires both intern list and host department needs.

In a Gantt, these tasks would appear in sequence with some overlap (e.g., orientation material can be prepared while interviews occur).

5.5.3 Risk examples and responses (exam-grade)

Risk: delays in contract sign-off (P=Medium, I=High)
- Mitigate: early legal engagement; draft based on prior templates
- Contingency: provisional contracts with approval later (if allowed)
Risk: fewer eligible applicants than required (P=Low to Medium, I=Medium)
- Mitigate: expand recruitment channels
- Contingency: adjust selection criteria or extend recruitment window (requires sponsor approval)
Risk: host departments delay accepting interns (P=Medium, I=High)
- Mitigate: weekly confirmations; escalation path
- Transfer: use formal MOUs if possible

5.5.4 Quality plan

Acceptance criteria:
- Contracts signed by sponsor and legal
- Orientation attendance verified for all 50 interns
- Final report submitted and presented
QA activities:
- document review checkpoints
QC activities:
- attendance records audit, eligibility verification checks

5.5.5 Communication plan

Sponsor: bi-weekly steering updates
Host departments: weekly confirmation meetings
Interns and applicants: recruitment updates through defined channels
Weekly internal status report for project team

A full integrated plan like this typically earns strong marks because it connects scope → WBS → schedule dependencies → risk/quality → communication.

5.6 University exam relevance: what NMU BCom markers typically value

In South African BCom project management modules, examiners commonly look for:

correct use of project management terminology,
structured application (not only definitions),
ability to compute and interpret simple schedule/cost measures,
coherent recommendations linked to identified risks and stakeholders.

Using frameworks (WBS, schedule baseline, risk register, QA/QC, change control) consistently and applying them to the scenario is often more important than using advanced jargon.

5.7 Quick “write-this-in-your-exam” checklist

When you start an exam question, mentally run this checklist:

Identify objectives and deliverables (scope clarity)
Provide WBS decomposition (if asked or helpful)
Address dependencies and schedule logic
If CPM asked: compute ES/EF → float → critical path → total duration
Address cost baseline and budget controls (if numbers given)
Add a risk register with responses and triggers (at least 3 risks)
Include quality assurance/control and acceptance criteria
Provide communication and change control steps
Close with acceptance/lessons learned (if closing asked)

5.8 Final consolidation: how each tool fits together

Project management tools are not separate “topics”—they link into an integrated system:

WBS breaks scope into manageable work packages.
Schedule assigns time to work packages and uses dependencies to produce a baseline.
Costing attaches budget to work packages and builds a cost baseline.
Risk management anticipates uncertainties that threaten schedule/cost/scope.
Quality management ensures deliverables meet requirements and reduces rework.
Communication & stakeholder engagement ensure approvals, resource availability, and adoption.
Monitoring & controlling compares actual performance to baselines and triggers corrective actions.
Closing ensures formal acceptance and smooth transition to operations.

In WPM201, marks usually reflect how well you maintain this logic chain while answering the specific command in the question.

If you want, I can also generate fully worked practice exams (with mark allocations and model answers) tailored to the typical WPM201 question styles: (1) WBS + scheduling, (2) CPM float + critical path, (3) risk register + response planning, and (4) cost variance interpretation.