Associate Member of Project Management South Africa (PMSA) Prep Notes

If you are preparing for the PMSA Associate Member pathway, you need more than generic “project management theory.” You need a practical, South African–aligned understanding of how organisations plan, execute, monitor, control, and close projects—paired with the ability to evidence competence through work experience and structured project thinking. These exam-style preparation notes focus on what is typically assessed: project governance, planning discipline, risk and stakeholder management, monitoring and reporting, and professional conduct consistent with PMSA expectations.

The notes below are organised into five university-focused clusters, mirroring how South African students often study for UNISA, CUT, UKZN, UP, and TUT modules that closely relate to project management and development practice (e.g., UNISA-style project management and planning content; CUT/UKZN/UP/TUT-style management and project planning modules). Each section builds your readiness in a way that you can translate directly into your application narrative and any knowledge-based assessments.

Section 1: UNISA-style Project Management Competence (PMSA Knowledge + Evidence)

Why UNISA-style preparation matters for PMSA Associate Member

UNISA students are often trained to demonstrate competence through structured learning outcomes, linking theory to applied tasks, and writing logically reasoned responses. In PMSA Associate Member prep, that same approach is useful because the assessment commonly rewards candidates who can:

Explain project fundamentals using standard terms (scope, schedule, cost, quality, risk, procurement).
Show how decisions were made (assumptions, constraints, trade-offs, governance).
Provide clear evidence that they can operate in a project environment (e.g., stakeholder engagement, progress tracking, reporting).

Rather than memorising definitions, you want to practice “exam answers” that look like work-based explanations: “Here is the problem, here is the plan, here is what we measured, here is how we corrected course, and here is what we learned.”

Core PMSA-aligned project management knowledge areas (exam lens)

Use these as your “minimum coverage checklist” for both written preparation and the way you describe your experience.

Project life cycle and governance
- Initiation → planning → execution → monitoring & controlling → closing.
- Governance basics: roles, accountability, decision points, approvals.
- The difference between project governance (decision structures) and project management (delivery activities).
Scope management
- Requirements vs deliverables.
- Work Breakdown Structure (WBS) concept: breaking work into manageable components.
- Change control: how scope changes are assessed and approved.
Time/schedule management
- Activity sequencing and logical dependencies.
- Estimation: how duration is derived, and how uncertainty is handled.
- Baseline vs current performance: tracking variance.
Cost management
- Budgeting at appropriate level (WBS or cost breakdown).
- Cost baseline and forecasting.
- Distinguish between incurred costs, committed costs, and remaining budget.
Quality management
- Quality planning: define standards and acceptance criteria.
- Quality assurance vs quality control.
- Practical thinking: how inspections, test plans, checklists, and sign-offs are used.
Risk management
- Risk identification, analysis, response planning, and monitoring.
- Risk register discipline: probability/impact scoring, triggers, owners.
- Contingency vs contingency reserve (conceptual separation).
Stakeholder management
- Stakeholder identification and mapping.
- Communication plan: what information, when, and to whom.
- Handling resistance and aligning expectations.
Procurement and contracting (if relevant)
- Contract scope clarity.
- Vendor performance monitoring.
- Procurement risks: delays, quality, cost escalation.

What exam questions often test (typical patterns)

Even if your assessment format varies, the structure tends to be similar. Common question styles include:

“Explain the project life cycle and justify why each phase exists.”
“Given a scenario with delays, cost increases, and stakeholder conflict, propose corrective actions using monitoring and control principles.”
“Design a risk register approach and give examples of risk statements, causes, and responses.”
“Discuss stakeholder communication planning and how you would manage disagreements.”

In your answers, always include:

Context (what project type, what constraints)
Process (the steps you would take)
Evidence/outputs (documents/artifacts: charter, plan, baseline, risk register, reports)
Corrective action (what you would do when variances occur)
Outcome/learning (what changed because of your intervention)

Practical UNISA-style writing framework: the “STAR-P” answer model

For exam readiness and PMSA evidence writing, practise this model:

STAR-P:

Situation: what problem or project context you faced.
Task: what responsibility you had (your specific role).
Action: the steps you took (planning, analysis, communication, controls).
Result: what happened, with measurable impacts when possible.
Products/Proof: what documents, approvals, logs, minutes, dashboards, or sign-offs exist.

Example micro-answer you can rehearse:

Situation: A community refurbishment project faced scope creep due to late user requests.
Task: You were responsible for tracking scope changes and updating the schedule baseline.
Action: You facilitated a change-request process, documented impacts on cost and time, and presented decisions to the project governance structure.
Result: Scope changes were approved only when trade-offs were clear; schedule variance reduced after formal change control.
Product/Proof: Change request forms, updated WBS, revised schedule baseline, and meeting minutes.

Evidence building for PMSA: turning experience into competence

PMSA Associate Member preparation is strengthened when you can align experience to competence themes. Prepare a “project evidence bank” that you can reuse:

Create a personal record with entries like:

Project name and type
Your role (assistant project manager, planning support, risk controller, etc.)
Tools used (Gantt charts, risk registers, Excel tracking, MS Project, procurement trackers)
Meetings supported (progress meetings, steering committee, stakeholder engagement sessions)
Documents produced (weekly status reports, RAID logs, change logs)
Corrective actions you implemented (replanning, renegotiation of deadlines, mitigation steps)

Even if your formal title is not “Project Manager,” PMSA Associate Member candidates often demonstrate competence by showing they contributed to key management processes.

Short practice: how to respond to “scope change scenario”

Scenario type: “A client adds a new requirement mid-project. What do you do?”

A strong PMSA-style answer:

Record the request formally (change request).
Analyse impact (scope, time, cost, quality, risk).
Consult affected stakeholders and internal teams.
Present options: accept as-is, trade-off elsewhere, defer to a later phase, or reject.
Obtain approval according to governance rules.
Update baseline(s) and communicate the change using the communication plan.

This is exactly the type of structured thinking UNISA-style writing often rewards.

Section 2: CUT & Project Planning Applications (Time, Cost, Risk, Monitoring)

CUT-focused thinking: planning discipline and measurable control

South African universities often emphasise planning and operational control. In a CUT-style preparation approach, your goal is to move from conceptual knowledge into planning methods and monitoring logic. The PMSA Associate Member assessment commonly expects you to understand not only what should be done, but also how you can detect problems early and correct them.

In practice, this section equips you to answer questions like:

“How would you build a schedule baseline?”
“How do you manage risk over time?”
“What indicators would you use to report progress?”

Schedule baseline and time management: more than “make a Gantt chart”

A common student mistake is treating scheduling as a one-off creation of a Gantt chart. Instead, scheduling is an ongoing control system.

Step-by-step: building a realistic schedule baseline

Define activities from the WBS.
Sequence activities based on dependencies (finish-to-start, start-to-start, etc.).
Estimate durations:
- Use past data where available.
- Use expert judgement if no history exists.
- Consider learning curves and resource constraints.
Assign resources (even at a high level).
Develop the schedule (network logic → calendar plan).
Validate assumptions (what must be true for the schedule to hold).
Create the baseline: once approved, it becomes your reference point for variance analysis.

Monitoring schedule performance: variance-based control

Use terms and reasoning like:

Planned vs actual progress
Schedule variance (time slippage or acceleration)
Forecast at completion (if you must predict final delivery)
Critical path logic (if one activity slips, what happens downstream?)

If you are asked for corrective actions, mention:

Fast-tracking (overlap activities if risks allow)
Crashing (additional resources at cost trade-offs)
Re-sequencing (changing order where feasible)
Scope or quality trade-offs (only with approved governance)

Cost baseline and cost control logic

Cost management is not just “track expenses.” For exam and evidence, you must connect cost to work performed.

Building a cost baseline

Start with the WBS.
Assign cost estimates to work packages.
Summarise to budgeting levels.
Include contingencies (for known-unknowns) and reserves (for unknowns; use correct terminology consistently in your narrative).

Cost monitoring

A strong answer includes:

Earned vs incurred concept (even if simplified in your exam response)
Budget remaining
Cost variance and trend analysis
Linking cost changes to causes (scope changes, inefficiency, procurement delays)

Example scenario (practise)

A small construction project has:

Planned budget baseline: R 2,000,000
After two months, actual cost incurred is R 650,000
Planned value for the same period is R 500,000

A good exam answer states:

Costs are running ahead of planned value → risk of cost overrun.
Investigate causes: are tasks completed earning less than expected? Is there rework?
Take corrective actions: tighten estimating, improve productivity tracking, confirm supplier lead times, review change control.

You can present cost reasoning without needing complex formulas; the key is linking numbers to work and decisions.

Risk management: RAID log discipline with examples

Risk management questions typically want:

A clear risk statement format
Cause + event + impact
Probability and impact scoring
Response strategy and ownership
Monitoring triggers

Risk statement format that scores well

Use:

Risk event: “If X happens…”
Cause: “because/ due to…”
Impact: “then Y will occur… affecting (cost/time/quality/scope)…”
Owner: “owned by…”
Response: prevention/mitigation, contingency, and fallback

Example risk entries you can reuse

Procurement delay
- Cause: supplier lead times longer than forecast
- Event: delivery delayed by 3–4 weeks
- Impact: schedule slippage on installation activities
- Response: dual sourcing or expedite shipping for critical materials
Stakeholder requirement changes
- Cause: user feedback arrives late
- Event: new requirement affects design
- Impact: scope expansion → cost/time increase
- Response: formal change control; early stakeholder workshops
Quality failure
- Cause: inadequate inspection during early construction stages
- Event: rework due to non-compliance with standards
- Impact: cost increase and schedule delay
- Response: strengthen QA plan and hold points

Monitoring and reporting: using dashboards and weekly status reports

A key exam competence is communication in project control.

Weekly status report components

Include:

Progress against milestones
Top issues and risks (with mitigations)
Schedule: what is on track vs off track
Budget: spending trend and forecast
Decisions needed from governance
Next week’s plan

Common reporting pitfalls

Reporting activities instead of outcomes (“we worked on” vs “we completed”)
Not updating forecasts
Failing to link risks to actions
Overloading stakeholders with detail without decisions

Corrective and preventive action: “when things go wrong”

For PMSA readiness, you should demonstrate the logic of corrective action:

Identify variance and root cause (why the baseline is being missed).
Evaluate options (correct now vs adjust baseline vs reduce scope).
Implement corrective actions (who does what by when).
Update plans and communicate changes.
Verify effectiveness (did the variance improve?).

Also mention preventive actions:

Improving process controls
Training and standardising work
Updating estimation assumptions

Mini-case exercise: schedule + risk combination

Scenario: “Three weeks into the project, a critical supplier has delayed a component. Progress is behind schedule and a key milestone is threatened.”

Good response structure:

Reassess schedule baseline feasibility and critical path impact.
Update forecasts: what is likely to be delivered and when?
Update risk register: procurement delay risk becomes active with higher probability/impact.
Mitigation: expedite alternative supplier or adjust dependent activities.
Governance: escalate decision needs (additional cost, scope adjustment, milestone revision).
Communications: keep stakeholders informed with clarity on trade-offs.

This is the kind of controlled, measurable thinking that both planning-heavy modules at CUT and PMSA assessment expectations reward.

Section 3: UKZN & Stakeholder/Communication Mastery (People, Power, and Project Success)

Why UKZN-style management skills matter in PMSA

Many PMSA candidates focus heavily on schedules and costs and underestimate stakeholder dynamics. Yet in South African organisational environments—especially in public sector, NGOs, and community-facing projects—stakeholder alignment often determines whether plans survive contact with reality.

A UKZN-style preparation cluster emphasises:

Social and organisational context
Structured communication
Managing conflict and expectations
Ethical professional behaviour

This section equips you to answer questions that require “people-first project management” competence without losing the technical discipline.

Stakeholder management fundamentals (exam-grade)

Stakeholder management is often assessed through scenario prompts.

Identify stakeholders systematically

Start with:

Internal stakeholders: project sponsor, steering committee, line managers, finance, HR, engineering, procurement.
External stakeholders: clients/users, community leaders, contractors, regulators, suppliers, utilities.

Map influence and interest

A stakeholder power-interest grid helps you tailor engagement.

High power, high interest: manage closely; frequent engagement; co-decision.
High power, low interest: keep satisfied; periodic updates.
Low power, high interest: keep informed; involve in feedback.
Low power, low interest: monitor; minimal communication.

Turn mapping into a communication plan

Your plan should specify:

Message content (progress, risks, decisions)
Channel (meetings, reports, emails, workshops)
Cadence (weekly status, monthly governance, daily operational check-ins)
Audience and responsibility

Communication plans that earn marks

Many candidates write “we will communicate regularly.” That is not enough. For better answers, include granularity.

Example communication plan (template)

Stakeholder group	Purpose	Frequency	Deliverable	Owner
Steering committee	Decisions & approvals	Monthly	Governance pack	Project manager / sponsor
Project team	Operational alignment	Weekly	Team meeting + action log	PMO/Project lead
Client users	Feedback & requirement validation	Bi-weekly	Workshop notes + requirement updates	Business lead
Contractors/suppliers	Performance & delivery coordination	Weekly/As needed	Delivery schedule update	Procurement lead

Even in short exam answers, demonstrating that you can structure communication shows competence.

Managing conflict: stakeholder disagreement scenario

Scenario type: “The client wants additional features; engineering says it will delay commissioning.”

A strong PMSA answer uses:

Clarify the requirement
- What exactly is being requested?
- What is the acceptance criterion and priority?
Quantify impact
- Schedule impact (which activities are affected?)
- Cost impact (what budget line increases?)
- Quality impact (will new features change testing requirements?)
Explore options
- Option A: accept and extend timeline
- Option B: accept with cost increase
- Option C: accept but reduce scope elsewhere
- Option D: defer to phase 2
Governance decision
- Escalate with a recommended option and trade-offs.
- Document decision and update baselines if approved.
Close the loop
- Communicate decision outcomes.
- Update stakeholders on changed expectations.

This demonstrates stakeholder management linked directly to governance and planning controls.

Ethical and professional conduct (often quietly examined)

Associate Member preparation should reflect professionalism:

Respect confidentiality of project information.
Avoid misrepresentation of progress (e.g., reporting tasks as complete when they are not).
Ensure fair procurement and transparent tender processes where applicable.
Maintain accurate recordkeeping: decisions, approvals, risks, and action logs.

A good answer about ethics does not sound moralistic; it sounds like operational discipline:

“We validated delivery evidence before marking work complete.”
“We kept an audit trail of change approvals.”

Cultural and local context in communication (South Africa relevance)

In South Africa, communication success often depends on:

Language and clarity (avoid ambiguous jargon)
Time sensitivity and stakeholder availability realities
Community engagement requirements (where projects affect communities)
Managing expectations of employment and procurement opportunities in development projects

In exam answers, you can demonstrate awareness without stereotyping by saying:

Stakeholder engagement must be planned with the stakeholder’s constraints.
Use accessible communication formats and confirm understanding.
Document decisions and feedback to avoid misunderstandings.

Case mini-study: public-facing delivery risk

Imagine a community services upgrade project where local representatives expect continuous updates and rapid resolution of concerns. Delayed communication increases tension and can lead to:

Complaints escalating to leadership
Work stoppages by contractors if permissions are withdrawn
Delays due to re-mobilisation

A PMSA-aligned response:

Create an engagement calendar aligned to milestone phases.
Assign a responsible person for community liaison (with escalation routes).
Track issues in an issues log and resolve within defined timelines.
Provide progress updates that connect actions to timelines, and show what is still pending and why.

This is stakeholder management as operational risk control.

Section 4: UP & Governance, Quality, and Procurement Readiness (Assurance + Decision-Making)

Governance as a project success engine

UP (University of Pretoria)-style business and management modules often emphasise governance structures and decision-making systems. For PMSA Associate Member prep, you want to articulate how governance supports delivery:

Who approves what?
How are decisions recorded?
What are the control gates between phases?
How do you manage escalations?

A governance-focused exam answer should include:

A description of decision-making bodies (sponsor, steering committee, project board)
The approval artifacts (charter, business case, project plan, risk management plan, change approvals)
Escalation thresholds (e.g., cost variance beyond X triggers review; schedule slip beyond a milestone triggers governance)

Even if your exam does not require numeric thresholds, showing that governance is rule-based—not informal—is important.

Quality management: building acceptance and reducing rework

Quality is frequently tested through scenario analysis (“defects found late,” “inspection failures,” “client dissatisfaction”).

Quality planning and acceptance criteria

Quality planning requires:

Standards reference (SOPs, specs, codes)
Acceptance criteria (what counts as “done”?)
Inspection and test plan (when and how checks occur)
Documentation requirements (reports, sign-offs, compliance evidence)

A strong PMSA answer includes:

“Quality assurance” = process to ensure correct processes are followed.
“Quality control” = checks to confirm deliverables meet requirements.

Handling non-conformance

A scenario might say:
“After installation, tests show non-compliance. How do you respond?”

Your response should mention:

Identify non-conformance and stop further affected work.
Analyse root cause (why did it fail? training gap? wrong materials? incorrect procedure?).
Corrective action and verification plan.
Document and communicate impact on schedule and cost.
Prevent recurrence (training, procedure update, tighter inspections).

This connects quality discipline to schedule/cost controls and stakeholder trust.

Procurement readiness (when third parties are involved)

Even if you are an assistant or planner, procurement understanding is useful because many projects rely on external vendors.

Procurement planning essentials

Define procurement requirements clearly (scope, specification, deliverables)
Choose procurement strategy appropriate to risk and urgency
Include evaluation criteria that align with project objectives: quality, delivery timelines, compliance, cost

Contract performance monitoring

Track vendor deliverables and acceptance tests
Manage variations (change notices with approved process)
Address delays with documented causes and remedies
Monitor claims/disputes in a professional manner

Governance gate thinking: phase transitions and “decision points”

A common governance exam question asks about why you have gates.

Gates exist to:

Confirm that the project is still justified (business case review)
Confirm readiness for next phase (scope and resources)
Validate quality and risk readiness
Ensure approvals and funding are in place

Your answer can refer to typical phase deliverables:

Project charter (or equivalent initiation document)
Project plan and baselines (scope, schedule, cost)
Risk and stakeholder engagement plans
Execution readiness checklist
Close-out report and lessons learned

Example governance-and-quality scenario (practise)

Scenario: “During execution, a contractor provides materials that meet some specs but fail others. If you accept immediately, you risk rework; if you reject, the schedule slips.”

UP-style governance response:

Convene governance/technical review: confirm acceptance criteria.
Evaluate trade-offs: cost of rework vs cost/time of replacement.
Apply quality control procedures: test evidence and compliance documentation.
If rejection causes milestone risk, request an approved change plan or recovery schedule.
Document decision and update baselines if required.

This shows that quality decisions are not “technical-only”; they are governance decisions with cost/time consequences.

Procurement and risk integration: RAID logic for vendors

A high-quality exam response also integrates procurement with risk management.

Example vendor-related risks:

Delivery delay risk
Quality non-compliance risk
Resource availability risk (contractor workforce shortages)
Contract interpretation risk (ambiguity in scope)

Then define responses:

Alternative sourcing
Increased inspection frequency for critical items
Clear contract deliverables and acceptance criteria
Escalation clauses and performance reporting cadence

Section 5: TUT & Integrated Case Practice (Putting It All Together for PMSA Associate Member)

Integrated preparation: the “one project, many systems” approach

TUT-style applied learning often rewards integrated thinking: you can’t treat schedule, risk, quality, stakeholders, and governance separately. PMSA Associate Member readiness benefits from seeing the project as a system where each management area reinforces the others.

This section provides an integrated exam-ready approach using a single coherent practice scenario you can mentally “run” during revision and during your actual assessment/application narrative.

Integrated scenario: a South African project with realistic constraints

Project type: Community facility refurbishment and minor upgrade
Project aim: Refurbish selected facility areas and deliver improved service functionality.
Key constraints:

Tight schedule window due to community usage needs
Stakeholder expectations for transparency and updates
Procurement dependency on contractors and suppliers
Quality compliance requirements for workmanship and safety

Assume you are the planning/support associate assisting the project lead with:

Schedule updates and milestone tracking
Risk monitoring and RAID log updates
Weekly status reporting
Change request tracking and supporting documentation
Stakeholder communication preparation

Build the baseline plan (scope, time, cost) coherently

Scope definition and WBS creation

Your first exam step should be to show how you would create a WBS:

Break refurbishment work into areas (e.g., electrical works, plumbing, finishes, signage, access improvements).
Define deliverables and work packages for each area.
Link each work package to schedule activities and quality acceptance requirements.

Schedule baseline

Identify dependencies (e.g., plumbing before finishes).
Sequence activities logically.
Add buffers where risks are known (procurement lead times).
Approve the baseline under governance.

Cost baseline

Allocate costs per work package.
Include contingency aligned to known risks (e.g., supplier lead time variability).
Forecast regularly.

In exam answers, always show you can link these baselines:

A scope change affects WBS → schedule → cost → risk.

Manage change requests: controlled flexibility

Mid-project, the scenario introduces a change request:

Users request an additional component (e.g., improved signage and a minor access modification).
The request is partly justified by safety and operational needs, but it arrives later than planned.

Your response should:

Log the change formally.
Assess impact on:
- Scope (what’s added/what’s removed)
- Schedule (which activities shift)
- Cost (which budget lines change)
- Quality (what acceptance testing changes)
- Risks (new risk or increased risk)
Propose options (accept, defer, reduce elsewhere).
Obtain approvals via governance.
Update baselines and communicate.

This integrated change response is often the core competency tested for associate-level roles.

Risk monitoring and escalation during execution

Assume you maintain a RAID log (Risks, Assumptions, Issues, Dependencies). During execution:

A risk materialises: a supplier component is delayed.
A new issue appears: stakeholder meetings are delayed due to availability constraints.
An assumption fails: alternative access route availability is different from the initial plan.

Your PMSA-aligned actions:

Update risk probability/impact scores immediately.
Assign owners and define actions with deadlines.
Develop response strategies:
- Procurement mitigation: expedite or alternative supplier (if contract allows)
- Schedule recovery: adjust dependent activities
- Stakeholder mitigation: adjust communication cadence and provide written updates
Escalate through governance if thresholds are exceeded.

In a written answer, you can show maturity by stating:

“We escalated because the delay threatens a milestone and requires decision on trade-offs.”

Quality assurance integration: prevent late defects

During refurbishment, you discover inconsistent workmanship in one area.

A mature integrated response includes:

Stop further affected work and isolate the problem.
Perform root cause analysis (procedure not followed? materials variance? inadequate supervision?).
Implement corrective actions:
- rework if necessary
- update QA checklist
- reinforce workmanship standards
Verify effectiveness via re-tests and sign-offs.
Report quality impact on schedule and cost transparently.

Exams often reward candidates who connect quality to schedule:

Rework changes the activity durations and can alter critical path.

Stakeholder communication: transparency as risk control

Stakeholders expect:

Weekly updates
Clarity on what is on track and what is at risk
A clear process for resolving complaints and change requests

Your communication outputs:

Weekly status report (progress, risks, issues, decisions needed)
Updated milestone dashboard (planned vs actual)
Action log with owners and due dates
Meeting minutes and tracked commitments

A strong answer explains that communication prevents escalation:

When stakeholders understand constraints and trade-offs, acceptance increases.

Close-out and lessons learned: convert experience into improvement

At the end of the project:

Confirm completion against acceptance criteria.
Ensure documentation is complete (handover packs, compliance evidence).
Conduct lessons learned:
- What risks were most impactful?
- Were schedule estimates accurate?
- Did stakeholder communication reduce conflict?
- Which quality controls were most effective?
Create recommendations for future similar projects (template improvements, procurement lead time adjustments, stakeholder engagement schedules).

For PMSA Associate Member preparation, close-out reflection demonstrates professional maturity. It shows you can learn and improve systems, not just “finish tasks.”

Exam-style integrated question practice (with answer structure)

Practise answering in this order:

Identify the management systems involved
- scope/time/cost/quality/risk/stakeholders/governance
State the problem clearly
- “Supplier delay threatens milestone” and “users request extra work”
Explain your plan
- WBS linkages
- schedule recovery approach
- change control process
- risk updates (RAID log)
- quality implications
- stakeholder communication plan
Indicate governance and decision points
- who approves changes
- what escalation threshold triggers steering committee review
Describe outputs/evidence
- updated baselines, change logs, updated risk register, weekly status report, meeting minutes
Describe likely outcomes
- reduced variance after controls
- improved stakeholder alignment

Common pitfalls to avoid (TUT applied learning lens)

Isolated thinking: changing schedule without updating cost and risk.
Incomplete risk response: identifying risks but not assigning owners or actions.
No governance clarity: treating decisions as informal approvals.
Quality as “end of project”: waiting until testing to address process issues.
Vague stakeholder communication: using generic statements rather than structured plans and documented feedback.

Quick revision checklist (PMSA Associate Member readiness)

Use this as your final memory scaffold:

I can explain the project life cycle and governance gates.
I can describe how baselines are created (scope, schedule, cost).
I can explain change control with impact analysis.
I can show risk management is active (RAID log, probability/impact, owners, triggers).
I can report progress with clear indicators and decisions needed.
I can manage stakeholders with tailored communication and documented feedback.
I understand quality assurance vs quality control and non-conformance response.
I know how procurement risks connect to schedule and quality outcomes.
I can close properly with acceptance evidence and lessons learned.

Final Exam Mindset: How to Turn These Notes into Your PMSA Submission

The PMSA Associate Member pathway is best approached as a demonstration of integrated competence: your ability to participate in structured project management, supported by evidence of your role in planning, controlling, communicating, and improving outcomes. Study using scenarios, practise answer structures (especially change control and risk escalation), and maintain a personal evidence bank that links your real work to the management areas described above.

If you want the highest probability of success, your revision should not only improve what you know—it should improve what you can justify: why you chose a specific action, what process you followed, which documents or records exist, and how you measured or observed improvement. That is the professional thinking that aligns with PMSA expectations at associate level and is strongly consistent with university-style project management assessments in South Africa (UNISA/CUT/UKZN/UP/TUT).