Occupational Certificate: Project Manager (CPUT) Full Notes Pack

The Occupational Certificate: Project Manager (CPUT) is a career-focused qualification that blends project management foundations with practical workplace competence. These exam notes consolidate the kinds of knowledge and skills you are expected to demonstrate—planning, risk management, scheduling, stakeholder management, quality control, budgeting basics, reporting, and team coordination. The pack is written in an exam-friendly style for South African learners who may also be studying modules similar to UNISA and CUT course material (e.g., project planning, procurement, and management fundamentals), while staying anchored to the typical outcomes assessed in CPUT occupational programmes.

1) Core Project Management Concepts (CPUT Occupational Certificate Alignment)

Understanding a Project vs a Process vs Operations

A common exam starting point is differentiating a project from a process and operations.

• Project: A temporary endeavour with a defined beginning and end, producing a unique output.
  • Example: Building a small office refurbishment for a client, ending when handover and acceptance occur.
• Process: A set of recurring activities that produce the same result repeatedly.
  • Example: Monthly payroll processing.
• Operations: Ongoing activities that keep the organisation functioning.
  • Example: Customer support desk running daily.

Why it matters in exams: Many competency-based tasks require you to justify why planning tools (WBS, schedule, risk register) are necessary in a project setting, but not in a stable operational environment.

Typical pitfalls:

• Calling something a “project” when it has no end date and no unique deliverable.
• Treating operational repetition as if it required full project governance every time.

Project Lifecycle (What Happens and When)

A project usually moves through stages, though the exact labels differ by methodology (PMBOK, PRINCE2, agile). A practical lifecycle you can use for CPUT-type assessments:

1. Initiation
   • Define problem/opportunity.
   • Identify stakeholders.
   • Preliminary feasibility.
2. Planning
   • Create scope, schedule, budget assumptions.
   • Develop risk plan and quality approach.
   • Plan communication and procurement (if needed).
3. Execution
   • Coordinate resources and team.
   • Manage work packages.
   • Ensure quality checks happen.
4. Monitoring & Controlling
   • Compare actual vs planned.
   • Update schedule and risk register.
   • Track progress and risks.
5. Closure
   • Finalize deliverables.
   • Handover and acceptance.
   • Lessons learned.

Exam tip: When asked “What should a project manager do at this stage?”, match the action to the lifecycle phase, not just to a generic PM habit.

Stakeholders and the Stakeholder Register

A stakeholder is any person, group, or organisation that affects or is affected by the project.

Core stakeholder groups:

• Project sponsor / management
• Client / end users
• Project team members
• Suppliers / contractors
• Regulators / authorities
• Community / beneficiaries
• Internal departments (finance, HR, procurement)

A stakeholder register typically includes:

• Name / group
• Role (sponsor, client, contractor, etc.)
• Interest level (high/medium/low)
• Influence level (high/medium/low)
• Requirements / concerns
• Engagement strategy (inform, consult, involve, manage closely)

Concrete example (refurbishment project):

• Building facilities manager: high influence (access, maintenance)
• End users (staff): high interest (work disruptions)
• Municipal inspector: low interest until approvals, but high influence at compliance stage

Why this matters: Exams often test whether you can identify stakeholder communication needs—e.g., weekly updates for high-interest groups, formal documentation for regulators.

Triple Constraint: Scope, Time, Cost

A classic project management concept: you can’t change one of the triangle sides without affecting at least one other.

• Scope: What deliverables and work is included/excluded.
• Time: How long the project takes.
• Cost: Budget and resource expenditure.

Scenario question practice:
If a client requests a new feature mid-way:

• Scope increases
• You must either extend time or increase cost—or negotiate both
• Without change control, you risk cost overruns and delays

Change Control and Version Control

Many occupational certificate assessments include the ability to manage change formally.

Change control should include:

1. Request
   • Who requested? What change?
2. Impact analysis
   • Scope impact, schedule impact, cost impact, quality impact, risk impact
3. Approval
   • Who has authority?
4. Implementation plan
   • Update documents (schedule, WBS, budget)
5. Communication
   • Tell affected parties
6. Record keeping
   • Maintain change logs and version history

Version control examples:

• Contract documents updated after approval
• Project plan revised after schedule changes

Work Breakdown Structure (WBS) Basics

A WBS breaks the project into manageable work packages.

How to think about it:

• Start from deliverables (outputs)
• Break deliverables into sub-deliverables
• Continue breaking until tasks are manageable (often aligned to responsibility)
• Each work package should be:
  • Clearly defined
  • Assignable to someone/team
  • Scheduled and costed (at least at planning level)

Exam exercise style:
You may be given a project description and asked to propose:

• 3–5 major deliverables
• 6–15 sub-items under each deliverable
• A short description for each work package

Common mistake: Building a WBS out of activities without linking them to deliverables. Deliverables-based WBS is typically stronger.

2) Project Planning and Scheduling Skills (CPUT Practical Focus)

Scope Definition and Statement of Work (SOW)

Planning starts with scope. Scope includes deliverables and boundaries: what is included and what is excluded.

A good Scope Statement should cover:

• Project objectives (high-level)
• Deliverables (what will be produced)
• Inclusions/exclusions
• Assumptions and constraints
• Acceptance criteria (how you know deliverables are done)
• Stakeholder requirements summary

In many workplace tasks, you’re expected to read a Statement of Work and identify:

• Key deliverables
• Milestones
• Responsibilities
• Reporting requirements

Acceptance criteria example:

• “The refurbished office is completed and passed inspection with electrical compliance certificates, and handover documentation is delivered.”

Planning Deliverables and Milestones

A milestone is a significant point in time, usually tied to completed outputs.

Examples:

• “Survey completed”
• “Design sign-off received”
• “Materials ordered”
• “Electrical works completed”
• “Handover and client acceptance”

Why milestones are exam-worthy: They are used for progress tracking; you can’t “almost complete” a milestone without clear evidence.

Estimating Time and Effort (Simple and Defensible)

Exams often reward estimations that are:

• Transparent
• Based on assumptions
• Tied to work packages

Estimation approaches you may reference:

• Expert judgment (experienced team members)
• Historical data (similar projects)
• Three-point estimates (optimistic/most likely/pessimistic)
• Bottom-up estimation (sum of work package durations)

A useful simple method for exam questions:

• Break into work packages
• Estimate duration per work package
• Adjust for dependencies

Dependencies: Finish-to-Start and Beyond

Scheduling relies on identifying relationships between tasks:

• Finish-to-Start (FS): Task B starts when Task A finishes.
• Start-to-Start (SS): Task B starts when Task A starts.
• Finish-to-Finish (FF): Task B finishes when Task A finishes.
• Start-to-Finish (SF): Rare; Task B finishes when Task A starts.

In a refurbishment example:

• Painting (Task B) cannot start until plastering (Task A) is completed: FS dependency
• Electrical fixture selection can begin early with design: SS dependency (selection starts when design starts)

Critical Path Method (CPM) / Network Logic (Conceptual)

You may not need full numeric CPM calculations, but you should understand:

• The critical path is the longest sequence of dependent tasks determining project duration.
• If any critical path task slips, the end date slips (unless crashing or re-planning occurs).

Exam scenario:
You have a network of tasks. Identify which tasks are on the longest dependency chain.

Gantt Charts and Schedule Updates

A Gantt chart visualises tasks over time.

Key elements:

• Bars showing start and finish dates
• Milestones (often diamonds or markers)
• Dependencies (arrows/lines)
• Progress shading or % complete

Schedule updating:

• Use actual progress data
• Adjust remaining duration
• Re-check dependencies
• Update forecast completion date

Common exam trap: “If task A is 50% done, then the whole project is 50% done.” This is false—schedule progress must reflect critical tasks and milestones.

Resource Planning and Resource Levelling

Resource planning answers:

• Who does the work?
• When do they start and finish?
• How much effort is required?

Resource constraints in real workplaces:

• Limited skilled electricians
• Limited budget for materials
• Limited project manager time
• Overlapping projects

Resource levelling aims to:

• Reduce resource over-allocation
• Maintain feasible schedule without unrealistic assumptions

Cost Basics and Budgeting (High-Level, Occupational Level)

Even if the occupational certificate does not require full cost engineering, you must demonstrate understanding of cost planning fundamentals:

• Budget is the planned spending baseline.
• Costs can be:
  • Labour
  • Materials
  • Equipment
  • Subcontractors
  • Overheads
  • Contingency

Contingency: A buffer for identified-unknowns and estimation uncertainty (not for ignoring risks).

A typical exam structure:

1. Identify cost drivers in scope
2. Assign costs to work packages
3. Sum to total budget
4. Include contingency based on risk level

Quality Planning: Doing it “Right the First Time”

Planning includes quality, not only schedule.

A practical quality plan should mention:

• Standards and specifications (client requirements or regulatory standards)
• Quality assurance (process checks)
• Quality control (inspection/verification)
• Acceptance criteria
• Documentation required (reports, certificates)

Example quality checks:

• Electrical compliance certificate after installation
• Dimensional checks after structural work
• Functional test after commissioning

Why quality belongs in planning: If you plan quality checks too late, you discover defects after rework becomes expensive.

Communication Plan and Reporting Cadence

A communication plan defines:

• What information is shared
• With whom
• How often
• By which channel
• Who prepares it

Typical project reporting:

• Weekly progress report to sponsor
• Daily coordination meetings with team
• Risk review meetings (e.g., bi-weekly)
• Stakeholder updates at milestones

Report content (minimum exam-friendly elements):

• Progress vs plan (tasks/milestones)
• Issues and risks
• Decisions required / approvals needed
• Next-week forecast
• Changes since last report (if any)

3) Project Execution, Monitoring & Controlling (Managing Performance)

Executing Work Packages and Managing the Team

Execution is where the project plan becomes reality.

Key execution activities:

• Assign tasks to responsible persons
• Provide resources and instructions
• Coordinate subcontractors
• Ensure compliance with quality plans
• Maintain documentation

In an occupational certificate context, you may be assessed on:

• How well you coordinate work
• Whether you escalate issues
• How you keep communication professional and clear

Case-style example (team coordination):
During a refurbishment:

• Plastering crew completes work earlier than planned
• Painting crew is waiting on materials delivery
• Project manager must adjust schedule (swap task order if possible) and track risk of delayed procurement

Monitoring and Control: Measuring Actual Performance

Monitoring involves collecting data:

• % complete of work packages
• milestone attainment
• time spent vs planned
• defect counts and rework
• risk status changes

Controlling involves actions:

• Update schedule and forecasts
• Manage changes via change control
• Address root causes of issues
• Re-plan resources if constraints change

Issue Management vs Risk Management

Exams often confuse these. Clear definitions help.

• Risk: A potential future event that may occur.
  • Example: “Materials may be delayed due to supplier backlog.”
• Issue: A problem that has already occurred.
  • Example: “Materials delivery is now 5 days late.”

Response actions:

• For risks: implement preventive/contingency plans
• For issues: solve root cause, document impact, and prevent recurrence

Risk Management Framework

A robust risk framework includes:

1. Risk identification
   • Workshops, checklists, lessons learned
2. Risk analysis
   • Likelihood and impact
3. Risk evaluation
   • Prioritise (e.g., high-likelihood/high-impact first)
4. Risk response planning
   • Avoid, mitigate, transfer, accept
5. Risk monitoring
   • Track triggers and changes
6. Documentation
   • Maintain risk register

Likelihood and Impact (Simple Scales)

A common exam scoring approach uses a 1–5 scale.

Example:

• Likelihood: 1 (rare) to 5 (almost certain)
• Impact: 1 (minor) to 5 (catastrophic)

Then compute:

• Risk score = Likelihood × Impact

Example risk register snippet (conceptual):

Risk	Likelihood (1-5)	Impact (1-5)	Score	Response
Supplier delays materials	4	4	16	Mitigate: dual sourcing; Contingency: alternate brands
Labour shortage	3	3	9	Mitigate: schedule adjustment; cross-train team

(If numbers are used in exam tasks, be consistent and show your scoring logic.)

Change Requests and Re-baselining (When Plans Must Move)

A project baseline is the approved plan for scope, schedule, and cost. If changes are significant, you may need re-baseline procedures.

Actions:

• Submit change request
• Approve or reject
• If approved: update baseline (after formal approval)
• Communicate change and update documentation

Exam scenario prompt:

• Client requests additional work; approval granted.
• What documents must change?
  • Schedule, scope statement, WBS, budget estimate
  • Risk register (new risks)
  • Quality plan (new deliverables may need inspection points)

Progress Tracking with Milestones

Progress tracking relies on evidence.

Methods:

• Milestone sign-off
• Deliverable verification
• Work package acceptance records
• Timesheets and progress evidence

Why evidence matters: Without evidence, claims of progress are unreliable.

Handling Project Delays: Practical Corrective Actions

When a critical path task delays:

• Determine cause (weather, procurement, labour, design change)
• Assess impact (how many days and what tasks affected)
• Choose response:
  1. Re-sequence tasks (fast tracking if feasible)
  2. Add resources (crashing) within budget
  3. Extend schedule if justified and approved
  4. Reduce scope (only with change control)

Fast tracking example:

• Start painting before plaster fully cures (not recommended if quality standards require full cure). This becomes a quality risk.

Crashing example:

• Use additional labourers for plastering, but check if quality and supervision capacity remains sufficient.

Quality Control in Execution

Quality control is the operational side of quality.

Common tools:

• Inspection checklists
• Testing and verification records
• Review meetings at key points
• Non-conformance reporting (defects, deviations)

Non-conformance handling:

1. Identify defect
2. Record issue and impact
3. Corrective action plan
4. Re-inspection after correction
5. Prevent recurrence (update process or training)

Documentation and Records Management

Occupational assessments often expect document competence, including:

• Version-controlled documents
• Change log entries
• Risk register updates
• Meeting minutes
• Daily work reports
• Handover pack for closure

Typical closure documents:

• Final deliverables
• As-built drawings/specifications (if relevant)
• Certificates (e.g., compliance)
• Final project report
• Lessons learned summary

Contractor/Subcontractor Management (Practical Expectations)

If the project includes subcontractors:

• Ensure contract scope aligns with project scope
• Confirm deliverables, timelines, and quality standards
• Monitor performance:
  • On-time delivery
  • Quality compliance
  • Safety requirements
• Manage variations via change control

Exam style example:

• Subcontractor claims delay due to client-supplied materials.
• Project manager response should:
  • Verify facts and dates
  • Check contractual responsibility
  • Document the impact on schedule
  • Submit claim/change request if required

4) Project Communication, Leadership, Ethics, and Exam-Style Competencies

Leadership as a Project Manager Competency

A project manager is not only a planner; they lead people and coordinate outcomes.

Key leadership behaviours:

• Set direction (clear objectives and priorities)
• Communicate consistently
• Build trust and accountability
• Coach team members
• Manage conflict professionally

Exam scenario:

• Two team members disagree on task order.
• Strong response:
  • Reference the project schedule and dependencies
  • Check quality implications
  • Decide and document rationale
  • Communicate the decision to both parties

Stakeholder Engagement: Managing Expectations

Stakeholders have different expectations:

• Sponsor wants value and progress
• Client wants deliverables and compliance
• Team wants clarity and manageable workload
• Regulators want compliance proof

Stakeholder management requires:

• Tailored communication frequency and format
• Transparent risk and issue communication
• Documentation of decisions

Engagement strategy based on influence/interest:

• High influence & high interest: manage closely, frequent updates
• High influence & low interest: keep informed, fewer updates
• Low influence & high interest: consult and communicate
• Low influence & low interest: monitor with minimal communication

Conflict Management and Negotiation

Projects frequently involve competing needs.

Common conflict sources:

• Resource allocation (who gets the electrician?)
• Schedule priorities (which work package first?)
• Scope interpretation (what’s included?)
• Quality disputes (is this acceptable deviation?)

Conflict handling steps:

1. Listen and clarify facts
2. Identify interests and constraints
3. Refer to documented scope/standards
4. Propose options and trade-offs
5. Agree on decision and document it
6. Follow up and monitor outcome

Ethics, Professional Conduct, and Safety Culture

Occupational certificates strongly emphasise ethical competence and professional conduct.

Ethics in project management includes:

• Honesty in reporting progress and risks
• Avoiding misrepresentation of completion percentages
• Managing conflicts of interest
• Respecting confidentiality
• Following safety and regulatory requirements

Safety considerations:

• Risk assessments for workplace hazards
• PPE requirements
• Incident reporting and corrective action

Exam example:
If a defect is discovered, hiding it for schedule reasons is unethical and increases later costs.

Professional Communication: Writing That Gets Results

Exams sometimes test your ability to structure communication. Use professional formats:

Progress report structure

1. Overview (project status)
2. Milestones achieved this period
3. Work completed vs planned
4. Issues encountered
5. Risks and mitigation actions
6. Forecast for next period
7. Decisions needed (if any)

Meeting minutes structure

• Date/time/location
• Attendees
• Agenda items
• Decisions taken
• Actions (owner and due date)
• Risks/issues raised

Presentation Skills in Workplace Contexts

If your assessment includes oral or practical components:

• Use clear language
• Avoid jargon unless required
• Support claims with evidence (dates, milestones, risk status)
• Show options and justify recommended action

Alignment with South African University Study Themes (UNISA / CUT-style Learning)

South African universities often assess similar project-management and management themes, even if module names differ. Learners in UNISA and Cape Peninsula University of Technology (CPUT) frequently encounter planning logic, report writing, and competency-based workplace tasks.

You may see knowledge comparable to:

• Project planning logic and risk considerations found in management and project modules (varies by department)
• Leadership and performance measurement ideas connected to general management education
• Case analysis skills (interpreting scenarios and proposing actions)

Exam writing approach that fits these styles:

• Start with a definition (what/why)
• Apply to the given scenario (what should you do)
• Justify using the project management concept (why your action is correct)
• Note consequences and follow-up actions

Exam-Style Competency Mapping (How to Score High)

Occupational certificates often evaluate “competence demonstration” rather than memorised theory. To score high, your answers should include:

1. Correct concept
2. Applied example
3. Evidence / documentation references
4. Clear next steps
5. Risk and quality considerations
6. Communication and stakeholder handling

Example answer skeleton (for a scenario):

• Identify problem/requirement
• State relevant planning tool (WBS, risk register, schedule update)
• Show how to manage impact (scope/time/cost)
• Explain quality and stakeholder communication
• Conclude with next steps and documentation

5) Integrated Case Study Practice (Complete Scenarios for CPUT Occupational Certificate)

Case Study Overview: “Refurbish and Re-open Client Office”

To practise integrated thinking, consider a realistic workplace scenario that combines many typical exam requirements.

Project: Refurbish a small client office for re-opening.
Key deliverables:

1. Site readiness and approvals
2. Electrical installation and compliance testing
3. Flooring and wall finishes
4. Painting and final internal fit-out
5. Documentation and client handover

Time window (planned): 6 weeks total.
Milestones:

• M1: Survey and design sign-off
• M2: Electrical work completed and tested
• M3: Finishes completed (flooring/walls)
• M4: Final painting complete
• M5: Handover and acceptance

Assume a simplified task dependency network with:

• Electrical inspection must pass before final wall finishes
• Painting follows finishes completion
• Handover requires completion evidence and certificates

Planning Inputs: Scope, Stakeholders, Risks

Stakeholder list (example used consistently)

• Sponsor: Client Managing Director
• Client representative: Office Manager
• Project execution team: Project Team (CPUT learner cohort simulated)
• Subcontractor: Electrical Contractor
• Authority: Municipal Inspector
• Internal support: Finance Officer

Scope assumptions and constraints (example)

• Materials will be purchased based on approved specifications.
• Electrical work must meet compliance requirements.
• The office must remain secure; restricted access times exist.

Risks (example risk register entries)

1. Supplier delay for finishing materials
2. Labour shortage for skilled painting crew
3. Inspection rescheduling due to municipal inspector availability
4. Quality defects leading to rework (e.g., uneven plaster)

For each risk, responses must be planned:

• Mitigate: dual sourcing, buffer stock, backup suppliers
• Contingency: adjust schedule, reserve inspection slots, hold additional internal quality checks
• Escalate: early communication to authority and sponsor

Scheduling and Milestone Logic (Mock Network Reasoning)

A simplified schedule logic used for practice:

1. Survey and design sign-off (M1) must happen before ordering and start of electrical works.
2. Electrical installation must occur before inspection.
3. After electrical testing (M2), wall finishes can proceed.
4. After finishes (M3), painting can be completed (M4).
5. After painting and final checks, handover documents enable acceptance (M5).

If M2 slips:

• M3 cannot happen
• M4 and M5 are delayed unless corrective actions restore schedule

Exam question possibility: “Which tasks are critical and why?”
Answer should mention the dependency chain tied to milestones.

Budgeting and Cost Control (Conceptual with Example Numbers)

Assume a simplified budget split for the 6-week project:

• Labour: R 120,000
• Materials: R 80,000
• Subcontractors: R 90,000
• Equipment & consumables: R 10,000
• Contingency (for risks): R 20,000

Total planned budget: R 320,000

If a material supplier delay occurs and you need an alternate supplier at higher cost:

• Contingency is reduced
• If contingency is not enough, change control may be required (increase budget or reduce scope)

Exam best practice: When introducing cost impacts, always link them to risk or change events, and state how they affect the baseline.

Execution Phase Events and How to Respond (Issue vs Risk)

Event 1: Supplier delay triggers an issue

• Planned delivery: Day 10
• Actual delivery: Day 15

This is an issue because it has already occurred. You must:

1. Update schedule for affected work packages
2. Reassess critical path impact
3. Decide response:
   • Use contingency: purchase alternate finishing materials
   • Re-sequence tasks: complete other readiness activities in the meantime
4. Communicate to sponsor and client representative

Progress report snippet (exam-style):

• “M2 remains on track assuming electrical testing remains available on the planned inspection date.”
• “Finishes start is impacted by supplier delay; mitigation includes resequencing and alternate supplier procurement.”
• “Contingency will be adjusted accordingly.”

Event 2: Municipal inspector rescheduling

• Inspection was planned for Day 18
• Rescheduled to Day 22

This is an issue with schedule impact.
Corrective actions:

• Confirm new inspection availability in writing
• Update schedule and communicate revised dates
• Prevent rework by ensuring the electrical work is fully ready for inspection when the inspector arrives
• Consider internal quality checks to reduce risk of failure at inspection

Quality Control Incident and Corrective Action

Assume after wall finishes, a quality defect is discovered:

• Uneven surface requires rework

This becomes a non-conformance issue.
Steps:

1. Record defect with location and severity
2. Assess impact:
   • Time impact: rework duration
   • Cost impact: labour and materials
   • Quality impact: compliance with specification
3. Implement corrective action:
   • Rework plaster/fill and re-level
4. Re-inspection:
   • Ensure readiness before painting
5. Prevent recurrence:
   • Add an earlier finishing checklist for future work packages

Exam scoring: Don’t just state “fix it.” Show the structured chain: record → assess → corrective action → verification → update plan.

Change Control: Client Adds an Upgrade

At Week 3, the Office Manager requests an upgrade:

• Replace standard door handles with premium handles
• Also requests minor aesthetic changes around trims

This is scope change requiring change control:

1. Draft change request
2. Impact analysis:
   • Scope: yes
   • Time: small extension (e.g., 1–2 days for procurement/fit)
   • Cost: additional cost for premium handles
3. Approval:
   • If sponsor approves, update scope and baseline
4. Update schedule and budget:
   • Reduce or use contingency accordingly
5. Communicate:
   • Inform team and relevant subcontractors

Consistency requirement: If you claim additional cost is taken from contingency, contingency must be adjusted consistently in your plan narrative. For instance:

• Contingency initial amount: R 20,000
• If handles cost an extra R 6,000, remaining contingency becomes R 14,000

Communication and Reporting in the Case Study

Deliver communication outputs as exam evidence:

1. Weekly progress report
2. Risk and issue update section
3. Change log entry for upgrade request
4. Meeting minutes excerpt with action items

A realistic “Weekly Progress Report” (mock):

• Status: On track for electrical milestone with risk “inspection rescheduled”
• Completed work: Survey completed (M1 achieved), electrical installation completed
• Issues: Supplier delay for finishes; inspection rescheduled to Day 22
• Actions:
  • Electrical readiness checklist completed by Day 21
  • Alternate material procurement in progress to protect M3
• Next milestones:
  • M2 verification by new inspection date
  • M3 targeted immediately after inspection sign-off

Lessons Learned and Closure

Closure includes:

• Final acceptance and handover
• Documentation compilation:
  • compliance certificate(s) from inspection
  • completion report
  • as-built or confirmation documentation (as applicable)
• Final budget reconciliation (planned vs actual at high level)
• Lessons learned:
  • What worked (e.g., early readiness checklist reduced inspection delay risk)
  • What didn’t (e.g., single supplier for finishing materials)
  • Recommendations:
    • Always keep dual sourcing for long-lead items
    • Lock inspection dates earlier and have backup slot agreements

Exam closure emphasis: Lessons learned must be tied to specific events from the scenario (supplier delay, inspection rescheduling, quality rework, and change request).

Additional Exam Resources Embedded into Practice

How to Answer “Explain” Questions

Use the pattern:

1. Define the concept
2. List key components (3–6 points)
3. Provide an example relevant to a project context
4. State why it matters (impact on time/cost/quality)

How to Answer “Discuss” Questions

Discuss should show:

• Importance
• Benefits
• Limitations and counter-arguments
• What conditions make it effective

Example counter-argument style:

• “A change request should not be rejected automatically; however, approvals must follow impact analysis to prevent uncontrolled scope growth.”

How to Answer “Apply” Questions (Scenario Problems)

Application answers require:

• Correct tool: WBS, risk register, schedule update, change control
• Direct mapping to scenario facts (dates, milestones, stakeholders)
• Concrete actions with sequencing
• Evidence of understanding impact (scope/time/cost and quality)

Quick Reference Checklists (CPUT Exam-Ready)

Project Manager Checklist: Before Execution

• Scope defined (includes/excludes)
• Stakeholder register completed
• WBS developed for deliverables and work packages
• Schedule drafted with dependencies and milestones
• Risk register created with responses
• Quality plan defined with acceptance criteria
• Communication plan agreed (frequency and recipients)
• Budget estimated per work package with contingency

Project Manager Checklist: During Execution

• Resources assigned to work packages
• Quality checks performed according to plan
• Progress tracked against milestones
• Risks monitored; register updated
• Issues logged; root cause investigated
• Change control followed for scope/time/cost impacts
• Stakeholders informed through the communication plan

Project Manager Checklist: During Closure

• Deliverables verified and accepted
• Compliance documents compiled
• Final report produced (progress, issues, risks, changes)
• Budget reconciliation (high level acceptable unless specified)
• Lessons learned captured
• Handover completed and recorded

Consistent Keyword Coverage for CPUT + South African Exam Styles

To match common CPUT project management occupational certificate expectations—and the broader themes tested in South African university management/project-learning—ensure your study includes mastery of these keywords:

• scope, milestones, WBS, dependencies, critical path (conceptual), Gantt chart
• risk register, likelihood/impact scoring, contingency plans
• issue management, corrective action, non-conformance
• change control, baseline, version control
• quality assurance vs quality control
• stakeholder engagement, communication plan
• report writing, meeting minutes, progress tracking
• closure, handover, lessons learned

This language is not just theory; it becomes your “exam operating system” for scenario questions.

End-to-End Master Summary (High Impact Revision)

A project manager in the CPUT Occupational Certificate: Project Manager context must demonstrate capability across the full project lifecycle: planning (scope, WBS, schedule, risks, quality, communication), executing and coordinating resources, monitoring and controlling performance (progress vs plan, risks and issues, quality verification), managing change formally (impact analysis and approvals), and closing properly (acceptance, documents, lessons learned). Strong answers connect concepts to workplace scenarios with clear sequencing, documented actions, and stakeholder-aware communication—showing not only what should be done, but how it should be done and recorded.