CPUT Short Course in Project Management Level 1 Notes (CPUT) — Project Planning, Scheduling & Basic Risk/Cost Control (MNG0001–style Exam Focus)

These CPUT Short Course in Project Management Level 1 Notes provide a structured, exam-ready set of concepts, definitions, and practical tools aligned to what South African students commonly prepare for when they study project management modules such as CPUT project management short courses and related undergraduate units (e.g., management/business studies entry-level modules with planning/scheduling/risk/problem-solving content often assessed similarly to MNG 0001-style introductory management papers). The notes focus on building competence in project initiation, scope definition, work breakdown, scheduling, cost estimation, risk assessment, stakeholder communication, and basic monitoring/control.

Across the document, examples are anchored in realistic scenarios typical of South African workplaces—small construction projects, departmental IT upgrades, and community development initiatives—so that you can translate theory into answers during tests and assignments.

Section 1: Project Management Foundations (CPUT Level 1 Focus)

A project is a temporary endeavour undertaken to create a unique product, service, or result. At CPUT Short Course in Project Management Level 1, the emphasis is usually on understanding what makes projects different from routine operations, and on mastering the core vocabulary used in short-course assignments and exams.

What a “Project” Is (and What It Is Not)

A strong exam answer starts with clear distinctions:

• Project (temporary):
  • Has a defined beginning and end.
  • Produces a unique output (even if similar projects exist).
  • Has constraints, typically including time, cost, and scope.
• Operations (ongoing):
  • Continuous, repetitive processes.
  • Focus on maintaining output quality and delivering services day after day.

Common Level 1 misconceptions

• Misconception 1: “Any task is a project.”
  • Correction: A project has coordination and a unique outcome.
• Misconception 2: “Project management is only about timelines.”
  • Correction: It includes scope, cost, risk, quality, procurement, people, and communication—timelines are only one piece.

Core Project Management Concepts You Must Know

At Level 1, candidates are often assessed on definitions and basic process understanding. Use crisp, structured language.

Key terms

• Stakeholders: Anyone who can affect, be affected by, or is interested in the project outcome (sponsor, client, team members, suppliers, community).
• Scope: The boundaries of what the project will and will not deliver.
• Deliverables: Tangible outputs (e.g., “training session completed,” “code deployed,” “site health-and-safety plan implemented”).
• Constraints:
  • Time constraint (deadline).
  • Cost constraint (budget limit).
  • Scope constraint (must deliver specific requirements).
• Assumptions and risks:
  • Assumptions are “supposed to be true” facts without proof yet.
  • Risks are uncertainties that could affect objectives positively or negatively.

Project Life Cycle and Phases (Typical Level 1 Model)

Most introductory course notes teach a life cycle that looks like this:

1. Initiation
   • Identify the problem/opportunity.
   • Appoint project sponsor/manager (or at least define responsibilities).
   • Define the high-level project objective.
2. Planning
   • Define scope, deliverables, and work.
   • Estimate time and cost.
   • Identify risks and plan responses.
   • Build schedule and basic management plans.
3. Execution (Implementation)
   • Coordinate resources.
   • Carry out work packages.
   • Manage quality and communication.
4. Monitoring & Controlling
   • Track progress against baseline plans.
   • Manage changes and corrective actions.
5. Closing
   • Obtain acceptance of deliverables.
   • Evaluate performance.
   • Document lessons learned.

A high-mark answer explains that monitoring/control is ongoing during execution, not a separate “end phase”.

The Triple Constraint and Why It Matters

The classic triple constraint is:

• Scope
• Time
• Cost

If one changes, at least one of the others typically changes. For example:

• Increase scope → either increase time or cost (or reduce quality).
• Reduce time deadline → either add cost (overtime/more resources) or reduce scope/quality.

In Level 1 exams, you may be asked:

• “Explain the triple constraint in your own words.”
• “Give an example of how changing one constraint affects the others.”

Example (South African workplace)

A municipal department wants to upgrade a public library’s computer lab:

• Original scope: 20 computers + network setup.
• Deadline: 6 weeks before school holidays.
• Budget: fixed.
  If the client requests 10 additional computers (scope increase), the project manager can:
• extend the timeline (cost unchanged), or
• buy additional computers (cost increase), or
• reduce other elements (scope reduction elsewhere), such as delaying training.

Basic Stakeholder Analysis (Level 1 Entry Skill)

Because Level 1 includes communication basics, stakeholder analysis is essential.

Simple stakeholder categories

• Sponsor: Provides funding/authority; expects benefits and accountability.
• Client/User: Defines requirements; approves deliverables.
• Project team: Executes work; needs clarity and resources.
• Suppliers/contractors: Provide goods/services; influence schedule and cost.
• Regulators/community: May impose compliance requirements and social impact considerations.

Level 1 stakeholder analysis method

Create a table (in an exam, you can present as bullet points) with:

• Stakeholder name/role
• Interests/requirements
• Influence/authority
• Likely concerns
• Communication needs (frequency, format)

Skills of a Project Manager at Level 1

While advanced project management includes technical methodologies, Level 1 typically focuses on foundational competencies:

• Planning thinking: Convert objectives into activities and deliverables.
• Communication: Clear updates, meeting notes, and status reports.
• Organising work: Break work into manageable tasks.
• Risk awareness: Identify uncertainties early and plan responses.
• Problem-solving: Address deviations quickly and logically.
• Time awareness: Build schedules that reflect real constraints.

Micro-example: “Status reporting”

A Level 1 project manager should be able to say:

• What was completed last week?
• What will be completed next week?
• Are we on track for time/cost/scope?
• What issues or risks need escalation?

Section 2: Project Initiation & Planning Essentials (Scope, WBS, Scheduling Basics)

This section builds the practical backbone of CPUT Short Course in Project Management Level 1. Many students lose marks because they can define terms but cannot produce exam-ready structure: scope clarity, work breakdown, and schedule logic.

Problem Statement → Objectives → Deliverables

A strong initiation/planning answer shows a chain of logic:

1. Problem/opportunity
2. Project objective(s)
3. Deliverables that satisfy objectives
4. Work activities that produce deliverables

Example scenario used for planning logic (consistent throughout)

Scenario: “CTL Renovation & Training Setup”
A small department at a South African TVET/college wants:

• Renovation of a training room (basic improvements)
• Installation of a projector and laptops
• A short staff training session so the room can be used immediately after completion

Project goal (high level):
Make the training room fully operational by the start of the next term.

You will use this scenario across multiple sections to demonstrate planning tools.

Writing Project Objectives (SMART)

Objectives in Level 1 are often expected to be SMART:

• Specific
• Measurable
• Achievable
• Relevant
• Time-bound

Example objectives for the scenario

• Specific: Renovate walls, improve lighting, paint room.
• Measurable: Complete painting of designated surfaces; install 1 projector and 10 laptops.
• Achievable: Use selected contractors and approved suppliers available locally.
• Relevant: Supports departmental training delivery.
• Time-bound: Finish all installations by Week 6 and training by Week 7.

Even if an exam question does not ask for SMART explicitly, you can often include it to strengthen answers.

Scope Definition: Inclusions and Exclusions

Scope can be expressed using:

• Inclusions: What will be delivered.
• Exclusions: What will not be delivered (prevents “scope creep”).

Example scope for the CTL Renovation & Training Setup project

In scope:

• Basic painting and lighting improvements.
• Installation of projector and configuration for presentations.
• Setup of 10 laptops (accounts + basic software).
• One staff training session: 2–3 hours on how to use the equipment and access training materials.
• Basic documentation: equipment user guide and simple maintenance checklist.

Out of scope:

• Major structural changes (e.g., re-building walls).
• Upgrading internet bandwidth beyond existing capacity.
• Developing new training content (only use existing materials provided by the department).

Work Breakdown Structure (WBS)

A Work Breakdown Structure (WBS) is a hierarchical decomposition of the project into smaller components:

• Project
  • Major deliverables
    • Work packages
      • Activities/tasks

Why WBS is scored heavily in Level 1

Because it demonstrates:

• clarity of deliverables,
• ability to plan work logically,
• basis for estimating time/cost.

Example WBS for the CTL Renovation & Training Setup project

Level 1 (Project): CTL Renovation & Training Setup

Level 2 (Major Deliverables):

1. Room Renovation
2. Equipment Installation
3. Training Session & Documentation

Level 3 (Work packages):

1. Room Renovation

   • 1.1 Procurement of paint and materials
   • 1.2 Surface preparation (cleaning, sanding)
   • 1.3 Painting (walls/ceiling surfaces as defined)
   • 1.4 Lighting improvement (replace/balance lighting units)
   • 1.5 Final inspection for completion readiness

2. Equipment Installation

   • 2.1 Projector setup and mounting
   • 2.2 Laptop setup (imaging, login creation)
   • 2.3 Software installation (presentation tools and basic learning platform access)
   • 2.4 System testing (projector alignment + laptop connectivity)

3. Training Session & Documentation

   • 3.1 Schedule and invite staff participants
   • 3.2 Deliver training session
   • 3.3 Create user guide and maintenance checklist
   • 3.4 Obtain sign-off/acceptance

In an exam, a diagram-like WBS with numbering (1.1, 1.2, etc.) is usually appreciated because it signals methodical thinking.

Estimating: Time and Effort (Level 1 Practical Logic)

At Level 1, you may not need advanced techniques like PERT/Monte Carlo, but you must understand estimation logic:

• Use historical data where possible.
• Consider resource availability.
• Identify dependencies (what cannot start until something else finishes).

Estimation terms

• Duration: How long a task takes.
• Effort: Total work time (person-hours/days); effort can be spread across multiple people.
• Dependencies:
  • Finish-to-start (FS): Task B starts after 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.

Building a Basic Schedule

Most Level 1 exams test your ability to create a sensible sequence and interpret a simple schedule.

Example activity list with durations (consistent model)

Assume the following durations for the CTL project:

Room Renovation

• 1.1 Procurement of paint and materials: 1 week
• 1.2 Surface preparation: 1 week
• 1.3 Painting: 2 weeks
• 1.4 Lighting improvement: 1 week
• 1.5 Final inspection readiness: 0.5 week

Equipment Installation

• 2.1 Projector setup and mounting: 1 week
• 2.2 Laptop setup: 1.5 weeks
• 2.3 Software installation: 1 week
• 2.4 System testing: 0.5 week

Training & Documentation

• 3.1 Schedule and invite staff: 0.5 week
• 3.2 Deliver training session: 1 week
• 3.3 Create user guide & maintenance checklist: 0.5 week
• 3.4 Sign-off/acceptance: 0.5 week

Dependencies (typical assumptions)

• Surface preparation (1.2) needs procurement (1.1) → FS.
• Painting (1.3) needs surface preparation (1.2) → FS.
• Lighting improvement (1.4) can occur after procurement (1.1) but may require room readiness; simplest assumption FS after 1.2.
• Final inspection readiness (1.5) needs painting and lighting work.
• Projector mounting (2.1) can happen after some room readiness; simplest: after procurement and basic surfaces done; for Level 1, use FS after 1.4.
• Laptop setup (2.2) can start when laptops and required materials are available; assume procurement occurs in renovation phase, but realistically could be parallel—Level 1 often allows parallel planning. For this model, assume laptops arrive around Week 2.
• Software installation (2.3) depends on laptop setup (2.2).
• System testing (2.4) depends on projector and laptop/software.
• Training scheduling (3.1) depends on near-completion of room and equipment readiness; assume FS after 2.4.
• Training session (3.2) depends on equipment testing (2.4).
• Documentation (3.3) can run partially during training prep; assume FS after 2.4 for accuracy.
• Sign-off (3.4) after training delivery (3.2).

Critical Thinking: Schedule Reasonableness and “What Can Go Wrong”

Level 1 should train you not just to list tasks but to justify sequencing.

Example question style

“Why might the schedule be unrealistic?”

Possible answers:

• Procurement may take longer than assumed.
• Contractors may be unavailable.
• Equipment delivery may be delayed.
• Staff availability for training could conflict with workloads.
• Room may not be accessible due to other campus activities.

In exam responses, you score marks for:

• identifying plausible causes,
• linking cause to task delays,
• proposing mitigation (e.g., buffer time, alternative supplier, early scheduling).

Basic Quality Planning (Even in a Level 1 Schedule)

Some modules include “quality” basics. You don’t need to cover complex standards, but you should:

• define acceptance criteria,
• plan inspections,
• use checklists for installations.

Example acceptance criteria

• Painting: no visible patchiness on specified surfaces; correct number of coats.
• Lighting improvement: each designated light fixture works; brightness acceptable.
• Projector: aligned display within acceptable keystone limits.
• Laptops: successful login, correct software installed, projector connectivity verified.
• Training: participants demonstrate basic competency (e.g., can start a presentation, access learning platform).

Section 3: Costing, Budgeting, Procurement, and Baseline Control (Level 1 Mechanics)

This section turns planning into costing and control. Many students struggle when questions require numbers, even basic ones. The goal is to teach how to think in categories, and how to present a budget and cost baseline clearly.

Cost Estimation Methods (Level 1)

At Level 1, you typically encounter:

• Analogous estimating: Use costs from similar past projects.
• Bottom-up estimating: Sum costs of individual work packages from WBS.
• Parametric estimating: Use cost per unit (e.g., cost per laptop setup, cost per square meter painting).

You can choose one depending on what the exam question provides.

Recommended exam approach

• If the question supplies unit rates: use parametric.
• If it supplies work packages: use bottom-up.
• If it supplies “similar project cost”: use analogous.

Example Cost Model for the CTL Project (Consistent Numbers)

To ensure internal consistency, we use a sample budget for the CTL Renovation & Training Setup project.

Assume the following estimated costs (in South African Rand, ZAR):

Room Renovation costs

• 1.1 Procurement of paint and materials: R 7,500
• 1.2 Surface preparation (labour & consumables): R 5,000
• 1.3 Painting (labour): R 10,000
• 1.4 Lighting improvement (fixtures & labour): R 6,500
• 1.5 Final inspection readiness (inspection labour/time): R 1,500

Equipment Installation costs

• 2.1 Projector setup and mounting (labour): R 4,000
• 2.2 Laptop setup (imaging & accounts): R 9,000
• 2.3 Software installation (IT admin & licences assumption as “admin time”): R 3,500
• 2.4 System testing (lab labour): R 2,000

Training & Documentation costs

• 3.1 Schedule and invite staff (admin): R 800
• 3.2 Deliver training session (trainer time & materials): R 2,500
• 3.3 Create user guide & maintenance checklist: R 1,200
• 3.4 Sign-off/acceptance (coordination): R 1,000

Calculate estimated direct cost (sum)

Let’s add the direct cost items:

Room Renovation:

• R 7,500 + R 5,000 + R 10,000 + R 6,500 + R 1,500
  = R (7,500 + 5,000 + 10,000 + 6,500 + 1,500)
  = R 30,500

Equipment Installation:

• R 4,000 + R 9,000 + R 3,500 + R 2,000
  = R (4,000 + 9,000 + 3,500 + 2,000)
  = R 18,500

Training & Documentation:

• R 800 + R 2,500 + R 1,200 + R 1,000
  = R (800 + 2,500 + 1,200 + 1,000)
  = R 5,500

Total estimated direct cost:

• R 30,500 + R 18,500 + R 5,500
  = R 54,500

Contingency and Budgeting

In Level 1 exams, you may be asked to include:

• contingency reserve (for known-unknowns),
• management reserve (for unknown-unknowns, sometimes not explicitly demanded at Level 1).

A practical simple approach:

• Add a contingency percentage to direct costs.

Assume a contingency reserve of 10%.

• Contingency = 10% of R 54,500
  = 0.10 × 54,500
  = R 5,450

Total project budget (cost baseline):

• Budget = Direct cost + Contingency
  = R 54,500 + R 5,450
  = R 59,950

This means any exam question referencing “budget” should use R 59,950 for consistency when discussing the baseline.

Cost Baseline and Change Control (Conceptual + Practical)

A cost baseline is the approved budget distribution used for comparing actual performance.

When actual costs differ from planned:

• if it is within contingency and aligned with change control, you may adjust internally;
• if the variance exceeds thresholds or scope changes occur, a change request may be required.

Simple cost control language for exams

• Track actual expenditures weekly or at milestones.
• Compare:
  • Actual cost vs budgeted cost.
• Investigate variance:
  • labour delays,
  • rework due to quality issues,
  • price increases in materials,
  • overtime due to schedule slippage.

Procurement Basics: Make vs Buy and Vendor Selection

Level 1 includes understanding procurement as acquiring goods/services.

Common procurement planning components

• Identify what to procure (materials, fixtures, labour contracts).
• Decide procurement method (competitive bidding, supplier quote requests).
• Define evaluation criteria (price, delivery time, quality).
• Manage contract requirements and delivery timelines.

Make vs buy (exam-ready points)

• Make: internal labour/resources; may reduce cost but increases workload and risk of delays.
• Buy: outsource to vendors; can be faster and specialised, but depends on market availability and contract terms.

Example for CTL project

• Painting and surface preparation: may be outsourced to a local contractor.
• Laptop imaging: might be done internally by IT staff (make) if available.
• Projector mounting: outsource to a technical installer (buy) due to specialised mounting.

Budget Allocation by Category (Tabular Example)

In many exams, presenting costs by category earns marks. Here’s a consistent table using the CTL scenario cost model.

Category	Included Work Packages (from WBS)	Estimated Cost (ZAR)
Room Renovation	1.1–1.5	R 30,500
Equipment Installation	2.1–2.4	R 18,500
Training & Documentation	3.1–3.4	R 5,500
Direct Cost Total		R 54,500
Contingency (10%)	Reserve for known-unknowns	R 5,450
Cost Baseline / Total Budget		R 59,950

All totals align: R 54,500 + R 5,450 = R 59,950.

Monitoring Cost at Level 1 (Basic Variance Discussion)

Even without sophisticated earned value analysis, Level 1 expects you can interpret variance.

Example variance calculation (hypothetical)

Suppose by Week 4:

• Actual spend on renovation tasks (1.1–1.2) is R 13,000
• Planned spend for 1.1–1.2 based on the baseline is:
  • R 7,500 + R 5,000 = R 12,500

Variance = Actual − Planned
= R 13,000 − R 12,500
= R 500 over budget

A good exam answer also mentions:

• possible reasons (procurement price increase, additional labour due to prep issues),
• recommended response (review supplier quote, check work quality, adjust remaining forecast using change control).

Procurement Risk Link (Why Cost and Risk Connect)

Procurement is often a major risk driver. For Level 1, tie procurement delays and price changes to schedule and cost.

Example risks:

• Supplier delays → schedule slippage → overtime costs.
• Materials shortages → cost increases and rework.
• Contractor quality problems → redoing painting surfaces → additional cost.

In answers, always link back to scope/schedule/cost objectives and mention early planning and controls.

Section 4: Risk Management, Quality, and Communication Planning (Keeping the Project on Track)

This section focuses on what typically differentiates strong Level 1 candidates: the ability to identify risks systematically, propose realistic mitigation actions, and show basic competence in communication and quality assurance.

Risk Management Cycle at Level 1

A simplified risk management process:

1. Identify risks
2. Assess risks (likelihood and impact)
3. Plan responses
4. Monitor risks during execution

You should be prepared to use a risk register format even in short answers.

Identifying Risks: Common Sources

For the CTL project, risks could arise from:

• Technical risks: projector not compatible with existing laptop software.
• Schedule risks: contractors not available; painting takes longer due to weather/humidity.
• Cost risks: materials price increases; lighting fixtures backordered.
• People risks: staff training attendance low due to workload.
• Quality risks: poor surface preparation leads to peeling paint.
• External risks: campus access restrictions; power supply issues.

Risk Assessment: Likelihood and Impact

A simple Level 1 risk matrix uses categories like:

• Likelihood: Low, Medium, High
• Impact: Low, Medium, High

Then compute a risk priority qualitatively:

• Low + Low → low priority
• High + High → critical priority

Example risk register (CTLE scenario consistent)

Risk ID	Risk Description	Likelihood	Impact	Priority	Possible Response
R1	Paint/material delivery delayed	Medium	High	High	Order early; use alternative supplier; add contingency
R2	Lighting fixtures arrive late/backordered	Medium	Medium/High	High	Confirm stock availability; pre-book installer time; backup option
R3	Projector mounting/installation requires rework	Low/Medium	Medium	Medium	Verify wall/ceiling mounting requirements; test before final sign-off
R4	Laptop imaging/software installation fails for some units	Medium	High	High	Do test imaging on 2 units first; keep IT admin support; document fixes
R5	Staff cannot attend training session (conflicting duties)	Medium	Medium	Medium	Invite early; schedule multiple sessions if feasible; record training materials
R6	Poor surface prep leads to paint quality issues	Medium	High	High	Quality checkpoints after sanding/prep; use painting checklist
R7	System testing reveals connectivity issues between laptops and projector	Low	Medium	Medium	Run compatibility checks early; have spare cables/adapters

This register is exam-friendly because it shows:

• a clear risk statement,
• likelihood and impact,
• a response.

Planning Risk Responses (Avoid, Mitigate, Transfer, Accept)

Level 1 usually expects understanding of response strategies:

• Avoid: Change plan to remove the risk source.
• Mitigate: Reduce likelihood or impact.
• Transfer: Shift impact to third parties (insurance, contract clauses).
• Accept: Accept risk with contingency if it is unlikely/low impact.

Apply response strategies to CTL risks

• R1 (delivery delayed): mitigitate (early order), avoid (alternative supplier), accept part via contingency.
• R4 (imaging fails): mitigate (test imaging on sample units), transfer (if possible, vendor support), accept minimal via contingency labour.
• R6 (surface prep quality issue): avoid/mitigate by enforcing checklists and inspections.

Monitoring and Updating Risks

A risk register is not a once-off document. Monitoring includes:

• checking if mitigation actions were executed,
• reviewing whether likelihood/impact changed,
• adding new risks.

At Level 1, you can mention a practical method:

• Review risks in weekly project meetings.
• Use status reports to capture whether planned mitigations are still on track.

Quality Management at Level 1 (Quality as “Fitness for Purpose”)

Quality is not “gold-plating”; it’s meeting requirements and acceptance criteria.

Quality assurance vs quality control (basic distinction)

• Quality assurance (QA): Processes that ensure quality (how you work).
• Quality control (QC): Inspection/testing of outputs (what you deliver).

Example quality approach for CTL

• QA actions:
  • Use checklists for surface preparation.
  • Standard imaging procedure for laptop setup.
  • Test plan for system connectivity.
• QC actions:
  • Final paint inspection (1.5).
  • System testing (2.4).
  • Training competency demonstration and sign-off (3.4).

Communication Planning (Who Needs What, When, How)

Communication planning is essential in Level 1 because poor communication is often cited as a cause of project failure.

Elements of a communication plan

• Audience / stakeholder
• Message content
• Purpose (inform, approve, escalate)
• Channel (email, meeting, report)
• Frequency (weekly updates, milestone reports)
• Owner (project manager, team lead, sponsor)

Example communication plan for the CTL project

• Project manager → Sponsor
  • Weekly status report
  • Focus: budget burn, schedule progress, key risks
  • Frequency: weekly
• Project manager → Contractors/installers
  • Daily/when required coordination (or at least 2–3 times per week)
  • Focus: readiness of room, installation dates, acceptance requirements
• Project manager/IT lead → Team
  • Short standups: 3 times per week
  • Focus: imaging progress, software compatibility issues
• Project manager → Staff participants
  • Training invitation email 1 week before session (or earlier)
  • Provide agenda and simple pre-requisites (e.g., bring login credentials)

Conflict and Issue Management (Related Skill)

In projects, “risks” might occur in the future, but issues/problems are current.

Level 1 candidates should differentiate:

• Issue: Already happening now (e.g., “paint contractor is unavailable this week”).
• Risk: Might happen (e.g., “materials could be delayed”).

Issue escalation (exam example)

If lighting fixtures delivery moves beyond the plan and threatens Week 6 completion, escalate to sponsor:

• Explain impact on schedule and cost baseline.
• Present options:
  • alternative supplier,
  • resequencing tasks,
  • adjust training date if absolutely required.

Section 5: Stakeholder Management, Change Control, Monitoring & Closing (Turning Plans into Delivery)

The final section brings everything together: how to manage people/stakeholders, control changes, and complete the project properly. It is common for Level 1 questions to include short scenario-based prompts requiring structured response.

Stakeholder Management at Level 1: Support, Resistance, and Engagement

Stakeholder management is not “nice to have”—it reduces misunderstandings and protects scope and schedule.

Stakeholder engagement strategies

• Supportive stakeholders: keep informed, involve in feedback cycles.
• Neutral stakeholders: provide clear info, avoid overwhelming detail.
• Resistant stakeholders: involve them early, address concerns, align on benefits and constraints.

Example stakeholder groups for CTL project

• Sponsor (department head)
• Client/user (training coordinator)
• IT support team (laptop setup)
• Contractors (painting and lighting, projector installation)
• Staff participants (training attendees)
• Campus facilities/security (room access restrictions)

Managing Expectations: Scope Creep and the “Hidden Requirements” Problem

Scope creep occurs when new requests appear without change control. Level 1 exam answers should include:

• a definition of scope creep,
• a recognition of why it happens,
• a method to manage it.

Why scope creep happens

• stakeholders assume “you can just add it” because you are already working in the area,
• unclear scope statement,
• weak sign-off processes.

Prevention actions

• clear inclusions/exclusions (already covered in Section 2),
• document acceptance criteria,
• require change requests for additions.

Change Control Process (Simple but Real)

A Level 1 “change control” process often includes:

1. Identify change request
2. Assess impact (scope/time/cost/risk/quality)
3. Decide approve/reject/defer
4. Implement changes with updates to baselines and documentation

Example change request for CTL scenario

Client asks: “Can we also install additional wall-mounted speakers for better audio?”

Potential impacts:

• Scope: extra deliverable (audio system).
• Time: add installation and testing tasks.
• Cost: additional hardware and labour.
• Quality: new acceptance criteria needed.
• Risk: supplier availability for speakers.

A strong exam response:

• describes steps,
• references that change needs impact assessment,
• ties back to baseline.

Monitoring & Controlling Progress (Milestones and Simple Tracking)

Even at Level 1, it is useful to use milestones:

• “Room ready for equipment installation”
• “System tested”
• “Training completed and signed off”

Example milestone plan (for CTL project)

Assuming the schedule logic:

• Milestone 1: Room Renovation completion readiness (after 1.5)
• Milestone 2: System testing complete (after 2.4)
• Milestone 3: Training session delivered (after 3.2)
• Milestone 4: Sign-off acceptance (after 3.4)

When asked “how do you monitor?”, you can mention:

• comparing current status to planned baseline dates,
• reviewing deliverables completion,
• reviewing cost baseline progress (spend vs planned),
• reviewing risk register updates.

Mini Example: Linking Schedule to Cost Baseline

Suppose by Week 4 you are halfway through painting:

• Painting (1.3) planned duration: 2 weeks
• If painting started in Week 2, by Week 4 it should be nearly complete.

If Week 4 ends and painting is only 50% done, you can:

• identify schedule variance (delay),
• forecast cost variance due to potential overtime or contractor rescheduling,
• recommend corrective action: resequence lighting tasks, add labour, or revise milestone timeline.

In cost terms, you would:

• update forecast of remaining work packages based on realistic durations and risks,
• manage within contingency if possible, otherwise propose a budget change.

Earned Value Concept (Optional at Level 1, but Useful)

Some courses mention earned value analysis (EVA) at an introductory level.

If your module doesn’t require formulas, you can still use conceptual framing:

• Planned work vs completed work vs spent money.
  If the exam expects calculations, formulas are typically:
• PV (Planned Value), EV (Earned Value), AC (Actual Cost)

If not required, focus on milestones and variance reasoning.

Quality Acceptance and Project Closure

Closing is where you secure formal acceptance and record lessons learned—often where marks are gained for “project management maturity”.

Closing activities at Level 1

• confirm deliverables completed per acceptance criteria,
• collect sign-offs from client/user,
• ensure documentation exists:
  • user guides,
  • checklists,
  • maintenance notes,
  • training attendance record or training materials used,
• finalise contractor payments and reconcile procurement documents,
• capture lessons learned (what went well / what to improve).

Lessons Learned: Turning Experience into Future Success

A lessons learned log should include:

• Issue/incident
• Root cause (if known)
• Impact (cost/time/scope/quality)
• Corrective action taken
• Recommendation for next project

Example lessons learned for CTL project (plausible)

• If laptops imaging took longer than planned:
  • root cause: insufficient testing on sample units,
  • impact: system testing delayed,
  • response: created faster troubleshooting procedure,
  • recommendation: test imaging on at least 2 units earlier next time.

Sustainability and Benefits Realisation (Light Touch at Level 1)

While benefits realisation is more advanced, Level 1 often expects you to mention:

• ensure the project outcome can be used by stakeholders,
• training ensures equipment is actually utilised,
• documentation ensures long-term maintenance.

For CTL project:

• training session (3.2) and user guide (3.3) are not “extras”; they are part of benefits enabling.

South African University Exam-Relevant Study Pointers (How to Score for CPUT Short Course Level 1)

Because students in South Africa commonly prepare with blended resources from CPUT and other business/management faculties, it helps to use exam techniques consistent with how these modules are structured: clear frameworks, diagrams, and scenario reasoning.

Answer Structure That Works in South African Exams

Use this approach in short-answer and scenario questions:

1. Define the concept (1–2 sentences)
2. Apply to the scenario (use the CTL Renovation & Training Setup example logic)
3. Add one tool or diagram (WBS, risk register, communication plan, change control steps)
4. End with a reason/impact (why it matters, how it improves outcomes)

“Tool-Based” Marks: Where Students Lose Points

Common mistakes:

• listing items without structure (e.g., describing risk but not using likelihood/impact),
• sequencing tasks without dependency logic,
• presenting cost tables but not summing totals,
• discussing change requests without impact analysis.

A fast fix:

• always show numbered steps and consistent totals,
• always show at least one risk response strategy and one communication frequency/channel.

Consistency Checklist (CPUT Level 1 Style)

Before submitting an exam answer, verify:

• Scope inclusions/exclusions are clear.
• WBS work packages map to deliverables.
• Schedule tasks have dependencies or a justified sequence.
• Costs are summed correctly to direct cost.
• Contingency is calculated correctly (e.g., 10% × R 54,500 = R 5,450).
• Total budget matches the baseline (R 59,950).
• Risk register includes both likelihood and impact and at least one response action.
• Change control includes impact assessment and approval decision.

Final Consolidation: Key Models and Formulas to Remember

Project Planning Core Models

• Project life cycle phases: Initiation → Planning → Execution → Monitoring/Controlling → Closing.
• Triple constraint: Scope, Time, Cost.
• WBS logic: Project → Deliverables → Work packages → Activities.
• SMART objectives: Specific, Measurable, Achievable, Relevant, Time-bound.
• Risk register: Risk ID, description, likelihood, impact, priority, response.

Costing Numbers to Recall (From the CTL example)

• Direct cost total: R 54,500
• Contingency (10%): R 5,450
• Total project budget / cost baseline: R 59,950

Communication and Control Essentials

• Communication plan includes stakeholder, channel, frequency, and purpose.
• Monitoring uses baseline comparison: schedule progress + cost burn + updated risks.
• Change control process includes impact assessment and approved action.

If you want, I can also format these notes into mng0001-style exam question practice (with 10–15 short questions and full model answers) using the exact CTL Renovation & Training Setup scenario so you can rehearse under exam conditions.