PRM360S Project Management 3 Study Guide (CPUT): Exam Notes, Key Concepts & Practice Scenarios

PRM360S (Project Management 3) at Cape Peninsula University of Technology (CPUT) focuses on advanced project management thinking: integrating processes, controlling performance, managing stakeholder expectations, and applying project planning and governance in realistic organisational settings. This study guide is written in an exam-focused style using common university language and includes practical examples that mirror how questions are typically framed in South African university assessments (including similar question patterns found in modules such as CPUT PRM modules, Unisa project management-related modules, and CUT/other university project planning/control papers).

The guide is structured into five substantial sections, each anchored to a particular “cluster” of study material for CPUT Project Management (PRM360S)—from core integration and governance to risk, scheduling, quality, cost/control, and communications/leadership.

Section 1: PRM360S Foundations — Project Integration, Governance, and the “Why” Behind PM Processes (CPUT Cluster)

Project management success is rarely the result of a single tool. In PRM360S-type content, you are expected to understand how project processes connect: how planning decisions influence execution, how performance monitoring feeds corrective actions, and how governance structures keep stakeholders aligned. A typical PRM360S examination may test your ability to (1) select the correct process for a scenario, (2) explain inputs/tools/outputs, and (3) justify why a management action is appropriate.

Understanding Project Governance and Why It Matters

In many organisations, “governance” means how decisions are made and monitored during the project lifecycle. This includes:

Project steering committees (or management review boards)
Reporting lines and escalation procedures
Stage gates (approve/continue/stop)
Policies for change control, procurement, and risk ownership
Accountability for schedule, cost, scope, quality, and benefits

Governance is not bureaucracy for its own sake. It prevents:

Uncontrolled scope growth (“scope creep”)
Spending without business justification
“Zombie projects” continuing long after objectives are no longer achievable
Conflicts between project teams and sponsor expectations

Exam-style scenario to practise:
A sponsor approves a project at the concept stage, but later stakeholders request additional deliverables not included in the baseline. Governance determines whether the change is:

handled through a formal change control process, and
assessed for cost/schedule/benefit impacts before approval.

Project Integration Management: The Core “Linking” Skill

Integration management is frequently tested as “the connecting tissue” across knowledge areas. It asks you to explain how multiple elements are aligned into one coherent plan.

A good integration answer usually references these themes:

A project is managed as a system, not independent parts.
Planning is iterative: as risks become known, baselines and controls may need updating (via formal approvals).
Monitoring and controlling feeds back into execution through corrective and preventive actions.
Changes are managed through integrated change control, not ad hoc decisions.

Key Concepts and Terminology You Must Know

You should be fluent in these exam-relevant terms:

Project Charter
- Authorises the project at a high level.
- Identifies objectives, high-level risks, summary schedule, and budget range.
- Establishes the project manager authority.
Project Management Plan
- The “single source of truth” describing how the project will be executed, monitored, and controlled.
- Includes subsidiary plans (schedule plan, cost plan, quality plan, risk plan, communications plan, etc.).
Baseline
- The approved version of scope/schedule/cost used for measurement.
- Any deviation triggers analysis and potentially change control.
Integrated Change Control
- A process for reviewing proposed changes and deciding whether to approve them.
- Ensures impacts are assessed across scope, schedule, cost, quality, resources, and risk.
Corrective vs Preventive Actions
- Corrective actions address identified performance issues.
- Preventive actions reduce probability of future issues (e.g., training to avoid recurrent errors).

Tools and Techniques: How Questions Often Test Them

PRM360S questions often expect you to list tools/techniques and match them to scenario needs. Common tools and techniques include:

Expert judgment: when no standard data exists; relies on experience.
Stakeholder analysis: classifies influence/interest and helps plan engagement.
Meetings: used as decision platforms, but must be structured with agendas, minutes, decisions, and actions.
Data analysis:
- Root cause analysis (e.g., “5 Whys”)
- Variance analysis (actual vs planned)
- Trend analysis
Change control system:
- A defined mechanism for submission, review, approval, documentation, and communication of changes.

Integration in Practice: A Case Example (Built for Exam Use)

Case: Campus Wi-Fi Upgrade Project
A technology services department wants to upgrade campus Wi‑Fi coverage for improved student access. The project includes:

Network equipment procurement
Installation of access points
Configuration and security hardening
Testing and training for support staff

Common integration decisions:

Charter states the goal: improve coverage and uptime by measurable targets.
Management plan states execution approach (phased deployment during off-peak hours).
Quality plan defines acceptable performance thresholds.
Risk plan identifies major risks:
- Supplier delays
- Equipment compatibility issues
- Security vulnerabilities discovered late
Communications plan defines reporting cadence:
- weekly progress report to project sponsor
- monthly steering committee review
During execution, monitoring shows a schedule slippage due to supplier lead time.
Integrated change control assesses options:
- expedite shipping (increase cost)
- swap to alternative compatible equipment (risk and quality evaluation)
- adjust phased deployment schedule (scope impact evaluation if downtime increases)

Your exam answer should demonstrate the logic of “one project system” rather than isolated tool knowledge.

Exam Skills: How to Score High in Integration Questions

When answering, aim to:

Start with what the process is (definition).
Mention why it is needed (purpose).
Link to inputs and outputs (even if you summarise briefly).
Provide a scenario action (what you would do next).
Use consistent project terms: baseline, change control, corrective actions, stakeholder engagement.

Section 2: Project Scheduling, Scope, and Quality Control — Managing Performance Against the Plan (CPUT Cluster)

Schedule management and quality management are frequently tested because they generate measurable performance comparisons: planned vs actual time, and expected vs actual quality criteria. PRM360S expects you to explain not only definitions but also decision-making under constraints.

Scheduling Basics: From Work Breakdown to Control

Work Breakdown Structure (WBS) and Activity Definition

A typical exam question may ask how to create clarity in a schedule:

Break the project deliverables into smaller components (WBS).
Convert WBS components into activities with clear start/finish criteria.

Activity definitions should include:

deliverable description
constraints and assumptions
dependencies (what must happen before or after)
duration estimate logic (historical data, expert judgment)

Estimating Duration: What Students Get Wrong

Many students confuse:

duration (time for an activity)
with
effort (labour hours)

Duration depends on staffing and process speed; effort depends on staff hours. In exam answers, if you mention resource allocation, also clarify that duration changes when resources change (e.g., adding staff can reduce duration but may increase cost and coordination complexity).

Network Diagrams and Critical Path Logic

A network diagram helps represent dependencies. Two concepts often appear:

Forward Pass
- Calculates earliest start/finish times.
Backward Pass
- Calculates latest start/finish times.

Critical Path is the sequence with zero (or minimal) float: delays on critical-path activities affect project completion time.

Float (Slack) and Its Managerial Meaning

Float represents schedule flexibility. Exam questions may ask what to do with float:

Activities on non-critical paths can often absorb delays without affecting completion (within float limits).
But using float “carelessly” may expose the project to risk near milestone dates.

Exam advice: mention that float can be “consumed” by delays, and therefore must be monitored.

Schedule Control: Variance, Trend, and Corrective Actions

Schedule control compares:

baseline schedule vs actual performance
forecasted completion vs planned completion

Key schedule monitoring practices include:

weekly status updates with activity progress
measuring % complete accurately (not “gut feel”)
identifying causes of variance (resource constraints, rework, procurement delays)

Common Corrective Actions

Crashing: add resources to reduce duration (higher cost).
Fast-tracking: overlap activities previously done sequentially (increases risk).
Rebaselining: formal update of baseline if approved change fundamentally alters scope/schedule targets.

Important: In integrated governance terms, rebaselining typically requires approval and documentation.

Scope Management: Preventing Scope Creep

In project environments, scope creep often happens when stakeholders request “small” additions. PRM360S answers should treat scope as a controlled system:

Scope baseline: approved scope statement, WBS, and WBS dictionary (or equivalent).
Changes follow integrated change control.
Use scope verification and requirements traceability (as appropriate).

Scenario to practise:
A sponsor asks for additional reporting dashboards “only for a few departments.” You should:

treat it as a change request unless explicitly included in scope,
assess impact on cost, schedule, and quality,
confirm whether it affects acceptance criteria.

Quality Management: Planning and Control

Quality in PRM360S is not “policing”; it is planned assurance that deliverables meet requirements. Quality management involves:

Quality planning: define quality standards and metrics.
Quality assurance: process-focused activities to ensure quality is built into work.
Quality control: product-focused inspection/testing activities.

Quality Criteria and Acceptance

A high-scoring answer will mention measurable acceptance criteria:

performance thresholds (e.g., coverage percentage, system uptime)
usability requirements (e.g., response time targets)
compliance requirements (e.g., security standards)

When stakeholders disagree, quality control should use objective evidence:

test results
inspection checklists
statistical sampling (if applicable)
audit findings

Quality Control Techniques: Practical Examples

Quality control methods can include:

inspection (reviewing deliverables against standards)
testing (functional and performance tests)
process audits
Pareto analysis (identify top causes of defects)
control charts (monitoring variability)

If asked “which technique?” choose based on the scenario:

If you have a defect log and want to prioritise root causes: Pareto.
If you need to verify conformity to specs: inspection/testing.
If the issue is process variability: control charts and process audit.

Case: Event Management System Development (CPUT-Type Example)

Project goal: build an online event management system for workshops and seminars.

Deliverables:

registration module
payment integration
administrator dashboard
reporting exports

Quality metrics:

registration form completes within 3 seconds on average under standard load
payment transactions succeed at least 98% of attempts during testing
exports produce reports within 1 minute and in the correct format

During execution, users report that exports sometimes take 5–7 minutes. A quality control approach would:

collect evidence (test logs, time stamps, query performance)
identify root cause (database indexing missing, heavy queries, server load)
decide corrective action (add indexes, optimise query, adjust caching)
verify fix (re-test exports and confirm they meet acceptance criteria)

A top answer also links to schedule and cost:

if fixing requires major refactoring, it may affect timeline
change control is required if scope is impacted

Section 3: Cost Management and Performance Monitoring — Earned Value, Forecasting, and Decision-Making (CPUT Cluster)

Cost management in PRM360S usually goes beyond simple budgeting. It includes controlling spending and interpreting performance signals—especially through earned value concepts. Even if your course uses a simplified approach, exam questions often test your ability to interpret variances logically.

Cost Baseline and Budgeting Structure

A cost baseline is the planned budget for project work. You may see these components:

Budget at Completion (BAC): total planned cost for the project baseline.
Cost breakdown: categories such as labour, materials, equipment, subcontractors, overheads.
Funding schedule: how funds are distributed over time.

Common student error: confusing “budget” with “cash flow.” Budget is planned cost; cash flow is actual timing of payments.

Tracking Actual Cost and Earned Value (Core Logic)

Earned Value Management (EVM) connects:

Planned value (PV): what you planned to spend for the work scheduled by a given date.
Earned value (EV): what the budgeted cost of completed work actually is.
Actual cost (AC): what you actually spent for the completed work.

These three values allow you to derive:

Schedule variance (SV = EV − PV)
Cost variance (CV = EV − AC)
Cost performance index (CPI = EV / AC)
Schedule performance index (SPI = EV / PV)

Interpreting Signs (What Examiners Look For)

If CV is negative, you’re over budget for the work performed.
If SV is negative, you’re behind schedule for the work performed.
If CPI < 1, cost efficiency is poor.
If SPI < 1, schedule efficiency is poor.

Forecasting: Estimating Future Project Performance

EVM supports forecasting metrics such as:

Estimate at Completion (EAC)
Estimate to Complete (ETC)
Variance at Completion assumptions (depending on method)

In exam contexts, you should usually provide:

a forecast based on current efficiency assumptions
justification for which assumption method is reasonable

A Fully Worked PRM360S-Style Numeric Example

Assume a project has:

BAC = R 2,000,000
At a specific reporting date:
- PV (planned value) = R 800,000
- EV (earned value) = R 650,000
- AC (actual cost) = R 720,000

Compute:

Schedule variance (SV) = EV − PV = 650,000 − 800,000 = −R 150,000
Cost variance (CV) = EV − AC = 650,000 − 720,000 = −R 70,000
CPI = EV / AC = 650,000 / 720,000 ≈ 0.903
SPI = EV / PV = 650,000 / 800,000 = 0.8125

Interpretation:

SV is negative → behind schedule.
CV is negative → over budget.
CPI ≈ 0.903 → cost efficiency is about 90.3% of plan.
SPI ≈ 0.813 → schedule efficiency is about 81.25% of plan.

Likely exam follow-up: What would you do?

Perform root cause analysis:
- why schedule is behind (procurement delays? rework? staffing? approvals?)
- why costs are high (overtime? supplier changes? waste? defects?)
Decide corrective actions:
- negotiate lead times
- adjust staffing plan
- improve productivity
- enforce quality controls to reduce rework

Cost Control: Variances, Reconciliation, and Change Control

Cost control is not only arithmetic; it requires decision governance:

If the project is over budget due to approved changes, the baseline may need update.
If it’s over budget due to poor control (e.g., rework from not meeting quality standards), corrective action is needed without changing scope baseline.
If variances are caused by resource misallocation, update the resource plan and enforce progress measurement accuracy.

Distinguishing “Problem” Categories

Consider three variance sources:

Legitimate changes (approved scope or external conditions)
Performance issues (inefficiency, delays, rework)
Measurement issues (incorrect EV measurement; inaccurate status reporting)

High marks come from identifying the likely category and proposing a control method.

Case: Construction Minor Works with Supplier Delays

A small facilities upgrade project includes:

electrical fittings procurement
ceiling repairs
repainting and finishing

By reporting date:

EV indicates less work completed than planned.
AC is higher due to rework caused by delays (work crews idle then rushed later).

A strong answer:

does not assume “always blame labour”
suggests:
- re-check procurement risk triggers
- evaluate supplier performance
- ensure contract terms include delivery penalties or mitigation

Section 4: Risk Management and Stakeholder Engagement — Planning for Uncertainty and Aligning Expectations (CPUT Cluster)

PRM360S commonly tests risk management with scenario questions. You must show both:

risk identification and analysis (probability/impact thinking), and
risk response planning (avoid/mitigate/transfer/accept), plus monitoring and escalation.

Stakeholder engagement is also critical: stakeholder power and interest affects how you communicate and how quickly you manage conflict.

Risk Management Process: A Structured Approach

A typical risk management structure includes:

Plan Risk Management
- Decide methodology: risk scoring, templates, thresholds.
- Define roles: who owns risks, how often risks are reviewed.
Identify Risks
- Source risks from scope, schedule, cost, technical requirements, procurement, resources, external factors.
- Use workshops and expert judgment.
Perform Qualitative Risk Analysis
- Rank risks by priority using probability and impact.
- Not everything must be quantified (qualitative ranking is faster).
Perform Quantitative Risk Analysis (if required)
- Use numeric methods for more complex decisions (e.g., expected monetary value, scenario analysis).
Plan Risk Responses
- Choose strategies and define actions.
Implement Risk Responses
- Assign resources and deadlines.
Monitor and Control Risks
- track triggers, review effectiveness, update risk register.

Probability and Impact: How to Explain Scoring

You should be able to explain a simple scoring model:

Probability scale (e.g., 1–5)
Impact scale (e.g., 1–5) across cost, schedule, scope, and quality
Risk score = probability × impact (or similar)

Exam tip: If your course uses a different formula, align to course conventions—but the reasoning remains the same: higher probability and higher impact yield higher priority.

Risk Response Strategies: Avoid, Mitigate, Transfer, Accept

Use these strategies correctly:

Avoid: change plan to eliminate the risk.
Mitigate: reduce probability and/or impact.
Transfer: shift impact to another party (insurance, contracts), without removing responsibility entirely.
Accept: acknowledge the risk and be ready with contingency; may include passive acceptance or active acceptance with contingency reserves.

What Makes a Good Risk Response Plan?

A high-quality response includes:

owner (a named role/team)
trigger conditions (early warning indicators)
specific action steps
budget/time for response actions
target outcomes (reduce impact, reduce probability)

Risk Register: What Examiners Expect to See

A risk register often includes columns such as:

Risk ID
Description
Cause
Probability
Impact
Score/Priority
Response strategy
Owner
Trigger
Contingency/residual risk after response
Current status (open/closed/monitoring)

Even if your exam doesn’t ask for a full register, it expects you to mention these elements logically.

Quantitative Risk Analysis Example (Simple Expected Value)

Assume:

Risk: equipment delivery delay.
Probability: 20% (0.2)
Impact: additional cost of R 100,000

Expected cost impact:

0.2 × 100,000 = R 20,000

This number can support a decision: whether investing in a mitigation plan is worthwhile.

If mitigation costs R 15,000 and reduces probability to 10%:

New expected impact = 0.1 × 100,000 = R 10,000
Expected savings = R 20,000 − R 10,000 = R 10,000
Net effect = savings − mitigation cost = 10,000 − 15,000 = −R 5,000
In that case, a rational decision might be not to mitigate at that cost, unless other benefits exist (like schedule certainty).

Stakeholder Engagement: Power–Interest Lens

Stakeholder analysis typically classifies stakeholders by:

power/influence
interest/concern

Common stakeholder categories:

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

Engagement Strategies That Score

For each category, align communication:

high-power stakeholders need decision-focused updates
high-interest stakeholders need frequent progress and clarity
low-power stakeholders still require updates to avoid surprises

Conflict and Expectations Management

Stakeholders may want conflicting outcomes:

sponsor wants cost efficiency and speed
users want maximum functionality and minimal disruption
compliance teams want strict adherence to standards

A high-scoring PRM360S answer:

acknowledges stakeholder needs
uses governance and change control
frames trade-offs clearly:
- what’s being added/removed
- impacts on schedule and budget
- how quality and acceptance criteria remain protected

Case: Digital Learning Platform Rollout

A rollout project includes:

content migration
user training
device compatibility testing
support desk readiness

Risks:

content formatting issues (probability 3/5, impact 4/5 → high)
device compatibility problems (probability 2/5, impact 5/5 → high)
training attendance drop (probability 4/5, impact 2/5 → moderate)

Stakeholders:

sponsor: high power, moderate interest
lecturers: high interest, moderate power
IT support team: high power for technical delivery
students: high interest, low direct power but high impact on adoption

Your response strategy should include:

technical testing and early pilot
communications plan for training
escalation plan when risks become active

Section 5: Communications, Leadership, Procurement, and Project Closure — Delivering and Ending Projects Correctly (CPUT Cluster)

Advanced project management includes people, communication flow, procurement decisions, and closure activities. PRM360S often expects you to show that “project work” includes the ability to end correctly: lessons learned, transition planning, and formal acceptance.

Communications Management: Planning for Clarity and Control

Communications management ensures the right information reaches the right people at the right time. A communications plan typically includes:

stakeholder list
information needs (what they need)
frequency (weekly/monthly/milestones)
channels (meetings, email, dashboards, reports)
owners (who produces it)
approval/escalation routes

Communication Complexity: More Than Reporting

Good communication:

reduces misunderstandings
provides decision-ready summaries
records decisions and action items
supports transparency for governance

Exam trap:
Students often describe communication as “send updates.” High marks come from linking communication to:

stakeholder engagement strategy
governance decision points
change approvals
risk escalation

Leadership and Team Management in Project Delivery

Project managers in PRM360S contexts are expected to:

lead cross-functional teams
manage performance and accountability
resolve issues and remove blockers
facilitate stakeholder alignment

Leadership is not only motivating; it includes:

setting expectations
clarifying roles and responsibilities (RACI)
managing conflict constructively
ensuring effective meeting decisions

RACI as an Exam Tool

RACI defines:

Responsible: does the work
Accountable: final answer/approval
Consulted: gives input
Informed: notified

Use RACI to demonstrate control:

procurement approvals
scope changes
quality sign-offs
schedule baseline approvals

Procurement Management: Managing External Dependencies

Procurement includes buying goods/services from external suppliers. It may be central in PRM360S because procurement delays create schedule and cost impacts.

Key procurement topics include:

procurement planning
contracting strategy (fixed price vs time-and-materials, etc.—as per module coverage)
supplier selection
contract administration
acceptance and closing

Exam scenario example:
A supplier consistently delivers late. Your response could include:

revisit procurement risk
check contract delivery terms
renegotiate lead times or specify penalties
consider alternative supplier qualification
adjust schedule with governance approval

Procurement and Change Control Connection

Procurement decisions must align with project change control:

if specifications change, buyer must ensure suppliers can deliver updated scope
quality standards must be communicated and verified
variations must be approved (avoiding “informal changes” that become cost escalations)

Managing Project Meetings and Decision Records

Meetings are often listed as a tool in integration and stakeholder processes, but exam answers should mention how meeting outputs matter:

agendas and objectives
minutes recording decisions
action item owners and due dates
escalation decisions

Practical example:
In a weekly project meeting, a technical lead reports that a design change will reduce defects but adds 2 weeks. The project manager:

logs it as a change request,
assesses impacts (schedule, cost, quality),
presents it to steering committee at the next review,
updates the schedule baseline only if approved.

Quality Acceptance and Formal Closing

Project closure includes:

verifying deliverables meet acceptance criteria
final reporting: performance, lessons learned, handover documentation
administrative closure: contract closure, archive records
transition planning: operational handover to business unit

Closure is often tested as a short-answer:
What activities must happen before closing?

acceptance sign-off
final cost/schedule reconciliation
documentation completion
lessons learned report
release of resources

Lessons Learned: Turning Experience into Organisational Improvement

Lessons learned should include:

what worked well
what didn’t work and why
recommendations for future projects
changes to process templates (if applicable)

A good lessons learned entry:

is specific
links to measurable causes (e.g., inaccurate duration estimates)
explains corrective actions (e.g., improved estimation method and verification step)

Case: Closure of a Research Equipment Upgrade

A university research unit upgrades lab equipment and completes installation.

Closure steps:

technical acceptance tests completed successfully
training provided to lab staff
support documentation delivered (user manuals, maintenance schedule)
supplier contracts closed with confirmation of delivery acceptance
final project report prepared:
- scope status (all deliverables completed)
- schedule performance (timing vs baseline)
- cost performance (final reconciliation)
- risks resolved or residual risks communicated

Stakeholders involved:

project sponsor (sign-off)
lab manager (operational readiness confirmation)
procurement office (contract closure)
IT/security (if equipment includes networked components)

An exam answer that describes closure as “end the project” earns fewer marks than one that describes closure as a structured transition with evidence and documentation.

Final Exam Practice Toolkit (Rapid Application Across PRM360S Themes)

To help you practise quickly, use these “micro-skill frames.” They are not substitutes for your course material, but they match the way marks are often awarded in PRM-style examinations.

Frame A: “Choose the Right Process for the Scenario”

When a question gives you a story, identify:

What is the problem? (scope, schedule, cost, quality, risk, stakeholder conflict)
What stage is the project in? (planning, execution, monitoring/controlling, closing)
What decision must be made? (approve change, reduce risk, adjust schedule, verify quality)
Which governance mechanism supports it? (change control, steering committee, quality sign-off)

Frame B: “Explain Integration with Trade-offs”

Strong answers state trade-offs clearly:

reducing schedule usually increases cost (crashing)
improving quality may increase time (more testing) but reduces rework risk
adding scope requires assessment of cost/schedule impacts and acceptance criteria

Frame C: “Use Numbers with Meaning”

If EVM or variance numbers appear:

compute correctly (EV, PV, AC)
interpret signs
propose action based on interpretation
link action to governance (change control and approvals)

Frame D: “Stakeholder Communication Must Match Power/Interest”

If asked about communication:

high power: decision-focused, timely escalation
high interest: frequent progress and responsiveness
keep low power stakeholders informed to reduce surprise and resistance

Summary: What to Memorise and What to Practise

PRM360S success depends on disciplined use of core project management logic:

Integration and governance: ensure everything is connected and changes are controlled.
Scheduling and quality control: track performance and maintain acceptance criteria.
Cost management and performance monitoring: interpret variances and forecast responsibly.
Risk and stakeholder engagement: plan uncertainty and align expectations proactively.
Communications, leadership, procurement, and closure: deliver outcomes and transition correctly.

If you practise scenario questions using the frames above—especially those involving change control, schedule variances, cost variances, and risk response—you will be prepared for the reasoning style typical of South African university assessments in project management modules within the CPUT PRM curriculum.