PRM260S – Project Management 2 Exam Notes (CPUT)

PRM260S (Project Management 2) exam notes are built around the practical, decision-focused side of project management: planning with structure, executing with control, and closing with value delivery. These notes align with the kind of applied work students encounter in courses such as CPUT PRM260S, and are written to help you answer both calculation/problem questions and scenario-based theory questions. They emphasize frameworks, governance, stakeholder communication, scheduling, and risk/control—exactly the areas that typically appear in “Project Management 2” style assessments.

Section 1: PRM260S Exam Essentials — Project Life Cycle, Governance, and Integrated Planning (CPUT)

In PRM260S, you are expected to show more than definitions. The exam usually rewards candidates who can apply concepts to a project scenario: what happens first, who decides what, which documents are created, how scope/schedule/cost are balanced, and how project performance is monitored. This section focuses on the life-cycle logic, the governance structures, and the integrated planning mechanisms that connect them.

Project Life Cycle and Phase Gates (What the examiner wants)

A project life cycle describes how a project evolves from initiation to closure. While different industries use different models (waterfall, incremental/iterative, hybrid), PRM260S expects you to understand the standard phase-based approach and the purpose of phase gates.

A typical life cycle (conceptually) looks like this:

1. Initiation / Concept

   • Identify the need or opportunity.
   • Draft a high-level project concept.
   • Establish the business case and feasibility direction.
   • Appoint sponsors and key governance roles.

2. Planning

   • Develop the scope baseline: deliverables, acceptance criteria.
   • Create the schedule baseline and cost estimate baseline.
   • Build the risk plan, communication plan, procurement plan (if relevant), and quality approach.
   • Create the project management plan(s).

3. Execution

   • Perform the work defined in the scope.
   • Manage resources and stakeholder engagement.
   • Procure goods/services where applicable.
   • Ensure quality assurance and control.

4. Monitoring & Controlling

   • Track performance versus baselines.
   • Manage change requests.
   • Track risks, issues, and stakeholder sentiment.
   • Report progress and forecasts.

5. Closing

   • Validate deliverables and acceptance.
   • Close contracts (if applicable).
   • Capture lessons learned.
   • Formalize handover and operational readiness.

Phase gates are decision points between phases. They ensure the project doesn’t simply “continue” by momentum. At each gate, the governance team checks whether prerequisites are met (e.g., adequate funding, acceptable scope clarity, risk mitigations in place) before approving the next stage.

Exam angle: When you see wording like “approval to proceed,” “gate,” “authorization,” or “Go/No-Go,” translate it into “phase gate governance” rather than treating it as a generic sentence.

Governance: Roles, Authority, and Decision Systems

PRM260S typically draws a distinction between:

• Project governance (the decision-making structure)
• Project management (the work of planning and controlling)
• Operational management (runs business processes once outputs are handed over)

You will often be asked to match responsibilities to roles.

Common governance roles you should recognize

• Project Sponsor / Executive
  • Owns the business case.
  • Provides resources and resolves escalations.
  • Ensures alignment with organizational strategy.
• Project Manager
  • Responsible for project execution discipline.
  • Builds baselines (scope, schedule, cost) and manages changes.
  • Leads risk/quality/scheduling/communications execution.
• Steering Committee / Governance Committee
  • Provides oversight.
  • Approves major changes and milestone movement.
  • Monitors performance and funding alignment.
• Functional Managers
  • Provide skilled resources (people, equipment).
  • Ensure staffing commitments and competences.
• Project Team
  • Performs tasks.
  • Reports progress and risks at work package level.
• Stakeholders
  • Customers, end-users, communities, regulators, suppliers.
  • Influence acceptance, risks, and communication needs.

Key exam concept: Governance determines “what is allowed” and “who can approve what.” Project management determines “how” work is done and “how” performance is controlled against baselines.

Integrated Planning: Baselines and Project Management Documents

A common exam style is to present a project scenario and ask: “Which document should exist at this stage?” or “What is the baseline?” To answer effectively, you need a clear mental map.

Baselines: The control anchor

A baseline is the agreed reference point used to measure performance.

• Scope baseline: deliverables, requirements, work packages
• Schedule baseline: planned dates, milestones, duration assumptions
• Cost baseline: estimated budget by work package/time period

From these, you can compare:

• what was planned vs what was actually done,
• what is forecast to happen vs what was planned.

Core planning documents you should be able to name and describe

Depending on the project model, your exam may require the following:

• Project Charter
  • Purpose, high-level objectives, stakeholders, authority of the PM.
• Project Management Plan
  • Integration of subsidiary plans:
    • scope management plan
    • schedule management approach
    • cost management approach
    • quality management plan
    • risk management plan
    • stakeholder engagement plan
    • communications plan
    • procurement plan
    • change management approach
• Work Breakdown Structure (WBS)
  • Decomposes scope into manageable components.
• Schedule (activities and logic)
  • Activity list, sequencing, critical path logic, milestones.
• Budget and cost estimates
  • Resource cost assumptions, contingency, escalation.
• Risk Register
  • Risks, probabilities, impacts, triggers, responses, owners.
• Issue Log
  • Captures problems requiring action.
• Quality Plan
  • Quality standards, methods, audits, acceptance criteria.
• Communication Plan
  • Who needs what, when, how, and why.

Consistency matters: if your exam question says “during planning,” then your answer should not jump to “closing documents” (e.g., lessons learned report) unless asked to explain their timing.

Scope Management Foundations (Why scope control is central in PM2)

Scope is not just “the deliverables.” In PRM260S terms, scope control is a discipline that includes:

1. Collecting requirements
2. Defining scope
3. Creating the WBS
4. Validating scope
5. Controlling scope
6. Handling change

Requirements vs deliverables

• Requirements: what must be true (e.g., “system must support 200 users”)
• Deliverables: tangible outputs (e.g., “implemented system module,” “installed network”)

In exam scenarios, if a stakeholder requests a new feature, determine whether it is:

• a correction of an original requirement,
• an enhancement not included in the baseline,
• or a requirement clarification.

That classification determines how change management applies.

Integrated Change Management: Avoiding Scope Creep

Scope creep is a common problem and a favorite exam topic. It occurs when new work is added without baseline approval.

A high-scoring answer should include:

• Definition of scope creep
• Typical causes (unclear requirements, poor stakeholder control, weak governance)
• Effects (schedule slippage, budget overrun, quality dilution)
• Mitigation (change control process, requirements documentation, stakeholder engagement)

Example scenario (typical exam logic)

Imagine a project to build an online student portal for a university.

• The original scope baseline includes:
  • login, student profile, course registration module, timetable view.
• During execution, a stakeholder asks for:
  • “add scholarship calculator” and “enable WhatsApp notifications.”

If those items are not in the approved baseline, they must enter the change control process:

• change request submitted,
• assessment by PM and team,
• estimated impact on schedule and cost,
• steering committee approval (or rejection),
• updated baselines if approved.

Exam tip: Always link the change to the baselines—scope, schedule, cost.

Quality and Acceptance Criteria: Planning for “Done”

Many students treat quality as “inspections at the end.” PRM260S expects you to understand quality planning and quality control throughout the project.

Quality planning typically involves:

• defining standards (internal policies, regulatory requirements, customer standards),
• specifying acceptance criteria,
• selecting quality assurance activities (process checks),
• selecting quality control activities (product checks).

If acceptance criteria are unclear, it becomes impossible to verify deliverables and causes disputes at closing.

Communication Discipline: Stakeholder Engagement as a Control System

Stakeholder management isn’t “relationship building only”; it is also information control.

A communications plan should specify:

• audience
• message type (status, risks, approvals, changes)
• frequency
• channels (email, meeting, dashboard, report)
• responsibility (PM, team lead, sponsor)

A frequent exam scenario: “Stakeholders complain they weren’t informed.” This indicates failure in the communication plan or in governance escalation.

Section 2: Scheduling, Cost Estimation, and Performance Monitoring — From Baselines to Control (CPUT)

This section connects planning to monitoring. In Project Management 2, exams often test whether you can:

• build or interpret schedules,
• reason about critical paths,
• estimate costs using structured assumptions,
• forecast outcomes using performance concepts.

Building Schedules: Activities, Sequencing, and Logic

A schedule is more than a list of dates. In robust project planning, a schedule includes:

• activities
• dependencies
• constraints
• estimated durations
• milestones
• resource assumptions (sometimes included at this stage)

Types of dependencies

• Finish-to-Start (FS): successor starts after predecessor finishes
• Start-to-Start (SS): successor starts after predecessor starts
• Finish-to-Finish (FF): successor finishes after predecessor finishes
• Start-to-Finish (SF): uncommon in practice, predecessor starts before successor finishes

In exam problems, the dependency type determines schedule logic. If you misinterpret FS vs SS, your critical path logic may become wrong.

Critical Path Method (CPM) — The Practical Exam View

The critical path is the longest path in the network diagram that determines project duration (under the assumed durations and dependencies). Activities on the critical path have zero float (or near-zero depending on method).

Key schedule terms

• Earliest Start (ES) / Earliest Finish (EF)
• Latest Start (LS) / Latest Finish (LF)
• Float/Slack:
  • Total float = LS − ES (or LF − EF)
  • If float = 0, activity is critical
• Milestones mark significant events (e.g., “approval of design complete”)

How to answer critical path questions

Typical exam steps:

1. Identify activity dependencies and build the network logic.
2. Compute ES and EF forward pass.
3. Compute LS and LF backward pass.
4. Determine float for each activity.
5. Identify critical activities where float = 0.

Worked Exam-Style Scheduling Example (Network Reasoning)

Consider a simplified project:

Activity	Duration (days)	Dependency
A	4	Start
B	6	A (FS)
C	3	A (FS)
D	5	B (FS) and C (FS)
E	2	D (FS)

Compute forward:

• A: ES 0, EF 4
• B: ES 4, EF 10
• C: ES 4, EF 7
• D: depends on both B and C → ES = max(EF of B, EF of C) = max(10, 7) = 10 → EF = 15
• E: depends on D → ES 15, EF 17

Backward pass (project finish assumed at 17):

• E: LF 17, LS 15
• D: successor is E → LF 15, LS 10
• B and C both feed D:
  • B: LF = LS(D) = 10, LS = 4
  • C: LF = 10, LS = 7

Floats:

• A: LS 0, ES 0 → float 0
• B: LS 4, ES 4 → float 0
• C: LS 7, ES 4 → float 3 days
• D: LS 10, ES 10 → float 0
• E: LS 15, ES 15 → float 0

Critical path: A → B → D → E (duration 17 days).
Non-critical with float: C can slip up to 3 days without affecting project completion (unless it causes other constraints/resources conflicts).

Exam insight: If the question asks “what happens if activity C is delayed by 2 days?” you should check float.

• C float = 3 → 2-day delay still allows completion at day 17.
• A 4-day delay would push project finish to day 18 (because delay exceeds float by 1).

Cost Estimation: From Resource Needs to Budget Baselines

Cost estimation connects tightly to the WBS and schedule. You estimate cost using assumptions about labor, equipment, materials, and external services.

Cost elements you should include

• Direct labor (hours × rate)
• Materials (units × unit cost)
• Equipment (rental or depreciation)
• Subcontractors / services
• Travel and accommodation
• Overheads (sometimes separated; depends on marking scheme)
• Contingency (risk-based reserve)
• Management reserve (often for unknown unknowns)

Estimation methods you may be expected to know

Depending on course emphasis:

• Analogous estimation (use past similar projects)
• Parametric estimation (use statistical relation, e.g., cost per unit)
• Bottom-up estimation (estimate each WBS work package, then aggregate)
• Three-point estimating (for probabilistic estimates)

In exam questions, identify the method implied by the data:

• If question provides past project costs and similarity, it suggests analogous.
• If it provides “cost per meter” or “cost per user,” it suggests parametric.

Bottom-Up Cost Example (WBS-to-Budget)

Suppose you have three work packages in a small “IT infrastructure rollout”:

1. Cabling installation
   • 120 labor hours at R200/hour → R24 000
2. Router configuration
   • 40 labor hours at R250/hour → R10 000
3. Testing and commissioning
   • 30 labor hours at R300/hour → R9 000

Total direct labor estimate = R24 000 + R10 000 + R9 000 = R43 000.

If you add:

• materials estimated at R12 000
• contingency 10% of base estimate (base = R43 000 + R12 000 = R55 000)
  • contingency = R5 500

Then total budget estimate = R55 000 + R5 500 = R60 500.

Exam tip: When contingency is given as a percentage, show the arithmetic and clearly define the base.

Performance Monitoring: The Logic of “Planned vs Actual vs Earned”

PRM260S commonly uses earned value concepts or equivalent monitoring logic: compare what you planned to do, what you actually did, and what value you earned for the work performed.

At minimum, understand these relationships:

• Planned Value (PV): budgeted cost of work scheduled by a date
• Earned Value (EV): budgeted cost of work actually completed
• Actual Cost (AC): actual money spent on the completed work

From these, you can compute indicators such as:

• Schedule Variance (SV) = EV − PV
• Cost Variance (CV) = EV − AC

Interpretation:

• SV < 0 → behind schedule
• SV > 0 → ahead of schedule
• CV < 0 → over budget
• CV > 0 → under budget

You may also be asked about performance indices:

• CPI = EV / AC
• SPI = EV / PV

Worked Earned Value Example (Interpretation Required)

Assume at the end of week 4:

• PV = R80 000 (planned progress)
• EV = R72 000 (earned for completed work)
• AC = R85 000 (spent)

Compute variances:

• SV = EV − PV = R72 000 − R80 000 = −R8 000 (behind schedule)
• CV = EV − AC = R72 000 − R85 000 = −R13 000 (over budget)

Interpretation:

• The team has achieved 72k worth of work but planned for 80k by this time; also they spent 85k, which is more than earned value suggests.
• This points to both schedule slippage and cost inefficiency.

Exam extension: If asked for corrective action:

• schedule: re-sequence tasks, add resources carefully, remove blockers.
• cost: review procurement, reduce rework, renegotiate rates, ensure scope stability.

Forecasting: What Will Happen by Project End?

Earned value forecasting often includes:

• Estimate at Completion (EAC)
• Estimate to Complete (ETC)
• Variance assumptions (e.g., whether CPI continues as-is)

One typical approach (conceptual) is:

• If performance continues at the current CPI, then EAC = BAC / CPI

Where BAC = Budget at Completion.

If BAC is R300 000 and CPI = EV/AC = R72 000 / R85 000 ≈ 0.8471,
then EAC ≈ 300 000 / 0.8471 ≈ R354 200 (approx).

Exam warning: Marking schemes differ. If the course uses different formulas, follow the one you are taught. The safe strategy is: write the meaning clearly, then show calculations using the provided formula.

Monitoring Risks and Issues Alongside Cost/Schedule

A common mistake is to treat risk and performance monitoring as separate topics. In PRM260S, strong answers integrate them:

• A risk materializes → scope/schedule changes → cost and quality impacts.
• A mitigation plan might require extra spend early to avoid bigger failure later.

So in scenario questions, if a risk occurs, mention:

• whether it triggered,
• response action taken,
• update to risk register,
• and its impact on baselines.

Section 3: Risk, Quality, and Stakeholder Communication — Management Plans That Survive Real Constraints (CPUT)

This section focuses on three management areas that often differentiate high and low marks: risk management, quality management, and stakeholder communication. These are not isolated—they combine to produce a stable delivery environment. In practical PRM260S scenarios, an exam question might show:

• early warning signs,
• stakeholder dissatisfaction,
• a quality defect,
• and you must decide which corrective and preventive actions apply.

Risk Management: Identification to Response

Risk management is a structured cycle:

1. Risk identification
2. Risk analysis (qualitative and/or quantitative)
3. Risk response planning
4. Risk monitoring and control
5. Risk communication and documentation updates

Risk register essentials (what to include)

A risk register should typically include:

• risk description
• risk category (technical, schedule, cost, stakeholder, external)
• probability (P)
• impact (I)
• risk rating (e.g., P×I)
• triggers (early indicators)
• mitigation/response strategy
• owner (who manages the response)
• contingency plan (what to do if it occurs)
• status updates

Qualitative Risk Analysis: Probability–Impact Matrices

Qualitative analysis ranks risks rather than calculating exact expected monetary values.

A common pattern:

• probability scale: 1 (low) to 5 (high)
• impact scale: 1 (low) to 5 (high)
• risk rating: P×I

Example:

• Risk: “Supplier delays in network equipment”
  • probability = 4
  • impact = 5
  • rating = 20 → high priority

Exam question style: You may be given several risks and asked which are most critical. Use the rating and justify.

Risk Response Strategies (Avoid, Mitigate, Transfer, Accept)

Each response has different costs and trade-offs.

• Avoid: change plan so risk no longer applies
  Example: redesign reduces dependency on long-lead equipment.
• Mitigate: reduce probability and/or impact
  Example: dual sourcing, buffer stock, supplier performance checks.
• Transfer: shift impact to another party
  Example: contracts with penalties, insurance.
• Accept: acknowledge risk, prepare contingency, no active reduction
  Example: minor risk; prepare workaround.

Exam scoring logic: If you respond “mitigate” but propose a vague action, marks may drop. The best answers specify:

• what you do,
• who owns it,
• when you do it,
• and what trigger you monitor.

Worked Risk Example: Choosing the Best Response

Suppose you have a risk:

• “Design approval delay”
  • probability 3/5
  • impact 4/5
  • rating = 12 (medium-high)

Two response options:

1. Mitigate by scheduling review sessions with stakeholders weekly (cost: R8 000).
2. Transfer by adding contract incentives (cost: R6 000) but still depends on stakeholder approvals.

A strong answer:

• considers that delays depend partly on stakeholders, not only on contractors, so transfer may not fully eliminate the probability.
• mitigation directly improves review engagement and reduces approval cycle time.

Then justify choosing option 1 if it reduces probability more strongly.

Quality Management: Quality Planning, Assurance, Control

Quality is about meeting requirements and intended use, not “luxury.” In PRM260S, you should know the structure:

• Quality planning: determine standards and how to comply
• Quality assurance: ensure processes will produce outputs meeting standards
• Quality control: verify outputs meet acceptance criteria

Acceptance criteria examples

Depending on project type:

• software: performance metrics (e.g., response time), bug thresholds
• construction: dimensional tolerances, inspection sign-offs
• training: attendance and competency checks

Exam angle: If a deliverable “fails acceptance,” the correct approach is not to blame the team informally; it should trigger quality control actions and possibly change management if scope requires revision.

Defects and Rework: Why Quality Costs Money Early

Many exams reward candidates who explain the cost trade-off:

• prevention costs less than correction
• rework consumes schedule and budget
• poor quality damages stakeholder trust

If you create a defect prevention plan, you might include:

• peer reviews
• test plans
• inspection points aligned with milestones
• documented sign-offs

Stakeholder Communication: Managing Expectations and Preventing Conflict

Stakeholders influence:

• acceptance criteria,
• perceived project success,
• escalation of issues,
• and the authorization of changes.

A high-quality communications answer includes:

• stakeholder mapping: power/interest, influence/impact
• tailored messaging (different channels and detail levels)
• feedback loops and escalation routes

Stakeholder mapping (Power vs Interest)

You might classify stakeholders into:

• High power, high interest: manage closely, frequent updates
• High power, low interest: keep satisfied, periodic updates
• Low power, high interest: keep informed, encourage engagement
• Low power, low interest: monitor with minimal communication

Example Scenario: Stakeholder Pushback and Quality Risk

Imagine a facility upgrade project. A key stakeholder (Facility Manager) insists on a new safety signage standard mid-way.

This triggers:

• scope change if it wasn’t included,
• potential schedule delay if signage procurement changes,
• quality considerations (safety compliance must be met).

A good PRM260S response would:

1. classify it as change request,
2. assess schedule and cost impacts,
3. update risk register (e.g., procurement delay risk),
4. coordinate quality acceptance criteria (safety standard compliance),
5. communicate the decision outcome through governance.

Important: Do not treat stakeholder demands as automatically “must do.” In governance terms, sponsor/steering approval determines whether the baseline changes.

Integrating Risk and Stakeholder Communication

A risk event often becomes a stakeholder event. For example:

• If “vendor delay” risk occurs, customers lose confidence quickly.
• You must communicate transparently, including:
  • what happened,
  • impact assessment,
  • mitigation actions,
  • revised schedule expectation (if approved).

Exams may ask: “What do you do after identifying a high-impact risk?” The best answer includes communication, not only technical mitigation.

Section 4: Procurement, Contract Management, and Resource/Change Control for Sustainable Delivery (CPUT)

Project Management 2 frequently includes questions on procurement and contracting because external dependencies commonly cause delays, cost overruns, and quality defects. Even when PRM260S focuses primarily on project management, you are expected to understand the governance logic around procurement.

Procurement Planning: When and What to Buy

Procurement planning answers:

• what should be procured,
• how it should be procured,
• timeline for procurement,
• selection method,
• contract type considerations.

Procurement triggers you should recognize

• you need specialist services not available internally
• you need materials with long lead times
• you must comply with supplier standards or legal requirements
• internal capacity constraints require external support

A strong exam answer links procurement to:

• WBS work packages,
• schedule dependencies,
• and risk mitigation.

Make-or-Buy Decision (Simple but examinable)

A make-or-buy decision examines whether you should:

• build internally (make),
• purchase externally (buy),
• or use mixed approaches.

You should mention:

• cost comparison,
• capability availability,
• speed to deliver,
• quality control implications,
• contractual and legal complexity.

Contract Types: Understanding Trade-offs

Contract type affects risk distribution.

Common contract types include:

• Fixed-price: contractor gets fixed amount; contractor carries more cost risk.
• Time-and-materials: time and materials billed; project carries cost risk unless controlled.
• Cost-plus: reimbursement plus fee; requires strong oversight because cost can inflate.

In exams, if you see phrases like “risk should be on supplier,” it often points to fixed-price or clauses that penalize performance. If you see “requirements may change,” time-and-materials or staged scope approaches may appear.

Procurement Process Steps

While organizations differ, a typical procurement cycle includes:

1. Request for proposal/quotation (RFP/RFQ)
2. Vendor solicitation
3. Vendor evaluation (technical and price criteria)
4. Bid clarification
5. Award decision (approved by governance)
6. Contract signing
7. Contract execution and monitoring
8. Contract closure

Exam nuance: If asked “what is the purpose of evaluation criteria,” answer: it ensures fair selection aligned to project needs and reduces contract disputes.

Contract Management: Monitoring Deliverables, Performance, and Compliance

After award, contract management ensures:

• scope of contracted work matches the deliverables needed,
• supplier meets quality standards,
• schedule obligations are met,
• change orders are governed.

Key contract documents often referenced:

• statement of work (SOW)
• service level agreements (if relevant)
• schedules and milestones
• acceptance testing procedures

Worked Contract Change Example: When a Supplier Delivers Late

Assume a supplier contract includes:

• milestone payment upon delivery of equipment.
• delivery is contractually due by week 6.
• penalty clause triggers if delivery is late by more than 5 business days.

If delivery arrives at week 8 (late by about 10 business days), you:

• verify delivery compliance,
• assess impact on project schedule critical path,
• consider whether penalties apply,
• and update forecasts.

A high mark answer also mentions:

• documentation: written notices,
• governance: sponsor/steering approval for any schedule rebaseline,
• stakeholder communication: customer expectations.

Resource Management and Constraints

Even without deep HR theory, PRM260S tests resource planning: ensuring correct skills at right times.

You should mention:

• resource leveling vs resource smoothing (conceptually)
• handling competing demands from other projects
• escalation when resources become unavailable

If a key technician is pulled to another urgent project, you should respond with:

• impact assessment on schedule,
• options (swap resources, resequence tasks, extend duration),
• governance approval if baselines must change.

Change Control System: Integration Across Scope/Schedule/Cost

Change control ensures that adjustments happen with governance and documentation.

A standard change control system includes:

1. Change request
2. Impact analysis (scope, schedule, cost, quality, risk)
3. Decision (approve/reject/defer)
4. Update baselines (if approved)
5. Communicate change to stakeholders
6. Implement and monitor effects

Exam question style: If asked “what makes change control effective,” mention:

• clear authority levels,
• documented criteria,
• impact assessment discipline,
• and baseline updates.

Quality and Procurement Interlock

A procurement failure is often a quality failure too (wrong specs, incomplete deliverables). Therefore, integrate procurement monitoring with quality control:

• incoming inspection requirements
• vendor quality reports
• acceptance criteria alignment

If you do not align acceptance criteria early, disputes occur at closure.

Section 5: Project Closure, Lessons Learned, and Exam-Focused Scenario Answers (CPUT)

Closing is not just paperwork. In PRM260S, closure should confirm deliverables meet acceptance criteria, contracts are finalized, and future projects benefit through lessons learned. Many exams include scenario questions that test whether you can identify what must be done at the “end of the project” while still addressing unresolved issues.

Closing Processes: What “Done” Means

Project closure includes:

• deliverable acceptance
• contract closure (if applicable)
• administrative closure
• handover to operations
• final performance reporting
• lessons learned capture
• archive project records

“Acceptance” is central:

• it confirms requirements were met,
• it prevents disputes,
• it signals readiness for operation or next project.

Lessons Learned: From Experience to Actionable Knowledge

Lessons learned should not be vague. A good set includes:

• what happened (facts)
• what should have happened (standard/expectation)
• why it happened (root cause categories)
• what to do next time (recommendation)
• owner and timing for implementing recommendations

In exam questions, if you see “lessons learned” asked, provide:

• at least one process improvement,
• one risk management improvement,
• one stakeholder communication improvement,
• or one planning/scheduling improvement—depending on the scenario.

Final Performance Reporting: Baselines vs Actual Outcomes

Closing reports often compare:

• scope delivered vs planned,
• schedule actual vs baseline,
• cost actual vs baseline,
• quality metrics vs acceptance criteria,
• risk outcomes (what materialized and what was controlled).

If earned value was used earlier, you can summarize:

• overall variances,
• whether the project was delivered within tolerances.

Even if the exam doesn’t require formulas, demonstrating structured reporting wins marks.

Example Closure Scenario (Typical PRM260S Style)

A project to install a campus network upgrade is completed but:

• two buildings still lack connectivity,
• the supplier claims the missing configuration files are “non-critical,”
• stakeholders want the project closed because it supports the upcoming semester.

A strong closure answer must:

1. address acceptance criteria:
   • are the remaining buildings required for acceptance?
2. handle issue log:
   • confirm whether this is a defect, missing work, or scope exclusion.
3. use change control logic:
   • if closing means excluding those buildings, it requires formal change approval.
4. manage stakeholder escalation:
   • inform sponsor/steering, document risks.
5. choose one of two closure outcomes:
   • full closure with acceptance and operational handover, or
   • partial close with defined transition plan and open issue ownership.

Exams often reward you for refusing “premature closure” without meeting acceptance requirements.

Transition to Operations: Handover and Readiness

A project’s output must be usable in operations. Transition planning includes:

• documentation handover (user manuals, technical docs)
• training for operational staff
• support arrangements (if promised)
• operational readiness checks
• maintenance schedules and responsibility assignments

If the scenario says “operations staff were not trained,” then closing should include remedial actions rather than simply filing documents.

Stakeholder Closeout and Communication

Closure communication should include:

• final status report,
• summary of achievements vs objectives,
• confirmation of acceptance sign-off,
• communication of open items and responsibility,
• celebration/recognition (optional in scoring, but it shows maturity).

If a stakeholder is unhappy, closure communication should include:

• explanation of what was delivered,
• why decisions were made,
• and what will happen with remaining gaps.

Integrating Prior Topics in One Scenario (Exam Synthesis)

Many PRM260S exam questions test synthesis. Here’s how to structure an answer under time pressure:

Step-by-step exam answer structure (apply to scenarios)

1. Identify the project stage (initiation/planning/execution/monitoring/closing).
2. Identify the baseline relevant to the issue (scope/schedule/cost).
3. Identify the governance decision required (PM decision vs steering committee approval).
4. Apply the correct control process:
   • change control if scope affected,
   • risk response if risk triggered,
   • quality control if defects found,
   • procurement contract management if supplier involved,
   • schedule re-baseline if milestone shifts are approved.
5. State communication actions:
   • who must be informed,
   • when,
   • with what information (impact, decision, next steps).
6. End with a corrective/preventive action plan.

This structure ensures you hit multiple marking criteria: stage appropriateness, governance logic, control discipline, and communication.

Full Mini-Case (Integrated PRM260S Scenario) with Model Answer Logic

Scenario:
A hospital project is implementing a new patient registration system. After month 3 of the project, the sponsor reports: “We are behind schedule, the vendor changed one of the modules, and nurses say the usability is poor. Also, the risk register hasn’t been updated since month 1.”

Assume:

• baseline scope included three modules: registration, appointments, and basic reporting.
• the vendor now proposes an alternative reporting module.
• the usability issues appear to affect speed and error rates.

What the exam expects you to do

1. Determine whether this is scope change or requirement clarification

   • If reporting module alternative is not part of approved scope baseline, treat as change.
   • Ask for specification comparison to the original requirements.

2. Apply change control

   • request submission from vendor (formal change request)
   • impact analysis:
     • schedule impact (testing effort may increase)
     • cost impact (vendor rework or license fees)
     • quality impact (usability and error rate metrics)
     • risk impact (implementation complexity)

3. Quality control and acceptance criteria

   • define usability acceptance criteria:
     • e.g., transaction time target, acceptable error threshold.
   • initiate verification:
     • user testing sessions with nurses
     • bug triage and regression testing plan

4. Update risk register

   • identify new or changed risks:
     • usability adoption risk
     • integration risk due to reporting module changes
     • schedule risk due to additional training/testing
   • assign owners and triggers

5. Communicate governance decisions

   • inform steering committee (or sponsor) with quantified impact:
     • “EV/PV/CPI” style indicators if used by the organization, or at minimum:
     • forecast “new expected completion date” and “revised cost estimate” contingent on decisions.

6. Corrective and preventive actions

   • corrective: fix usability issues, retest, correct module integration
   • preventive: update requirements documentation, strengthen vendor change governance, schedule periodic stakeholder usability reviews

Why this is a strong answer: It links scope baseline, change control, quality acceptance, risk updating, and stakeholder communication into one coherent response.

How to Handle Common Exam Traps

Trap 1: Treating change as purely administrative

If a change impacts scope, schedule, cost, or quality, it must be treated through impact analysis and governance approval.

Trap 2: Saying “we will manage risks” without details

Risk management requires:

• identification,
• analysis,
• response strategy,
• owners and triggers,
• monitoring.

Trap 3: Blaming vendor or team without governance logic

Even if the vendor caused the problem, the project manager must:

• document and assess impact,
• enforce contract terms (where applicable),
• communicate and escalate through governance.

Trap 4: Weak closing logic

Closing requires:

• acceptance criteria satisfaction,
• contract closure,
• handover readiness,
• final reporting and lessons learned,
• not just “project work finished.”

South African University Exam Context: How to Write Like a PRM260S Candidate (CPUT-aligned style)

Students in South Africa often face exam marking patterns shaped by applied project management rubrics. The most reliable writing style includes:

• Use correct terminology consistently (baseline, change request, acceptance criteria, risk owner).
• State “what, who, when, and how”
  • What is the action?
  • Who approves?
  • When does it happen?
  • How is it executed and controlled?
• Show calculation steps when numbers appear (especially earned value and scheduling).
• Tie answers back to scenarios rather than listing generic definitions.

Even if your course uses a particular framework, examiners usually reward structured reasoning over memorized paragraphs.

Final Exam Checklist (Fast Revision for PRM260S)

Use this as a last-minute mental checklist:

Core concepts you must recall accurately

• Project life cycle phases and purpose of phase gates
• Governance roles: sponsor, project manager, steering committee, functional managers
• Baselines: scope, schedule, cost
• Change control system: request → impact → decision → update baselines → communicate
• Schedule logic: dependencies, critical path, float
• Cost estimation: direct costs, contingency, budget baselines
• Performance monitoring: PV, EV, AC and interpretation of variances
• Risk management: register, probability/impact, response strategies, triggers
• Quality management: planning, assurance vs control, acceptance criteria
• Stakeholder communication: mapping, tailored updates, escalation
• Procurement and contract management: process and contract performance
• Project closure: acceptance, transition, contract closure, lessons learned

Quick “scenario answer template”

1. Identify stage
2. Identify baseline impacted
3. Identify governance decision required
4. Apply correct control process
5. Quantify where possible
6. Communicate escalation and next steps
7. Provide corrective + preventive actions

If you want, I can also generate PRM260S-style practice questions (with memos/solutions) covering critical path, earned value interpretation, risk register prioritization, and change control—tailored to the same concepts used in these exam notes.