UCT Department of Information Systems PM Course Material Exam Notes (PM Course Content, Processes & Past-Style Practice)

University of Cape Town (UCT) students often access Project Management material through the Department of Information Systems context—especially where project work intersects with information systems, technology, governance, and delivery discipline. These exam notes consolidate the most commonly examined Project Management (PM) concepts, with an emphasis on how they appear in course material, assignments, and application-style questions for UCT-related PM modules.

The focus is practical: definitions are linked to processes, processes are linked to deliverables, and deliverables are linked to how exam questions are typically structured. The guide also includes scenario-based practice and “what examiners look for” logic, so you can transfer learning into different question formats.

UCT Project Management PM Course Material: Core Course Foundations (What the Exam Tests)

Project Management in an information systems environment is not only about “knowing terms.” In UCT-style assessments, the strongest answers typically demonstrate (1) process understanding, (2) decision logic, and (3) appropriate justification using project management language (scope, schedule, risks, stakeholders, governance, quality, procurement, and communication).

PM as a Structured Discipline (Not Just Planning)

A useful way to interpret PM course material is to treat it as a structured set of management cycles:

1. Initiate the project (why, who, what problem).
2. Plan (how the work will be controlled and executed).
3. Execute (how the plan is carried out and adapted).
4. Monitor & Control (how deviations are detected and corrected).
5. Close (how delivery is completed and benefits realised).

In a typical exam question, the examiner rarely asks you to simply define “monitor and control.” Instead, they describe a situation like:

• A project is delayed because of vendor issues.
• Requirements keep changing.
• Quality defects appear after deployment.
• Stakeholders disagree on priorities.
• Costs are rising faster than planned.

To score marks, you must map the situation to the correct process area and then state the specific actions you would take.

Common exam traps

• Calling everything “planning.” If risk materialises, the required actions are more often monitor & control, not planning alone.
• Assuming one-off decisions. Many decisions require updates (e.g., schedule re-baselining after approved scope changes).
• Confusing governance with execution. Governance monitors and approves, while execution performs the work.

Tripartite Balance: Scope, Time, Cost (and Quality)

Many PM modules emphasise the “iron triangle” idea, but the UCT-information-systems context typically expands it:

• Scope: What the project will deliver.
• Time: When outcomes will be achieved.
• Cost: What resources will be used.
• Quality: How well deliverables meet requirements and standards.
• Benefits (often implicit): Why the project exists beyond output completion.

A high-scoring answer doesn’t stop at listing the triangle; it explains consequences. For example:

• If scope expands (new features added) without schedule/cost adjustment, the project becomes inconsistent.
• If schedule compression occurs, quality processes (testing, review, controls) may be weakened unless compensated by better resourcing or streamlined delivery.

Stakeholders and Communications as Central Exam Themes

In UCT PM assessments, stakeholder management often appears through:

• stakeholder analysis,
• communication planning,
• managing expectations,
• resolving conflicts,
• escalation and approvals.

Even if the formal topic is “project planning,” exam questions frequently reward answers that include:

• Who needs what information?
• How often?
• Through what channel?
• What decisions require approval?
• What artifacts confirm progress (e.g., reports, minutes, change requests, risk registers)?

Deliverables and Artifacts (Exam-Friendly Vocabulary)

PM course material tends to be assessed through the ability to link documents/outputs to the process that produces them. Typical artifacts you should be able to identify:

• Project Charter: authorization, purpose, high-level scope.
• Project Management Plan: integrated guidance on executing/controlling.
• Work Breakdown Structure (WBS): decomposition of scope into manageable work packages.
• Schedule Baseline: accepted timing plan.
• Cost Baseline: accepted budget plan.
• Risk Register: identified risks, analysis, response plans.
• Issue Log: current problems that require resolution.
• Change Request Form: formal path for changes.
• Requirements Documentation: functional/non-functional requirements.
• Quality Management Plan: how quality is planned, assured, and controlled.
• Communication Plan: audience + frequency + channel.
• Procurement Plan: what will be sourced externally.
• Acceptance Criteria and Handover Checklist: closure discipline.

In exam scenarios, you should not only name these artifacts; you should state what information goes into them and how they are used.

Integrated Project Management: Why “Links” Matter

One reason PM course materials feel broad is that they are integrated. An isolated concept rarely earns full marks. Consider a scenario:

“A system implementation is behind schedule. A stakeholder says the solution is also missing requirements.”

A high-mark answer explicitly links:

• Schedule slippage → affects resource allocation and timeline assumptions.
• Missing requirements → indicates incomplete scope/requirements management.
• Requirements gaps discovered late → indicates weak stakeholder engagement and quality assurance timing.
• Response → adjust priorities via change control, update baselines if approved, update risk responses, and re-plan testing/implementation.

This integrated logic aligns with how course outcomes are often evaluated: not memorisation, but reasoning and correct process selection.

UCT PM Course Material Processes: Scope, Time, Cost, Risk, Quality, and Governance (How to Answer Application Questions)

This section focuses on the process knowledge that most frequently appears in PM exam questions, especially where project work involves technology delivery, systems configuration, procurement, testing, and stakeholder decision-making. You will learn a “process-to-scenario mapping” approach.

Scope Management: Requirements, WBS, and Change Control

Scope management ensures the project delivers exactly what it is supposed to deliver—no more, no less—within constraints.

Define scope clearly (and document it)

In information systems projects, scope commonly includes:

• functional requirements (features),
• non-functional requirements (performance, security, availability),
• interfaces and integrations,
• constraints (e.g., must use existing infrastructure or specific vendor tools),
• acceptance criteria (what “done” means).

An exam question may describe ambiguous requirements or “scope creep.” A strong answer includes:

1. Clarifying requirements with stakeholders.
2. Ensuring requirements traceability to deliverables.
3. Validating scope changes through formal approval.

WBS and work packages

A WBS is one of the highest-yield topics. Examiners expect:

• that the WBS decomposes the project deliverables into smaller components,
• that work packages can be assigned owners,
• that work packages support estimation and scheduling.

A practical UCT-style approach is to describe how the WBS helps in controlling the project. For example:

• If delivery is late, the WBS allows you to identify which work packages are behind and why (dependency, resourcing, unclear requirements).
• If costs increase, the WBS supports variance analysis at the work package level.

Scope creep: why it happens and how to respond

Scope creep often occurs when stakeholders request new features informally. The correct response is typically:

• Log the request as a change request.
• Assess impact on time, cost, risk, and quality.
• Present options (approve, defer, reject).
• Obtain formal approval (governance decision).

A common exam pattern: you must distinguish between change requests and requirements clarification. If requirements were misunderstood initially, you may need clarification; if the deliverable is genuinely new, it is a change.

Time Management: Sequencing, Dependencies, and Baselines

Time management focuses on producing a schedule that is realistic and controllable.

Sequencing and dependencies

Examiners often test your ability to identify dependency types:

• Finish-to-start: predecessor finishes before successor starts.
• Start-to-start: successors can start when predecessor starts (less common, but appears in parallel testing).
• Finish-to-finish: successor finishes at same time or after predecessor finishes.
• Start-to-finish: rare in typical projects.

In systems implementation scenarios, dependencies frequently include:

• data migration depends on data extraction preparation,
• integration testing depends on interface readiness,
• user acceptance testing depends on training completion,
• deployment depends on final security approvals and sign-off.

Your answer should mention how you would revise the schedule when dependencies fail.

Schedule baseline and control

A baseline is an accepted plan used for performance measurement. If the schedule changes due to an approved scope change or major risk event:

• you update the schedule,
• you document the change,
• you may re-baseline after formal approval.

If the question asks “what do you do when the schedule is slipping,” a good answer includes:

1. Identify what is behind (which tasks/work packages).
2. Diagnose root causes (resource constraints, delayed approvals, external dependencies).
3. Decide whether you need corrective actions (e.g., adjust staffing, reorder tasks, reduce non-critical scope).
4. If changes are approved, update baselines and communicate.

Cost Management: Budgeting and Variance Logic

Cost management in PM exams commonly tests whether you can:

• estimate properly,
• understand the difference between budget and actuals,
• explain variance and corrective action.

Even without numbers, you must demonstrate correct thinking:

• If actual spend exceeds budget, determine whether it is due to legitimate changes, inefficient execution, or estimation errors.
• Corrective actions might include re-forecasting, re-planning, or scope adjustment (if approved).

Resource planning as a cost driver

In information systems projects, costs frequently depend on:

• developer capacity,
• contractor/vendor costs,
• test environments,
• training sessions,
• licensing and infrastructure.

A scenario-based exam question often includes a clue like: “the team has been under-resourced,” “vendor delivery is delayed,” or “additional environments were needed.” Your answer should connect those clues to cost and schedule impacts.

Risk Management: Identification, Analysis, and Response

Risk management is a highly exam-friendly process because you can earn marks by using consistent language and giving a structured response.

Identify risks: what counts as a risk?

A risk is an uncertain event that could affect objectives. It differs from an issue:

• Risk: could happen (uncertainty).
• Issue: has happened (certainty needing action).

Examiners like this distinction. In your answer:

• classify events correctly,
• explain triggers,
• outline prevention/detection/contingency.

Risk analysis and response strategies

Common response strategies include:

• Avoid (change plans to eliminate the risk).
• Mitigate (reduce probability/impact).
• Transfer (shift impact to a third party—e.g., insurance or contract terms).
• Accept (acknowledge and plan to manage if it happens).

In an information systems context, typical risks include:

• security vulnerabilities discovered late,
• delays in vendor procurement,
• data quality issues affecting migration,
• stakeholder availability affecting sign-off,
• integration failures due to API changes.

A good exam answer doesn’t stop at naming strategies. It explains how you’d implement them. For example:

• Mitigate security risk by early security assessments, secure coding standards, and scheduled penetration testing.
• Transfer vendor delivery risk through contractual SLAs (service level agreements), penalties, and clear acceptance criteria.

Risk registers and monitoring

You should describe what the risk register contains (risk description, probability, impact, risk owner, response plan, trigger). You should also mention how risk monitoring works:

• review risks at scheduled intervals,
• update probability/impact as project context changes,
• implement risk responses when triggers occur.

Quality Management: Planning, Assurance, and Control

Quality is often the most misunderstood topic because students treat quality as only “testing.” In PM course material, quality includes broader governance.

Quality planning

Quality planning answers:

• what standards apply (internal policies, compliance requirements),
• how quality will be measured,
• how you will ensure deliverables meet acceptance criteria.

For example, for a software implementation:

• coding standards,
• security controls,
• performance thresholds,
• test coverage expectations,
• documentation completeness.

Quality assurance vs quality control

A clear distinction can win marks:

• Quality assurance: activities that build confidence in processes (e.g., process audits, peer reviews).
• Quality control: activities that evaluate deliverables (e.g., inspection, testing, defect tracking).

An exam scenario might mention:

• “defects are found during acceptance testing” → quality control failure or late testing.
• “developers bypass review process” → quality assurance/process control failure.

Acceptance criteria and sign-off

Acceptance criteria are essential in systems projects. They show up in:

• test plans,
• user acceptance testing,
• deployment readiness,
• closure handover.

A strong answer explains how acceptance criteria are used to avoid disputes at the end.

Governance and Stakeholder Decision-Making

Governance is a system of rules, roles, and decision pathways that control project direction and approvals.

In UCT-style PM scenarios, governance appears in:

• escalations,
• sign-offs,
• steering committee meetings,
• approval of change requests,
• risk acceptance decisions,
• procurement approvals.

A high-mark answer includes:

• Who makes which decisions?
• How are decisions documented?
• What evidence supports the decision?

You should be able to discuss governance artifacts such as:

• meeting minutes,
• decision logs,
• escalation records,
• approved change requests.

UCT PM Course Material: Estimation, Scheduling Techniques, Procurement, and Practical Case Scenarios

This section adds depth by focusing on estimation, scheduling tools (conceptually), procurement planning, and realistic case scenarios. The goal is to provide exam-ready templates for answering “how would you do it?” questions.

Estimation Fundamentals (How PM Makes Plans Credible)

Estimation is central to time and cost planning. In exam questions, poor estimation is often the cause of project failure, not lack of effort.

Estimation approaches

Common estimation approaches you should understand and describe:

• Expert judgement: subject-matter experts provide estimates.
• Analogous estimation: use historical data from similar projects.
• Parametric estimation: use formulas and statistical relationships (e.g., cost per function point).
• Bottom-up estimation: estimate detailed work packages and aggregate.

Your answer should mention that estimation is iterative and refined as uncertainty decreases.

Dealing with uncertainty

In early phases, you rarely have perfect data. The best exam answers reflect a strategy:

• create a preliminary estimate,
• identify assumptions and constraints,
• plan how estimates will be refined,
• track actual performance vs estimates.

A scenario may provide a clue like “requirements are still evolving,” which implies that bottom-up estimates may be unreliable early.

Scheduling Techniques (Use the Logic, Not Just Names)

Many students memorise acronyms; fewer explain logic. You should be able to state what a technique helps you do.

Critical Path logic

The critical path concept (often tested in exams) refers to the sequence of activities that determines minimum project duration. If a critical-path task slips, the project finish date usually changes.

To answer exam questions about “what will cause delay,” you:

1. Identify activities with no slack (critical activities).
2. Explain how schedule slippage affects downstream tasks.
3. Recommend schedule actions: expedite critical tasks, add resources, or adjust dependencies.

Dependencies and float (slack)

Float is time an activity can slip without affecting the project finish date. In exam scenarios:

• if an activity is non-critical, you may still manage it, but the urgency differs.
• your corrective actions may prioritise critical-path work.

Even without calculations, the examiner rewards correct prioritisation logic.

Resource Planning and Capacity Constraints

In systems projects, the schedule may fail due to capacity constraints:

• developers are unavailable,
• testers are only available at certain times,
• security specialists need lead time.

A high-scoring answer includes resource levelling ideas conceptually:

• adjust task assignments to match availability,
• sequence work to avoid resource contention,
• negotiate timeline adjustment if capacity limits cannot be resolved.

Procurement and Vendor Management

Procurement management appears frequently in PM course material when projects involve external vendors, licensing, and outsourced development.

Procurement planning: what to source externally?

You need to decide what to procure based on:

• required expertise,
• cost-effectiveness,
• delivery urgency,
• internal capacity.

A procurement plan typically includes:

• procurement strategy (buy/build/partner),
• contract type rationale (fixed price vs time & materials—conceptually),
• vendor evaluation criteria,
• acceptance and performance requirements.

Vendor selection and evaluation

Exam questions may ask how to select a vendor. A typical approach includes:

• define requirements and evaluation criteria,
• request proposals or bids,
• score vendors based on capability, timeline, risk, compliance,
• negotiate contract terms for deliverables and SLAs.

In systems projects, vendor contracts must address:

• change management,
• delivery milestones,
• support and maintenance,
• acceptance testing responsibilities.

Contracting and governance

Procurement failures often stem from unclear acceptance criteria or weak change control with vendors. A strong answer states:

• clarify deliverables,
• specify quality expectations,
• define what constitutes acceptance,
• include provisions for delays and change requests.

Practical Case Scenario 1: ERP Module Implementation with Scope Creep

Scenario: A university department begins an ERP module implementation. After the initial discovery phase, a stakeholder requests additional reporting dashboards. The request arrives informally via email. Testing begins for the original scope while the requested dashboards are still being designed.

Key issues:

• scope creep (new features),
• schedule strain (testing overlaps with design),
• quality risk (insufficient testing time).

Your exam answer (structured):

1. Log the request as a formal change request.
2. Assess impact on:
   • scope (new dashboards),
   • time (test cycles and integration),
   • cost (extra development and testing hours),
   • quality (additional test coverage required).
3. Confirm requirements and acceptance criteria for dashboards.
4. Present options to governance:
   • approve and adjust schedule/resources,
   • defer dashboards to a later phase,
   • reject dashboards as out of scope.
5. Update:
   • risk register (testing and integration risk increases),
   • communication plan (stakeholders informed),
   • schedule baseline only if approved changes occur.

What examiners award marks for:

• Correct classification as change (not clarification).
• Specific impacts across time/cost/quality.
• Governance step (approval).
• Updated control artifacts.

Practical Case Scenario 2: Data Migration Risk Materialises Late

Scenario: A system migration has a high risk of poor data quality. The risk was identified early, but the mitigation plan was minimal. During migration rehearsal, multiple records fail validation, and users report that historical orders appear incorrect.

Key issues:

• quality control gap,
• risk response underperformed,
• stakeholder confidence damaged.

Exam answer approach:

1. Treat this as an issue resulting from a risk event.
2. Use an issue log to track:
   • data validation errors,
   • root causes (missing fields, inconsistent formats),
   • affected scope areas (which tables/datasets).
3. Run corrective actions:
   • remediation rules,
   • re-migration for affected datasets,
   • additional validation checks.
4. Update the risk register:
   • probability may increase for remaining waves,
   • new risks emerge (user rework, training delays).
5. Coordinate with governance:
   • decide whether to delay deployment,
   • ensure acceptance criteria are re-validated.
6. Communicate with stakeholders:
   • provide facts, not guesses,
   • propose mitigation timeline.

Examiner logic: you are expected to show the difference between risk identification and risk execution. You also should show how a late risk event affects deployment and acceptance.

Practical Case Scenario 3: Vendor Delays and Cost Overruns

Scenario: A vendor delivering a security module misses a milestone. The vendor claims delays due to internal resourcing. Meanwhile, the internal team begins integration without the module, resulting in rework. The project’s budget is now significantly above forecast.

Exam answer approach:

1. Identify what changed:
   • milestone slip,
   • downstream integration rework.
2. Assess impacts:
   • schedule,
   • cost,
   • risk to security compliance.
3. Contract/governance actions:
   • check SLAs and contract provisions,
   • initiate claims/penalty logic if applicable (conceptually),
   • request recovery plan from vendor.
4. Corrective actions:
   • re-plan integration tasks (pause dependent work or shift to non-dependent tasks),
   • adjust internal priorities to reduce rework.
5. Update:
   • cost forecast,
   • schedule updates (only with approved changes),
   • risk register (security compliance risk increases).
6. Communicate:
   • escalate to steering committee if governance threshold exceeded.

Marks gained come from connecting procurement delay to schedule/cost and demonstrating governance discipline.

UCT PM Course Material Capstone Skills: Monitoring & Control, Change Management, Documentation, and Exam-Winning Answer Structure

This final section synthesises skills that typically decide exam outcomes: monitoring & control techniques, change control, documentation discipline, and how to structure answers to score maximum marks. It includes a set of exam-style practice prompts with model answer outlines.

Monitoring & Control: Measuring Performance and Driving Corrective Action

Monitoring & control ensures the project remains on track or responds correctly when it is not.

Performance measurement logic

In PM exams, performance measurement is about comparison:

• planned vs actual progress,
• planned vs actual costs,
• planned deliverables vs completed deliverables,
• schedule forecasts vs baseline.

Even if you are not asked to calculate earned value directly, exam questions still test whether you understand what performance indicators mean.

Corrective actions vs preventive actions

You should distinguish:

• Corrective actions: applied to address problems already occurring.
• Preventive actions: applied to reduce the likelihood of future issues.

Example:

• If defects are already occurring in testing, you apply corrective actions (improve test process, patch code).
• If risk indicators show defects might increase (e.g., rushed development), you apply preventive actions (additional reviews, more test cases).

Change Management: From Request to Decision to Implementation

Change management is often the difference between a controlled and a chaotic project.

Steps in a change control process

A typical change control flow in PM course material:

1. Receive change request (formal).
2. Log it and assign ownership.
3. Assess impact on scope/time/cost/quality/risk.
4. Review with governance stakeholders (steering committee or project sponsor).
5. Approve, reject, or request modifications.
6. Implement change if approved.
7. Update baselines and communicate outcomes.

Why documentation matters

Exams often reward students who show discipline: “If it’s not documented, it doesn’t count.” That includes:

• change request forms,
• impact assessment reports,
• meeting decisions,
• updated plans.

In real projects, unclear change records cause:

• disputed acceptance,
• inability to measure variance,
• stakeholder frustration.

Communication Planning: Keeping Stakeholders Aligned

Communication can appear simple, but it is deeply linked to stakeholder satisfaction and governance success.

Communication plan elements

A communication plan usually includes:

• audience (project sponsor, end users, vendors, team members),
• content (status, risks, change decisions),
• frequency (weekly, fortnightly, monthly, at milestones),
• channel (email, meetings, dashboards, reports),
• ownership (who prepares and who approves).

A common exam scenario: “Stakeholders are surprised by changes at the end.” A correct answer identifies communication gaps:

• stakeholders were not included early,
• status reports did not highlight risk and trade-offs,
• change decisions were not communicated with rationale.

Documentation and Project Closure

Project closure is frequently overlooked. Exams may test closure through:

• documentation handover,
• final acceptance,
• lessons learned.

Closure deliverables

Closure typically includes:

• final product handover,
• documentation complete (user guides, operational manuals),
• contract closure with vendors,
• lessons learned report,
• formal sign-off and archiving.

In systems projects, closure also includes operational readiness:

• support transition to operations/IT,
• monitoring configuration completed,
• training delivered and confirmed.

How to Structure High-Scoring Exam Answers

A strong PM exam answer is usually:

1. Identify the process area (scope/time/risk/quality/governance/change/control).
2. Diagnose the situation correctly (risk vs issue, change vs clarification, cause vs symptom).
3. Propose actions in an ordered list.
4. State which artifacts are updated or created.
5. Justify decisions using PM principles (impact across constraints, stakeholder approval).
6. Close with what success looks like (acceptance, baseline update, resolved issue).

Mark distribution logic (what examiners tend to reward)

While you cannot know the exact marking scheme, typical marks come from:

• Correct identification (1–3 marks)
• Correct process steps (multiple marks)
• Correct artifacts/documentation mentions
• Clear linkage between impacts and responses
• Realistic prioritisation (critical tasks first)

Exam-Style Practice Prompts (With Model Answer Outlines)

Below are prompts that mirror typical UCT PM assessments. The outlines show the structure and language you should use. Use them as templates for writing your own answers under exam pressure.

Practice Prompt 1: Scope Creep and Testing Overlap

Prompt: A project team starts user acceptance testing for a system. During testing, multiple new requirements appear that were never included in discovery. The sponsor demands immediate inclusion.

Model answer outline:

1. Classify: new requirements as likely scope change (not clarification).
2. Immediate control:
   • pause acceptance for affected features or record defects as scope-related items,
   • log requests as change requests.
3. Impact assessment:
   • time (UAT retesting cycle),
   • cost (extra development and test labour),
   • quality (additional test cases and regression testing),
   • risk (integration and deployment risk).
4. Governance decision:
   • present options to sponsor/steering committee: approve with re-baseline, defer to phase 2, or reject.
5. Update artifacts:
   • change log, updated requirements documentation,
   • updated test plan if approved,
   • updated schedule baseline (if re-baselined).
6. Communication:
   • inform users and affected stakeholders of what is in-scope for the current UAT cycle.

Practice Prompt 2: Risk Monitoring Failure

Prompt: A risk about vendor delivery is logged, but no triggers are defined. Vendor delivers two weeks late and blames “unexpected internal issues.” Project schedule is now at risk.

Model answer outline:

1. Identify: the event is an issue derived from previously planned risk.
2. Use issue log:
   • track delivery slip, dependency impacts, acceptance consequences.
3. Trigger logic:
   • define triggers that should have been set (e.g., missed milestone dates, lack of progress reporting).
4. Risk re-assessment:
   • update probabilities and impacts for remaining vendor-related tasks.
5. Vendor management:
   • request recovery plan,
   • consult procurement contract terms and SLAs (conceptually).
6. Schedule correction:
   • reorder dependent tasks to reduce idle time,
   • fast-track where appropriate with approval.
7. Baseline update and governance escalation if thresholds exceeded.
8. Communication: escalate to steering committee and provide risk outlook.

Practice Prompt 3: Quality Defects Late in Deployment

Prompt: After deployment to a pilot site, critical defects are found. The team wants to release quickly to “catch up” with schedule.

Model answer outline:

1. Quality diagnosis:
   • identify whether defects indicate weak quality assurance (process) or quality control (testing).
2. Corrective action:
   • triage defects by severity,
   • halt release if critical defect violates acceptance criteria/security compliance.
3. Validation:
   • rerun relevant testing (regression),
   • verify non-functional requirements (performance/security).
4. Governance:
   • update decision on release readiness,
   • obtain approval to proceed.
5. Preventive actions:
   • strengthen peer reviews, coding standards, automated testing where possible.
6. Documentation updates:
   • defect register, lessons learned, revised test plan.

Practice Prompt 4: Procurement Contract Misalignment

Prompt: A vendor delivered a module that technically functions but does not meet acceptance criteria defined by the client. The vendor argues “the contract says it is delivered.”

Model answer outline:

1. Identify conflict:
   • acceptance criteria vs vendor interpretation.
2. Refer to:
   • acceptance criteria documents,
   • contract scope and deliverables,
   • change requests (if requirements changed).
3. Governance response:
   • request corrective action plan from vendor,
   • escalate if unresolved.
4. Quality control:
   • verify deliverable against acceptance criteria through testing/inspection.
5. Resolution options:
   • remediation at vendor cost,
   • re-negotiation with approved change request,
   • acceptance with documented residual risks (only if sponsor accepts).
6. Contract closure:
   • ensure formal sign-off after meeting criteria.

Putting It All Together: A “Universal” PM Answer Template

When you face an unfamiliar scenario, use a consistent template:

1. State the core problem (what is happening, what objective is threatened).
2. Choose the process area:
   • scope? time? cost? risk? quality? governance? change?
3. Differentiate risk vs issue and change vs clarification.
4. List actions in priority order:
   • control now, diagnose causes, propose corrective/preventive actions.
5. Mention artifacts:
   • risk register updates, issue log, change requests, schedule baseline, quality plan, acceptance criteria.
6. Explain how you’d communicate and escalate to decision-makers.
7. Conclude with measurable success criteria:
   • updated baseline approved, acceptance achieved, defects resolved within severity threshold, vendor deliverables validated.

This approach matches how PM course material is typically assessed: structured reasoning, correct process selection, and disciplined documentation and stakeholder management.

Final Consolidation: The UCT-Style PM Course “Must Know” Checklist

Use this checklist as a final revision tool before an exam. It is written to reflect the kinds of marks often awarded in PM modules.

Core process knowledge

• Initiation purpose and authorization
• Planning: scope/time/cost/risk/quality/communication/procurement
• Execution: deliverables creation and stakeholder coordination
• Monitoring & control: performance measurement and corrective actions
• Closure: handover, acceptance, contract closure, lessons learned

Scope and requirements

• WBS decomposition logic
• Requirements documentation and acceptance criteria
• Change control procedure
• Stakeholder validation and traceability discipline

Time and schedule

• Dependencies and critical path reasoning
• Schedule baselines and re-baselining discipline
• Resource capacity alignment

Cost and estimation

• Estimation approaches (analogous, parametric, bottom-up)
• Assumptions tracking and iterative refinement
• Forecasting and variance reasoning

Risk and issue management

• Risk register contents and risk response strategies
• Risk monitoring and trigger-based actions
• Issue log discipline and corrective actions

Quality and governance

• Quality assurance vs quality control distinction
• Testing readiness and regression mindset
• Governance approvals for change and release readiness

Procurement

• Vendor selection logic and evaluation criteria
• Contract acceptance criteria alignment
• SLAs, recovery plans, and escalation pathways

Communication and closure

• Communication plan structure (audience, frequency, channel, ownership)
• Closure deliverables: handover, documentation, lessons learned

Consistency Note (Course Material Alignment)

UCT-focused PM learning outcomes generally converge on the same assessment behaviours: correct process identification, structured reasoning, disciplined documentation, and stakeholder/governance alignment. This guide is designed to help you demonstrate those behaviours reliably, even when scenarios differ.