UP Programme in Project Management (PPM) Complete Study Notes

The UP Programme in Project Management (PPM) is designed to build practical competence in planning, executing, monitoring, and closing projects using structured project management principles and tools. These complete exam notes focus on what you are most likely to be assessed on: terminology, process knowledge, governance, scope/schedule/cost control, risk and procurement, and the integration of these topics into coherent project decisions. The notes are written to align with the kind of work typically tested in South African university project management modules (e.g., aspects that appear in Project Management and Operations/Management style courses at universities such as University of Pretoria (UP), University of South Africa (UNISA), and CUT).

1) Foundations of Project Management in the UP PPM: Concepts, Governance, and Project Life Cycles

What is a Project (and what is not)?

A project is a temporary endeavour undertaken to create a unique product, service, or result. This “temporary” quality means it has a defined start and end; “unique” means the output is not repeated exactly the same way every time. In exam questions, the most common errors are to confuse projects with routine operations (for example, ongoing manufacturing or recurring administrative tasks).

Project vs. Operations (high-yield distinction):

• Projects
  • Temporary: start/end defined
  • Unique deliverables
  • Progressive elaboration: requirements may become clearer over time
  • Risk and uncertainty are prominent
• Operations
  • Ongoing (continuous)
  • Repetitive outputs
  • Focus on efficiency and stable processes

Example scenario (typical exam style):
A municipality runs a regular service (water supply). That is operations. However, building and commissioning a new water treatment plant with a defined completion date is a project.

Project Management as an integration discipline

A major theme in the UP PPM is that project management is not a set of isolated tools. It is a discipline of integration: scope, schedule, cost, risk, quality, communications, procurement, and stakeholder management must be aligned.

If one area changes, others are affected. For instance:

• Increasing scope (more deliverables) usually increases cost and often impacts schedule.
• Tightening schedule typically increases risk (e.g., more overtime, rushed procurement).
• Ignoring stakeholder expectations may lead to poor acceptance at closure even if the technical work is correct.

Project life cycle: phases, governance, and decision gates

Most projects can be described through a life cycle composed of phases, each ending in some form of review or decision point. Typical phases include:

1. Initiation / Concept
2. Planning
3. Execution / Implementation
4. Monitoring & Controlling (often runs continuously)
5. Closing

A crucial exam insight: the life cycle phases are not the same as the project management process groups—though they interact. In practice, the life cycle determines the structure of decision-making and resource allocation.

Decision gates (common in governance):

• Gate 1: business case approval
• Gate 2: detailed plan approval
• Gate 3: readiness-to-execute approval
• Gate 4: acceptance of deliverables

Stakeholders and governance (why exams love this)

Stakeholders are individuals, groups, or organizations who can affect, be affected by, or perceive themselves to be affected by a project. Governance is the system of decision rights, reporting lines, and controls used to ensure accountability.

In the UP PPM context, you should expect questions about:

• Who are stakeholders?
• What power/interest do they have?
• What information do they need?
• How does the reporting structure support decisions?

Common stakeholder categories:

• Sponsor / Steering Committee: ensures resources, resolves escalations, approves major changes
• Project Manager: accountable for planning and delivery within constraints
• Functional managers: provide staff and expertise
• Customers / end users: validate deliverables, confirm acceptance criteria
• Regulators / auditors: ensure compliance
• Suppliers / contractors: deliver components or services per contract

Roles, responsibilities, and escalation

A frequently tested governance concept is RACI (Responsible, Accountable, Consulted, Informed). While RACI can be implemented at different levels, the exam expectation is that you understand accountability boundaries:

• The Project Manager is generally accountable for delivery performance and integrated planning.
• The Sponsor typically owns the business case and authorizes major changes.
• Steering committees provide oversight and decision escalation.

Example (escalation pathway):
If a cost overrun exceeds a tolerance threshold (e.g., 10%), the Project Manager escalates to the Steering Committee for approval of corrective actions (e.g., scope trade-off, schedule adjustment, additional funding request).

Knowledge areas mapped to project outcomes

A conventional project management framework divides work into knowledge areas such as:

• Integration
• Scope
• Schedule
• Cost
• Quality
• Resources
• Communications
• Risk
• Procurement
• Stakeholder management

Exams frequently test whether you can:

• identify which knowledge area is relevant to a given problem,
• select the correct tool/approach,
• explain the rationale.

Exam-ready takeaway

In UP PPM-style questions, you are rarely asked to memorise definitions only. You are asked to apply concepts:

• distinguish project vs operations,
• describe life cycle and decision gates,
• explain stakeholder influence and governance,
• justify the integration of planning controls.

2) Planning and Baselines: Scope, Schedule, Cost, Quality, and Change Control

Building the Project Management Plan

The Project Management Plan is a central document that consolidates subsidiary plans and baseline components used to manage execution and change. It typically includes:

• Scope management plan
• Schedule management plan
• Cost management plan
• Quality management plan
• Resource management plan
• Communications management plan
• Risk management plan
• Procurement management plan
• Stakeholder engagement plan

A strong exam answer explains not only what a plan contains, but why it exists: it provides consistent rules of the game for monitoring, control, and performance evaluation.

Scope management: requirements, scope definition, WBS

Requirements and scope definition

Requirements are conditions or capabilities needed by stakeholders. Scope definition converts high-level requirements into a more structured project description.

Key exam concepts:

• Product scope: features and functions of the deliverable.
• Project scope: work required to deliver the product.

Work Breakdown Structure (WBS)

The WBS decomposes the project into manageable deliverables and work packages. The WBS is often considered the backbone of accurate:

• scheduling (you schedule at work package level),
• costing (you cost at the same or compatible level),
• control (you track progress and performance per work package).

Example WBS snippet (construction or IT implementation):

• 1.0 Project Management
• 2.0 Requirements and Design
• 3.0 Infrastructure Setup
• 4.0 Software Development
• 5.0 Testing and Commissioning
• 6.0 Training and Handover

Under each, work packages include more specific tasks. In exam scenarios, you might be asked to identify:

• what belongs in the WBS,
• what doesn’t (e.g., activities not required for deliverables),
• whether an item is a deliverable vs a task.

Scope baseline and scope verification

A scope baseline often consists of:

• scope statement (with acceptance criteria),
• WBS,
• WBS dictionary.

Scope verification is confirming deliverables meet requirements. Scope control deals with managing changes to scope. If the customer acceptance criteria are not explicit, scope verification becomes subjective and leads to disputes during closing.

Schedule management: activities, sequencing, estimating, and critical path

Schedule work includes:

• defining activities,
• sequencing them (dependencies),
• estimating durations,
• developing the schedule,
• controlling schedule changes.

Dependencies (commonly tested)

• Finish-to-Start (FS): predecessor must finish before successor starts.
• Start-to-Start (SS): successor can start when predecessor starts (with lag).
• Finish-to-Finish (FF): successor cannot finish before predecessor finishes.

If you identify the wrong dependency type, the schedule logic breaks—an exam grader usually expects you to justify your choice.

Estimating and uncertainty

Duration estimates can be deterministic or probabilistic depending on method. A typical exam expectation is at least:

• understand what “estimate” means vs “commitment,”
• note that reserves exist to handle uncertainty.

Critical path (the logic behind exam questions)

The critical path is the longest path through the network diagram in terms of duration. Activities on the critical path affect project end date directly.

A high-quality exam response does not only state “critical path is X”; it explains:

• how float works (positive float = non-critical),
• why schedule slippage happens if critical activities slip,
• why schedule compression may increase cost or risk.

Cost management: budgets, cost estimates, and performance measures

Cost management includes:

• estimating costs,
• determining budget,
• controlling costs.

Cost baseline and budget

The cost baseline is the approved budget allocated to specific periods and components. Changes require formal control.

A standard exam framing: budget is not merely the total number; it is distributed across schedule time and work components.

Earned Value Management (EVM) as a control tool

EVM integrates scope, schedule, and cost to measure performance. The core metrics frequently tested include:

• PV (Planned Value): what should have been done by now (planned progress value)
• EV (Earned Value): what work was actually accomplished in terms of approved budget
• AC (Actual Cost): what it cost to achieve EV

Derived metrics:

• SV (Schedule Variance) = EV − PV
• CV (Cost Variance) = EV − AC
• CPI (Cost Performance Index) = EV / AC
• SPI (Schedule Performance Index) = EV / PV

Example (numerical logic):
If at a reporting date:

• PV = R200,000
• EV = R180,000
• AC = R210,000

Then:

• SV = 180,000 − 200,000 = −R20,000 (behind schedule)
• CV = 180,000 − 210,000 = −R30,000 (over budget)
• CPI = 180,000 / 210,000 ≈ 0.86 (cost efficiency poor)

Exams often ask you to interpret rather than just compute:

• negative variances mean underperformance,
• CPI < 1 implies spending more than earned value.

Quality management: standards, quality planning, assurance, control

Quality management is not just “inspection at the end.” It is proactive planning, assurance, and control.

Key concepts:

• Quality planning: determine quality standards and how to meet them.
• Quality assurance: audits and process improvements to ensure planned quality.
• Quality control: checking outputs (inspections, tests) to confirm compliance.

In South African exam settings, you may be expected to connect quality to compliance, documentation, and acceptance procedures. For example, deliverables in regulated domains (health, construction, safety) require traceability between requirements and test evidence.

Change control: integrated change management

In many projects, the biggest threat is not technical difficulty; it is uncontrolled changes. Integrated change control ensures changes are identified, evaluated, approved (or rejected), and documented.

Change control process (general structure):

1. Identify change
2. Document the change request
3. Evaluate impact on scope, schedule, cost, quality, risk, and stakeholder satisfaction
4. Decide approval or rejection
5. Communicate the decision
6. Update baselines and project documents when approved

A high-mark exam answer explains why “approval” matters:

• if you do not update baselines, you cannot measure performance accurately,
• stakeholders may assume changes are approved when they are not.

Baselines: what they are and what they protect

A baseline is a reference point. Typical baselines include:

• scope baseline,
• schedule baseline,
• cost baseline.

Baselines protect the integrity of planning. When performance is measured against baselines, the organization can determine:

• whether the project is progressing as expected,
• how much deviation exists,
• whether corrective actions are needed.

Practical example: managing scope creep in a university IT project

Consider a scenario:

• A university upgrades its LMS (learning management system) for enhanced accessibility and improved reporting.
• Initial scope: upgrade core modules, migrate 2,000 course pages, and deliver training for lecturers.
• Mid-project, stakeholders request additional features: a new analytics dashboard and integration with a separate timetabling system.

A strong planning-and-change answer would describe:

• the additional features as scope additions,
• the need for change requests,
• impact evaluation:
  • schedule impact (new development and integration testing),
  • cost impact (extra contractor time, additional software licenses),
  • quality impact (new test plans and acceptance criteria),
  • risk impact (integration complexity),
• how to update baselines and communicate changes.

Exam-ready takeaway

Planning and baselines are the foundation for credible control. In a UP PPM exam, you should demonstrate:

• WBS logic and scope control,
• schedule reasoning and critical path understanding,
• cost baseline and EVM interpretation,
• proactive quality management,
• integrated change control to protect baseline integrity.

3) Execution, Monitoring & Controlling, and Performance Reporting: Risk, Communication, Stakeholders, and Procurement

Execution: turning the plan into deliverables

Execution is where the project plan becomes real:

• direct and manage project work,
• acquire resources,
• manage quality during delivery,
• implement approved changes,
• manage communication and stakeholder engagement.

A key exam point: execution is not “doing tasks only.” It includes managing how tasks interact, ensuring deliverables meet acceptance criteria, and dealing with emerging issues using the governance structure.

Monitoring and controlling: what it includes

Monitoring and controlling runs throughout the project and includes measuring:

• scope status,
• schedule performance,
• cost performance,
• quality compliance,
• risk changes and issue status,
• stakeholder satisfaction signals,
• procurement status.

A good exam answer emphasizes that monitoring requires data:

• progress reports,
• test results,
• financial updates,
• contract performance,
• risk register updates.

Performance reporting: content and purpose

Performance reports are not just status. They explain:

• progress against plan,
• variances and trends,
• forecasted outcomes,
• decisions needed from governance bodies.

Typical reporting contents:

• planned vs actual progress (EVM metrics if used),
• key milestones achieved and upcoming,
• issues requiring escalation,
• changes approved since last report,
• risk updates including new threats and mitigations,
• resource constraints and commitments.

Risk management: identification to response implementation

Risk management is often assessed because it blends analysis, decision-making, and communication.

Risk identification

Risks can be identified through:

• brainstorming workshops,
• expert interviews,
• historical data,
• lessons learned repositories,
• analysis of assumptions.

Risk analysis

Risk analysis can be qualitative or quantitative, but exam answers should at least address:

• likelihood vs impact,
• risk ranking for prioritization,
• identifying triggers.

Risk response planning

Responses include:

• Avoid (change plan to eliminate risk)
• Mitigate (reduce likelihood or impact)
• Transfer (shift to another party via contract)
• Accept (no proactive action, with contingency reserves)

Risk monitoring and reassessment

As the project progresses, risks evolve:

• a mitigation might reduce likelihood but increase cost,
• new information can create new risks,
• risk “burn-down” is not automatic; it must be managed.

Issues management (separate from risk)

A common exam confusion: risks are uncertain events; issues are events that have already occurred. If a risk becomes reality, it should be moved into the issue register.

Example:

• Risk: “Supplier delivery may be late due to customs clearance.”
• Issue: “Supplier delivery arrived 2 weeks late.”

Proper exam answers describe how response strategies change once a risk becomes an issue.

Communication management: stakeholder needs and channels

Communication planning aligns messages with stakeholder roles, power, and information needs.

Key concepts:

• communication frequency,
• communication methods (email, meetings, reports),
• escalation routes,
• confidentiality and document control.

A high-mark communication example:
If procurement delays occur, the Project Manager should not only inform the procurement team but also:

• escalate to the sponsor if milestones or budgets are at risk,
• inform functional managers if staffing plans depend on delivery dates,
• notify end users if acceptance timelines shift.

Stakeholder management: engagement, resistance, and acceptance

Stakeholder management in UP PPM contexts is assessed because stakeholder alignment often determines acceptance and closure success.

A stakeholder engagement approach often includes:

• identify stakeholders and their interests,
• assess current engagement and desired engagement,
• plan engagement strategies (inform, consult, involve, collaborate, manage closely),
• monitor engagement effectiveness.

Resistance scenario:
End users may resist system changes if training is inadequate. Even if the technical deliverable meets requirements, poor adoption can lead to dissatisfaction and formal rejection or post-closure disputes.

Procurement management: make-or-buy and contract control

Procurement involves acquiring products, services, or results from outside the project organization.

Make-or-buy decisions

A make-or-buy decision considers:

• cost,
• capability and capacity,
• risk,
• timeline urgency,
• quality and compliance requirements.

Contract management

Once contracts are awarded, procurement control involves:

• monitoring supplier performance,
• managing contract changes,
• handling claims and disputes,
• ensuring delivered items meet acceptance criteria.

Procurement risks and transfers

A typical exam pattern is to explain:

• what risks can be transferred via contract,
• what risks remain internal (e.g., project planning mistakes, stakeholder acceptance problems).

Example:

• If a contractor is responsible for delivery of a module with a clear acceptance test, schedule risk is partly transferable.
• However, integration risk remains internal if the project team fails to plan interface testing or requirements traceability.

Monitoring supplier performance: measurable acceptance and evidence

Supplier performance measurement should be evidence-based:

• delivery dates,
• test results and defect rates,
• adherence to documentation and standards,
• responsiveness to change requests.

A strong exam answer ties procurement outputs to project baselines:

• if a supplier delivers late, schedule baseline must reflect agreed changes (or corrective schedule actions must be taken),
• if acceptance criteria fail, scope verification fails and closure cannot proceed.

Integrated response: an example of combining risk, cost, and schedule control

Consider a project budget situation consistent with exam logic:

• Planned value at reporting date (PV): R500,000
• Earned value (EV): R420,000 (progress behind plan)
• Actual cost (AC): R480,000 (spending less than earned value but still behind)

Compute:

• SV = EV − PV = 420,000 − 500,000 = −R80,000
• CV = EV − AC = 420,000 − 480,000 = −R60,000
• CPI = EV / AC = 420,000 / 480,000 = 0.875
• SPI = EV / PV = 420,000 / 500,000 = 0.84

Interpretation:

• negative CV and CPI < 1 indicate cost inefficiency relative to work accomplished,
• SPI < 1 indicates schedule slippage.

Then connect to risk:

• a high-risk item (e.g., integration testing) is delayed due to a supplier defect.
• mitigation: accelerate internal test resources, negotiate supplier corrective action, and adjust schedule logic.

A strong exam conclusion:

• show that EVM signals performance problems,
• propose corrective actions,
• justify why changes should go through integrated change control if baselines are impacted.

Exam-ready takeaway

This section tests the ability to:

• describe execution responsibilities,
• explain monitoring & controlling mechanisms,
• interpret performance reporting and EVM metrics,
• implement risk/issue management,
• plan stakeholder communication effectively,
• manage procurement with acceptance evidence and change discipline.

4) Tools, Techniques, and Quantitative Thinking for PPM: Network Logic, Estimation, EVM, Quality Tools, and Decision-Making

Why UP PPM exams test quantitative logic

Even when the course focus is applied project management, examiners assess whether you can reason with numbers and logic:

• if tasks are sequenced incorrectly, schedules fail,
• if estimates are unrealistic, budgets and baselines become meaningless,
• if EVM is misinterpreted, decisions become harmful.

This section builds the core computational and reasoning skills commonly required.

Network diagrams and schedule reasoning

Activity-on-node (AON) logic

In AON networks:

• each node is an activity,
• arrows represent dependencies.

In exam contexts, you may be asked to:

• identify critical path,
• calculate earliest start/finish and latest start/finish,
• compute float.

Float reasoning (conceptual):

• Total float = latest start − earliest start
• If total float = 0, activity is critical
• If total float > 0, activity can shift without affecting completion (until it consumes float)

Lag and lead (advanced but not always)

• Lag: delay between predecessor and successor
• Lead: negative delay (successor starts before predecessor finishes)

A strong answer includes:

• what lag/lead means in plain terms,
• why it changes the schedule.

Estimating methods: from expert judgment to structured estimates

Projects use estimation methods because uncertainty cannot be eliminated.

Types of estimates

Common categories:

• Order of magnitude: early rough estimate
• Budgetary estimate: planning-level estimate
• Definitive estimate: detailed, near-commitment

Estimation discipline

An exam-friendly answer should explain:

• why estimates should be updated as information improves,
• how assumptions must be documented,
• how cost and schedule reserves relate to uncertainty.

Cost forecasting with EVM (the logic behind CPI/SPI)

Beyond SV and CV, projects forecast future performance using EVM. A common calculation uses assumptions like:

• future performance may continue at current CPI/SPI rates,
• remaining work may require re-estimation based on trend.

Even if your course does not require all advanced formulas, it is important to interpret:

• CPI < 1 tends to indicate higher forecast cost,
• SPI < 1 tends to indicate delayed forecast completion (unless corrective actions occur).

Quality tools: beyond “inspection”

Quality control can use tools such as:

• checklists,
• run charts / control charts,
• Pareto analysis,
• cause-and-effect (fishbone) diagrams,
• sampling plans.

A high-mark exam response links tools to action:

• Pareto: focus on the few defect causes causing most problems,
• fishbone: systematically explore root causes across categories like people, process, equipment, materials, environment.

Risk quantification concepts (qualitative-first expectation)

Many project management courses start with qualitative risk assessments. Quantitative methods may include probability-impact modeling.

An exam answer should at minimum:

• define risk exposure conceptually,
• explain how probability and impact are combined for prioritization.

Decision-making under constraints: trade-offs and “best for project objectives”

A recurring exam theme is trade-offs between:

• scope,
• schedule,
• cost,
• quality,
• risk,
• stakeholder expectations.

A decision-making answer can be structured as:

1. Identify constraint(s) and objective(s)
2. Evaluate options
3. Estimate impacts on constraints and stakeholders
4. Choose option with best alignment to project objectives
5. Update baselines if approved changes occur
6. Communicate decisions

Mini case study (integrated quantitative reasoning)

Scenario: A university department launches an online learning support system.

Baseline plan:

• Deliver initial version by end of August
• Budget allocated for development and testing
• Acceptance criteria include system performance tests and user training completion

During execution:

• The team experiences defects in a critical module.
• The supplier is late with a prerequisite component.
• Stakeholders request additional reporting features.

As a student, you are expected to do integrated reasoning:

• Identify whether defects represent an issue and whether the requested features represent scope change.
• Explain which process groups and knowledge areas are triggered:
  • issues: monitoring & controlling; corrective action
  • new features: integrated change control; scope change; possible schedule and cost impacts
• Use EVM logic:
  • If EV < PV, progress behind plan.
  • If AC > EV, cost inefficiency.

Then propose actions:

• For defects: implement corrective and preventative actions, update quality control metrics.
• For supplier delays: renegotiate recovery schedule, consider whether contract change orders are needed.
• For extra features: evaluate priority vs schedule risk; decide accept/reject/phase features into a later release.

This case demonstrates the “UP PPM” style: structured logic, not just narrative.

Exam-ready takeaway

To score high, you need to demonstrate that you can:

• interpret schedule dependencies and critical path logic,
• relate estimation quality to planning reliability,
• use EVM metrics to forecast and decide,
• apply quality tools to improve deliverable acceptance,
• explain trade-off decisions in integrated terms.

5) Exam Practice Masterclass for UP PPM: Writing High-Scoring Answers, Common Pitfalls, Sample Questions, and Consolidated Frameworks

How to structure exam answers (a proven method)

UP PPM exam questions often require you to:

• define terms accurately,
• apply concepts to scenarios,
• justify choices,
• demonstrate understanding of processes.

A reliable structure:

1. Identify the concept/knowledge area
   (e.g., “This is an integrated change control issue.”)
2. Define and outline the correct process
   (briefly but correctly—what steps happen)
3. Apply to the scenario
   (what specifically you would do and why)
4. Add impacts and justification
   (scope/schedule/cost/quality/risk/stakeholder consequences)
5. Conclude with governance/communication
   (how you ensure accountability and updates to baselines)

Common pitfalls that lose marks

Pitfall 1: Confusing risk with issue

• If it has already happened, treat it as an issue.
• If it might happen, treat it as a risk.

Pitfall 2: Forgetting acceptance criteria at closure

A project can “finish” work but still fail to close if deliverables are not verified and accepted.

Pitfall 3: Ignoring baselines

Many marks are awarded for connecting control measures to baselines:

• without baselines, you cannot credibly measure performance.

Pitfall 4: Treating quality as a final inspection task

Quality planning and assurance are needed; relying only on inspection late increases rework.

Pitfall 5: Scope creep without formal change control

Uncontrolled additions are a direct path to variance and stakeholder dissatisfaction.

Sample exam question set (with model approach)

Below are common question types. They are written to mirror exam expectations: apply frameworks, interpret numbers when needed, and link processes to decisions.

Sample Question A: Project vs operations

Question: A company updates its production line for compliance every year and treats it as a “project.” Explain whether this is a project and justify your answer.

High-scoring approach:

• Use the project definition: temporary and unique deliverables.
• Contrast with operations: ongoing repetitive work.
• If compliance updates are routine and planned annually with predictable outputs, it is closer to operations; if each year’s update has unique outputs and temporary scope with defined end, it can be a project.

Sample Question B: Identify life cycle phases

Question: For a project to implement a new campus-wide learning platform, list likely phases and give one governance decision at the end of each phase.

High-scoring approach:

• Initiation: business case approval
• Planning: plan approval including baselines
• Execution: readiness-to-implement / milestone sign-off
• Monitoring and controlling: checkpoint approvals (risk and change reviews)
• Closing: acceptance and operational handover approval

Sample Question C: EVM interpretation

Question: At a reporting date, PV = R300,000, EV = R240,000, AC = R270,000. Determine SV, CV, and interpret schedule and cost performance.

Model calculation:

• SV = EV − PV = 240,000 − 300,000 = −R60,000 (behind schedule)
• CV = EV − AC = 240,000 − 270,000 = −R30,000 (over budget)
  Interpretation:
• Schedule is behind plan and costs are inefficient relative to earned value.

High-scoring addition:

• propose corrective action categories:
  • schedule: re-sequence, add resources (with caution),
  • cost: evaluate cost drivers, control rework,
  • change: verify if scope changes occurred and update baselines if approved.

Sample Question D: Integrated change control

Question: A customer requests additional features mid-project. Explain how to manage this request without harming baseline integrity.

High-scoring approach:

• treat as change request,
• evaluate impact across scope/schedule/cost/quality/risk,
• decide approval/rejection,
• if approved, update baselines and communicate changes.

Sample Question E: Risk response strategy selection

Question: A supplier may be late due to transportation disruptions. Suggest risk responses and justify which strategy best fits.

High-scoring approach:

• avoid may be difficult if supplier already chosen
• mitigate: buffer time, parallel procurement planning, early shipping
• transfer: use contract clauses for delivery and penalties
• accept: only if cost-effective and with contingency
  Justification uses likelihood/impact reasoning.

Consolidated frameworks you should memorise (but also understand)

Framework 1: Process-to-outcome mapping

• Scope definition → clear deliverables and WBS → better schedule/cost control
• Quality planning → fewer acceptance failures → smoother closure
• Risk planning → early mitigation of high-impact uncertainty
• Procurement planning → predictable external contribution and acceptance evidence
• Communication and stakeholder engagement → fewer late-stage surprises

Framework 2: Baseline integrity

When you measure performance against baselines:

• if you update without approval, you destroy control meaning,
• if you do not update after approved changes, you misinterpret performance.

Thus, integrated change control is essential.

Framework 3: Data discipline

Project control depends on credible data:

• progress data must reflect completed work,
• test results must have traceability,
• financial data must map to work packages.

“South Africa exam reality”: what markers look for

Although project management principles are global, South African examiners typically reward:

• structured answers using frameworks,
• correct terminology,
• application to local or plausible contexts (universities, public sector delivery, infrastructure, IT deployments),
• clarity about governance and accountability,
• and sensible numerical reasoning.

In many South African university curricula, students may see related course content in:

• Project Management modules at UP,
• management and systems modules at UNISA,
• and project/planning and operations-linked assessments at institutions like CUT.

So your answer should show that you understand how concepts are implemented—not only defined.

Mini integrated practice: one scenario, multiple questions

Scenario: A project to develop a “Student Support Portal” for a university.

Initial scope:

• user registration module
• ticket submission module
• knowledge base content upload process
• training for support staff

Midway, stakeholders request:

• an additional chatbot-like search feature,
• tighter integration with an existing student records system.

Problems encountered:

• supplier delay in a prerequisite integration component,
• increased defect rates during testing,
• support staff complain about insufficient training.

Questions (typical exam style):

1. Classify the chatbot request: risk or issue or scope change?
2. Explain what governance step should occur before implementing the requested chatbot feature.
3. Identify the most relevant control area for defect rates.
4. Describe what you would communicate to the sponsor given schedule delays and rising defects.

High-scoring answers:

1. Chatbot request is scope change (new feature request).
2. Integrated change control: evaluate impacts and approve/reject; update baselines if approved.
3. Quality control/assurance: implement defect root-cause analysis, adjust testing strategy, ensure acceptance criteria alignment.
4. Provide performance reporting:
   • schedule variance,
   • cost impact estimate,
   • risk/issue summary,
   • decisions needed (e.g., add testing resources, approve scope trade-off, revise milestone).

This integrated practice demonstrates competence across the UP PPM exam themes.

Final exam-ready synthesis (what to remember under pressure)

To pass—and especially to score well—in the UP Programme in Project Management (PPM) exam style, your brain must quickly connect scenario signals to correct actions:

• If requirements change → change control and scope impact evaluation
• If deadlines slip → schedule control, use critical path/EVM logic
• If spending rises → cost control and CPI interpretation
• If deliverables fail tests → quality control and root cause actions
• If uncertain events might occur → risk management
• If events already happened → issues management
• If external providers are involved → procurement control and acceptance evidence
• If stakeholders complain → stakeholder engagement and communication adjustments
• If governance decisions are needed → escalate with performance reporting and options

Cross-University Study Note (UP PPM Alignment with Common South African Module Styles)

In South Africa, students often cross-reference study patterns across universities. Even when modules differ (for example, a UP PPM module vs a UNISA management module), markers commonly assess:

• whether you know the process language (baselines, change control, WBS, quality assurance/control, risk registers),
• whether you can apply it to a plausible project scenario,
• and whether your answer is structured and justified.

A UP PPM-focused exam response that succeeds typically looks like:

• definitions + correct process steps,
• a scenario application with impacts across scope/schedule/cost/quality/risk,
• and at least one example (even short) to show understanding.

If you can do this, you are exam-ready

When you read any project management question, practice a rapid checklist:

1. What is the main problem type? (scope, schedule, cost, quality, risk, procurement, stakeholder, change)
2. What process should be used?
3. What is the baseline impact?
4. What evidence/data supports decisions?
5. Who decides and how do you communicate?

That is the practical heart of UP Programme in Project Management (PPM) Complete Study Notes—the integration of concepts into decision-making under constraints.