Advanced Project Management (APM) UJ Study Material

Advanced Project Management (APM) is where traditional project management evolves into a strategic, high-risk, decision-heavy discipline. For students preparing for the University of Johannesburg (UJ)—especially those studying within the College of Business & Economics—APM content typically expects strong command of planning under uncertainty, stakeholder governance, risk and change control, quality and benefits management, and the leadership skills required to deliver complex outcomes in real organisations.

This study guide is written to align with the kinds of competency areas assessed in APM-style modules you may encounter in UJ programmes (and related South African project management courses). It also integrates the practical exam approaches common in South African universities such as Unisa and CUT, while remaining focused on what you likely need for UJ examinations and assignments: well-structured answers, correct frameworks, and evidence-backed examples.

Section 1: Advanced Project Planning, Scope Control, and Strategic Alignment (UJ exam focus)

1.1 From “basic planning” to advanced planning logic

In introductory project management, planning often looks like: define scope → draw a schedule → assign tasks → start execution. In Advanced Project Management (APM), planning becomes a more sophisticated decision system because the project environment is rarely stable. Instead of planning for an ideal world, APM plans for:

Uncertainty (unknowns about requirements, markets, technology, or approvals)
Constraints (time, budget, capacity, legal compliance, procurement lead times)
Conflicting stakeholder interests (e.g., business wants speed; compliance wants controls)
Dynamic scope evolution (new requirements, de-scoping pressures, change requests)

A strong APM answer typically explains that advanced planning is not only about producing documents—it’s about setting up governance, controls, and assumptions so the project can adapt without losing alignment to objectives.

1.2 Strategic alignment: why “doing the project” is not enough

APM assessments frequently test the difference between activity delivery and value delivery.

Strategic alignment requires you to demonstrate how the project contributes to one or more of the following:

Organisational strategy (growth, cost reduction, service improvement, digital transformation)
Corporate governance objectives (risk management maturity, regulatory compliance)
Service outcomes (reliability, customer satisfaction, turnaround times)
Financial outcomes (ROI, cost avoidance, revenue uplift)
Capability outcomes (new competencies, improved processes)

A useful exam phrasing is:

The project plan must be traceable to business objectives through measurable benefits, and governance must ensure that scope decisions preserve that traceability.

1.3 Problem framing and scope hierarchy

Advanced planning begins with clarity on what problem the project solves. A common technique is to treat scope as a hierarchy, not a single statement.

A practical scope hierarchy can be:

Project purpose (why it exists)
Project outcomes (what changes in the organisation)
Deliverables (tangible outputs)
Work packages / activities (how outputs are produced)
Acceptance criteria (how you know you got it right)

Example: upgrading an enterprise reporting system

Consider a hypothetical UJ-aligned scenario: a university department needs an enterprise reporting system upgrade. Your scope hierarchy could be:

Purpose: improve decision-making through accurate dashboards
Outcomes: reduced reporting cycle time; improved data accuracy
Deliverables: upgraded reporting platform; validated data models; training materials
Work packages: requirements workshops; data migration; dashboard development; user training
Acceptance criteria: dashboards produce agreed metrics; system uptime target met; training completion records verified

In an exam, if you describe deliverables without linking them to outcomes and acceptance criteria, your answer usually loses marks because APM expects traceability.

1.4 Scope definition vs scope control

A key APM concept is that scope control is an ongoing governance function, not a one-time “scope statement” exercise.

Scope definition (front-end work)

Scope definition activities include:

Requirements elicitation (interviews, workshops, surveys)
Stakeholder analysis (who needs what and why)
Requirements documentation and prioritisation
High-level WBS (Work Breakdown Structure) creation
Initial estimates and feasibility review

Scope control (during execution)

Scope control typically includes:

Change request management
Impact assessment (time, cost, quality, risk, resources)
Configuration management (especially for deliverables with versions)
Requirements traceability and acceptance testing

Exam point: If you must write a short answer, include both “definition” and “control” to demonstrate full comprehension.

1.5 Change control: integrated and disciplined

Advanced projects usually experience change. The difference between success and failure often lies in how change is handled.

A disciplined approach includes:

Log the change request (so decisions remain auditable)
Analyse impact using integrated thinking:
- Schedule impact (critical path changes)
- Cost impact (labour, materials, vendor changes)
- Quality impact (does it reduce or increase defect risk?)
- Risk impact (new uncertainties introduced)
- Stakeholder impact (training, communications workload)
Decide (approve/reject/approve with conditions)
Update plans (WBS, schedule, budget, risk register)
Communicate decision (so expectations remain aligned)
Verify and close the change (ensure acceptance criteria met)

Case illustration: scope creep in a procurement project

Imagine a logistics project: a contractor delivers a warehouse management system. During testing, stakeholders ask for additional integration with a legacy inventory system. If the change isn’t controlled:

Developers may add features “quickly” without proper testing coverage.
UAT (User Acceptance Testing) extends.
Defects increase.
Delivery date slides.
Procurement costs rise (additional licences, vendor hours).

In an APM exam answer, you should explicitly show how the change control mechanism prevents this: change request → impact assessment → governance decision → plan update.

1.6 Work Breakdown Structure (WBS) for advanced estimation

A simple WBS is not enough. Advanced WBS practices include:

Decomposition to a level that supports reliable estimation
Clear ownership (work packages assigned to responsible roles)
Definition of deliverable boundaries (what’s included/excluded)
Traceability to requirements and acceptance criteria
Alignment with cost accounts and reporting structures

WBS quality checks (useful for exam marks)

You can mention:

Does each work package have a measurable output?
Can the package be estimated realistically?
Are dependencies identified (interface points)?
Is duration or effort derived from reasonable assumptions?
Do work packages sum back to deliverables?

1.7 Scheduling under uncertainty: beyond deterministic logic

Advanced scheduling includes risk-aware planning.

Approaches often discussed in APM contexts:

Buffering (project buffers, feeding buffers)
Contingency reserves (time/cost contingency linked to risk)
Rolling wave planning (detail near-term work, keep long-term broader)
Critical chain thinking (resource constraints acknowledged)
Monte Carlo style thinking (in theoretical exam cases, probabilities for completion)

In exam answers, you don’t need to calculate Monte Carlo simulations unless the question demands it—but you should demonstrate the principle: plan with uncertainty and reflect it in reserves.

Section 2: Risk Management and Governance—From Risk Registers to Decision Quality

2.1 Risk in APM: the shift from “list risks” to “manage outcomes”

In many undergraduate settings, risk management becomes a spreadsheet exercise. In APM, you’re expected to show decision quality: identify risks, analyse them properly, choose responses intentionally, and monitor them with governance.

A strong APM risk management answer includes:

Risk identification using structured techniques
Risk analysis (likelihood, impact, sometimes exposure)
Response planning (avoid, mitigate, transfer, accept, exploit)
Ownership assignment (who is responsible)
Monitoring and triggers (what would make you act?)
Integration with schedule/cost baselines and change control

2.2 Risk identification techniques (with exam-ready examples)

You can explain commonly tested methods, such as:

Brainstorming with cross-functional stakeholders
Delphi method (anonymous expert input to reduce bias)
Interviewing subject matter experts
Checklists from similar projects
Root cause analysis (especially for known recurring problems)
Assumption analysis (identify fragile assumptions)
SWOT-linked risk mapping (strengths/opportunities can be exploited; weaknesses/threats become risks)

Example: assumption-driven risk register

In a project where suppliers must deliver equipment by a fixed date, assumptions might include:

Suppliers have stock available
Customs clearance will not delay shipments
Installation team availability matches schedule

If an assumption is violated, risk levels rise. APM expects you to treat assumptions as “pre-identified vulnerabilities.”

2.3 Risk analysis: qualitative, semi-quantitative, and quantitative thinking

Even if the exam question is theoretical, you should explain levels.

Qualitative analysis

Likelihood rating (Low/Medium/High)
Impact rating (Low/Medium/High)
Risk matrix for prioritisation

Semi-quantitative analysis

Numerical scoring (e.g., likelihood 1–5; impact 1–5)
Exposure approximations (not necessarily full probabilistic modelling)

Quantitative analysis (when required)

Expected monetary value (EMV) for specific risks
Probabilistic schedule estimation
Sensitivity analysis (which assumptions drive results?)

Consistency note for exam writing: If you provide a scoring method once, stick to it in your answer. For instance, if “High impact = 5” in one part, don’t later treat “High impact = 4.”

2.4 Response strategies: choosing the right response

APM expects more than naming response types. You must link responses to the risk nature.

Common responses:

Avoid: change plan to eliminate risk
Mitigate: reduce likelihood or impact
Transfer: shift impact to another party (insurance, contract terms)
Accept: no proactive action; monitor and keep contingency
Exploit (for positive risks): ensure opportunities materialise
Enhance: increase probability/impact of opportunities

Example: transfer risk vs mitigate risk

If risk is “vendor delays delivery,” you can:

Transfer: implement penalty clauses and strict milestones in the procurement contract
Mitigate: add supplier redundancy, qualify alternative vendors, or shorten internal dependency time
Accept: do nothing beyond monitoring, but reserve contingency time

An APM exam marker values the explicit justification:

Why choose mitigation instead of transfer?
What happens if the contract penalty is unenforceable?

2.5 Risk ownership and escalation governance

A risk owner is not just a person who “knows about the risk.” In APM, risk ownership implies:

The owner can influence the risk (direct control or leverage)
The owner monitors indicators
The owner prepares response actions
The owner escalates if triggers are breached

A governance-aligned model can include:

Weekly project risk review in team meetings
Monthly steering committee review for top risks
Formal escalation thresholds (e.g., “if risk impact rating increases from Medium to High, escalate within 48 hours”)

2.6 Triggers and early warning indicators

A frequent exam weakness is vague monitoring: “monitor risk” without specifying indicators.

Use early warning indicators such as:

Schedule triggers: milestone slippage beyond a threshold
Cost triggers: labour productivity variance exceeds a planned limit
Quality triggers: defect rates exceed testing thresholds
Vendor triggers: late delivery frequency or missed QA documents
Stakeholder triggers: repeated feedback contradictions or approval delays

Example: procurement early warning

For a procurement-driven project:

Trigger: supplier lead time estimate increases by more than 10%
Response: activate alternative supplier plan or renegotiate delivery terms

2.7 Integrated risk with schedule and budget (contingency logic)

Advanced APM ties risk response to contingency reserves:

Time contingency: protects schedule against uncertain duration risks
Cost contingency: protects budget against uncertain cost drivers

In answers, you should show the logic:

Identify critical risks affecting the critical path
Allocate contingency proportionally (or at least rationally)
Keep reserves auditable via risk response linkage

2.8 Governance in APM: steering committees and decision cadence

Governance is the system that ensures correct decisions happen at the right time.

Common governance structures include:

Project sponsor (owns business case and escalations)
Steering committee (oversight, approvals, policy decisions)
Project manager (operational control)
Technical review board (quality/engineering assurance)
Procurement board (contracting decisions)

APM exam questions often ask how governance reduces risk of:

Unauthorised scope expansion
Misaligned priorities
Decision delays
Conflicting stakeholder approvals

A high-quality APM answer states governance must define:

Decision rights (who approves what)
Reporting frequency
Escalation paths
Acceptance and sign-off responsibilities

Section 3: Stakeholder Management, Communication Planning, and Quality/Benefits Integration

3.1 Stakeholders as active drivers of project outcomes

Advanced projects are rarely derailed by “technical difficulty alone.” They are derailed by mismanaged stakeholder expectations, unclear decision rights, or inadequate communications.

In APM, stakeholder management includes:

Identifying stakeholders and their influences
Understanding stakeholder needs and constraints
Mapping power/interest and engagement level
Designing tailored engagement strategies
Managing conflicts through governance and structured negotiation

3.2 Stakeholder analysis: power, interest, and influence mapping

A stakeholder matrix typically uses:

Power (ability to affect resources, approvals, or constraints)
Interest (how strongly they care about outcomes)

But APM adds more nuance:

Stakeholder influence may not equal formal power.
Influence can be operational (e.g., engineering leads) even without executive authority.
Stakeholder positions can shift over time (e.g., as project risks change).

Example: university-led system implementation

For a university internal project:

Senior finance manager may have high power and high interest.
Department lecturers may have moderate power but high interest (because system affects teaching/admin workflows).
IT support staff may have high influence but low formal power (they determine feasibility and integration success).

APM answers should mention engagement strategies:

High power/high interest: frequent briefings, involvement in key decisions
Low power/low interest: periodic updates
High power/low interest: ensure they are satisfied enough to maintain approval
Low power/high interest: keep them informed and reduce resistance

3.3 Communication planning: not just reporting, but tailoring

Communication in APM must match stakeholder needs.

Common communication artefacts:

Project charter summary (strategic purpose)
Status reports (schedule/cost/risks/decisions)
Risk and issue logs (for governance scrutiny)
Change control notices (what changed and why)
Quality reports (defects, audits, compliance)
Benefits tracking dashboards (value realisation)

Tailoring communications

For example:

Sponsor: needs trend signals, decision requests, and business case implications.
Technical leads: needs detail, testing results, and interface risks.
End users: needs training timelines, process changes, and support availability.

A common exam expectation is to include communication objectives:

Inform
Consult
Involve
Collaborate
Empower (advanced engagement)

3.4 Issue management vs risk management

Another frequent APM distinction:

Risks: uncertain events that may occur
Issues: events that have occurred and require action

APM exam answers often score higher when you:

Show how risks become issues when they materialise
Explain how issues are prioritised and resolved
Mention escalation mechanisms and corrective action closure

3.5 Managing conflict: structured negotiation and decision rights

Stakeholder conflict may emerge around:

Scope: “must-have” vs “nice-to-have”
Time: delivery date vs quality assurance time
Cost: procurement budgets vs vendor requirements
Compliance: regulatory demands vs operational convenience

Advanced APM uses structured approaches:

Clarify decision rights (RACI-style responsibility/authority concepts)
Use objective criteria (e.g., business case impact, compliance requirements)
Run trade-off analyses
Document decisions and assumptions

In an exam, you can use phrasing like:

“Trade-offs are governed through change control; decisions are traceable to acceptance criteria and business objectives.”

3.6 Quality management: quality planning, assurance, and control

Quality in APM is not “inspection at the end.” It includes:

Quality planning: define standards, acceptance criteria, quality metrics
Quality assurance: process audits to ensure work will meet standards
Quality control: verify outputs meet requirements (testing, inspections, reviews)

Example: software deliverable quality

Quality dimensions could include:

Functional correctness (features work as specified)
Performance (response time)
Security (access controls)
Usability (end-user workflow compliance)
Maintainability (documentation and support readiness)

An APM answer should link quality to acceptance criteria and change control. If a stakeholder requests a feature but it violates security requirements, the change should be assessed through governance and quality standards.

3.7 Benefits management: moving from delivery to value realisation

APM increasingly emphasises benefits because projects are funded for outcomes.

A benefits management approach includes:

Benefits identification linked to organisational strategy
Benefits ownership (who owns the benefit after project close)
Benefits measurement plan (how benefit will be tracked)
Baseline definition (what is the “before” state?)
Benefits realisation schedule (benefits may not appear immediately)

Example: benefits in a reporting system upgrade

Possible benefits:

Reduced report compilation time
Improved data accuracy reducing rework
Faster decision-making cycle times

To make this exam-ready, you could specify measurement:

Baseline: average report compilation time is 3 days
Target: reduce to 1.5 days
Measurement: monthly analytics on completion time and accuracy checks

3.8 Integrating quality, benefits, and stakeholder acceptance

Stakeholders accept deliverables differently. APM must integrate:

Quality standards (what is technically acceptable)
Acceptance criteria (how delivery is formally signed off)
Benefits metrics (how the project is judged after delivery)

A frequent exam trap is to describe “quality” only as defect-free. In APM, quality is also:

Fit for purpose
Meets compliance and operational constraints
Supports intended benefits

Section 4: Cost Management, Procurement, Resource Planning, and Performance Measurement (APM with real exam structures)

4.1 Cost management: baselines, estimation, and control

In APM, cost management is more rigorous than budgeting.

Core concepts:

Cost baseline created from estimates
Control through tracking actuals vs planned
Forecasting to estimate final cost at completion
Managing cost risks and contingency reserves

Estimation methods (conceptual)

Depending on project maturity, estimation may use:

Expert judgement
Analogous estimation (similar past projects)
Parametric estimation (using parameters)
Bottom-up estimation (estimating work packages in WBS)

If an exam asks “which method is best,” you should answer with conditional logic:

Early stages: analogous/parametric may be more feasible
Detailed planning: bottom-up improves accuracy

4.2 Resource planning under constraints: capacity is not infinite

APM recognises that schedule is limited by people, systems, and vendor capacity.

Resource planning includes:

Identifying resource types (skills, roles)
Estimating availability and constraints
Planning labour curves and utilisation
Managing resource bottlenecks

A practical advanced concept: a schedule can be technically feasible but operationally impossible if resource availability is ignored.

4.3 Procurement management: contracts and performance accountability

Procurement becomes complex when:

Deliveries depend on vendors with uncertain capacity
Contracts include performance-based requirements
There is cross-border shipping, compliance, and acceptance testing

APM procurement excellence includes:

Make-or-buy decisions aligned with capability strategy
Procurement documentation quality (scope clarity reduces disputes)
Contract terms that reflect acceptance criteria and service levels
Vendor performance monitoring
Change management across procurement interfaces

Example: vendor contract performance clauses

A contract may specify:

Milestone delivery acceptance criteria
Penalties for late delivery
Payment terms linked to acceptance
Warranty and support obligations
Change order procedure

APM exam answers should include how procurement and change control interact:

if requirements change, procurement documents and vendor deliverables must be updated consistently.

4.4 Earned Value Management (EVM): performance measurement for APM

EVM is widely used in advanced project performance measurement questions.

Even if your syllabus does not require deep calculations, you should understand:

Planned Value (PV): budgeted cost for planned work
Earned Value (EV): budgeted cost for completed work
Actual Cost (AC): actual cost for work performed

From these, performance indicators can be interpreted:

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

You can also mention performance indices:

Cost Performance Index (CPI) = EV / AC
Schedule Performance Index (SPI) = EV / PV

Simple numeric illustration (typical exam style)

Suppose at a checkpoint:

PV = R 1,000,000
EV = R 900,000
AC = R 1,050,000

Then:

SV = EV − PV = R 900,000 − R 1,000,000 = −R 100,000 (behind schedule)
CV = EV − AC = R 900,000 − R 1,050,000 = −R 150,000 (over budget)

An APM answer should interpret meaning:

Negative SV indicates less work completed than planned.
Negative CV indicates higher actual cost than earned value.

In exam writing, interpretation matters as much as calculation.

4.5 Forecasting to completion: CPI/SPI-driven thinking

When you have EVM data, forecasting can estimate final cost and schedule outcomes.

A common advanced approach:

Use CPI and/or SPI trends to estimate at completion
Update forecasts during risk events and change events

Even when calculations are simplified in exams, the logic should be consistent:

If CPI < 1, costs are trending above plan; forecast should reflect that.

4.6 Cost baseline changes: when and how

Cost baselines may be adjusted through formal governance.

APM emphasises:

A baseline is not a “best guess” that can be altered casually.
Baseline changes require:
- approved scope changes,
- approved contract changes,
- formal change control,
- documented reasons and approvals.

This is where APM and governance integrate directly with cost control.

4.7 Performance reporting: decisions over narrative

Advanced reporting is decision-oriented, not story-based.

A typical APM reporting structure includes:

Executive summary (status and key risks)
Progress against milestones
Cost and schedule variance analysis
Top risks and issues
Decisions required from sponsor/steering committee
Updates to forecasts
Change control decisions

In South African university marking, clarity and structure often outperform overly long narrative.

Section 5: Integration, Professional Practice, and APM Exam Answer Engineering (UJ-style preparation)

5.1 Project integration management: coordinating everything

Integration management is the “glue” in APM: the project manager ensures that planning artefacts, control systems, stakeholder actions, and deliverables all reinforce each other rather than conflict.

Integration management responsibilities include:

Developing the project charter (high-level justification and authority)
Building project management plan (integrated baselines)
Directing and managing work
Monitoring and controlling work
Performing integrated change control
Closing the project or phase

An APM exam can test integration through scenarios: for example, a schedule slip occurs while a scope change request is submitted—what must be updated, who must approve, and how will risk and cost forecasts be adjusted?

5.2 Integrated change control: a “single source of truth”

Integrated change control ensures changes are managed consistently across:

Scope statement and deliverables
WBS
Schedule baseline
Cost baseline
Risk register
Quality management approach
Procurement documentation (where vendors are involved)
Stakeholder engagement plans

Example exam scenario (fully integrated reasoning)

Assume:

A project for upgrading reporting dashboards is delayed due to vendor data access delays.
Meanwhile, stakeholders request additional metrics requiring rework.

An integrated APM response would state:

Log the change request.
Assess impact:
- schedule: extended development and additional UAT time
- cost: additional labour and possibly vendor hours for data interface
- risk: increased likelihood of defects and testing delays
- quality: security review needed for new metrics
Assess whether schedule delay is related to risk realisation (risk becomes issue).
Decide through governance (sponsor/steering committee if required).
Update baselines and communicate.

This shows you understand “integration” as coordination of control systems.

5.3 Professional ethics and accountability in APM

APM in organisations is not only technical; it is professional.

Ethical considerations include:

Accurate reporting (no concealment of schedule/cost problems)
Transparency in risk exposure
Fair procurement practices and conflict-of-interest controls
Respect for stakeholder confidentiality
Safety and compliance integrity
Honest benefits tracking (avoid “gaming” benefits metrics)

In exam answers, ethics sometimes appear as “professional practice.” You can earn marks by explicitly connecting ethics to governance credibility.

5.4 Handling common APM exam question types

Type A: “Discuss” questions

You should:

Define the concept briefly
Provide a structured explanation (framework + components)
Add a scenario example
Conclude with why it matters for project success

Example for “Discuss integrated change control”:

Define it
Show steps
Mention who participates
Explain why it prevents baseline drift

Type B: “Compare and contrast” questions

Common pairs in APM include:

Risks vs issues
Quality assurance vs quality control
Stakeholder management vs communications
Preventive vs corrective actions
Avoid vs mitigate (responses)

A good comparison answer includes:

Similarities (shared goal)
Key differences (purpose, timing, tools)
Example applications

Type C: Scenario-based questions

Scenario-based APM questions usually ask:

What would you do?
What documents would you update?
What decisions must be escalated?
How would you measure performance?

A high-mark structure is:

Identify the problem(s)
Identify constraints and stakeholders
Apply frameworks (risk, change, quality, benefits, EVM)
Propose actions in logical order
Show reporting/decision escalation path
Tie actions to expected outcomes

5.5 Building an “APM answer template” that scores marks

Because assessment in South African universities often rewards structure, a consistent exam template helps.

A practical template:

Definition / relevance (2–4 lines)
Core framework (bullets and subsections)
Step-by-step process (numbered list)
Example (brief but concrete)
Benefits and risks (what improves? what could go wrong?)
Governance and documentation (who, what, how updated)
Conclusion (one strong concluding sentence)

Use this template differently for each question, but keep the structure consistent.

5.6 Exam writing mechanics: clarity and precision

High-scoring APM answers tend to be precise about:

Terms (risk vs issue; deliverable vs activity; acceptance vs verification)
Baselines (schedule baseline vs cost baseline; contingency reserves)
Decision rights (who approves change; who owns benefits)
Traceability (how deliverables link to outcomes)
Evidence (use small numeric examples where appropriate)

Also:

Avoid long uncontrolled paragraphs.
Use bullets for lists and steps.
Use consistent terms from start to finish.

5.7 Mini-case study: a fully integrated APM walkthrough (exam-ready)

Consider a hypothetical UJ-aligned case: a student services upgrade project.

Project goals:

Improve student support responsiveness
Reduce average ticket resolution time
Implement a new ticketing workflow integrating with existing systems

Key risks:

Legacy system integration delays (vendor and technical uncertainty)
Stakeholder change requests as new workflows are discovered
Quality risk: incomplete workflow validation causing misrouted tickets
Benefits risk: end users may not adopt the new workflow fully

Stakeholders:

Sponsor (Head of Student Services)
Steering committee (Finance and IT representatives)
Project manager and team (delivery)
End users (support agents)
Technical team (integration)
Governance board (quality and compliance assurance)

APM plan (integrated):

Scope is defined with deliverables: workflow configuration, integration interfaces, user training pack, acceptance testing evidence.
WBS breaks work into work packages: integration mapping, configuration, testing, training.
Risk register includes integration and adoption risks, with triggers such as missed interface test milestones.
Communication plan includes weekly technical updates, bi-weekly stakeholder status, and monthly steering committee decisions.
Quality management includes acceptance criteria for ticket routing correctness and performance targets.
Benefits management tracks ticket resolution time baseline and adoption metrics.
Earned Value analysis supports schedule and cost forecasts at checkpoints.
Integrated change control ensures new workflow requests are assessed for schedule/cost/quality impacts and that baselines are updated only with approvals.

In an exam, if you show how each part connects (scope ↔ change ↔ risk ↔ quality ↔ benefits ↔ performance), you demonstrate advanced understanding.

5.8 Common pitfalls and how to avoid them

To maximise exam marks, avoid:

Only listing theory without applying it to a scenario
Mixing risk and issue without recognising the distinction
Ignoring governance (who approves, escalation paths)
Updating scope without updating schedule/cost/risk/quality plans
Treating quality as only defect-free output rather than fitness for purpose and acceptance criteria
Discussing benefits without measurement baselines and ownership
Using EVM calculations without interpreting results

For many UJ and South African university exam markers, these are repeat errors that cost marks consistently.

Final revision checklist (fast recall for APM)

Use this condensed checklist before exams:

Scope: define deliverables, acceptance criteria, traceability to outcomes
Change control: log → impact analysis → approve/reject → update baselines → communicate
Risk: identify with structured methods; analyse; assign owners; set triggers; integrate with contingency
Stakeholders: map power/interest; tailor communications; manage conflicts via decision rights
Quality: plan/assure/control; link to acceptance criteria and compliance
Benefits: baseline → measurement plan → benefit ownership → realisation tracking
Cost & performance: baseline; EVM interpretation; forecast to completion; governance for baseline changes
Integration: ensure all systems update together; no isolated plan documents

If you are preparing specifically for a UJ APM-style module, it helps to pair these notes with past papers and marking guidelines, focusing on how your lecturers expect you to structure scenario answers: framework → process → example → governance and measurement.