This study pack consolidates the most commonly assessed concepts in a University of Johannesburg (UJ) short course in Project Management, aligned to the way South African universities (including UJ, UNISA, and other institutions) commonly test project management theory in exams and assignments. It blends core frameworks (scope, time, cost, risk, procurement, stakeholder management) with practical exam-ready techniques: how to define terms, structure answers, apply models to scenarios, and avoid common marking pitfalls.
The pack is written as College of Business & Economics (CB&E)-appropriate material, focusing on the logic and decision-making behind project management—rather than only formulas—so you can respond effectively to scenario questions, case studies, and short-answer theory prompts.
Section 1: Project Management Foundations (UJ Short Course) — Concepts, Terminology, and How Exams Test Them
Project management is often misunderstood as “just planning,” but exam questions typically test whether you can connect project purpose, constraints, and governance to real decision-making under uncertainty. In a UJ short course context, questions frequently resemble the style used across South African university modules such as UNISA project-related study units: define concepts, classify processes, explain why choices matter, and interpret outcomes from given project information.
1.1 What a Project Is (and Why Definitions Matter in Exams)
A project is a temporary endeavour undertaken to create a unique product, service, or result. The word temporary signals a definite start and end; unique signals that the outcome isn’t a mass-produced repeat.
Examiners often award marks for:
- Mentioning temporary and unique explicitly.
- Differentiating project work from operations (ongoing, repetitive work).
- Using the “product/service/result” language correctly.
Operations vs Projects (classic exam distinction):
- Operations: continuous, stable processes (e.g., daily banking operations).
- Projects: temporary, change-oriented efforts (e.g., launching a new digital banking feature).
Example scenario (typical in exams):
A bank updates its mobile app security every year through a recurring process.
- If it is repeatable and continuous → likely operations (or a continuous improvement cycle).
- If it is a one-time rollout of a new security architecture with a defined deadline and scope → likely project.
1.2 Programme and Portfolio: How to Avoid Losing Marks
In many CB&E exam settings, students are expected to know that:
- A programme is a group of related projects managed in a coordinated way to achieve outcomes.
- A portfolio is a collection of projects/programmes managed to meet strategic objectives.
Common exam issue: students incorrectly say portfolio = programme or vice versa. A good rule:
- Portfolio = strategic selection and resource alignment
- Programme = benefits and coordinated delivery
- Project = delivery of a defined result
Example:
UJ (fictional for study practice) wants improved graduate employability.
- The overall plan could be a programme with multiple initiatives: career workshops, employer partnerships, curriculum redesign.
- The university’s investment in multiple such initiatives across faculties could be part of a portfolio.
1.3 Key Project Constraints: The “Triple Constraint” and Beyond
The famous triangle: scope, time, cost—often called the triple constraint. Many exam questions ask you to explain trade-offs.
Scope: what work is included (and excluded).
Time: duration and milestones.
Cost: budget for resources and activities.
However, modern answers also often mention:
- Quality/Performance
- Risk/Uncertainty
- Resources/Capabilities
- Stakeholder expectations
Exam-ready phrasing:
- If scope increases and time is fixed, cost typically increases or quality decreases.
- If time is reduced (crashing/fast tracking), cost often increases due to additional resources.
1.4 Stakeholders and Governance (Where CB&E Exams Often Go Next)
Most project management questions move quickly from “what is a project” to “who influences decisions.”
A stakeholder is any person, group, or organization that can affect or be affected by project outcomes.
In a UJ short course, you may see questions about:
- Identifying stakeholders
- Assessing power/interest
- Managing expectations
- Explaining governance: who approves, who monitors, who escalates issues
Stakeholder Power–Interest Grid (common in exams):
- High power / high interest: manage closely
- High power / low interest: keep satisfied
- Low power / high interest: keep informed
- Low power / low interest: monitor
Practical example:
In a project to implement a new ERP system:
- Finance executives often have high power and high interest (affected by reporting).
- End users (clerks) may have lower power but high interest (daily workflow changes).
- External regulators may have moderate power but high interest (compliance verification).
1.5 Project Management Processes: How Marks Are Allocated
Even though you may not be required to list every process, exams often test the logic behind “planning → executing → monitoring and controlling → closing.” This aligns with typical frameworks (including PMI-style process group logic).
A high-scoring answer often uses:
- Initiation (why and what)
- Planning (how, by what, by when)
- Execution (do the work)
- Monitoring & Controlling (track, compare, correct)
- Closing (hand over, lessons learned)
Scenario-based exam prompt (typical):
“During implementation, the project is behind schedule. Which process group should the manager focus on, and what tools should be used?”
High-quality response:
- Focus on Monitoring & Controlling
- Use variance analysis, progress measurement, schedule forecasting, corrective actions
1.6 Core Knowledge Areas You Must Recognize in Question Wording
UJ CB&E exam questions frequently echo standard knowledge areas. You should be able to map question cues to:
- Integration management (coordination across plans, changes)
- Scope management (requirements, work breakdown)
- Schedule management (sequencing, durations)
- Cost management (budgeting, forecasting)
- Quality management (standards, assurance/controls)
- Resource management (roles, staffing, team development)
- Communications management (information flow)
- Risk management (identify, analyze, respond)
- Procurement management (buy vs make)
- Stakeholder management (engagement, expectations)
Example of cue words in exams:
- “Change request” → Integration / Change control
- “Dependencies” → Schedule management
- “Contingency reserve” → Risk management
- “RACI” → Communications / stakeholder responsibility
- “Bid evaluation” → Procurement
Section 2: Scope, Time, and Cost Planning — From WBS to Critical Path, and Budget Logic That Holds in Scenarios
Once foundations are clear, exams typically test whether you can build coherent plans and interpret outcomes. This section teaches the practical mechanics—WBS, schedule techniques (CPM/critical path logic), and budget management—using exam-style numerical and narrative reasoning.
2.1 Scope Management: Requirements, WBS, and “What Is Not Included”
Scope management answers “What exactly are we delivering?” Exams reward clarity: define scope, explain how requirements are gathered, and show how the work is structured.
2.1.1 Requirements and Deliverables
A deliverable is an output (document, system module, training session, etc.). Requirements specify what that deliverable must do.
In exams, requirements may appear as:
- Functional (what the system must do)
- Non-functional (performance, usability, security)
Example:
For a website project, requirements might include:
- Functional: user login, admin dashboard
- Non-functional: response time under 2 seconds, availability 99%
You must show that requirements drive scope boundaries.
2.1.2 Work Breakdown Structure (WBS): The Exam Backbone
A Work Breakdown Structure breaks the project scope into manageable components. It is often treated as a “must-have” structure in answers.
Typical exam expectations:
- WBS should be hierarchical: major deliverables → work packages → activities.
- Work packages should be small enough to estimate and schedule.
- WBS helps develop scope baseline and supports cost/time estimates.
Example WBS (practice layout):
Project: “Launch a campus event registration platform”
- Project Management
- Requirements & Design
- User stories
- Wireframes
- Development
- Front-end build
- Back-end build
- Database setup
- Testing & Security
- Test planning
- Automated tests
- Penetration testing
- Deployment & Training
- Deployment scripts
- Training for staff
- Handover documentation
Exams often ask: “Why is WBS important?” Good points:
- Enables estimation
- Supports scheduling (activities)
- Supports budgeting and monitoring
- Helps manage change (scope creep detection)
2.1.3 Scope Creep: The Hidden Mark Loss
Scope creep occurs when additional work is added without adjusting time, cost, or resources. A strong exam response links scope creep to poor change control and stakeholder misalignment.
Common cause:
- “We thought that was included.”
- Requirements changed but approvals didn’t follow a change control process.
Strong exam counterpoint:
Not all change is negative. Some changes are essential (e.g., regulatory updates). The key is whether the project updates its baselines and approves changes formally.
2.2 Schedule Management: Logic, Dependencies, and Critical Path
Schedule management is a frequent exam target because it tests whether you can move from activity lists to a logical timeline.
2.2.1 Estimating Activity Durations (and Being Careful With Assumptions)
Exams may give durations or ask you to reason qualitatively. Key reminders:
- Duration vs effort: duration is calendar time; effort is labor required.
- Activity duration assumptions matter in calculations.
2.2.2 Sequencing and Dependencies
Dependencies define which activities must occur before others:
- Finish-to-Start (FS): Activity B starts after Activity A finishes.
- Start-to-Start (SS): Activity B starts when A starts (with possible lag).
- Finish-to-Finish (FF): B finishes when A finishes.
- Start-to-Finish (SF): rare in practice.
Exams often ask: “Given these dependencies, which activity must occur first?” Or “Why can’t we start X yet?”
2.2.3 Critical Path Method (CPM): What You Must Be Able To Interpret
The critical path is the longest path through the network that determines the project duration. Activities on the critical path have zero slack (or slack that matters relative to the chosen baseline). In exam problems, you may need to:
- Identify critical path
- Calculate earliest start/finish times
- Calculate latest start/finish times
- Compute slack
Exam-style numerical example (single coherent scenario)
Consider a small project with activities and dependencies:
| Activity | Dependency | Duration (days) |
|---|---|---|
| A | None | 3 |
| B | A (FS) | 4 |
| C | A (FS) | 2 |
| D | B and C (FS) | 5 |
Step 1: Earliest Start/Finish
- A: ES=0, EF=0+3=3
- B: ES=3, EF=3+4=7
- C: ES=3, EF=3+2=5
- D: ES=max(B EF=7, C EF=5)=7, EF=7+5=12
Project duration = 12 days.
Step 2: Latest Finish/Start (backward pass)
- D ends at project end: LF=12, LS=12-5=7
- For C and B to support D’s LS:
- C must finish by D LS=7: LF(C)=7, LS(C)=7-2=5
- B must finish by D LS=7: LF(B)=7, LS(B)=7-4=3
- A must finish to support both B and C:
- A EF must be ≤ min(B LS=3, C LS=5) depending on dependency network; here both B and C depend on A finish.
- Since B LS=3 and C LS=5, A EF must be ≤3 to allow B to start by 3.
- Therefore LS(A)=3-3=0 and ES(A)=0.
Slack:
- A slack = LS-ES =0-0=0 → critical
- B slack =3-3=0 → critical
- C slack =5-3=2 → not critical
- D slack =7-7=0 → critical
Critical path: A → B → D, total 3 + 4 + 5 = 12 days.
Why critical path matters in exams
Because it informs where to apply schedule control:
- If you delay a critical path activity, project end date shifts.
- If you delay a non-critical activity, there may be no immediate effect if slack absorbs it.
2.2.4 Fast Tracking vs Crashing (and Exam Trade-offs)
If the project must finish sooner:
- Fast tracking: doing activities in parallel that would normally be sequential.
- Risk: rework if assumptions change.
- Crashing: adding resources to shorten durations.
- Cost: typically increases.
Exams often ask you to justify which method is more appropriate given constraints:
- If cost is flexible and risks are manageable → crashing may be acceptable.
- If uncertainty is high and parallel work increases rework risk → avoid fast tracking.
Counterargument points (for high marks):
- Crashing can also cause quality problems if overburdening teams.
- Fast tracking may increase dependencies and integration complexity.
2.3 Cost Management: Budgeting, Baselines, and Variance Thinking
Cost management isn’t just “track spending.” Exams often emphasize baselines and variance logic.
2.3.1 Estimating Costs and Setting a Cost Baseline
Cost estimation includes:
- Labor costs
- Materials and equipment
- Contractor services
- Overheads (as applicable)
- Contingency for known-unknowns (risk-based)
A cost baseline is the approved budget plan over time.
2.3.2 Budgeting and Time-Phased Spending
Budgets are often distributed across time. In scenario questions:
- If cash flow doesn’t match work progress, you may need revised resource scheduling or procurement timing.
2.3.3 Earned Value Management (EVM): Frequently Tested Conceptually
Many short courses include EVM at least conceptually. Typical metrics:
- PV (Planned Value): what you planned to spend by a certain date.
- EV (Earned Value): what work you actually earned in terms of planned budget.
- AC (Actual Cost): what you actually spent.
Common derived indicators:
- Schedule Variance (SV) = EV − PV
- Cost Variance (CV) = EV − AC
Interpretation:
- SV < 0 means behind schedule.
- CV < 0 means over budget.
Example (consistent arithmetic):
Suppose by day 10:
- PV = R 500,000
- EV = R 430,000
- AC = R 470,000
Then:
- SV = 430,000 − 500,000 = −R 70,000 (behind schedule)
- CV = 430,000 − 470,000 = −R 40,000 (over budget)
Exams often ask: “What does this tell the project manager?” A good response:
- The project is both behind schedule and spending more than earned progress indicates.
- Corrective actions may include re-planning schedule, addressing resource allocation, and controlling cost drivers.
2.3.4 Budget Forecasting and Corrective Actions
After variance identification, the next exam step is: “What should you do?”
Possible actions:
- Re-baseline after approved change (if needed)
- Corrective actions to bring performance back in line
- Preventive actions to avoid recurrence (e.g., stronger estimation process, improved risk tracking)
Important exam framing:
Variance itself is not the solution; it is the signal that triggers analysis and action.
Section 3: Project Risk, Quality, and Resource Management — Turning Uncertainty into Control
After scope, schedule, and cost planning, exams often assess the ability to manage uncertainty and performance standards. This section covers risk management, quality planning/assurance, and resource staffing—with practical response strategies for exam scenarios.
3.1 Risk Management: Identification to Response
Risk management answers: “What could happen, how likely, how severe, and what do we do about it?”
3.1.1 Types of Risk
Exams typically want classification:
- Threats: negative impacts (delay, cost overrun)
- Opportunities: positive impacts (cost savings, faster delivery)
- Internal vs external sources
A strong answer also includes:
- Risk events
- Risk causes
- Risk impacts
3.1.2 Risk Register: The Core Artefact
A risk register commonly includes:
- Risk description (event + cause)
- Probability and impact ratings
- Risk score (if used)
- Owner
- Response strategy
- Trigger/indicator
- Status
Exam tip: If a question asks “How would you document risk management?” the risk register is the expected answer.
3.1.3 Probability–Impact and Risk Scoring
If you’re given a matrix:
- Higher probability and higher impact yield higher priority.
- Students often lose marks by mixing up categories.
Example risk scoring logic
Suppose a risk matrix uses:
- Probability: 1 to 5
- Impact: 1 to 5
- Score = Probability × Impact
Risk A: Probability 4, Impact 3 → Score 12
Risk B: Probability 2, Impact 5 → Score 10
Risk A is higher priority in this scoring.
3.1.4 Risk Responses: Avoid, Mitigate, Transfer, Accept (and Exploit/Enhance)
Classic response strategies:
- Avoid: eliminate the risk cause (change plan)
- Mitigate: reduce probability or impact
- Transfer: shift impact to a third party (insurance, contracts)
- Accept: no action except contingency monitoring
- For opportunities:
- Exploit: ensure opportunity happens
- Enhance: increase probability/impact
- Share: involve partners
Scenario question example:
A software project risks delay due to third-party API instability.
- Transfer: contract SLAs with provider.
- Mitigate: build fallback logic and test against alternative endpoints.
- Avoid: use a different provider (likely expensive).
3.1.5 Contingency Reserves vs Contingency Plans
An exam trap is confusing money/time reserves:
- Contingency reserve: budget/time set aside to respond to identified risks.
- Contingency plan: the actions you will take if risk occurs.
Good exam answer:
- “We set a reserve of X for contingency, and the plan is Y.”
Even if X isn’t given, you must explain the purpose and distinction.
3.2 Quality Management: Meeting Standards Under Real Constraints
Quality is not perfection; it is meeting requirements and standards.
3.2.1 Quality Planning and Quality Assurance
Quality management often splits into:
- Quality planning: define standards and how to meet them
- Quality assurance: process-focused activities to ensure quality is achieved
- Quality control: inspection/testing to detect defects
Exams may ask:
- Which is prevention vs detection?
- Assurance = prevention and systematic improvements
- Control = detection through testing/inspection
3.2.2 Common Quality Tools (Exam-Friendly)
You may be expected to reference:
- Checklists
- Sampling
- Statistical analysis (as concepts)
- Cause-and-effect diagrams (Ishikawa)
- Control charts (conceptual)
Because CB&E short courses might not go deep into advanced statistics, conceptual understanding typically scores higher than complex calculations.
3.2.3 Example: Quality in Procurement and Delivery
Suppose a construction contractor supplies materials with risk of non-compliance. Quality management can involve:
- Vendor quality requirements in contract (specs, acceptance criteria)
- Incoming inspection (quality control)
- Audits of supplier processes (quality assurance)
Exams reward the alignment between quality requirements, verification methods, and acceptance criteria.
3.3 Resource Management: Staffing, Roles, and Capacity Planning
Resource management ensures the project has the right people and the right availability.
3.3.1 Roles, Responsibilities, and RACI
A common stakeholder tool is RACI:
- R Responsible (does the work)
- A Accountable (final decision)
- C Consulted (gives input)
- I Informed (kept updated)
Exams may ask for:
- How to reduce decision delays
- How to clarify ownership
Scenario example:
A design change is needed urgently.
If nobody is clearly Accountable, delays occur, impacting schedule. RACI reduces this risk.
3.3.2 Team Development and Performance
Resource management includes team effectiveness:
- Training
- Conflict management
- Communication norms
- Motivation and accountability
In exam answers, emphasize:
- People are part of the delivery system.
- Project performance depends on coordination and clarity.
3.3.3 Capacity vs Demand
An exam-friendly concept:
- If demand exceeds capacity, you either:
- add resources,
- reduce scope,
- adjust schedule,
- or change requirements.
Tie it back to triple constraint.
Section 4: Integration, Communications, Procurement, and Stakeholder Engagement — The “Management” Side of PM
Most marks in project management exams come not from isolated definitions but from explaining how different areas connect. This section integrates project integration management, communications, procurement, and stakeholder engagement, using scenario reasoning.
4.1 Integration Management: The Change Control Mindset
Integration management is often tested through questions about:
- coordinating plans
- managing change
- ensuring baselines align with deliverables
4.1.1 Project Charter and Project Management Plan
Typical exam content:
- Project Charter: authorizes the project and provides high-level purpose, objectives, and governance.
- Project Management Plan: the blueprint for how the project will be executed, monitored, and controlled.
A common question:
- “What is the difference between charter and plan?”
- Charter = “why and authority”
- Plan = “how we will execute”
4.1.2 Change Control: The Formal Approval Mechanism
Change control typically includes:
- Identify change
- Document change request
- Analyze impact (scope/time/cost/quality/risk)
- Decide approval/rejection
- Implement approved changes
- Update baselines and communicate
Scenario example:
A stakeholder requests additional reporting features.
High-scoring answer:
- Treat as a change request
- Assess impact on schedule and budget
- Update scope baseline if approved
- Communicate changes to affected parties
4.1.3 Counterpoint: “Why Not Every Change Is Bad?”
Exams like balanced answers. Not every change is harmful:
- Some changes improve alignment with business needs or reduce risks.
- The quality of change management—analysis and approval—determines whether change becomes scope creep or controlled evolution.
4.2 Communications Management: Planning and Execution Under Pressure
Communications management is about ensuring the right information reaches the right people at the right time.
4.2.1 Communication Plan
A communication plan can include:
- Audience
- Frequency
- Medium (email, meetings, dashboards)
- Purpose (inform, decide, escalate)
- Owner of communication
Exams sometimes ask:
- What would you include in a comms plan?
You can mention frequency and format, not only “stakeholders.”
4.2.2 Reporting: Status, Forecast, and Decisions
In projects, reporting usually covers:
- Progress vs plan (schedule status)
- Costs vs budget
- Risks and issues
- Decisions required
- Next steps
Best exam practice:
Separate:
- Issues (current problems)
- Risks (potential future events)
Students often lose marks by mixing them.
4.2.3 Example: Managing Executive Stakeholders
Executives typically need:
- Summary outcomes
- Whether baseline is threatened
- Required decisions
- Escalation triggers
Detailed technical information belongs elsewhere (technical reports), not executive dashboards—unless requested.
4.3 Procurement Management: Buying Goods/Services Without Losing Control
Procurement is often tested via:
- make-or-buy decisions
- contract types
- vendor selection logic
- managing procurement risk
4.3.1 Make or Buy
Make-or-buy is about whether to produce internally or outsource.
Exam-worthy reasoning:
- Evaluate cost, capability, time-to-deliver, and strategic impact.
- Consider internal capacity and quality.
4.3.2 Contract Types (Conceptual Overview)
Common contract types (conceptual):
- Fixed price: contractor bears cost risk
- Cost reimbursable: client bears more cost risk
- Time and materials: intermediate approach
Exams may ask:
- “Which contract is used when scope is uncertain?”
Answer depends on context: - Uncertain scope often pushes toward time/materials or cost-reimbursable, though it varies by procurement strategy.
4.3.3 Vendor Selection and Evaluation
A vendor selection process may include:
- Technical capability evaluation
- Commercial terms evaluation
- Compliance check
- Scoring model and negotiation
A high-scoring answer:
- Connects evaluation criteria to project requirements.
- Explains why transparency matters (fairness, auditability, reduced dispute risk).
4.4 Stakeholder Engagement: From Identification to Management Plans
Stakeholder management includes:
- Identify stakeholders
- Plan engagement
- Manage engagement
- Monitor stakeholder interactions
4.4.1 Engagement Strategies
Common strategies:
- Communicate regularly with high-power stakeholders
- Tailor information content to audience
- Involve users in testing to reduce resistance
4.4.2 Handling Resistance and Conflicting Expectations
Exams may present conflicting stakeholders:
- Marketing wants speed and features.
- IT wants stability and security.
High-scoring response:
- Use governance and change control
- Present trade-offs using scope/time/cost/quality
- Seek agreement based on project objectives
Counterpoint exam move:
Don’t assume one stakeholder is always right; justify decisions based on project objectives and constraints.
Section 5: Exam Practice Toolkit — Answer Structuring, Case Study Application, and UJ-Style Short Course Revision Patterns
The final section is designed as a high-yield exam toolkit: how to structure answers, how to apply frameworks to scenarios, and how to avoid common marking errors. It also uses multiple integrated mini-cases so you can practice reasoning across scope, schedule, cost, risk, quality, and stakeholders.
5.1 How UJ Short Course Exam Questions Are Typically Structured (and How to Answer)
Even when exact question formats differ, examiners consistently reward:
- Correct terminology
- Logical sequencing
- Direct reference to the scenario
- Explicit assumptions and calculations (when asked)
- Clear justification (“because…”)
A universal answer structure that often performs well:
- Define/identify the concept (1–2 sentences)
- Apply to the scenario (what is happening in the case)
- Explain impact (time/cost/scope/quality)
- Propose action (tools/response strategy)
- Risk/assumptions/limitations (brief but relevant)
5.2 Scenario Mini-Case 1: Schedule Slippage and Cost Overrun
Scenario:
A project to implement a student registration system is scheduled for completion in 12 weeks. After 6 weeks, progress reports show the team has completed only 45% of the planned work, yet 55% of the budget has already been spent. Stakeholders are concerned about the deadline.
5.2.1 What metrics to use?
If the exam asks for analysis, use the earned value logic conceptually:
- Planned progress at week 6: 50% (assume linear plan)
- Earned progress: 45%
- Actual cost consumed: corresponds to 55% of budget
If total budget is assumed in the problem (you would calculate if given), the logic remains:
- EV < PV → behind schedule
- AC > EV → over budget relative to earned progress
5.2.2 Which process group?
Correct direction:
- Monitoring & Controlling to evaluate performance
- then Integration management for corrective actions and change control decisions
5.2.3 Corrective actions (high-scoring ideas)
Options include:
- Schedule recovery plan (re-sequence activities, adjust dependencies)
- Resource reallocation (add staff if cost allows and quality remains)
- Scope review (confirm what is essential for the deadline)
- Risk reassessment (identify causes of delay: procurement, technical issues, training delays)
- Communication upgrade (provide executive forecast and decision points)
Exam counter-argument:
Avoid simply “work harder” without analyzing root causes—overworking increases defects and may worsen quality and cost.
5.3 Scenario Mini-Case 2: Scope Creep via Stakeholder Requests
Scenario:
During development of a marketing campaign project, the client adds new deliverables: additional design variations and new content sections. The team has started implementing these requests informally without updating the project plan.
5.3.1 Identify the problem
This is scope creep caused by:
- lack of formal change control
- unclear scope boundaries and uncontrolled requirements changes
5.3.2 What tool should be applied?
- Change request process
- Scope baseline comparison
- Impact analysis on time and cost
5.3.3 What corrective response should be proposed?
A high-quality response:
- Pause informal changes
- Request formal change documentation
- Evaluate impact:
- time: may require resequencing
- cost: may require budget adjustment
- quality: may require re-prioritization and testing
- Obtain approval/rejection
- Update baselines if approved
Exam mark justification:
The objective is not to stop change; it is to ensure change is controlled and aligned with constraints.
5.4 Scenario Mini-Case 3: Risk Prioritisation and Response Selection
Scenario:
A construction procurement project faces two risks:
- Risk 1: Delivery delays from supplier due to transport issues.
- Risk 2: Regulatory inspection failure due to documentation gaps.
5.4.1 Identify threats and likely impacts
Both are threats:
- Risk 1 threatens schedule and cost (idle time).
- Risk 2 threatens compliance and may cause rework, affecting time, cost, and even acceptance.
5.4.2 Risk response selection logic
-
Risk 1 (supplier delays):
- Mitigate: adjust procurement lead times, use backup suppliers.
- Transfer: contract SLAs with penalties for delay.
- Avoid: choose suppliers with proven logistics reliability (if feasible).
-
Risk 2 (documentation gaps):
- Mitigate: strengthen documentation process, checklist, QA audits before inspection.
- Avoid: ensure compliance standards are met early (process redesign).
- Accept: only if impact is minimal (often not the case for compliance failure).
5.4.3 Why prioritisation matters
If you prioritize wrongly:
- You may spend resources on low-impact risks while missing the compliance risk that actually stops project acceptance.
5.5 Integrated Mini-Case 4: Building a Coherent Plan from Scratch
Scenario:
A university faculty plans to run a one-semester project to launch an online tutoring service. The project must:
- deliver a working platform and training materials,
- start user onboarding by week 8,
- meet data protection requirements,
- and remain within budget.
5.5.1 Build the answer as an “end-to-end management” response
A high-scoring structured answer:
- Initiation: define project purpose, measurable objectives, governance.
- Planning:
- Scope: deliverables list (platform, training materials, onboarding process)
- WBS: break deliverables into work packages
- Schedule: estimate activities and dependencies; identify critical path logic
- Cost: estimate labor/software/subscriptions; set cost baseline
- Risk: identify threats (security, adoption delays) and opportunities (faster onboarding)
- Quality: define acceptance criteria and testing/assurance approach
- Communications: define stakeholder reporting cadence
- Procurement: decide what must be outsourced (e.g., hosting, security assessment)
- Execution: implement work packages; train staff; deploy.
- Monitoring & Controlling:
- track progress, manage changes, run risk reviews
- use variance concepts if numerical data is provided
- Closing: handover, evaluate outcomes, document lessons learned.
5.5.2 How to ensure coherence across sections
Exams punish contradictions. A consistent plan must align:
- WBS deliverables → scheduled activities
- Activities → cost estimates
- Risks → contingency reserves and response actions
- Quality standards → verification methods (testing, audits)
- Stakeholder needs → communication plan and engagement strategies
5.6 Common Errors That Cause Mark Loss (And How to Fix Them)
Error 1: Writing definitions only, without scenario application
Fix: always link back to what the case describes.
Error 2: Mixing risks and issues
Fix: issues are current; risks are potential future events.
Error 3: Confusing scope with schedule
Fix: scope is what you deliver; schedule is when you deliver it. Trade-offs often involve both.
Error 4: Unsupported calculations
Fix: if you compute EV/PV/SV or other values, show the arithmetic.
Error 5: No action proposal
Fix: examiners want “so what?”—what you would do next.
5.7 Revision Checklist (Rapid Pre-Exam Study)
Use this checklist to confirm exam readiness:
Project basics
- Can define project vs operations
- Can explain programme vs portfolio vs project
Scope
- Can explain WBS and why it prevents scope creep
- Can describe change control logically
Time
- Can use critical path reasoning (conceptual CPM)
- Can explain fast tracking vs crashing and trade-offs
Cost
- Can interpret PV/EV/AC conceptually
- Can explain what variance means and propose corrective actions
Risk & quality
- Can build a risk register conceptually
- Can propose risk responses appropriate to threats vs opportunities
- Can distinguish quality assurance vs quality control
Resources & stakeholders
- Can justify staffing/resource decisions from capacity constraints
- Can apply RACI conceptually to avoid decision delays
- Can propose stakeholder engagement strategies
Communications & procurement
- Can describe what belongs in a communication plan
- Can explain vendor selection evaluation and contract risk considerations
Summary and Final Exam Mindset
A UJ short course in Project Management rewards structured thinking: define correctly, apply frameworks to the scenario, calculate where asked, and propose actions that address root causes rather than symptoms. By mastering WBS and scope control, critical-path logic for scheduling, earned value concepts for performance measurement, and risk/quality/resource integration for delivery stability, you position yourself to answer both theoretical and applied case questions with confidence.
