Specialised Project Management Certificate Study Guide (Wits Plus) — Exam Notes for Wits University Short Courses & UNISA-Style Techniques

Specialised Project Management certificates sit between general project management fundamentals and advanced, industry-focused applications. They typically test your ability to apply the same core PM logic—scope, schedule, budget, risk, quality, procurement, governance—while tailoring it to a specific context such as construction, IT, healthcare, or infrastructure delivery. This study guide is written for South African students preparing for short/specialised project management certificates, using a Wits Plus (Wits University Project Management Short & Specialised Courses Notes) lens and exam-friendly techniques similar to what you see in UNISA (e.g., MNG/Project-Management related modules) and other local university offerings.

1) Specialised Project Management Foundations: What the Certificate Tests (and How to Answer Like an Exam Winner) — Wits Plus Core + UNISA-Style Applied Learning

Specialised project management certificates usually assume you already know the basics. The assessment focus shifts to application: scenario analysis, governance, integrated planning, and risk/quality/procurement decisions that make or break delivery. In South African marking schemes, exam questions often reward structured answers: define → apply → justify → reference tools → conclude.

1.1 The “Specialised” Difference: From PM Basics to Context-Driven Delivery

A general PM course might ask you to “explain” a concept. A specialised certificate often asks you to do something like:

• Given a project with changing stakeholder needs, propose a change control process and explain how you would manage approvals.
• Given a schedule slippage and cost pressure, re-baseline logically (and ethically) and justify what you would communicate.
• Given high regulatory requirements (e.g., safety/environmental compliance), build a quality and risk approach that integrates compliance checks.
• Given procurement constraints, select contracting/procurement strategies and explain how procurement affects schedule and risk.

To answer correctly, you should consistently demonstrate competence in the following “exam core” pillars:

1. Scope clarity (requirements, deliverables, acceptance criteria)
2. Time control (work breakdown structure, critical path reasoning, milestone planning)
3. Cost control (budgeting, cost baseline, earned value fundamentals where appropriate)
4. Risk & uncertainty management (risk registers, response planning, monitoring triggers)
5. Quality & compliance (quality plans, assurance vs control, audit/inspection logic)
6. Stakeholder & governance (roles, reporting lines, decision rights)
7. Procurement & contract interface (what you can control vs what contractors influence)
8. Communication planning (cadence, templates, escalation paths)

Even when the certificate is niche—say, construction, IT, or infrastructure—the exam usually checks whether you can connect tools to outcomes rather than list definitions.

1.2 How Wits-Style Short Course Assessments Are Marked (Typical Pattern)

Wits short/specialised certificates often grade in ways that mirror practical problem-solving:

• Marks are gained for relevance: the tool you propose must fit the scenario.
• Marks are lost for generic answers: “use a risk register” is insufficient without showing how and why.
• Marks are awarded for structure: bullet points and stepwise logic help.
• Marks are tested via “trade-offs”: e.g., faster schedule may increase cost and risk; your answer should acknowledge both.

Use this repeatable exam template:

1. Interpret the scenario (1–2 sentences)
2. State the decision you must make (what needs to be controlled/approved)
3. Name the tool/process (e.g., WBS, risk register, RACI, baseline)
4. Apply it to the facts (numbers, dates, stakeholders, constraints)
5. Justify the choice (why this is better than alternatives)
6. Conclude with next steps (who does what, by when)

1.3 UNISA-Style “Applied Explanation” Techniques You Should Copy

While Wits and UNISA differ, many South African students notice similar exam expectations: you must demonstrate understanding through applied reasoning. In UNISA project-management-related modules, you often see:

• Case-based questions
• “Explain and motivate” phrasing
• Short-answer marking that expects key points rather than essays

Adopt these habits:

• Use active voice: “I would” is acceptable in some contexts, but keep it professional (“The project manager would”).
• Use pairing: “assurance vs control,” “baseline vs re-baseline,” “risk vs issue.”
• Use linking phrases: “therefore,” “because,” “so that,” “as a result,” which makes reasoning visible.

1.4 Key Definitions That Commonly Appear in Specialised PM Certificates

These definitions are repeatedly tested; exam questions often hide them inside scenario language.

• Baseline: approved plan for scope/schedule/cost used for comparison.
• Re-baseline: formal update of baseline after approved changes; must be justified (otherwise it becomes “moving the goalposts”).
• Change control: process to assess impact of changes and obtain approvals.
• Risk vs issue:
  • Risk = uncertain event that may occur.
  • Issue = event that has occurred and needs action immediately.
• Quality assurance (QA): process to ensure quality planning and adherence.
• Quality control (QC): testing/inspection to verify deliverables meet requirements.
• Earned Value (if tested): performance measurement comparing planned value, earned value, and actual cost.

1.5 Mini-Case: How Marks Are Won (and Lost)

Scenario: A specialised project is implementing a new inventory system. Midway, users request extra reporting features that were not in the original scope. The vendor says delivery will still meet dates if the project team “just prioritises reporting and cuts testing.”

What you must show:

• You understand scope governance and change control.
• You can assess schedule/cost/risk/quality impacts.
• You can explain what you would do to avoid cutting testing.

A strong exam answer outline:

1. Recognise the request as a change (not “business as usual”).
2. Trigger change control: impact analysis on scope, schedule, cost, and quality.
3. Protect quality: testing cannot simply be removed; instead, propose options (e.g., phase reports, adjust test scope, extend schedule if necessary).
4. Escalate to steering/approval authority with a recommendation.
5. Update baselines only after approvals.

A weak answer would only say: “Manage scope changes using change control.” That may get partial marks but likely fails the “applied” requirement.

2) Integrated Planning & Governance for Specialised Delivery: Scope, Schedule, Cost, Quality, and Risk Together — Wits Plus + Infrastructure/IT Case Logic

Specialised certificates test whether you can integrate multiple knowledge areas. Many students treat scope, schedule, risk, and quality separately. Examiners want to see interdependencies: how a risk response changes schedule, how scope changes affect cost and quality, and how governance decides when baselines move.

2.1 Building the Integrated Project Plan: The Exam-Expected Logic

A typical specialised certificate question may present:

• A high-level project goal (e.g., reduce processing time, deliver a facility on a fixed date, implement a system for compliance)
• Constraints (budget ceiling, staffing limits, procurement lead times)
• Stakeholders (client, supplier, regulators, internal users)
• Risks (e.g., supplier delays, regulatory approvals, technical uncertainty)

To answer, present an integrated plan. The key is to show sequence.

Stepwise approach you can use in exam responses

1. Define deliverables and acceptance criteria
   • What exactly is “done”?
   • Who signs off and on what evidence?
2. Create a Work Breakdown Structure (WBS) aligned to deliverables
   • WBS is your “bridge” from scope to schedule.
3. Estimate effort and sequence activities
   • Identify dependencies (which tasks cannot start until others finish).
4. Develop a schedule with milestones
   • Milestones act as governance checkpoints.
5. Allocate resources and cost
   • Include internal labour and external vendor costs.
6. Create a risk register tied to schedule & cost
   • Each risk should influence a specific area.
7. Create a quality plan
   • QA activities prevent defects; QC activities verify compliance.
8. Define governance & reporting
   • Decision points, reporting cadence, escalation rules.

A good answer explicitly links items. For example: “Because procurement has a 6-week lead time, I build schedule milestones to allow early vendor selection; that also reduces schedule risk.”

2.2 Governance Structures That Appear in Specialised Certificates

Governance is often tested through roles and decision rights:

• Project Sponsor: authorises investment and resolves high-level escalation.
• Steering Committee / Executive Committee: approves major changes, ensures strategic alignment.
• Project Manager: accountable for delivery within constraints.
• Functional Leads (IT, Engineering, Procurement, Quality): responsible for specialist work.
• Supplier / Contractor: executes contracted scope under agreed KPIs/SLAs.

RACI (common in exams)

Use RACI for decision clarity:

• R (Responsible): does the work
• A (Accountable): final sign-off
• C (Consulted): input
• I (Informed): kept updated

Example use in an exam scenario:

• Change request for scope expansion
  • Project Manager: R
  • Sponsor: A for final approval
  • Quality Lead: C to assess compliance impacts
  • Users/Operations: C to confirm requirement value
  • Finance: C for budget impact
  • Steering Committee: I unless thresholds are exceeded

If the question asks “who approves,” you should show the approval authority and escalation triggers.

2.3 Schedule Planning With Realistic Constraints

Specialised projects often include constraints like:

• procurement lead times,
• regulatory approvals,
• resource bottlenecks,
• commissioning/hand-over windows.

To score well, do not rely on “best-case” thinking. Instead, show buffering logic:

• Early procurement: reduce schedule risk.
• Milestone-based governance: detect slippage early.
• Critical path identification (if discussed in the certificate content): focus risk responses on the critical chain.

Example schedule logic (with numbers)

Assume:

• Project duration target: 12 weeks
• Procurement lead time: 6 weeks
• Implementation duration: 4 weeks
• Testing and commissioning: 2 weeks
• Total: 12 weeks (fits exactly)

Now consider a procurement delay risk:

• Risk probability: 40%
• Impact: +1 week delay to procurement start

If procurement slips by 1 week, the schedule becomes 13 weeks unless corrective action occurs.

In an exam response, you could propose:

• Start procurement immediately and freeze requirements early.
• Use a vendor selection sprint and standardise procurement documentation.
• If delay occurs, negotiate contract terms for expediting or adjust downstream resources.

You should explicitly connect the risk to schedule outcomes.

2.4 Cost Planning and Trade-offs: “Cheaper Now, Expensive Later”

Specialised certificate questions often include cost pressure. Examiners want you to avoid simplistic “cut everything” thinking.

Cost structure example

Suppose a project has:

• Labour (internal): R 900,000
• Vendor development/implementation: R 1,200,000
• Testing tools and external QA support: R 300,000
• Contingency: R 300,000
  Total budget: R 2,700,000

Now the sponsor asks to reduce cost by R 200,000. If you cut external QA support, you risk:

• rework,
• defects,
• non-compliance,
• re-testing costs,
• schedule slips.

An exam-ready approach is:

1. Identify where savings are possible with minimal risk to quality.
2. Propose alternatives:
   • reduce the number of test cycles but strengthen targeted testing,
   • adjust QA scope to focus on the highest-risk components,
   • defer non-critical features (change control),
   • renegotiate vendor terms with penalty/bonus clauses.

You must show you considered risk/quality impacts, not just budget arithmetic.

2.5 Quality Management: QA vs QC and Acceptance Evidence

Quality in specialised PM is often compliance-heavy (safety, health, data protection, standards). A certificate exam can ask: “How do you ensure deliverables meet standards?”

Use this framework:

• QA (assurance): build the system/processes that produce quality.
  • Example QA: compliance checklists, process audits, training, documentation standards.
• QC (control): verify deliverables meet requirements.
  • Example QC: inspections, tests, user acceptance testing, document review.

Then link quality to governance:

• Deliverables should have acceptance criteria:
  • performance requirements,
  • compliance documents,
  • sign-off procedures.

A strong answer will mention evidence:

• test reports,
• inspection certificates,
• sign-off sheets,
• audit trails.

2.6 Risk Management Integrated With Delivery

Many students treat risk registers as “lists.” Specialised certificate questions reward risk thinking tied to decisions and schedule/cost.

Risk response options

For each risk:

• Avoid (change plan to eliminate risk)
• Mitigate (reduce probability/impact)
• Transfer (shift impact via contract/insurance)
• Accept (acknowledge risk; monitor; have contingency)

Example: turning a risk into a plan

Risk: Regulatory approval may take longer than expected.

• Probability: 30%
• Impact: +2 weeks delay
• Response: mitigate by early submission and pre-consultation with the regulator; prepare compliance documentation pack.

Governance link:

• Define a milestone “Regulatory submission completed” by Week 2.
• Add a review gate “Regulatory feedback received” at Week 4.

This shows how risk management influences schedule and governance.

2.7 Case Mini-Study: IT Implementation Under Compliance Pressure

Scenario (exam-style): A public-sector department must implement a digital workflow system compliant with internal governance and data handling requirements. The department requires pilot testing in a restricted environment. The supplier proposes to start training while configuration is still changing to save time.

Integrated plan points to include:

• Scope: what features are pilot-ready?
• Schedule: configuration stability required for pilot.
• Quality: compliance checks before pilot.
• Risk: training on changing configuration causes rework and user confusion.
• Governance: steering committee to approve pilot scope and sign-off.

A high-scoring answer would recommend:

1. Define pilot scope (deliverables and acceptance criteria).
2. Establish configuration freeze date for pilot environment.
3. QA plan: run compliance checks pre-pilot.
4. Training only after configuration sign-off for pilot.
5. Change control for post-pilot enhancements.

3) Advanced Specialised Techniques: Contract/Procurement Strategy, Stakeholder Complexity, and Risk/Quality Deep-Dives — Wits Plus + Realistic South African Delivery Scenarios

In specialised project management certificates, questions often shift from “planning” to “managing complexity.” Two major complexity engines are procurement/contracting and stakeholder dynamics—both influence schedule, cost, and risk outcomes.

3.1 Procurement Strategy: How Contracts Change Your Risk Profile

Procurement is not just buying goods; it is a risk allocation mechanism. Exams commonly test whether you can choose procurement/contract approaches based on uncertainty and performance needs.

Common procurement/contract types (conceptual)

• Fixed-price: clearer cost, but risks transferred to contractor; disputes can occur when requirements change.
• Time & materials (T&M): contractor billable time and materials; more flexible when scope uncertain, but budget control is harder.
• Design-build: contractor responsible for design and build; can reduce interface risk.
• Performance-based contracting: payment linked to outcomes/SLAs.

In exam scenarios:

• If requirements are uncertain and likely to change, fixed-price can increase delivery risk.
• If performance requirements can be measured and monitored, performance-based can align incentives.
• If schedule is critical and the contractor can bring capacity, design-build or early contractor involvement may reduce lead time.

3.2 Interface Management: Where Projects Actually Break

Specialised project delivery often fails at interfaces:

• Between procurement and delivery teams
• Between design and construction
• Between IT configuration and business process readiness
• Between quality and acceptance testing

Exam answers should identify interface failure modes and propose controls:

• Interface meetings (weekly cadence)
• Integrated change control (ensures procurement changes follow scope changes)
• Document/version control for specifications and requirements
• Clear acceptance evidence and handover procedures

3.3 Procurement Lead Time Planning With Governance Gates

You can earn marks by using lead-time logic.

Example:

• Supplier selection must happen by Week 2 to meet delivery.
• Contract signing must complete by Week 3.
• Delivery of key equipment occurs after Week 8.
• Commissioning occurs Weeks 10–11.
• Final sign-off occurs Week 12.

If procurement selection delays by one week, the commissioning window may be missed. In an exam response, you should propose:

• Procurement “rolling readiness” (pre-qualification, draft contracts ready)
• Early requirements confirmation (freeze specs)
• Contractual acceleration options (expedite clause)
• Resource allocation in parallel where possible

3.4 Stakeholder Management Beyond “Communication Plan”

Specialised certificates often test stakeholder conflict and power dynamics. Communication is necessary but not sufficient; you must manage decision-making and expectations.

Stakeholder mapping approach (exam-friendly)

Use three dimensions:

• Power (influence on approvals/resources)
• Interest (how much they care)
• Attitude (supportive, neutral, resistant)

Then propose tailored engagement:

• High power / high interest: formal governance engagement and frequent reporting
• High power / low interest: targeted updates, ensure no surprises
• Low power / high interest: training, frequent consultation
• Low power / low interest: minimal updates

3.5 Managing Resistance: A Practical Model for Exam Answers

Resistance often comes from:

• fear of job impact,
• mistrust of vendors,
• poor visibility,
• unclear acceptance criteria,
• past project failures.

In an exam scenario, propose:

• early co-design workshops (align expectations),
• transparent baselining (“these features are in; these are out”),
• change control transparency (why changes are approved/declined),
• quick wins to build confidence (pilot success measures),
• escalation protocols for unresolved concerns.

Counter-argument you should address

A common incorrect assumption is: “If stakeholders disagree, the project manager just enforces the plan.” In specialised contexts, that is risky. Instead:

• enforce baselines while using governance to adjust them when necessary,
• separate “must-have” compliance requirements from “nice-to-have” options,
• use impact analysis to show what trade-offs decision-makers are choosing.

3.6 Risk Deep-Dive: From Risk Register to Monitoring Triggers

Risk management in specialised certificates is not only planning; it’s monitoring and triggering responses. Examiners like “if-then” statements.

Example risk:

• Risk: data migration errors.
• Trigger: error rate exceeds 1.5% during test migration.
• Response: pause migration, fix mapping logic, re-run migration tests, update schedule if necessary.

This transforms risk from theory into operational control.

Risk categories you can include (to show breadth)

• Technical risks (integration failure, performance shortfall)
• Schedule risks (vendor delay, dependency slippage)
• Cost risks (scope creep, rework)
• Compliance risks (regulatory nonconformance)
• People/operational risks (training readiness, change adoption)
• Safety/health risks (construction/field work)
• Stakeholder risks (approval delays, political constraints)

3.7 Quality Deep-Dive: Audit Trails and Compliance Evidence

Specialised projects require evidence quality, not just deliverable quality. If a regulator or internal audit checks documentation, the project must deliver traceable proof.

Include:

• Document control:
  • versioning,
  • approval logs,
  • traceability matrix linking requirements to test results.
• Audit readiness:
  • ensure QA checklists are completed,
  • store inspection records,
  • document corrective actions.

Mini-case: Construction compliance

Even without naming a specific construction company, an exam scenario may include:

• safety compliance requirement,
• contractor subcontractors,
• inspection cycles,
• penalty clauses for noncompliance.

Answer should include:

• quality plan with inspection points,
• QA audits,
• reporting to sponsor/steering committee,
• corrective action process for nonconformities.

3.8 Worked Example: Change Request Decision With Trade-offs

Scenario: After procurement, the client requests a design modification. The supplier says it will add R 120,000 and +3 weeks. The sponsor wants to approve it immediately to “avoid client dissatisfaction.”

Your exam response should:

1. Call it a formal change request.
2. Assess scope impact: what deliverable changes?
3. Assess schedule impact: how it affects milestones.
4. Assess cost impact: R 120,000 addition.
5. Assess quality impact: does modification affect compliance?
6. Assess risk impact: increased complexity may increase rework probability.

Then propose decision options:

• Option A (approve now): accept +3 weeks, add budget R 120,000, update baselines via governance.
• Option B (approve with phased delivery): keep original core schedule; deliver modification in later phase; use acceptance criteria to maintain benefit.
• Option C (decline): offer alternative such as a workaround.

Finally:

• recommend which option is best and justify with risk/quality governance.

Even if the certificate isn’t “math heavy,” this shows structured decision reasoning, which is where most marks live.

4) Earned Value, Performance Measurement, and Reporting That Reflects Specialist Realities — Wits Plus + Exam-Ready Calculations & Narratives

Many specialised PM certificates include performance measurement concepts because real stakeholders demand visibility. Even when full earned value calculations are not required, exams often test your ability to interpret schedule/cost performance indicators and communicate implications.

4.1 Why Performance Measurement Matters in Specialised Projects

Specialised projects often have:

• long vendor lead times,
• complex integration,
• regulatory/compliance gating,
• high consequence of rework.

Performance measurement helps answer:

• Are we on track, and if not, why?
• Will current decisions improve outcomes or increase risk?
• What should the sponsor/stakeholders do next?

Exams reward both quantitative accuracy and qualitative interpretation.

4.2 Performance Indicators: Concepts You Should Expect

Common indicators include:

• Schedule variance (SV) and schedule performance (qualitative interpretation)
• Cost variance (CV) and cost performance
• SPI/CPI (if earned value is covered in the certificate)
• Forecast at completion (EAC) and estimate vs baseline
• Milestone trend reporting: on-time/at-risk/behind

If the certificate is not heavy on formulas, you still should:

• know what the indicators mean,
• interpret them in plain language,
• recommend corrective actions.

4.3 Earned Value Example (Numerical Consistency Required in Exams)

Assume a specialised IT project has:

• Planned Value (PV) at reporting date = R 1,000,000
• Earned Value (EV) at reporting date = R 850,000
• Actual Cost (AC) at reporting date = R 920,000

Then:

• Cost Variance (CV) = EV − AC = R 850,000 − R 920,000 = −R 70,000
  • Interpretation: you are spending more than the value earned.
• Schedule Variance (SV) = EV − PV = R 850,000 − R 1,000,000 = −R 150,000
  • Interpretation: you are behind schedule (earning less value than planned).

If CPI and SPI are used:

• CPI = EV / AC = 850,000 / 920,000 ≈ 0.93
  • cost efficiency below 1.
• SPI = EV / PV = 850,000 / 1,000,000 = 0.85
  • schedule efficiency below 1.

A strong exam answer doesn’t stop at numbers. It then asks:

• What caused the variance?
• Is it due to scope change, vendor delay, rework, or testing issues?
• What corrective action will reduce the variance?

4.4 Forecasting and Corrective Actions (How to Get “Application Marks”)

Corrective actions might include:

• re-sequencing tasks to reduce schedule impact,
• tightening requirements to reduce rework,
• adding resources if feasible (and if budget allows),
• negotiating vendor recovery plans,
• adjusting test plan with risk-managed scope.

Examiners like action plans with accountability:

• “The procurement lead will…”
• “The quality lead will…”
• “The project manager will escalate by…”.

4.5 Reporting Cadence and Content: What Sponsors Actually Need

Specialised certificate exams often include “prepare a report” style questions. Your answer should include:

• status summary (traffic-light)
• key achievements since last report
• progress vs baseline (schedule/cost)
• top risks and top issues
• change requests and approvals status
• decisions needed from sponsor/steering committee

Traffic-light interpretation

• Green: on track; no major risks needing decisions.
• Amber: some variances; managed but require attention.
• Red: off track; require sponsor decisions or escalations.

In your narrative, make sure “amber” or “red” is justified by:

• a variance measure,
• a risk probability/impact,
• a milestone slip.

4.6 Issue Management: Don’t Confuse Issues With Risks

A subtle exam trap is mixing language:

• Risks are uncertain and require mitigation planning.
• Issues are real and require immediate corrective action.

Exam-friendly way to correct:

• “This is an issue because regulatory feedback was not received by Week 4, causing an actual delay. Therefore we need corrective actions and schedule update.”

Then show response:

• corrective actions,
• updated timeline,
• communication and escalation.

4.7 Linking Performance to Quality and Compliance

In specialised projects, cost/schedule performance may look “okay,” but quality/compliance could be failing. Your reporting must include quality status.

Example:

• Schedule says milestones are met.
• But QC testing shows 12% defect rate beyond acceptable thresholds.
• That should drive amber/red despite schedule alignment.

Therefore, your reporting logic must include:

• quality metrics,
• compliance checks status,
• corrective action progress.

4.8 Mini-Case: Performance Variance Caused by Quality Rework

Scenario: EV is behind PV; CV is negative. Root cause is that earlier configuration did not meet integration requirements, causing rework during testing.

Your exam response should:

1. identify variance as symptoms,
2. diagnose cause: rework due to requirements mismatch,
3. propose corrective actions:
   • strengthen QA gates at configuration stage,
   • update traceability matrix,
   • implement additional integration testing earlier,
4. update schedule forecast due to rework reduction.

This demonstrates “root cause to corrective action” reasoning.

5) Exam-Ready Practice: Full Scenario Walkthroughs, Frameworks, and “What to Say” Answers — Wits Plus + UNISA-Style Question Responses

This final section is built to help you convert frameworks into exam responses. It provides scenario walkthroughs with structured outputs, plus mini “model answers” showing what examiners reward—without needing extra facts. The goal is to rehearse a mental process you can apply in any specialised project management certificate exam.

5.1 The Universal Scenario Answer Structure (Use This Every Time)

When the question provides a scenario, your response should typically include:

1. Identify the problem(s) (scope change, schedule delay, risk, governance failure)
2. Choose the correct control system
   • change control,
   • risk management,
   • quality management,
   • procurement governance,
   • reporting/escalation
3. Apply to facts
   • mention constraints, deadlines, parties, impacts
4. Provide a decision path
   • who approves, who executes, what evidence is used
5. Give next steps with timeline
   • “within 5 working days,” “by Week 2,” etc.

5.2 Scenario Walkthrough 1: Scope Creep in a Compliance-Focused Project

Scenario: A specialised compliance project must deliver four reports to meet internal audit requirements. After Week 4, stakeholders request additional fields in two reports. Quality indicates that changes will affect data validation rules. The sponsor asks the project manager to “just do it quickly” to meet the Week 12 deadline.

Your task: Describe how you would manage the change and protect compliance.

Model answer elements (what to include)

• Recognise change request as scope change requiring formal control.
• Create an impact assessment covering:
  • scope (new data fields),
  • schedule (testing impact),
  • cost (additional configuration and testing time),
  • quality/compliance (data validation rules and acceptance evidence).
• Establish governance:
  • Project manager prepares a change impact report.
  • Quality lead confirms compliance impacts and approval prerequisites.
  • Sponsor decides to approve/decline or phase the changes.

Concrete decision options you can propose

1. Phased delivery:
   • deliver original reports by Week 12 with agreed minimum compliance set,
   • deliver additional fields in Phase 2 with new acceptance criteria.
2. Baseline update:
   • if sponsor approves additional scope, update schedule/cost baselines after approval.
3. Alternative requirements management:
   • propose different reporting approach that achieves audit objectives without new fields.

Why this is the “exam-winning” logic

Because it balances:

• deadline pressure,
• compliance obligations,
• realistic quality assurance needs.

5.3 Scenario Walkthrough 2: Procurement Delay and Schedule Recovery Plan

Scenario: Procurement lead time for a key component is 6 weeks. Due to supplier mobilisation delays, procurement is now expected to deliver one week late. The project schedule is fixed at 12 weeks with commissioning in Weeks 10–11.

Your task: Propose recovery actions and describe governance communication.

What to include in your answer

• Identify schedule impact:
  • If procurement slips by 1 week, commissioning windows are threatened.
• Assess options:
  1. Accelerate procurement recovery (supplier expedite clause, alternative logistics).
  2. Re-sequence activities (perform tasks not dependent on the component earlier).
  3. Resource reallocation (increase internal testing capacity to keep within Weeks 10–11).
  4. Re-baseline if required (if recovery fails, propose updated schedule with sponsor approval).
• Risk response:
  • Treat as a risk if still uncertain; treat as an issue if confirmed delivery date has changed.
• Reporting:
  • Provide a schedule recovery dashboard to steering committee,
  • highlight decisions needed (approve additional budget for acceleration, approve re-sequencing plan).

Concrete “if-then” triggers (good for marks)

• If component delivery confirmation is not received by a specific milestone (e.g., within 5 working days), implement a contingency test plan that uses mock/testing alternatives.

Even if you don’t know exact exam marking points, this demonstrates control thinking rather than vague advice.

5.4 Scenario Walkthrough 3: Earned Value Variance With Quality Root Cause

Scenario: At the reporting date:

• PV = R 1,000,000
• EV = R 850,000
• AC = R 920,000

Testing indicates a high defect rate due to configuration mismatch; rework has begun. The sponsor wants to know whether the project is still salvageable by the target date.

Your task: Interpret EV/CV and propose corrective actions linked to quality.

What to write

• Calculate variances:
  • CV = EV − AC = −R 70,000
  • SV = EV − PV = −R 150,000
• Interpret:
  • spending is high relative to earned progress,
  • schedule progress is behind plan.
• Diagnose:
  • root cause is quality failure/rework due to configuration mismatch.
• Corrective actions:
  1. strengthen QA gates earlier (before full integration testing),
  2. rework traceability to ensure requirements map to configuration settings,
  3. adjust testing strategy (risk-based testing to quickly isolate defects),
  4. communicate recovery timeline and request sponsor decisions on any budget needed for additional testing resources.

This is how you turn “numbers” into “management decisions.”

5.5 Scenario Walkthrough 4: Stakeholder Resistance and Decision Rights

Scenario: End-users resist adopting a new workflow system. They argue the training sessions are too short and say the system is “not what they asked for.” Project reports show milestones are on schedule, but user adoption metrics are poor.

Your task: Provide a stakeholder engagement and adoption improvement plan.

What to include

• Clarify what is wrong:
  • schedule delivery isn’t the same as adoption/benefit realisation.
• Stakeholder engagement:
  • organise user workshops to confirm requirements,
  • revise training plan length and format,
  • include user champions and feedback loops.
• Governance:
  • define acceptance criteria that include usability/adoption measures,
  • decide whether changes require formal change control.
• Quality:
  • implement usability testing and acceptance sign-off based on evidence (e.g., task completion rates, error rates).
• Reporting:
  • report adoption metrics rather than only milestone completion.

This answers the deeper question: specialised PM cares about “delivery outcomes,” not only “task completion.”

5.6 Exam Practice Prompts (Answer Frameworks You Can Memorise)

Below are prompts that reflect how specialised certificates often write questions. For each, use the universal structure.

Prompt A: Risk Register and Response Plan

• “Identify at least five risks and propose responses. Justify your approach.”
  Framework: list risk → estimate probability/impact (even qualitative) → response option (avoid/mitigate/transfer/accept) → owner → trigger → timeline.

Prompt B: Quality Plan vs Testing Only

• “Explain how you ensure quality in a regulated project.”
  Framework: define QA vs QC → QA activities → QC activities → acceptance criteria → evidence and audit trail → corrective action loop.

Prompt C: Change Control Under Time Pressure

• “A change request threatens the deadline. What do you do?”
  Framework: impact assessment → options (phase/decline/baseline update) → governance approval → update baselines and communication plan.

Prompt D: Procurement Strategy Choice

• “Procurement uncertainty exists; choose contract type and justify.”
  Framework: link uncertainty to contract risk allocation → justify incentives → describe how you manage contractor performance and acceptance.

5.7 Common Marking-Point Mistakes (Avoid These)

Specialised PM certificates often mark harshly for the following:

• Too generic: naming tools without connecting to facts.
• Confusing risk and issue: proposing “risk mitigation” when it’s already an issue.
• No evidence: describing approval without saying what evidence is used to approve.
• Quality as an afterthought: reporting schedule progress without checking compliance/defect impacts.
• Skipping governance: failing to mention who decides, who approves, and how escalation works.
• No trade-offs: ignoring cost/schedule/quality interplay.

5.8 “What to Say” Short Answer Bank (Exam Language That Scores)

Use these phrases and concepts, adapted to your scenario:

• “This represents a scope change and requires formal change control.”
• “The impact assessment must cover schedule, cost, quality/compliance, and risk.”
• “Quality assurance activities will be performed to prevent rework; quality control will verify deliverables using agreed acceptance criteria.”
• “The delay shifts the project into an at-risk schedule status; we will escalate to the steering committee and request decisions on recovery options.”
• “Variances in schedule and cost indicate that corrective actions are required; we will perform root-cause analysis and adjust the plan accordingly.”
• “User adoption is a project outcome; therefore acceptance criteria must include usability and operational readiness evidence.”

These “exam language” moves don’t replace understanding—they demonstrate it clearly.

5.9 Consolidated Study Checklist (Use as Last-Week Revision)

Know how to apply

• WBS → schedule logic
• Change control → approvals → baseline updates
• Risk register → triggers → response plans
• Quality plan → QA/QC → evidence → corrective actions
• Procurement strategy → risk allocation → acceptance and performance monitoring
• Performance measurement → interpret variances → corrective actions
• Stakeholder mapping → engagement → decision rights

Practise writing answers that include

• stakeholder roles (who decides/executions)
• governance gates (what happens when milestones are missed)
• evidence and acceptance criteria
• trade-offs (schedule vs cost vs quality)

Closing Integration: How All Sections Fit Together

Specialised project management certificates ultimately test whether you can manage the whole delivery system, not just individual processes. Integrated planning links scope to schedule and cost; governance links decisions to accountability; procurement links contracts to risk outcomes; performance measurement links progress data to corrective actions; and quality/risk deep-dives protect compliance and reduce rework. Mastering these connections—and rehearsing structured scenario answers—is the fastest path to consistently strong marks in Wits Plus and South African university-style applied assessments.