Wits School of Governance Project Management Exam Packs

Project management is a core capability across public sector delivery, NGOs, consulting, and corporate operations—and at Wits University’s School of Governance (Wits SoG) it is taught with a strong governance lens. This study guide consolidates what you need to prepare for Wits School of Governance Project Management Exam Packs, including the kind of frameworks, exam-style reasoning, and practical application questions that commonly appear in short and specialised course assessments.

The guide also aligns learning language to what students in South Africa search for and study in formal programmes, including modules that map closely to themes found in Unisa, CUT, and other local qualifications. You will see recurring exam pack themes: scope and stakeholder management, risk and procurement thinking, schedule and cost control, and monitoring & evaluation—all organised into coherent, exam-ready clusters.

Wits Plus Exam Packs Focus: Project Management Foundations, Governance, and Exam Strategy (Wits University – School of Governance)

Wits School of Governance project management content typically blends standard project management approaches (like the PMBOK®-style process mindset) with the governance realities of public interest work: accountability, transparency, compliance, stakeholder legitimacy, and decision-making under constraints. When exam papers are built from “project management exam packs,” questions often test not only definitions but also the ability to choose the best tool for a given scenario and justify decisions.

1) What the “exam pack” usually expects: definitions + applied selection

In practical exam questions, you are rarely asked to repeat terminology without context. Instead, you’re asked to match a problem description to the best process or best artefact.

Common exam patterns include:

• Scenario-based: “The project is behind schedule; what should the project manager do next?”
• Governance-based: “A stakeholder group challenges procurement fairness; which governance step should be applied?”
• Trade-off questions: “Scope creep is happening; how do you respond while protecting the project objectives?”
• Quant reasoning: “Given schedule/cost variances, interpret performance and recommend actions.”
• Risk logic: “New regulations increase delivery risk; what risk responses are suitable?”

A strong exam response typically includes:

1. A correct identification of the relevant concept/process.
2. A brief explanation of why it fits.
3. The next action (what you would do operationally).
4. A governance or stakeholder implication (especially at Wits SoG).

2) Core terminology you must distinguish clearly

Many marks are lost when students blur similar concepts. Pay attention to these distinctions (they appear repeatedly in exam packs):

Scope vs. requirements vs. deliverables

• Scope: What work is included/excluded to achieve project objectives.
• Requirements: What the client/stakeholders need (often derived from needs and constraints).
• Deliverables: Tangible outputs produced by completing work packages.

Exam-style scenario: A community office says “we need more documents for the same service.”

• This sounds like a requirements expansion, which often becomes scope creep unless formally managed through change control.

Project vs. programme vs. portfolio

• Project: Temporary endeavour with defined outputs/outcomes.
• Programme: A group of related projects managed together to realise benefits.
• Portfolio: A set of projects/programmes managed to align with strategy.

Exam advantage: Even if the question looks like “project,” you can mention programme/portfolio alignment when discussing governance and prioritisation.

Stakeholders vs. beneficiaries vs. users

• Stakeholders: Those who influence or are influenced by the project.
• Beneficiaries: Those who gain from outcomes.
• Users: Those who use deliverables.

Exam pack angle: Governance questions often demand a stakeholder map and engagement plan, not just a generic list.

3) A governance lens: why Wits SoG emphasises “accountability in delivery”

In Wits School of Governance learning approaches, projects are not treated as isolated technical activities. They are treated as mechanisms for delivering public value. That means exam questions may include governance elements like:

• decision rights (who approves what),
• auditability (how decisions are recorded),
• ethical procurement,
• compliance with policy frameworks,
• transparency to affected stakeholders.

When answering, you can strengthen your response by adding governance language such as:

• “This decision should be escalated through the approved change control board (CCB).”
• “Engagement should follow a documented stakeholder communication plan.”
• “Procurement must align with fairness, competitiveness, and compliance criteria.”

Even if the question doesn’t explicitly ask for governance, Wits-style papers often reward it.

4) Exam-ready project lifecycle: from initiation to closure

A typical project management lifecycle you can use in your answers:

1. Initiation: Define purpose, feasibility, mandate, preliminary stakeholder identification.
2. Planning: Build scope baseline, schedule, cost baseline, risk register, stakeholder engagement plan, procurement plan.
3. Execution: Coordinate people/resources; implement procurement; deliver work.
4. Monitoring & controlling: Track performance, manage changes, address risks, report status.
5. Closing: Validate outputs, obtain acceptance, release resources, capture lessons learned.

Exam tip: If a scenario describes something happening “already,” then you’re probably in execution/controlling. If it describes “before work begins,” it’s initiation/planning.

5) How to write exam answers that maximise marks

Many learners focus only on “correct content.” Exam packs also reward structure. A high-scoring answer often uses a repeatable template:

1. Identify the problem and relevant PM concept.
2. Justify the choice using scenario evidence.
3. Specify the action plan (steps).
4. Address governance/stakeholders and controls.
5. Conclude with outcome expected.

Mini-example (how a 6–8 mark answer is often built)

• Identify: “This is scope creep and change control failure.”
• Justify: “New activities are being added without formal approval.”
• Action:
  • “Stop work on unauthorised additions.”
  • “Log change requests with impacts on time/cost/scope.”
  • “Assess impacts and decide through CCB.”
  • “Update baseline and communicate changes.”
• Governance: “Ensure audit trail and approvals documented.”
• Conclude: “Protect scope baseline and project objectives.”

6) Links to South African course language students recognise (Unisa/CUT-style alignment)

South African students often come from backgrounds where exam questions reflect module structures and competence areas in the Public Administration / Project Management / Development ecosystem.

Even when the exact Wits course code differs, the skill themes map strongly to areas seen in:

• Unisa qualifications such as Project Management-related modules (where students must apply frameworks to planning, monitoring, and risk).
• Central University of Technology (CUT) offerings that emphasise practical project execution and management of delivery constraints.
• Broad public sector governance competence common across SA universities.

That’s why this guide uses the kind of language you’ll recognise: deliverables, baselines, variances, risk registers, stakeholder engagement, procurement governance, and M&E logic.

7) Typical exam-pack question types and what they test

You should practice recognising question types:

1. Process matching: “Which process/tool should be used?”
2. Best-next-action: “What do you do next?”
3. Interpretation of performance: “What do CPI/SPI-like metrics imply?” (Even if the exam doesn’t use acronyms, it may ask you to interpret cost/schedule impacts.)
4. Stakeholder analysis: “Who should be involved and how?”
5. Risk response planning: “Transfer/mitigate/avoid/accept; justify.”
6. Monitoring & evaluation: “How do you measure progress and outcomes?”
7. Procurement ethics/compliance: “How do you ensure fairness and quality?”

Wits Plus Exam Packs: Scope, Stakeholder, and Risk Management for Governance-Focused Projects (Wits University – School of Governance)

A major portion of project management exam marks—especially within governance contexts—go to the “people-and-planning” side of delivery. In project management exam packs, scope and stakeholder questions are often used as a gateway to more advanced topics like risk response planning, change control, and performance reporting.

This section drills the exam logic behind three linked areas:

1. Scope management and change control
2. Stakeholder management and engagement planning
3. Risk management: identification, analysis, response, and monitoring

1) Scope management: building a scope baseline that survives real pressure

A strong scope answer starts with clarity: what you mean by scope and why it must be controlled.

What students often miss

• You don’t manage scope by “trying to stop changes.”
• You manage scope by capturing requirements, defining deliverables, establishing acceptance criteria, and using formal change control.

Exam question scenario (common pattern)

A department launches a systems upgrade. Midway, a new policy requirement appears, and the client requests additional reporting features.

A high-scoring response should:

• Treat this as a change request.
• Identify impacts on scope, schedule, costs, and risks.
• Use governance: approval mechanism through CCB or equivalent.
• Update baselines only after approval.
• Communicate implications and revise plans.

Scope baseline components (what to mention)

You can mention:

• WBS (Work Breakdown Structure) summary level
• Scope statement
• Deliverables list
• Acceptance criteria (what “done” means)
• Dependencies/assumptions

Even if the exam doesn’t require WBS drawings, referencing a WBS logic shows planning maturity.

2) Change control: the exam’s favourite “discipline under uncertainty”

Governance-oriented project questions often test whether you understand that change control is both:

• a technical control (baselines, impacts), and
• a governance control (approval, audit trail, transparency).

Practical change control steps (write as numbered steps)

1. Receive change request (from client/stakeholder).
2. Log request in change register (include rationale).
3. Assess impact on:
   • time/schedule,
   • cost/budget,
   • scope/deliverables,
   • quality/acceptance criteria,
   • risks and compliance requirements.
4. Recommend action (approve/reject/defer/rework).
5. Review and approve through CCB/authorised decision rights.
6. Update baselines and documents after approval.
7. Communicate change and update stakeholders and execution teams.
8. Monitor implementation to ensure expected outcome.

Counter-argument you can include (to show critical thinking)

Some students say “approve changes quickly to maintain stakeholder satisfaction.” A stronger exam answer notes:

• Speed matters, but uncontrolled approval increases risk of:
  • budget overruns,
  • schedule collapse,
  • conflicting deliverables,
  • audit and compliance failures.

Therefore, even urgent changes must pass through governance—but the assessment may be expedited.

3) Stakeholder management: mapping power, interest, and influence

Stakeholder management in exam packs typically asks you to do one of the following:

• identify stakeholders,
• decide engagement strategies,
• predict how stakeholder reactions affect project success.

Stakeholder categories you can use

A practical model for exams is often:

• Manage closely: high power, high interest
• Keep satisfied: high power, low interest
• Keep informed: low power, high interest
• Monitor: low power, low interest

Example scenario (stakeholder conflict)

A school infrastructure project has stakeholders including:

• provincial department (high power),
• municipal facilities unit (power),
• teachers (high interest),
• learners and parents (high interest),
• contractors (power via execution capacity).

If teachers insist on design changes after procurement begins:

• you must respond with change control and stakeholder engagement,
• confirm constraints (approved procurement, compliance, budget),
• explain the decision logic.

In your answer, mention engagement level:

• Use workshops or co-design sessions where appropriate.
• For high-power stakeholders, ensure formal reporting and approvals.

4) Engagement plan: what “good” looks like in an exam answer

An engagement plan can be presented as a table or bullet list. In many Wits-style exam questions, marks increase if you link engagement to purpose:

• Purpose: inform, consult, collaborate, empower
• Audience: which stakeholder groups
• Method: meeting, workshop, reporting dashboard, feedback loop
• Frequency: weekly, monthly, milestone-based
• Owner: project manager, procurement lead, M&E officer
• Output: decisions, actions, documented minutes

Even if the exam doesn’t ask for a full plan, you can show it as a mini version.

Example engagement plan outline (you can adapt)

• Senior decision-makers: monthly governance reporting + escalation mechanism.
• Implementation teams: weekly status meetings with risks and blockers.
• Community representatives: quarterly feedback sessions and complaint-handling.

5) Risk management: from risk register to actionable responses

Risk questions in exam packs are rarely just about listing risks. They are about:

• probability and impact,
• risk responses (avoid/mitigate/transfer/accept),
• ownership (who manages the risk),
• triggers and monitoring.

Risk register: what to include

A typical risk register row includes:

• risk description,
• category (schedule, cost, compliance, technical, stakeholder, external),
• probability and impact rating,
• risk score or level (if used),
• response strategy,
• owner,
• contingency/reserve,
• triggers,
• status (open/closed).

Risk response types (and how to justify)

• Avoid: change plan to eliminate risk.
• Mitigate: reduce probability or impact.
• Transfer: shift impact to a third party (e.g., insurance, contractual clauses).
• Accept: acknowledge risk and prepare contingency.

Exam justification examples

• Compliance risk: mitigation through legal review and audit readiness.
• Contractor performance risk: mitigate via performance-based contracting and monitoring.
• Supply chain risk: mitigate via alternative suppliers and lead-time buffers.

6) A full exam example: scope change triggers a risk response

Consider this integrated scenario (often used in exam packs):
A public-service project starts procurement for a component. Later, a stakeholder demands extra features, and procurement is already underway.

You should interpret it like this:

• Scope change introduces:
  • schedule risk (rework, tender amendments),
  • cost risk (variation costs),
  • compliance risk (tender fairness if specifications change unilaterally),
  • stakeholder trust risk (perception of unfairness).

So, you respond with:

1. Change request logging.
2. Impact assessment.
3. Governance decision by CCB.
4. Risk response planning:
   • mitigations: update scope documents through controlled procurement change process,
   • contingency: schedule float or budget reserve for variations,
   • stakeholder engagement: explain process and constraints.

This integrated structure is exactly how exam packs reward high marks.

7) Monitoring risks and stakeholder issues over time

A key exam point: risk management is not a once-off exercise. It’s iterative:

• risks must be reviewed at least at milestones or regular intervals,
• new risks emerge as scope evolves,
• stakeholder dynamics change with project progress.

A strong response includes:

• periodic risk review meetings,
• early warning indicators (triggers),
• escalation paths for high-risk items.

Wits Plus Exam Packs: Scheduling, Costing, Monitoring & Evaluation (M&E) and Performance Control (Wits University – School of Governance)

Once scope and risks are under control, exam packs often shift toward how you keep the project on track: schedule, cost, and performance reporting—plus the governance discipline of monitoring and evaluation.

This section focuses on:

1. planning schedule structure,
2. cost budgeting and control logic,
3. monitoring & evaluation measures,
4. interpreting performance signals,
5. reporting and decision-making under variance.

1) Scheduling fundamentals: building a realistic plan

A common mistake in exam answers is treating scheduling as “just dates.” Good answers treat schedule as:

• sequence of activities,
• durations,
• dependencies,
• critical constraints,
• schedule baseline.

Work planning logic you can describe

1. Identify activities based on WBS.
2. Determine dependencies.
3. Estimate durations.
4. Sequence activities (network logic).
5. Identify critical path (if taught in the course).
6. Create schedule baseline.
7. Add buffers (for uncertainty) where appropriate.

Even if the exam doesn’t ask for a CPM diagram, mentioning critical path or critical activities signals competence.

Example scenario: schedule pressure

A contractor requests acceleration to meet a deadline. If you blindly approve:

• quality could drop,
• cost might rise,
• risk might increase.

A strong answer considers:

• whether acceleration changes scope,
• whether procurement constraints allow it,
• whether resources are available,
• whether acceptance criteria remain the same.

2) Cost planning: budgeting, baselines, and cost control

A cost answer in an exam pack should clearly show:

• what the budget covers,
• how spending is planned and monitored,
• how variations are handled.

Key cost components to mention (typical)

• labour (internal project team, contractor labour),
• materials and equipment,
• professional services,
• procurement and logistics,
• indirect costs (if applicable),
• contingency/reserves,
• escalation allowances (for long projects).

Budget baseline logic

You set a cost baseline by:

• aggregating estimated costs for work packages,
• defining how and when costs are expected to be incurred,
• approving budget allocation.

Then you control costs by:

• tracking actual spending against planned spending,
• analysing variances,
• forecasting cost at completion,
• deciding whether to implement corrective actions.

3) Monitoring & controlling: variances and corrective actions

Exam packs may include numeric data or may ask for conceptual interpretation. Either way, your answer should follow a consistent logic:

1. Measure performance (progress, costs, quality checks).
2. Compare to baseline targets.
3. Analyse deviations:
   • Why is schedule behind?
   • Why is cost higher?
   • Are issues linked to risks or scope changes?
4. Recommend corrective actions:
   • re-sequence tasks,
   • adjust resources,
   • implement scope control,
   • mitigate risks,
   • renegotiate with suppliers (within governance).
5. Update plans and report.

Example corrective action set (write as bullet points)

• If schedule variance is due to supplier delays:
  • expedite procurement process (within fairness/compliance),
  • activate contingency supplier,
  • adjust downstream tasks to reduce idle time.
• If cost variance is due to rework:
  • diagnose root cause (quality, requirements clarity),
  • strengthen acceptance criteria and review gates,
  • apply lessons learned and process improvements.

4) Earned Value concepts (if applicable) and variance interpretation

Some exam packs include simplified performance metrics. Even when acronyms differ, the logic remains:

• Planned value: what you expected to spend for work planned.
• Earned value: value of work actually completed.
• Actual cost: what you actually spent.

Your exam answer may ask:

• Are you ahead or behind?
• Is cost performance better or worse?
• What does the trend mean for forecast?

If the exam doesn’t provide these metrics explicitly, you can still use the logic as:

• “Work completed is less/more than planned; therefore progress is behind/ahead.”
• “Actual cost is higher/lower than expected; therefore costs are over/under budget.”

5) Monitoring & Evaluation (M&E): outputs, outcomes, and indicators

Wits governance-oriented project work typically demands clarity on:

• outputs vs outcomes,
• indicators and measurement,
• data quality and reporting,
• using evaluation findings for decisions.

Outputs vs outcomes (exam-friendly explanation)

• Outputs: what the project delivers (e.g., number of training sessions, completed infrastructure works).
• Outcomes: changes resulting from outputs (e.g., improved service access, reduced processing time).

A strong answer includes that:

• outputs are measured frequently and close to delivery,
• outcomes often take longer and may require contribution analysis.

Indicators: what “good” looks like

Indicators should be:

• relevant to objectives,
• measurable with defined data sources,
• time-bound,
• realistic given capacity.

Example indicators for a training programme:

• Output indicator: “Number of learners trained (gender-disaggregated).”
• Outcome indicator: “Increase in competency scores or reduced error rates.”
• Governance indicator: “Training compliance rate with reporting requirements.”

6) A complete M&E mini-framework you can use in exam responses

When a question asks “how will you monitor and evaluate?”, a high-scoring approach is to present:

1. Results framework:
   • objectives → outputs → outcomes
2. Indicator matrix:
   • indicator, target, data source, frequency, method
3. Data collection plan:
   • who collects, tools used, sampling (if required), quality checks
4. Reporting cadence:
   • weekly operational, monthly management, quarterly governance
5. Evaluation approach:
   • formative (during delivery) and summative (after delivery)
6. Use of findings:
   • corrective actions and decision forums.

7) Reporting: making governance visible through status and dashboards

In governance contexts, reporting is not just for information; it’s for accountability.

A project status report can include:

• progress against schedule,
• spend against budget,
• risk status,
• change log summary,
• procurement status,
• quality/acceptance progress,
• next period plan,
• decisions required from governance bodies.

Example next-steps reporting line (exam-quality)

• “Request approval for scope change X; confirm procurement compliance approach; update schedule baseline upon approval.”

8) Integrated example: how M&E ties back to schedule and cost control

Consider a scenario:
A project for service improvement reports that:

• training workshops (output) are on time,
• but assessment results (outcome proxy) are below expected levels,
• and re-training costs have increased.

Your exam answer should connect:

• performance monitoring reveals outcome under-delivery,
• schedule/cost variance is caused by quality/rework,
• corrective action may include:
  • adjusting training design,
  • strengthening facilitation quality,
  • revising acceptance criteria,
  • updating risk register for quality risk.

This integration is often where top marks come from.

Wits Plus Exam Packs: Procurement, Contract Management, Ethics, and Close-Out Governance (Wits University – School of Governance)

Many project management exam packs include procurement and contracting because these areas are deeply tied to governance: fairness, compliance, value for money, contract performance, dispute resolution, and audit readiness. They also create practical constraints on schedule and cost—so procurement competence is a bridge to the earlier topics.

This section focuses on:

1. procurement planning basics and compliance logic,
2. contract management and performance assurance,
3. dealing with procurement-related risk,
4. closing projects with acceptance, lessons learned, and documentation.

1) Procurement planning: linking needs, scope, and governance

Procurement planning is not “ordering goods.” It is converting project needs into acquisition decisions under rules.

A governance-oriented exam answer can reference:

• procurement plan aligned to scope and schedule,
• specifications and evaluation criteria,
• supplier selection method,
• contract terms and deliverables.

Exam scenario: procurement begins before scope is stable

A project begins tendering for a service. Later, the requirements change materially.

A strong governance answer says:

• tender documents must remain consistent with approved scope,
• significant changes may require re-tendering or controlled amendments depending on compliance rules,
• decisions must be documented to ensure fairness and auditability.

2) Typical procurement decision points you can discuss in exams

You may be asked to justify:

• how to choose suppliers fairly,
• how to structure contracts for performance,
• how to manage lead times and dependencies.

Example decision list (write as steps)

1. Define what is needed (deliverables/specifications).
2. Confirm required quantity and quality requirements.
3. Identify procurement method consistent with governance rules.
4. Define evaluation criteria (quality, price, compliance, capacity).
5. Set contract deliverables and acceptance criteria.
6. Define performance monitoring and reporting obligations.
7. Manage contract variations through change control.

3) Contract management: ensuring delivery matches agreed outcomes

Contract management in project management exam packs typically covers:

• monitoring contractor performance,
• managing variations,
• ensuring quality,
• dispute escalation and resolution,
• documentation and reporting.

A high-scoring answer includes:

• milestones and deliverables,
• service level or performance requirements (as applicable),
• reporting requirements,
• remedies for non-performance (within contractual governance).

Example: contractor underperformance

A contractor misses a milestone due to staffing issues and requests a schedule extension.

Your response can include:

• verify performance data (progress reports, evidence),
• analyse root cause (risk analysis),
• check whether extension is justified or whether corrective action is required,
• apply contractual provisions for extensions/penalties/remedies,
• update schedule baseline through approved governance steps.

4) Procurement risk: how to manage it like a project manager

Procurement introduces specific risks:

• supplier capacity risks,
• delivery delays,
• quality non-compliance,
• price escalation,
• legal/compliance exposure if procurement is mishandled.

You should demonstrate risk management by:

• identifying procurement risks early (during planning),
• adding mitigations and contingency (alternative suppliers, lead-time buffers),
• defining triggers (late delivery indicators, quality test failures),
• assigning ownership (procurement lead, contract manager).

Example risk response pairing (use in exam answers)

• Risk: supplier delays due to limited capacity.
  Response: require capacity evidence at selection, set milestone reporting, include escalation clause, identify secondary supplier.
• Risk: quality non-compliance at acceptance.
  Response: define test/inspection procedures, quality assurance requirements, corrective action periods.

5) Ethics and transparency: where governance earns marks

Wits governance-oriented marking tends to reward ethical reasoning embedded in practical steps.

When asked about procurement ethics, students can mention:

• fair and competitive selection,
• conflict of interest management,
• transparency in evaluation criteria,
• documentation of decisions,
• compliance with procurement policy frameworks.

Counter-argument to show maturity:
Sometimes students assume “choosing the lowest bidder” is always fair. A stronger answer notes:

• fairness is not only about lowest price; it’s about consistent application of criteria that reflect value for money and capacity to deliver.

6) Contract variations: connecting procurement to change control

Variations are a practical exam favourite because they combine:

• scope/schedule impact,
• procurement compliance,
• governance approval processes.

A high scoring response uses the logic:

1. Recognise variation as a change request.
2. Assess impact and compliance implications.
3. Obtain authorised approval before instructing the contractor.
4. Document decisions and update baselines.

7) Project close-out: governance closure and acceptance

Close-out is sometimes treated as an afterthought, but exam packs often ask:

• how you confirm delivery,
• what documentation is required,
• how lessons learned are captured and used.

Close-out activities you should mention

1. Final deliverable verification:
   • acceptance testing or validation against acceptance criteria.
2. Stakeholder sign-off:
   • clients and governance bodies confirm completion.
3. Contract close-out:
   • final invoices, performance reports, warranties, handover documents.
4. Financial close-out:
   • reconcile spend, ensure compliance reporting, confirm remaining balances.
5. Documentation:
   • archiving of baseline documents, approvals, change logs, risk register history.
6. Lessons learned:
   • what worked, what didn’t, improvements for next project.

8) Lessons learned: turning experience into governance capability

Strong lessons learned responses include:

• specific causes (not just symptoms),
• concrete actions recommended,
• who should own improvements in future projects.

Example:

• Symptom: schedule slips due to late requirement clarification.
• Root cause: inadequate stakeholder engagement early.
• Lesson: implement earlier stakeholder workshop and formalise requirements baseline.
• Owner: project initiation lead; governance training.

9) Integrated close-out example: procurement mismatch and governance repair

Scenario:
A project delivers a set of components that meet technical specs, but documentation does not align with tender requirements. Audit flags a compliance gap.

A top exam answer includes:

• clarify whether the deliverables meet acceptance criteria technically,
• review contract compliance requirements and tender documents,
• document discrepancy and corrective actions (e.g., obtain missing compliance certificates),
• ensure governance sign-off and audit trail closure.

Even when the technical component works, governance documentation must be complete.

Practice Bank: Wits-Style Project Management Exam Pack Questions and Model Answer Structures (Unified for Wits Plus Preparation)

This section consolidates all prior themes into exam-pack-ready practice. It does not just provide “answers”—it provides structures you can replicate under exam time pressure. Each question shows the kind of reasoning the marking rubric typically rewards in Wits School of Governance contexts.

1) Question set on scope, change control, and stakeholder governance

Question 1 (scope and governance)

A community project is approved with a defined scope and deliverables. Two months into implementation, a powerful stakeholder requests additional features that were not in the approved scope. Work has already started on these additions without formal authorisation.

Required:
Explain what the project manager should do next and justify how governance should be applied.

Model answer structure (what to write)

1. Identify: scope creep and change control failure.
2. Stop and assess: pause unauthorised work.
3. Log change request and impacts:
   • scope, schedule, cost, quality,
   • stakeholder expectations and risk impacts.
4. Governance decision via CCB/authorised structure.
5. Communicate decision to stakeholders.
6. Update baselines only after approval.
7. Record audit trail and lessons learned.

Question 2 (stakeholder engagement)

During planning, a department identifies stakeholders but does not develop an engagement plan. Later, stakeholders oppose procurement decisions publicly, causing reputational risk.

Required:
Propose a stakeholder engagement approach suitable for governance-focused projects.

Model answer structure

• Stakeholder mapping (power/interest).
• Identify engagement objectives by stakeholder group.
• Select engagement methods (workshops, consultations, reporting).
• Frequency and ownership.
• Feedback loop and decision transparency.
• Link to procurement fairness and risk reduction.

2) Question set on risk management and performance control

Question 3 (risk response selection)

A major deliverable depends on supplier lead time. Probability of delay is medium, and impact on project schedule is high. The supplier indicates staffing constraints.

Required:
Recommend the best risk response strategy and monitoring actions.

Model answer structure

• Identify risk and categorise (schedule + external).
• Probability/impact interpretation.
• Response:
  • mitigate (alternative supplier, expedite logistics, revise schedule),
  • transfer elements if contract permits (where appropriate),
  • contingency planning and schedule float where feasible.
• Ownership assignment.
• Triggers (e.g., missed milestone by X days, production slippage).
• Monitoring and escalation.

Question 4 (corrective action under variance)

The project is behind schedule by 10% and costs are 15% higher than planned in the last reporting period. Progress on deliverables is incomplete, and rework is occurring.

Required:
Describe a monitoring and corrective action plan that addresses both schedule and cost drivers.

Model answer structure

1. Measure: confirm actual progress and costs; verify evidence of rework.
2. Compare: baseline schedule/cost vs actuals.
3. Diagnose root causes:
   • scope changes? quality issues? supplier delays? stakeholder changes?
4. Corrective actions:
   • implement corrective quality measures,
   • adjust sequencing and resource allocation,
   • apply change control to remove unauthorised scope.
5. Forecast and update baseline through governance approval.
6. Report transparently to stakeholders and decision-makers.

3) Question set on procurement and close-out governance

Question 5 (procurement ethics and compliance)

Tender specifications were not updated after a scope change request. As a result, the delivered items technically match the contract but not the updated stakeholder requirements. The audit team questions compliance with the intent of the approved scope.

Required:
Explain how the project should manage compliance, acceptance, and corrective actions.

Model answer structure

• Confirm technical acceptance vs scope compliance intent.
• Review contract and tender documentation.
• Use governance:
  • assess whether amendments were required,
  • whether corrective documentation can resolve compliance,
  • approval for any variation or corrective work.
• Obtain missing evidence/certificates/acceptance sign-offs.
• Document the compliance gap and closure plan.
• Lessons learned for future tender change control.

Question 6 (close-out)

At project end, stakeholders disagree on whether the project is “complete.” Contractors are ready to close, but some users indicate acceptance criteria were not met.

Required:
Outline close-out steps to resolve acceptance and ensure contract and governance closure.

Model answer structure

1. Re-check acceptance criteria and deliverables evidence.
2. Conduct final validation/testing or walkthroughs.
3. Capture outstanding issues and decide:
   • remedial work needed,
   • timeline and costs within governance.
4. Obtain stakeholder sign-off once criteria are met.
5. Contract close-out:
   • ensure final invoices and handover documentation.
6. Financial reconciliation and archiving.
7. Lessons learned and improvement actions.

4) Exam mini-case: integrated project (one narrative across topics)

Use the following integrated scenario for revision practice. You can answer sub-questions in different sections of your exam paper.

Mini-case scenario

A Wits governance-aligned delivery project aims to improve a local service process. The project includes (1) staff training, (2) an operational procedure update, and (3) a contracted implementation component.

• Month 1: Scope is approved with deliverables and acceptance criteria. Stakeholder engagement is limited to an initial meeting.
• Month 2: Stakeholders request additional reporting requirements. Change control is delayed because “decisions are still being discussed.”
• Month 3: Supplier lead time is threatened by staffing constraints. A minor delay occurs.
• Month 4: Training workshops are completed, but assessment results indicate insufficient competency. Rework training is requested.
• Month 5: Procurement documentation is questioned during a compliance check due to mismatched expectations from updated reporting requirements.
• Month 6: Stakeholders argue about project completion due to acceptance criteria confusion.

Exam tasks you should practise

1. Identify scope/change control failures and propose corrections.
2. Propose a stakeholder engagement plan that could have prevented Month 5 disputes.
3. Recommend risk responses for supplier delay and training effectiveness risk.
4. Explain how M&E would measure outcome progress (competency and service improvement).
5. Outline close-out steps that resolve acceptance disagreement.

Model answer approach

• Scope/change: log change requests, assess impacts, approve via governance.
• Stakeholders: power/interest mapping, structured engagement, transparency.
• Risk:
  • supplier delay: mitigate via alternative suppliers and contingency triggers,
  • training risk: mitigate with improved design, assessments, and remedial actions.
• M&E: define indicators (training outputs and competency outcomes), reporting cadence.
• Close-out: validate against acceptance criteria, remedial work decisions, sign-offs, contract/documentation closure.

Review Checklist: Wits Plus “Exam Pack” Readiness Map (Use in the last 7–10 days)

This final section is a condensed readiness checklist that still functions as a study guide. Use it to confirm you can do what exams demand: choose correct processes, justify decisions, and link technical delivery to governance and stakeholders.

1) Scope and change control mastery checklist

• I can explain scope vs requirements vs deliverables.
• I can define what a scope baseline includes.
• I can list a robust change control process with governance approval.
• I can demonstrate how changes affect time, cost, risk, and quality.
• I can connect scope changes to procurement compliance implications.

2) Stakeholder management mastery checklist

• I can map stakeholders by power and interest.
• I can propose engagement methods and frequency by stakeholder group.
• I can link engagement to reducing reputational and procurement risks.
• I can explain how to manage conflicts using documented communication and decision transparency.

3) Risk management mastery checklist

• I can build risk register entries with owner, triggers, responses, and monitoring.
• I can justify avoiding/mitigating/transferring/accepting.
• I can explain how risks evolve and how risk reviews are performed.
• I can connect risk responses to schedule and cost forecasts.

4) Scheduling and cost control mastery checklist

• I can describe schedule baseline creation and dependencies.
• I can explain cost budgeting and cost baseline control.
• I can interpret schedule/cost variances and propose corrective actions.
• I can connect quality/rework drivers to cost escalation and schedule slippage.

5) Monitoring & evaluation mastery checklist

• I can distinguish outputs vs outcomes.
• I can propose indicators with measurement method and frequency.
• I can describe data quality considerations (reliable sources, consistent reporting).
• I can explain how M&E evidence informs corrective governance decisions.

6) Procurement, ethics, and close-out mastery checklist

• I can explain procurement planning aligned to scope and schedule.
• I can describe contract management monitoring and variations through governance.
• I can provide ethics/transparency reasoning linked to fairness and auditability.
• I can outline close-out steps including acceptance, contract closure, financial reconciliation, documentation, and lessons learned.

South African Course Keyword Alignment (for Unisa/CUT-style search and exam note terminology)

South African students often search for exam notes using course codes and familiar module themes. While Wits School of Governance course titles and codes may differ by cohort, the following keyword-aligned phrases reflect what you typically need to practise for Wits Plus project management exam packs and similar university modules (including Unisa and CUT-style project management competence):

• “Project Management exam notes”
• “mng 0001 / project management introductory exam notes” (use as a search phrase even if your institution’s code differs; the study skills are the same)
• “Risk management study notes”
• “Stakeholder management and governance study notes”
• “Monitoring and Evaluation (M&E) in projects study notes”
• “Procurement and contract management exam notes”
• “Change control and scope management exam questions”
• “Earned Value analysis study notes” (where introduced in your course pack)

When practising, ensure your answers consistently include:

• a process identification,
• a justification grounded in the scenario,
• next-step action using governance language,
• stakeholder and risk impacts.

Final Self-Assessment: What a Top-Score Student Can Do

A student who is fully prepared for Wits School of Governance Project Management Exam Packs can do the following quickly and correctly:

• Translate a real scenario into a clear PM diagnosis (scope, stakeholder, risk, schedule, cost, procurement, or M&E).
• Select the appropriate tool/process and describe it as actionable steps.
• Justify choices using scenario evidence rather than generic definitions.
• Use governance language naturally: approvals, audit trail, fairness, compliance, documentation, and decision rights.
• Connect monitoring results (progress and performance evidence) to corrective actions.
• Close the project responsibly: acceptance, contract close-out, financial reconciliation, documentation, and lessons learned.

If you can consistently produce that type of reasoning under exam conditions, you are aligned with how Wits-style marking expectations typically award marks in short and specialised course assessments within Wits Plus collections.