The Advanced Diploma in Project Management (90009) is a structured, competency-driven qualification that strengthens your ability to plan, execute, monitor, and close complex projects in real organisations. This study pack is written to mirror how South African distance-learning students commonly prepare for UNISA (College of Economic and Management Sciences) assessments: with clear frameworks, practical examples, and exam-ready explanations of key project management knowledge areas. It is designed to help you understand not only what to do, but why and how to defend your answers under exam conditions.
1) Project Management Foundations for 90009 Exam Performance (UNISA-Style)
Advanced Diploma modules typically assume that you already know the basics of projects (initiating, planning, executing, monitoring & controlling, and closing). In Advanced Diploma in Project Management (90009), the emphasis shifts to integration of knowledge areas, decision-making under uncertainty, and governance—meaning you must show how project work aligns with strategy, stakeholders, and organisational systems.
1.1 What “Project Management” Means in Advanced Practice
A common exam pitfall is treating project management like a checklist. Instead, you must present it as a management system:
- Projects are temporary undertakings with a defined scope, time, and cost.
- Project management is the application of knowledge, skills, tools, and techniques to project activities to meet requirements.
- In advanced work, “meeting requirements” includes:
- Delivering outcomes (the “what”)
- Managing constraints (time, cost, scope, quality)
- Managing risks and stakeholders
- Using governance to control change
To score higher marks, explain your reasoning: e.g., why a particular approach is suitable, what could go wrong, and how you would respond.
1.2 The Core Project Lifecycle and Exam-Useful Controls
Most South African distance-learning exam answers should be built around lifecycle stages. A clean structure that examiners expect is:
- Initiation
- Define the business need and project purpose
- Identify stakeholders
- Produce high-level project charter / scope outline (depending on module wording)
- Planning
- Define scope breakdown (WBS)
- Plan schedule (activities, sequencing, estimating)
- Plan cost (budgeting)
- Plan quality (standards and acceptance criteria)
- Plan risk management (identify, analyse, respond)
- Plan communications (who needs what, when)
- Plan procurement (if required)
- Execution
- Mobilise resources
- Carry out work packages
- Manage communications and stakeholder engagement
- Track progress against plan
- Monitoring & Controlling
- Measure performance (schedule and cost variances)
- Manage issues
- Manage risks and change requests
- Re-baseline only with proper governance
- Closing
- Validate deliverables/acceptance
- Release resources
- Document lessons learned
- Formal project closure and handover
1.3 Integration: The “Glue” Topic Examiners Love
In advanced project management, you are often assessed on your ability to integrate across knowledge areas. Integration answers should include:
- How planning outputs become execution inputs
- How monitoring outputs trigger corrective actions
- How change requests are evaluated and approved
- How governance decisions link to risk, cost, and schedule
Exam-style integration example (what to write)
If scope grows (“scope creep”) and schedule slips, a strong answer explains:
- Scope creep increases required work → impacts WBS, schedule, and costs
- You must:
- Record the change request (with scope statement)
- Assess impact on cost, schedule, quality, and risk
- Consider alternatives (e.g., trade-offs, deferring non-critical features)
- Seek approval from relevant authority (e.g., steering committee)
- Update baselines only after approval
- Communicate changes through a controlled communications plan
This is integration: scope interacts with schedule, cost, risk, and governance.
1.4 Stakeholders: From Identification to Engagement Strategy
A high-quality stakeholder section is not a list. It must include:
- Stakeholder identification (internal/external, direct/indirect)
- Stakeholder analysis (power/interest, influence, expectations)
- Engagement strategy aligned to interest and influence
A typical exam classification:
- High power / high interest: manage closely; engage frequently
- High power / low interest: keep satisfied; minimal effort but effective communication
- Low power / high interest: keep informed; encourage participation
- Low power / low interest: monitor; only communicate when needed
Mini-case for stakeholder reasoning
Imagine a project to implement a new billing system in a South African telecoms provider:
- IT infrastructure team: high power, high interest
- Customer service representatives: medium power, high interest
- End customers: low power individually, but high collective interest
- Regulators: medium/high power, low interest (unless issues arise)
Your engagement approach must address training, communication timing, and risk mitigation (e.g., avoiding billing disruptions).
1.5 Common Exam Traps (and How to Avoid Them)
Below are pitfalls that reduce marks in South African diploma-level and advanced diploma exams:
- Writing only definitions (examiners want application)
- Ignoring governance (approval process, change control, reporting lines)
- Not linking outputs to actions (e.g., you “identify risks” but don’t show response)
- No quantitative logic when numbers are provided
- Inconsistent terminology (scope vs requirements, deliverables vs milestones)
- No structure: examiners reward coherent, logical steps
Use headings and bullet points to signal clarity.
2) Project Planning Depth: Scope, Schedule, Cost, Quality, and Risk (90009 Core)
Planning is where most marks are earned because you can demonstrate methodical thinking. For Advanced Diploma in Project Management (90009), planning answers should show you can produce outputs and apply them to scenarios.
2.1 Scope Management: From Requirements to WBS
2.1.1 Defining Scope Properly
Scope includes:
- Product scope: features and functions of the deliverable
- Project scope: work required to deliver the product
In exam answers, always connect scope to deliverables. A well-built scope explanation includes:
- Requirements (what must be achieved)
- Deliverables (tangible outputs)
- Acceptance criteria (how success is measured)
2.1.2 WBS (Work Breakdown Structure) in Exam Terms
A WBS decomposes project work into manageable components. High-scoring WBS answers:
- Are structured hierarchically
- Use deliverable-based decomposition where possible
- Identify work packages that can be scheduled and estimated
Example: WBS for a “Community Clinic Upgrade” project
Goal: Upgrade a small clinic facility including renovations and equipment installation.
A WBS might be:
-
- Project Management
- 1.1 Planning and control
- 1.2 Reporting and governance
-
- Site Preparation
- 2.1 Safety and site mobilisation
- 2.2 Demolition (where required)
-
- Building Renovations
- 3.1 Electrical works
- 3.2 Plumbing works
- 3.3 Wall and ceiling works
-
- Equipment Procurement and Installation
- 4.1 Procurement of diagnostic machines
- 4.2 Installation and testing
-
- Training and Commissioning
- 5.1 Staff training
- 5.2 Commissioning and handover
In an exam, you can represent this as a tree, or describe decomposition reasoning.
2.1.3 Scope Baseline and Change Control
Once scope is baselined, changes must be controlled. A good answer includes:
- How scope baseline is created (scope statement + WBS + WBS dictionary)
- How changes are captured (change requests)
- Who approves (change control board / delegated authority)
- Why baseline change is significant (cost/schedule impact)
2.2 Schedule Management: Activities, Sequencing, and Critical Thinking
2.2.1 Turning Scope into a Schedule
Scheduling translates WBS work packages into activities and sequences them with dependencies:
- Dependencies can be:
- Finish-to-start (FS)
- Start-to-start (SS)
- Finish-to-finish (FF)
- Start-to-finish (SF)
An exam-ready schedule explanation includes:
- Determine activity list
- Sequence activities based on dependencies
- Estimate durations
- Identify critical path
- Develop schedule baseline
2.2.2 Critical Path Logic (Exam-Friendly)
You don’t always need full calculations, but you must demonstrate method:
- Compute earliest start/finish times
- Compute latest start/finish times
- Identify activities with zero slack
- Critical path is the sequence that determines project duration
Mini scenario
A project includes activities A→B→C on one chain and A→D→E on another. If chain B→C has longer duration, the overall project duration depends on that chain. Your answer should explain that critical path governs project completion time.
2.2.3 Schedule Compression and Trade-offs
Advanced planning includes handling schedule pressure:
- Crashing: add resources to shorten durations (increases cost)
- Fast tracking: do overlapping where logical dependencies permit (increases risk)
In an exam, mention:
- Crash impacts: reduced duration but higher cost, potential quality risk
- Fast track impacts: increased rework risk if outputs not fully ready
2.3 Cost Management: Estimation, Budgeting, and Control
2.3.1 Cost Estimation Techniques (Concept + Use)
Even if you’re not required to compute every method, you should describe them:
- Analogous estimation: based on similar past projects
- Parametric estimation: based on statistical relationship (e.g., cost per m²)
- Bottom-up estimation: sum estimates of work packages
- Three-point estimation (often used with uncertainty):
- optimistic (O)
- most likely (M)
- pessimistic (P)
- expected value computed as weighted average (frequently (O + 4M + P)/6 in common practice)
A strong exam answer states when each technique is appropriate and why.
2.3.2 Budgeting and Baselines
Budgeting creates a time-phased cost baseline. A quality answer explains:
- Budget is allocated to cost accounts / WBS elements
- Baseline is used for performance measurement later
- Cost control compares actual performance to baseline
2.3.3 Earned Value Management (EVM): Advanced Control
If 90009 includes EVM concepts, your exam should cover:
- Planned Value (PV): what you planned to earn
- Earned Value (EV): what you actually earned for completed work
- Actual Cost (AC): what it cost to do that work
From these you derive:
- Schedule Variance (SV) = EV – PV
- Cost Variance (CV) = EV – AC
- Cost Performance Index (CPI) = EV / AC
- Schedule Performance Index (SPI) = EV / PV
A high-scoring answer doesn’t just compute; it interprets.
Interpretation example (how to write the conclusion)
- If CPI < 1, you are over budget for the work performed.
- If SPI < 1, you are behind schedule for the work performed.
- If both CPI and SPI are below 1, it indicates cost inefficiency and schedule slippage.
2.4 Quality Management: Standards, Assurance, and Control
2.4.1 Quality Planning in Practical Terms
Quality management answers should clarify:
- What quality means for the deliverable
- Which standards apply (internal, client, statutory)
- How acceptance testing will be performed
Quality planning should include:
- Quality metrics (e.g., defect rate, performance thresholds)
- Inspection and testing approach
- Document control and traceability requirements
2.4.2 Quality Assurance vs Quality Control
A common exam confusion:
- Quality assurance: processes to ensure quality is built in (system-level)
- Quality control: checking deliverables to confirm standards are met (product-level)
In your answer, demonstrate a sequence:
- Define standards and acceptance criteria
- Plan assurance activities (process audits, training)
- Plan control activities (inspections, tests)
- Handle nonconformities (corrective actions)
2.5 Risk Management: From Identification to Responses
2.5.1 Risk Identification
Risk identification methods you can mention:
- Brainstorming workshops
- Expert judgment
- Checklists
- Historical data
- Interviews and document review
Exam answers should also show you distinguish:
- Risks (uncertain events)
- Issues (events that already occurred)
- Opportunities (positive risks)
2.5.2 Risk Analysis: Qualitative vs Quantitative
- Qualitative: probability and impact ratings (e.g., low/medium/high)
- Quantitative: expected monetary value, probability distributions, simulation (where relevant)
A strong answer explains how rating affects prioritisation.
2.5.3 Risk Response Planning
Use the standard response categories:
- Avoid: eliminate the threat by changing the plan
- Mitigate: reduce probability and/or impact
- Transfer: shift impact to third party (insurance, contracts)
- Accept: acknowledge and plan contingency (if needed)
- Exploit/Enhance for opportunities (not just threats)
Example: Risk response in a procurement scenario
If importing equipment has a risk of customs delays:
- Avoid: source locally if possible (changes scope/cost)
- Mitigate: use freight forwarder with proven track record, expedite paperwork
- Transfer: contract includes delivery penalties and clear SLAs
- Accept: prepare contingency inventory or adjust schedule milestones
Your exam conclusion should link response to monitoring activities (how you’ll track triggers).
2.5.4 Risk Monitoring and Contingency
Advanced risk answers include:
- Risk register updates
- Trigger monitoring (leading indicators)
- Contingency reserves (time/cost)
- Reassessment after changes
Contingency use must be governed; not “spend freely.”
3) Execution, Monitoring & Control, Change, Governance, and Communications
This section focuses on the “doing and controlling” side: how work progresses, how you report, and how you manage control mechanisms.
3.1 Execution Management: Resources and Delivery Performance
Execution involves:
- Implementing the planned work packages
- Managing teams and vendors
- Ensuring quality practices are followed
- Managing stakeholder engagement in real time
A high-scoring execution answer includes:
- Resource management approach (skills matching, availability, mobilisation)
- Procurement and vendor coordination (if applicable)
- Work authorization and change triggers
- Tracking progress and capturing actuals
3.2 Communications Management: Stakeholder-Specific Reporting
In exams, communications management is often undervalued because it seems “soft.” But advanced project management treats communications as a control mechanism.
3.2.1 Communications Plan Essentials
A robust communications plan includes:
- Stakeholder list
- Information needs (what they need)
- Frequency (weekly, monthly, milestone-based)
- Format (report, presentation, meeting minutes)
- Ownership (who prepares and approves)
- Delivery method (email, dashboard, meetings)
3.2.2 Reporting Cadence Example
For a multi-stakeholder project (e.g., construction + equipment procurement), typical reporting:
- Project team: weekly operational updates
- Sponsor/steering committee: monthly performance and governance decisions
- Client: milestone sign-offs and monthly progress narrative
- Regulators: compliance reports per requirement schedule
Your exam answers should explain why different audiences need different levels of detail.
3.3 Monitoring & Controlling: Performance Measurement and Corrective Actions
3.3.1 What You Measure
Monitoring should track:
- Scope progress (deliverables completed vs planned)
- Schedule progress (milestone attainment)
- Cost performance (spent vs planned)
- Quality results (defects, test pass rates)
- Risk status (active risks, new risks)
- Issues and blockers
3.3.2 Corrective vs Preventive Actions
- Corrective actions address performance gaps already identified.
- Preventive actions address risks or root causes before they materialise.
A high-quality exam answer shows you differentiate and choose appropriate responses:
- If delays already occurred: corrective action might be re-sequencing tasks, adding resources where logical.
- If a recurring root cause is found: preventive might be process changes, training, updated estimation assumptions.
3.4 Change Management: Integrated Change Control
Change is inevitable. Advanced exams want to see structured handling.
3.4.1 Change Control Process (Exam-Friendly Steps)
A typical integrated change control sequence:
- Receive change request (scope, schedule, cost, quality, resources)
- Log it in a change register
- Assess impact:
- scope impact (what changes)
- schedule impact (which activities/milestones move)
- cost impact (direct and indirect)
- quality impact (standards, acceptance criteria)
- risk impact (new risks, changes in probability/impact)
- Consider options (reject, approve as proposed, approve with modifications)
- Obtain approval from authority (change control board/sponsor)
- Update baselines if approved (scope baseline, schedule baseline, cost baseline)
- Communicate decision and implement change
3.4.2 Change Authorization and Governance
Governance means:
- Who has the authority to approve changes
- What documentation is required
- How escalation works
- How conflicts between departments are resolved
In South African organisational settings, governance often includes steering committees and sponsor-level sign-off.
3.5 Issue Management: Turning Problems into Project Control
Issues are unlike risks because issues are already happening. Exam answers should show:
- How issues are identified and recorded
- How impact is analysed (time/cost/quality)
- How owners are assigned
- How resolution is tracked
- How closure is verified
A practical example:
- Issue: supplier’s delivery is delayed.
- Response:
- identify impact on installation dates
- update schedule and dependent tasks
- consider alternate supplier (procurement escalation)
- implement mitigation in contract management
- update risk register if this delay indicates systemic procurement risk
3.6 Procurement and Contract Management (Where Included in 90009)
Procurement knowledge matters in advanced diplomas because many projects depend on external suppliers.
3.6.1 Procurement Planning and Vendor Selection
Exam answers should cover:
- Make-or-buy decision (if relevant)
- Contract type implications (e.g., fixed price vs time and materials)
- Criteria for vendor selection (capability, cost, delivery capacity, quality record)
3.6.2 Contract Performance Control
You can show control by discussing:
- Delivery milestones and acceptance tests
- Service level agreements (where applicable)
- Payment terms linked to milestones
- Handling defects and nonconformities
- Change order process for procurement items
3.7 Closing and Transition: Making Closure Count
Closure is not just paperwork. For higher marks:
- Validate acceptance of deliverables
- Ensure documentation is complete:
- as-built documentation
- training records
- operational manuals
- warranties and maintenance schedules
- Release resources and close contracts
- Capture lessons learned:
- what worked
- what did not
- what to change in future planning
A good closing answer connects lessons learned to future improvement in estimation accuracy, stakeholder engagement, and risk planning.
4) Exam-Ready Tools, Techniques, and Quantitative Problem Skills (UNISA Competency Focus)
This section provides the kind of step-by-step reasoning students need for exam calculations and “show-your-work” answers. Even if your exam is scenario-based, quantitative logic often earns marks.
4.1 Scheduling Calculations: Activity Tables and Critical Path Methods
4.1.1 Building an Activity Table
When asked to calculate, you typically need to:
- list activities
- list durations
- list predecessors
- compute earliest start/finish
- compute latest start/finish
- compute slack
Your exam writing should show:
- Identify the network logic
- Forward pass (earliest times)
- Backward pass (latest times)
- Slack = LS – ES (or LF – EF depending on method)
- Critical activities have zero slack
4.1.2 Example Approach (Narrative + Calculation Readiness)
If Activity B depends on Activity A:
- ES_B = EF_A
- If A ends at 5 days, B earliest start becomes 5
Then you compute B earliest finish:
- EF_B = ES_B + duration_B
Repeat for all activities.
Even without full numerical detail, examiners reward structured reasoning and consistent application.
4.2 Cost and EVM: Turning Numbers into Management Decisions
4.2.1 EVM Calculation Framework
A frequent exam question provides:
- PV, EV, AC for a given reporting period
- Possibly a baseline estimate (BAC)
Then compute:
- CV, SV, CPI, SPI
- and forecast estimates to complete (depending on the exam scope)
A typical forecast (common variants):
- Estimate to Complete (EAC) may be computed using:
- EAC = BAC / CPI (if assuming CPI will continue)
- or EAC = AC + (BAC – EV) (if assuming schedule performance and remaining cost behave differently)
- Estimate at Completion (again depends on given formula instructions)
Your job in an exam is to:
- compute using the provided formula set
- interpret results for decision-making
4.2.2 Interpreting EVM Outcomes (What to Write)
If a project is:
- Over budget (CV negative, CPI < 1)
- Behind schedule (SV negative, SPI < 1)
Then a strong answer states:
- the project is inefficient in cost and progress is slower than planned
- management actions may include:
- corrective action: re-baseline only with governance
- intensify schedule control (re-sequencing, resource reallocation)
- cost control: reduce unnecessary spend, renegotiate where possible
- risk review: update probability/impact for drivers causing overruns
Examiners want the link between metrics and decisions.
4.3 Risk Quantification: Expected Monetary Value (EMV) Examples
If you are given:
- risk probability
- impact cost if the risk occurs
Then EMV = Probability × Impact.
A strong answer includes:
- threshold thinking: compare EMV to mitigation cost
- if mitigation cost < EMV, mitigation may be cost-effective
- if mitigation changes probability and impact, compute revised EMV
4.4 Quality Calculations (Defects, Pass Rates, Sampling)
Where included, quality questions may require:
- defect rate
- pass/fail percentages
- sample-based inference (if statistics appear)
Even if calculations are basic, explain the managerial meaning:
- High defect rates may indicate process failures → trigger corrective/preventive actions
- Poor acceptance test results cause schedule delays due to rework
4.5 Case Study Writing Technique: “Structure Wins Marks”
When the exam provides a scenario (common in project management modules), you should structure your response:
- Identify the problem(s)
- Identify relevant project management knowledge area(s)
- Provide recommended actions using a logical sequence
- Justify actions (why this approach fits)
- Mention governance and control (how decisions get approved and implemented)
This prevents random bullet listing and improves coherence.
5) South African Exam Preparation Strategy for 90009: Studying, Writing, and Mastering Common Scenarios (UNISA and Alignment with South African University Practice)
This final section consolidates your preparation strategy, focusing on how to convert understanding into exam marks for UNISA-style assessments and scenario-based questions. It also aligns with how students across South Africa approach project management modules in distance education environments.
5.1 Building a “Marking-Scheme Mindset” for Scenario Questions
In project management exams, questions often look like:
- “A project is experiencing delays and cost overruns… recommend how you would respond.”
- “You have received a change request affecting scope and schedule… describe integrated change control steps.”
- “Risks have not been managed; create a risk response plan.”
To score well:
- Use framework language (planning, executing, controlling)
- Use process language (log, assess impact, approvals, updates)
- Use management language (stakeholders, governance, corrective actions)
Avoid writing only what you would do. You must also show:
- how you would do it within governance and control systems
- how you would measure effectiveness
5.2 Creating a Personal 90009 “Cheat Framework” (What to Memorise vs What to Derive)
You should memorise frameworks, not the exact scenario text. Examples of frameworks to memorise:
- Lifecycle stages
- Stakeholder power/interest strategy
- WBS purpose and how it links to schedule and cost
- Risk response categories (avoid/mitigate/transfer/accept; opportunities exploit/enhance)
- Integrated change control steps
- EVM definitions and interpretation logic
But numerical answers should be derived based on the question data.
5.3 How to Answer Without Losing Marks: Writing Style Under Pressure
5.3.1 Use Clear Headings Inside the Answer
Even in exam booklets:
- start with a short heading or phrase
- use numbered steps when asked to “describe” processes
- use bullet lists for lists of stakeholders, risks, responses
5.3.2 Show Working for Calculations
For EVM, CPIs, or critical path calculations:
- show formulas
- substitute values
- compute results
- interpret results
If interpretation is missing, you may lose decision-making marks even if calculations are correct.
5.4 Building and Practising Mini-Case Responses (90009-Compatible)
Create practice answers based on plausible South African project scenarios. Below are three exam-compatible cases with detailed response outlines.
Case 1: IT Implementation Project—Schedule Slippage and Vendor Underperformance
Scenario outline: A system implementation for a South African organisation is behind schedule. The vendor delivered certain modules late, and internal testing is taking longer than planned.
Exam answer outline (what to include):
- Diagnose the cause
- compare planned vs actual delivery of vendor modules
- identify whether delays are vendor-caused or internal integration-caused
- Schedule control actions
- re-sequence dependent tasks where possible
- perform fast tracking only if dependencies permit
- consider crashing if cost approvals exist
- Cost control actions
- quantify additional cost drivers (overtime, rework, penalty impacts)
- compare EV/AC if EVM data is given
- Quality actions
- review testing scope and acceptance criteria
- identify defect root causes
- Governance and change
- if schedule baseline is threatened, prepare change request for approval
- update stakeholders through the communications plan
- Risk and issue update
- convert repeated vendor delays into risk or escalation issues
- define triggers and contingency plans
The marks come from linking: vendor delays → schedule → cost → quality → governance.
Case 2: Construction-Related Project—Scope Creep and Stakeholder Conflict
Scenario outline: A housing infrastructure project experiences repeated additions to scope. Community representatives request extra features. The contractor argues that these are outside agreed scope.
Exam answer outline:
- Identify scope change
- treat as change requests, not informal requests
- Assess impact
- cost: estimate additional materials and labour
- schedule: update dependent activities and milestones
- quality: determine whether standards change
- risk: new risks from complexity and procurement
- Governance
- convene change control board / sponsor decision
- Stakeholder engagement
- manage expectations: explain constraints and alternatives
- use engagement strategy based on power/interest
- Update baselines and documents
- update WBS and schedule only after approval
- Prevent future scope creep
- strengthen requirements sign-off
- improve change request intake procedure
Case 3: Training Project—Quality Failures and Poor Adoption
Scenario outline: A training program for a compliance role is completed, but post-training assessments show low competency. Managers complain staff are not adopting the process.
Exam answer outline:
- Quality diagnosis
- check whether training met acceptance criteria and competency frameworks
- Corrective and preventive actions
- corrective: re-train targeted groups, adjust coaching
- preventive: update training design and assessment methods
- Communications and stakeholder management
- involve managers in reinforcement
- improve timing and channels
- Close and re-plan
- re-open a corrective cycle if deliverable quality is not accepted
- update lessons learned for future training projects
5.5 University Alignment: UNISA and Common South African Project Management Study Patterns
Students studying Project Management at South African universities typically benefit from a consistent workflow:
- Read the module guide and identify assessment patterns
- Create summary notes per knowledge area (scope/schedule/cost/quality/risk/communication/change/closure)
- Practise scenario questions and calculations
- Revise using past-question-style prompts and mark-scheme logic
To keep study practical, structure your notes like mini “answer templates”:
- Start with definitions (1–2 lines)
- Then provide process steps (4–8 points)
- Then provide justification and example (1–2 paragraphs)
- Then include governance/controls (2–4 bullet points)
This approach matches what examiners usually look for: breadth + application + coherent structure.
5.6 Final Revision Plan (Two-Week Blueprint)
A realistic revision schedule for a working student can be:
- Day 1–2: refresh lifecycle, integration, stakeholder engagement, change control basics
- Day 3–4: deep revision of scope (requirements, WBS, baseline), schedule (critical path logic), quality (assurance vs control)
- Day 5–6: risk management planning and risk response categories + monitoring
- Day 7: intensive revision of EVM definitions, formulas, interpretation logic
- Day 8–9: write full scenario answers for 2–3 cases (timed)
- Day 10: focus on weak areas found in practice
- Day 11–12: do additional quantitative practice (critical path or EVM style)
- Day 13: review governance, procurement/contract control (if included), closure and lessons learned
- Day 14: rapid revision of frameworks and a final timed full scenario attempt
The key is to build speed without losing accuracy.
Suggested Reference Framework (Quick Use)
Use this consistent exam structure across questions:
- Identify the issue(s) in the scenario
- Select relevant knowledge areas
- Apply a process (steps)
- Justify with reasoning
- Control with governance, monitoring, and communication
- Conclude with expected outcome and lesson alignment
Closing Notes
Mastering Advanced Diploma in Project Management (90009) requires more than memorising concepts. Your goal in exams is to show integrated, defensible project management thinking: how planning becomes execution, how monitoring controls performance, and how governance manages change, risks, and stakeholder expectations. With structured scenario practice, disciplined calculation methods, and consistent communication-and-control logic, you can produce answers that align with South African university exam marking expectations and demonstrate real advanced competence.
