PMP Exam Preparation Course Notes (UP EUP)

These notes are designed for learners working through the University of Pretoria (UP) Programme in Project Management (PPM) Notes context, specifically aligned to the practical thinking you need for the PMI PMP® Exam. They blend the language of the PMBOK® Guide with scenario-based preparation so you can answer situational questions, not just recall definitions. You will find structured coverage of PM concepts, processes, tools and techniques, and exam-style decision logic—written for deep revision ahead of your PMP exam attempt.

University of Pretoria (UP) PMP Exam Readiness Notes: UP PPM–EUP Cluster Alignment

Positioning the PMP Exam Within UP PPM (EUP)

Learners often ask: “How do I connect UP PPM course content to the PMP exam?” The answer is to focus on the exam’s pattern of testing: the PMP does not reward memorisation alone—it rewards your ability to select the right next action given constraints like scope, schedule, cost, risk posture, stakeholder expectations, and governance.

In the UP Programme in Project Management (PPM) Notes collection, the “EUP” cluster is used here as a practical framing device: the focus is on exam readiness that mirrors the way projects are taught and evaluated in South African university modules—especially modules you might find in UP, UNISA, CUT, and similar institutions’ project management curricula. Typical module names vary by department, but common themes include:

  • Project Management principles and practice
  • Project integration and governance
  • Scheduling and cost estimating
  • Risk management and procurement
  • Stakeholder engagement and communication

Even if your course module codes differ, the PMP exam logic is consistent: you must understand how the process groups interact and how outputs flow into each other through the Knowledge Areas.

Exam skill that matters most

PMP questions usually present a situation and ask what the best action is. The “best action” is typically the one that:

  1. Uses the correct process group logic (e.g., planning vs executing vs monitoring/control vs closing),
  2. Uses the correct Knowledge Area logic (e.g., stakeholder engagement vs risk vs schedule),
  3. Respects the project management plan and change control,
  4. Treats governance and compliance requirements as first-class constraints,
  5. Applies tailoring: the right level of effort for the project’s complexity.

Exam Strategy for UP-Style Learning: From Concepts to Decision-Making

Many students underperform because they learn processes as isolated items. The PMP expects integrated thinking. For example:

  • You don’t “do risk management” generically; you do it with specific risk thresholds, risk categories, and tolerances.
  • You don’t “update the schedule”; you determine what schedule artifacts exist, decide the monitoring method, and then apply the appropriate schedule control updates.
  • You don’t “communicate”; you decide who needs what information, how often, and through which channels, based on stakeholder analysis and engagement strategy.

A strong UP PPM-style learning approach is to convert every concept into a decision chain:

Decision chain template (use for most PMP scenarios)

When you see a scenario, identify:

  1. What is happening? (e.g., change request, variance, risk event, stakeholder conflict)
  2. What is the artifact mentioned? (e.g., baseline, risk register, stakeholder register, project management plan)
  3. What is the governing mechanism? (e.g., change control system, configuration management, approval gates)
  4. What should happen next? (e.g., update planning outputs, request approval, implement corrective action)
  5. Which option aligns with best practice? (avoid “do everything” and avoid skipping control steps)

Mapping PMP Processes to What You’ll Recognise in Uni Modules

The PMP process structure (5 process groups × 10 knowledge areas) is sometimes taught as a grid. For exam readiness, you must instead treat it like a system:

  • Initiating: decide why and how the work begins; establish authority.
  • Planning: choose how to achieve scope objectives; create baselines.
  • Executing: do the work; manage people and resources.
  • Monitoring & Controlling: track performance against baselines; manage variances.
  • Closing: formalise acceptance and end.

A typical exam trap is to pick an answer that sounds reasonable but belongs to the wrong stage. Example patterns you’ll often see:

  • A question describes a variance discovered and asks the correct action—students might choose “plan improvements” (good idea) but the correct action is monitor/control first and decide corrective actions using baselines and performance metrics.
  • A change request is raised—students might choose “approve the change immediately.” The PMP expects change control, impact assessment, and approval decisions.

Stakeholder Engagement as a Core Exam Theme (UP PPM emphasis)

Even students who are strong in cost and schedule can lose points if stakeholder engagement is weak. PMP questions repeatedly test:

  • What information to communicate,
  • How often,
  • Which stakeholders to consult vs inform,
  • How to manage resistance and alignment.

A common scenario: a stakeholder is unhappy with project progress and begins influencing others. The best answer usually includes:

  • Verify information against project performance data,
  • Use stakeholder engagement strategy,
  • Escalate via appropriate governance if necessary,
  • Document communications and updates.

Governance and Compliance: The “Hidden” Determinant of Correct Answers

Governance appears indirectly in many PMP questions:

  • “Company policy requires procurement through a panel.”
  • “Regulator approval is needed before construction can proceed.”
  • “Contracts require formal change orders.”

If you ignore governance, you might choose a fast solution that violates constraints. The PMP expects you to:

  • Use the correct procedure,
  • Ensure approvals are obtained,
  • Update the project management plan and baselines properly.

Knowledge Areas and Process Group Integration: PMP Tools, Techniques, and Exam-Style Logic

Integration Management: The Backbone of PMP Scoring

Integration Management is tested heavily because it connects all other areas. It includes processes for developing the project charter, project management plan, directing and managing project work, monitoring and controlling project work, and managing knowledge/changes.

Key exam concepts you must operationalise

  1. Project charter: authorises the project and formally grants authority.
  2. Project management plan: the “single source of truth” integrating subsidiary plans and baselines.
  3. Direct and manage project work: execution coordination using plan guidance.
  4. Monitor and control project work: track, review, and identify variances.
  5. Perform integrated change control: evaluate changes and manage approvals.

A common exam question describes a change request. Students often try to solve it as a technical problem (e.g., redesign). The PMP expects you to solve it as an integration and governance problem:

  • What change control process is required?
  • What impacts must be assessed (scope, schedule, cost, risk, resources, quality)?
  • Who has authority to approve?

Mini case: Change request triggered by a stakeholder requirement

Scenario: A major stakeholder requests additional functionality not in the current scope. A junior manager says, “We can do it next sprint; it shouldn’t affect the schedule.”

Correct exam logic:

  • Treat this as a change request, not informal work.
  • Use integrated change control.
  • Assess impacts: the schedule baseline, cost baseline, risk posture, and quality requirements may shift.
  • Route for approval based on the configuration control board or governance mechanism.

Even if the additional functionality is beneficial, the PMP rewards the process that protects baselines and ensures decisions are traceable and approved.

Scope Management: Preventing Wrong “Replanning” Actions

Scope Management is tested through questions about:

  • requirement gathering quality,
  • scope definition accuracy,
  • WBS adequacy,
  • change control of deliverables.

Work Breakdown Structure (WBS) logic that appears in exam questions

A question might ask what the best next step is after deliverables change. Often the answer requires:

  • Updating WBS components,
  • Updating scope baseline,
  • Ensuring that requirements are reflected in deliverables and acceptance criteria.

Students sometimes confuse WBS with schedule. In PMP terms:

  • WBS supports scope control,
  • schedule is supported by activity definition and sequencing (though WBS can feed activity planning).

Acceptance criteria and “doing work without proving it”

Another exam trap is confusing “we completed tasks” with “we satisfied scope.” PMP requires acceptance criteria:

  • Confirm deliverables meet requirements,
  • Manage verification with quality processes,
  • Record acceptance in closing/handovers if appropriate.

Schedule Management: Variance Thinking and Correct Control Decisions

Schedule Management questions test your understanding of schedule performance:

  • planned vs actual progress,
  • critical path implications,
  • what reports indicate about future performance.

Tools and techniques you should recognise in scenarios

  • Critical Path Method (CPM) and float interpretation,
  • Schedule compression options (if described),
  • Progress reporting methods,
  • Schedule forecasts.

Example logic: Earned value used for schedule trend detection

Scenario: A project reports that tasks are behind schedule. Students might propose re-baselining immediately. The PMP typically requires:

  • Analyse variance (what part of the schedule is behind? is it critical path related?),
  • Forecast impacts using available data,
  • Recommend corrective actions through the governance and change control mechanism if baselines are at risk.

Cost Management: From Estimating to Performance Control

Cost Management is where many candidates struggle, especially those who learn cost estimates but don’t practise variance decision logic.

Core artifacts and baseline concepts

  • Cost estimates,
  • Cost baseline,
  • Funding requirements,
  • Performance reporting.

Earned Value Management (EVM) as exam heartland

EVM questions often ask:

  • What does a certain CPI or SPI mean?
  • What is the implication for future performance?
  • What action should follow?

For strong exam performance, you must be comfortable with the idea that:

  • CPI indicates cost efficiency,
  • SPI indicates schedule efficiency,
  • performance indices help forecasting and corrective action decisions.

Quantitative mini-scenario (EVM logic)

Imagine a project where Earned Value results show SPI < 1 (behind schedule) and CPI < 1 (over cost). The PMP likely expects:

  • Diagnose whether delays are impacting critical path,
  • Assess cost drivers,
  • Implement corrective actions tied to scope/schedule/resource needs,
  • Use change control if forecasts suggest baselines need formal updating under approval.

Quality Management: The “Conformance vs Performance” Distinction

Quality Management is tested in ways that reflect real project thinking:

  • prevention vs inspection-only approaches,
  • acceptance criteria vs “meeting internal standards”,
  • corrective vs preventive actions.

Exam-ready interpretation

  • Quality planning: define standards and how to meet them.
  • Quality assurance: processes ensure quality work is consistently delivered.
  • Quality control: verify deliverables meet requirements using metrics and inspection/testing.

Scenario pattern: a defect is found late. The best PMP answer typically includes:

  • Corrective action for the defect,
  • Preventive action to prevent recurrence,
  • Updates to quality management plan or lessons learned depending on severity and governance.

Resource Management: People Constraints and Assignment Logic

Resource Management includes planning, estimating, acquiring, and managing resources. The exam tests:

  • resource allocation realism,
  • skills-based assignments,
  • managing team performance.

Common stakeholder-and-team combined scenario

A team member leaves unexpectedly. Students might say “assign someone quickly.” The PMP expects:

  • Review resource requirements and availability,
  • Consider impact to schedule and scope,
  • Apply appropriate procurement or internal assignment,
  • Update relevant plans and communicate impacts through stakeholder channels and governance.

Communications Management: Stakeholder-Centric Communication Planning

Communications Management is frequently tested using:

  • communication planning,
  • information distribution,
  • performance reporting,
  • stakeholder communication management.

Exam trap: “More communication” is not always better

If a question says communication is too frequent or irrelevant, the best approach is often:

  • Update communication strategy based on stakeholder needs,
  • Use appropriate channels,
  • Ensure messages are meaningful, targeted, and timely.

Risk Management: Risk Register as a Living Governance Document

Risk questions often revolve around:

  • identifying risks,
  • analysing risks (qualitative vs quantitative),
  • planning responses,
  • tracking risks.

Risk response strategies you must apply correctly

  • Avoid,
  • Mitigate,
  • Transfer,
  • Accept,
  • Escalate response actions when thresholds are met.

Scenario pattern: a risk happens. The correct answer is usually:

  • Implement contingency plan,
  • Update risk register (outcomes and residual risks),
  • Analyse impacts to schedule/cost,
  • Communicate changes via stakeholder management and governance.

Procurement Management: Contracts, Change Orders, and Compliance

Procurement questions test:

  • when to procure,
  • how to plan procurements,
  • managing vendor relationships,
  • contract management and claims.

A frequent trap is ignoring contract terms. The PMP expects:

  • Change orders follow contract procedures,
  • Verification of deliverables according to contract requirements,
  • Proper acceptance and closure of procurement contracts.

Stakeholder Management: Managing Influence, Expectations, and Engagement

Stakeholder Management tests:

  • stakeholder engagement planning,
  • managing engagement (moving stakeholders toward desired outcomes),
  • monitoring engagement and adjusting actions.

Scenario-based logic

If a stakeholder is becoming resistant:

  • Assess current stakeholder engagement level,
  • Use engagement strategy adjustments,
  • Escalate issues according to governance,
  • Update stakeholder register and engagement plans.

Correctness often hinges on whether you:

  • address engagement through appropriate actions,
  • document communications and decisions,
  • avoid bypassing authority and governance.

UP PPM EUP Exam Drill: Five Process Groups with Full Scenario Walkthroughs

Initiating: When Authority, Need, and Boundaries Are Set

Initiating processes establish the “why” and “who authorises.” Exam questions often test:

  • whether the project charter exists,
  • whether stakeholders are properly identified,
  • whether business case rationale is used to justify decisions.

Project charter: what the exam expects you to do with it

In scenarios, the charter provides:

  • authority to start,
  • high-level objectives,
  • alignment with organisational strategy.

If the charter is missing, the correct approach is usually to:

  • ensure authorisation,
  • validate stakeholder needs and project objectives,
  • avoid execution without proper governance.

Mini case: Starting work without charter

Scenario: A team starts procuring materials before a charter is signed because the timeline is tight.

Best PMP logic:

  • Re-evaluate; execution needs governance authority.
  • Trigger corrective action through organisational processes.
  • Ensure charter and approval gates are met before committing resources.

Planning: Baselines, Subsidiary Plans, and Decision Coherence

Planning questions dominate because baselines are foundational:

  • scope baseline,
  • schedule baseline,
  • cost baseline,
  • and subsidiary plans that feed integrated decisions.

Baseline thinking in exam scenarios

When asked what to do after performance variance is discovered, the exam often tests whether you:

  • compare to baseline,
  • decide corrective vs preventive action,
  • decide whether a change control action is required.

Students sometimes choose “update baseline immediately.” PMP typically prefers:

  • perform analysis and corrective action first,
  • request change approvals if baselines truly need adjustment.

Planning outputs that often appear

  • Requirements documentation (and traceability logic),
  • WBS,
  • schedule management plan and schedule baseline,
  • cost management plan and cost baseline,
  • risk register and risk response plans,
  • stakeholder engagement plan.

Executing: Directing Work, Managing Team, and Implementing Approved Changes

Executing questions test:

  • whether work is done according to the plan,
  • whether changes are approved,
  • whether team dynamics and execution coordination are properly addressed.

Example: implementing an unapproved change request

Scenario: A contractor insists on a scope modification; the project manager says, “Let’s just proceed; we’ll paperwork later.”

Best PMP logic:

  • No—if it affects scope/schedule/cost, it must go through integrated change control.
  • Ensure approvals are obtained before implementation.
  • Use procurement contract change mechanisms if vendor involvement exists.

Monitoring & Controlling: Variance Analysis and Corrective Action Selection

Monitoring & controlling is about measuring performance and taking action when there’s variance.

Variance analysis pattern

Scenario: After a review, the team sees deliverables are trending toward non-compliance.

Correct exam response usually includes:

  1. Analyse performance data,
  2. Determine root causes,
  3. Recommend corrective actions aligned with scope/schedule/cost/quality,
  4. Update relevant documentation and reporting,
  5. If necessary, use change control.

The key is to avoid random action. The PMP expects a controlled, evidence-based response.

Example: risk realisation and control response

Scenario: A risk about supply delays occurs. The project is now behind schedule.

Correct actions commonly include:

  • implement contingency plans,
  • update risk register and assumptions,
  • coordinate schedule adjustments through plan-managed change,
  • communicate impact to stakeholders and governance.

Closing: Acceptance, Formal Completion, and Lessons Learned

Closing questions test whether you:

  • secure formal acceptance,
  • finalise procurements,
  • archive documents,
  • capture lessons learned.

A common trap: closing too early. PMP expects:

  • acceptance against requirements,
  • completion of contract requirements,
  • final reporting.

Mini case: procurement contract closure

Scenario: The vendor delivered goods but documentation is incomplete. The project manager closes the procurement contract anyway to “finish faster.”

PMP likely expects:

  • don’t close without required verification and documentation,
  • manage acceptance formally,
  • ensure contractual obligations are met.

UP PPM EUP Mastery Notes: Exam Math, Probability Thinking, and High-Probability Answer Patterns

Quantitative Reasoning for PMP: What You Must Be Comfortable With

Even though not every PMP question is arithmetic-heavy, the exam repeatedly tests quantitative reasoning:

  • interpreting indices (CPI/SPI),
  • understanding percent complete concepts,
  • reading schedule and cost performance narratives,
  • connecting forecasts to corrective actions.

Practical approach to PMP calculations

When you see a numeric question:

  1. Identify what the metric represents (efficiency vs cost impact vs schedule impact).
  2. Determine whether the question asks for interpretation or a derived number.
  3. Ensure unit consistency (days/weeks, currency, percentages).
  4. Choose answer options that reflect correct meaning, not just plausible math.

Probability Thinking in Risk Management

Risk questions often require understanding uncertainty:

  • likelihood and impact combination,
  • expected value logic in quantitative scenarios,
  • thresholds and triggering of responses.

Expected Monetary Value (EMV) logic (conceptual emphasis)

In EMV questions, you typically compute:

  • EMV = probability × impact (for that event),
  • compare EMVs across alternatives,
  • choose the response that best supports project objectives.

Even if a question is not explicit about EMV, the correct logic often resembles expected value thinking: you compare risk response options based on likelihood and impact.

Example: selecting a risk response under limited budget

Scenario: Two responses are available:

  • Option A reduces risk likelihood slightly,
  • Option B reduces risk impact substantially but costs more.

Best PMP logic:

  • evaluate trade-offs based on risk exposure and project priorities,
  • consider constraints and governance approval requirements.

Change Control Decision Patterns: The #1 “Process Selection” Theme

Many PMP questions are not about the “right technical solution” but about whether you:

  • follow change control,
  • protect baselines appropriately,
  • ensure approvals.

High-probability exam pattern: “Change has been requested; what’s the next step?”

Typical correct answer structure:

  1. Record the change request.
  2. Assess impacts on scope, schedule, cost, quality, risk, and resources.
  3. Review alternatives.
  4. Submit to the change control board or responsible authority.
  5. Once approved, update baselines and plans.

This pattern appears in scope changes, schedule shifts, budget increases, and requirement additions.

Counter-argument students often fall for

  • “It’s urgent; just do it and update documents later.”
  • “We already agreed verbally with the stakeholder; that’s enough.”

PMP logic counters:

  • verbal agreement is not governance,
  • updates must happen through approved mechanisms,
  • documentation supports traceability and auditability.

Stakeholder Conflict Scenarios: Evidence-Based Engagement

Stakeholder questions often include conflict:

  • delays due to approval cycles,
  • resistance to scope changes,
  • misunderstandings about deliverable expectations.

High-probability correct answer structure

Usually includes:

  • clarify requirements/expectations,
  • communicate performance data and rationale,
  • adjust engagement approach based on stakeholder needs,
  • escalate if governance indicates.

Example: stakeholder demands override team plan

Scenario: A powerful stakeholder demands a deliverable that violates acceptance criteria.

Best PMP response:

  • evaluate against requirements and acceptance criteria,
  • align the request through change control if it alters scope,
  • communicate implications to stakeholder and governance.

Procurement and Contract Change Logic: “Don’t Break the Contract”

Procurement questions often test:

  • contract management,
  • vendor performance monitoring,
  • change order processes.

Example: vendor claims additional compensation

Scenario: Vendor states additional payment is required due to delays caused by earlier project decisions.

Best PMP logic:

  • verify claim against contract terms,
  • review evidence, documentation, and schedule and scope responsibilities,
  • handle via procurement change control and legal/contract management mechanisms.

The PMP rewards structured contract handling rather than ad hoc negotiation.

Data-Driven Reporting: Selecting the Right Reporting Output

Monitoring and controlling questions often ask:

  • what report should be used,
  • what information should be included,
  • how to communicate it to stakeholders.

Typical PMP reporting components

  • performance against baselines,
  • variance analysis,
  • forecast status,
  • status of deliverables,
  • risk updates and response progress,
  • change requests status.

Best answers reflect:

  • correct stakeholder channel selection,
  • timely reporting,
  • evidence-based updates.

Intensive Exam Practice: Question Types, Answer Rationale, and Tactical Review Cycles

Understanding PMP Question Styles (What They Really Test)

PMP questions usually do one or more of the following:

  1. Process group recognition: what stage are we in?
  2. Knowledge area recognition: which domain is being impacted?
  3. Artifact recognition: which document/baseline/risk register is relevant?
  4. Governance recognition: approvals, compliance, and authority.
  5. Next-step logic: what should happen immediately next?

Your goal is to identify which of the five dominates.

Common Option Traps and How to Eliminate Them

Trap 1: “Jump to corrective action” without analysis

Correct answer often requires:

  • analyse variance first,
  • then decide corrective action.

Trap 2: “Update without governance”

Correct answer usually requires:

  • change control approval before baseline modifications.

Trap 3: “Communicate more broadly”

Correct answer usually requires:

  • targeted communication based on stakeholder needs and engagement strategy.

Trap 4: “Close early”

Correct answer usually requires:

  • acceptance and completion of obligations.

Trap 5: “Ignore procurement contracts”

Correct answer usually requires:

  • formal procurement and contract procedures.

Tactical Review Cycles: How to Study for Maximum Recall

A high-performing study approach cycles between:

  • concept refresh (definitions and process logic),
  • scenario drilling (exam-like question practice),
  • weak area remediation (targeted review).

A recommended UP PPM-friendly cycle (adapt to your schedule):

  1. Learn one Knowledge Area concept block (e.g., Risk responses).
  2. Immediately drill 10–20 scenarios focused on that concept.
  3. Identify incorrect option patterns.
  4. Review the process artifact and governance step.
  5. Re-drill a mixed set including Integration and stakeholder items.

This prevents the common failure mode: knowing definitions but missing the next-step selection.

Mini “Scenario Bank” for Rapid Revision

Below are short scenarios designed to rehearse decision logic. They are written to mirror PMP style without requiring heavy arithmetic.

Scenario A: Schedule variance discovered

The team reports that certain deliverables are slipping and the project manager wants to “fix it by increasing overtime immediately.”

Best exam logic:

  • analyse the variance and root causes,
  • assess impacts on cost and team resources,
  • implement corrective actions aligned with plan,
  • use change control if schedule baseline adjustments or significant cost changes are needed.

Scenario B: Quality nonconformance

A defect is discovered during inspection. The team says, “We will ignore it unless the stakeholder complains.”

Best exam logic:

  • conduct quality control verification and root-cause,
  • apply corrective actions,
  • update quality records and communicate risks/impacts appropriately.

Scenario C: Stakeholder requirement addition

A stakeholder requests additional features after planning is complete.

Best exam logic:

  • log change request,
  • assess scope/schedule/cost impacts,
  • route through integrated change control,
  • update baselines if approved.

Scenario D: Procurement vendor claim

Vendor submits claim due to alleged delays.

Best exam logic:

  • check contract obligations and evidence,
  • follow contract management and procurement change processes,
  • update project records transparently.

Final Consolidation: A Unified Checklist for PMP Exam Day Decisions

The “UP PPM EUP” Unified Checklist

Use this checklist when solving any PMP scenario question. It will help you choose the most correct answer rather than the most familiar one.

Step 1: Identify the project stage (process group)

  • Initiating: authority, charter, high-level definition.
  • Planning: baselines, subsidiary plans, risk response planning.
  • Executing: deliver work, manage team, implement approved changes.
  • Monitoring & Controlling: performance vs baselines, variance analysis, corrective actions.
  • Closing: acceptance, contract closure, documentation finalisation.

Step 2: Identify the Knowledge Area implicated

  • Integration: change control and plan coherence.
  • Scope: requirements, WBS, deliverables acceptance.
  • Schedule: variance, forecasts, schedule baseline integrity.
  • Cost: cost baseline, forecasting, EVM interpretation.
  • Quality: conformance, QA vs QC, corrective vs preventive actions.
  • Resources: acquisition, assignment, team performance.
  • Communications: distribution, reporting, stakeholder needs.
  • Risk: register updates, response implementation, thresholds.
  • Procurement: contract management, change orders, vendor performance.
  • Stakeholders: engagement plans and influence management.

Step 3: Identify the artifact and governance mechanism

Look for cues in the question:

  • baseline mentioned → compare and analyse, then control.
  • change request mentioned → integrated change control.
  • contract mentioned → procurement change processes.
  • stakeholder name/influence mentioned → stakeholder engagement plan updates.

Step 4: Choose the next step that aligns with evidence and approval

Best answers tend to be:

  • evidence-based (using performance data or documented criteria),
  • governance-aligned (approvals and controlled updates),
  • forward-moving without bypassing controls.

Exam-Day Triage: How to Handle Uncertainty

If you’re stuck between two answers:

  1. Prefer the option that follows correct process logic and governance.
  2. Prefer the option that references the correct artifact (baseline/risk register/stakeholder plan/contract).
  3. Avoid answers that skip approvals or ignore change control.
  4. Avoid “do everything” answers if they do not match the next-step requirement.

The “Most Correct” Mindset

PMP exam questions are often designed so that multiple options sound plausible, but only one is most correct in the sense of:

  • best aligned with PM best practice,
  • correct stage and domain,
  • correct sequencing of actions.

If you adopt that mindset consistently, your accuracy improves significantly.

Study Appendix: High-Frequency Concepts for Rapid Recall (UP PPM Revision Sheet)

High-Frequency Concepts to Memorise for Meaning (Not Just Words)

  • Project charter: authorises the project; links to business need.
  • Project management plan: integrated, includes baselines and subsidiary plans.
  • Integrated change control: evaluates and manages changes across baselines.
  • Corrective action vs preventive action: corrective fixes identified issues; preventive reduces likelihood of future issues.
  • Stakeholder engagement: tailored communications and actions based on stakeholder needs and influence.
  • Risk response implementation: contingency actions when triggers/thresholds are met.
  • Procurement contract management: performance tracking and change orders under contract terms.
  • Quality assurance vs quality control: system improvement vs deliverable verification.
  • EVM interpretation: efficiency indices guide forecasting and corrective decisions.

Rapid Concept-to-Scenario Mapping (One-Liners)

  • If it’s a new requirement → likely scope change request + integrated change control.
  • If it’s variance vs baselinemonitor/control + corrective action.
  • If it’s risk realisedimplement risk response + update risk register.
  • If it’s vendor performance or claimprocurement management + contract process.
  • If it’s acceptance or closureverification and formal closure.

End of PMP Exam Preparation Course Notes (UP EUP).

Select the fields to be shown. Others will be hidden. Drag and drop to rearrange the order.
  • Image
  • SKU
  • Rating
  • Price
  • Stock
  • Availability
  • Add to cart
  • Description
  • Content
  • Weight
  • Dimensions
  • Additional information
Click outside to hide the comparison bar
Compare