EPMO6808 – Project Management and Optimisation (UFS) Exam Guide (UFS Postgraduate)

EPMO6808 is a postgraduate-level course built around the practical integration of project management disciplines with optimisation thinking—so you can plan, execute, control, and improve projects using sound governance, measurable outcomes, and data-informed decision-making. This exam guide is aligned to how South African universities (including the University of the Free State (UFS)) typically assess project-management competence: structured problem-solving, justification of choices, and the ability to apply frameworks to realistic organisational scenarios. Use this guide to consolidate core concepts, master exam-style approaches, and practise applying techniques to optimisation and performance improvement.

UFS EPMO6808 Exam Structure: What You Must Demonstrate

EPMO6808 tends to test more than “knowing the definitions.” In a project management and optimisation context, examiners usually look for evidence that you can (1) interpret a scenario, (2) select appropriate methods, (3) justify them using theory and professional standards, (4) compute or structure outputs where needed, and (5) evaluate trade-offs (time vs cost vs scope/quality vs risk). A strong answer is typically a hybrid: narrative reasoning supported by tools and sometimes calculations.

Typical competency areas assessed

While different exam papers vary year to year, the following competency clusters are consistently relevant to a course named Project Management and Optimisation:

1. Project integration and governance

   • Linking project objectives to organisational strategy.
   • Stakeholder management and authority/control structures.
   • Compliance, reporting, and decision cadence.

2. Planning with optimisation logic

   • Scope definition and work breakdown.
   • Scheduling approaches (baseline, critical path, resource constraints).
   • Estimating and budgeting with assumptions explicitly stated.

3. Execution and control

   • Monitoring performance and managing deviations.
   • Change control systems and risk response implementation.
   • Benefits tracking and outcome orientation.

4. Optimisation techniques and trade-off reasoning

   • Using quantitative methods where applicable (e.g., cost–time trade-offs, capacity planning, basic scheduling heuristics).
   • Interpreting KPIs and selecting improvement levers.
   • Evaluating scenarios and making decisions with constraints.

5. Communication and professional practice

   • Presenting outputs clearly (tables, diagrams, structured steps).
   • Writing logically: “problem → method → computation → interpretation → recommendation.”

Exam-style answer anatomy (highly reusable)

To consistently perform well, your answers should follow a pattern that mirrors professional problem solving. A good template:

1. Restate the scenario in your own words
   Identify key constraints and goals (e.g., deadline is fixed, budget cap exists, stakeholders have conflicting expectations).

2. State assumptions (if the question requires it)
   Example: “Assume fixed resources and deterministic task durations unless stated otherwise.”

3. Select the relevant tool/framework
   Example: “Use the WBS for scope control, then derive the schedule baseline for control.”

4. Apply the method

   • Show computation steps if numbers are involved.
   • If diagrams are required, describe them and label outputs.

5. Interpret results
   Convert numbers into decisions: “This indicates we are at risk of missing milestone 3 by 12 days.”

6. Provide recommendation and rationale
   Include at least one alternative option and explain why your choice is better given constraints.

7. Address risks and governance
   Mention how you would control the change, escalate issues, and report progress.

This structure reduces the risk of losing marks for correct ideas placed in the wrong part of an answer.

Keyword bank for UFS-style grading cues

Examiners often reward phrases that map to marking criteria. Incorporate relevant language naturally:

• “Project charter” and “business case” (linking to rationale)
• “SMART objectives” and “success metrics/KPIs”
• “WBS/Work Breakdown Structure”
• “baseline” (scope/schedule/cost baselines)
• “change control” and “approval authority”
• “risk register,” “risk response strategy”
• “monitoring and controlling”
• “earned value management (EVM)” (where applicable)
• “benefits realisation”
• “lessons learned” and continual improvement

You do not need to use every keyword—use the ones that fit the question.

Project Planning and Optimisation Foundations (Linking Strategy to Execution)

This section focuses on how EPMO6808 integrates foundational planning with optimisation thinking. Optimisation in project management is not just “finding the shortest schedule.” It is about choosing the best course of action under constraints such as budgets, resources, risk tolerance, procurement lead times, regulatory requirements, and stakeholder expectations.

From organisational strategy to project objectives

A frequent exam scenario is that a project is announced without clarity about why it exists. In good answers, you demonstrate that the project lifecycle begins with strategic alignment:

1. Business need / opportunity

   • What problem does the organisation face?
   • What failure mode exists if the project does not happen?

2. Business case

   • Costs, expected benefits, and timeframe.
   • Often includes qualitative benefits (e.g., compliance, reputational risk reduction).

3. Project charter

   • High-level scope, objectives, stakeholders, governance structures.
   • Identifies authority for key decisions (e.g., who approves scope changes?).

4. SMART objectives and success metrics

   • Examples:
     • Schedule: “Complete within 18 months.”
     • Cost: “Within a budget of ZAR 12.6 million (excluding contingency).”
     • Quality: “Achieve 95% defect-free acceptance at handover.”
     • Benefits: “Reduce processing time by 30% by month 12 after go-live.”

Optimisation begins when objectives become measurable and constraints are explicit. Without measurable outcomes, trade-off decisions are vague and examiners penalise lack of clarity.

Scope definition and WBS: making optimisation possible

Optimisation needs granularity. If you cannot break down work, you cannot estimate accurately, schedule intelligently, or control scope.

Using WBS in exam questions

When a question asks about planning, your answer should show:

• Decomposition logic: deliverables → work packages.
• Work package clarity: each work package should have an owner, measurable outputs, and acceptance criteria.
• Link to cost and schedule: work packages become planning units.

A practical example you can adapt in exams:

• Project: “Implement a new student admissions workflow system.”
• Deliverables:
  1. Business process redesign
  2. System configuration
  3. Data migration
  4. User training
  5. Go-live and support

Then for a deliverable like “Data migration,” a WBS can include:

• Data profiling
• Data cleansing
• Migration testing
• Migration execution
• Migration validation and sign-off

This level of breakdown supports both:

• Scope control: what is in/out of the project.
• Optimisation: identifying which work packages drive schedule risk or cost overruns.

Scheduling baseline: critical path and constraints

EPMO6808 exam questions may include scheduling tasks or ask you to explain how schedule control works. Even if the question is conceptual, you should demonstrate scheduling logic.

Critical Path Method (CPM) as an optimisation foundation

CPM helps determine tasks that cannot slip without affecting the project completion date. For optimisation, you use CPM to focus management effort and cost/time levers where they matter most.

In an exam answer, you should mention:

• Determining task durations
• Identifying precedence relationships
• Calculating earliest start/finish and latest start/finish
• Identifying critical path (zero slack tasks)
• Updating baseline when controlled changes occur

Resource constraints: why “fastest” may not be “best”

Real projects face limited resources. A schedule that assumes unlimited staffing can be unrealistic. Optimisation therefore considers constraints like:

• Labour availability (e.g., only two analysts)
• Contracting lead times
• Machine availability
• Regulatory review windows

A strong answer will explicitly state:

• If the schedule is resource-constrained, you may need to:
  • Re-sequence tasks
  • Use overtime selectively
  • Outsource specific work packages
  • Adjust scope priorities
  • Use crashing/fast-tracking carefully

Cost estimation and budgeting with optimisation trade-offs

Cost estimation is often assessed indirectly: you may be asked to choose methods, justify contingency, or explain how budgets link to control.

Key planning elements

1. Cost baseline

   • Time-phased budget (often S-curve).
   • By work packages or cost accounts.

2. Contingency and management reserve

   • Contingency for identified risks.
   • Management reserve for unknown-unknowns or higher-level uncertainties.

3. Cost control logic

   • Baseline provides the reference point.
   • Deviations trigger corrective action or change control.

Optimisation logic: time–cost trade-off and the “marginal benefit” mindset

In a typical exam scenario, you might be asked what to do if the project is behind schedule. The optimisation answer is not just “work faster.” It is:

• Identify whether the delay is on the critical path.
• Evaluate crashing cost increases (e.g., overtime, additional resources).
• Compare the incremental cost to incremental benefit (e.g., reduced business disruption, avoided penalties, earlier benefits realisation).

Even without heavy numerical analysis, you can demonstrate this logic.

Risk and opportunity integration in planning

Optimisation is incomplete without risk thinking. Risks influence schedule, cost, and scope. Opportunities can justify investment in acceleration or quality improvements.

Risk register essentials

A well-structured risk register includes:

• Risk description
• Causes and effects
• Probability and impact assessment
• Risk owner
• Response strategy:
  • Avoid/mitigate/transfer/accept
• Trigger conditions and contingency actions

Probability–impact and prioritisation (exam-friendly)

A common approach is a risk matrix:

• Likelihood: Low/Medium/High
• Impact: Low/Medium/High
• Priority: identify high-likelihood/high-impact risks for early response planning

A good optimisation-focused answer:

• Links “top risks” to scheduling buffers or cost contingency.
• Demonstrates that risk responses are included in the plan (not only listed).

Benefits realisation as the end objective of optimisation

Many projects fail optimisation because they focus only on outputs (documents, system delivery, training) rather than outcomes (improved performance, user adoption, reduced processing time). EPMO6808 emphasises outcome orientation.

Exam questions may ask:

• How you would measure benefits at different stages.
• How benefits ownership is managed.

A robust benefits realisation approach includes:

• Benefit statements (what changes, for whom, by when)
• Baseline performance measures
• Tracking KPIs post go-live
• Governance for benefits ownership and corrective action if benefits lag

Governance, Change Control, and Performance Optimisation (Monitoring, EVM, and Decision-Making)

This section builds the “control” side of project management and shows how optimisation emerges from measurement. It also covers change control, reporting, and exam-ready decision-making under uncertainty.

Project governance and reporting cadence

Governance defines how decisions are made and how performance information flows.

Typical governance components

1. Steering committee / project board
   • Approves major decisions: scope changes, budget adjustments, milestone approvals.
2. Project manager authority
   • Executes day-to-day decisions within defined limits.
3. Functional managers
   • Provide resources and manage staffing commitments.
4. Risk and compliance roles
   • Ensure that risk responses and compliance checks happen at the right time.

Reporting outputs (what examiners expect)

Good answers often mention:

• Status reports (progress against plan)
• Issue logs (problems requiring decision/action)
• Risk register updates
• Change requests register
• Milestone achievement dashboards
• Forecasts (Estimate at Completion)

Even when the question is “conceptual,” naming reporting artefacts signals you understand real project administration.

Change control: the optimisation lever most students underuse

Optimisation is strongly affected by change. A project that controls changes efficiently can remain on track; a project without control can “optimise” itself into failure.

A practical change control process

A strong exam answer should include a structured flow:

1. Change identification
   • Trigger: stakeholder request, regulatory updates, technical discovery.
2. Change request submission
   • Describe proposed change, rationale, and expected impact.
3. Impact assessment
   • Evaluate schedule, cost, scope, quality, risk.
4. Options and trade-off analysis
   • Consider alternative ways to achieve the underlying need.
5. Approval decision
   • Identify who has authority (e.g., steering committee).
6. Implementation planning
   • Update baselines (if approved).
7. Communication and documentation
   • Inform impacted teams and update plans.

Optimisation principle in change control: “alternatives before acceptance”

A top answer often demonstrates that you:

• Challenge the request: what problem is the change solving?
• Seek minimal-change options.
• Evaluate whether the change affects critical path or high-cost work packages.

Performance monitoring: KPIs that matter for optimisation

Optimisation depends on choosing correct metrics. Not all KPIs are equally useful.

Performance indicators commonly used

1. Schedule performance

   • Milestone completion rate
   • Planned vs actual progress
   • Forecasted completion date

2. Cost performance

   • Spending vs budget (often time-phased)
   • Variance trends

3. Quality/acceptance

   • Defect rates, rework hours, acceptance pass/fail

4. Risk trend

   • Reduction in exposure
   • Early warning triggers achieved/triggered

5. Benefits indicators

   • Early adoption metrics
   • Process cycle time improvements post go-live

A good answer mentions how you would interpret conflicting indicators. Example:

• Schedule ahead but quality low → increased rework risk → forecast cost may rise later.

Earned Value Management (EVM): how to compute and interpret

EVM is a classic exam topic because it connects scope, schedule, and cost into measurable performance and forecasting.

If a question includes numerical values, your answer should show the calculations and interpretation.

EVM core metrics

Common EVM terms:

• PV (Planned Value): budgeted cost of work planned up to a point.
• EV (Earned Value): budgeted cost of work actually performed.
• AC (Actual Cost): actual costs incurred up to that point.

From these:

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

Exam interpretation rules of thumb

• EV > PV (positive SV) → ahead of schedule.
• EV < PV (negative SV) → behind schedule.
• EV > AC (positive CV) → under budget.
• EV < AC (negative CV) → over budget.
• SPI > 1 → efficient on schedule.
• CPI > 1 → efficient on cost.

Forecasting (typical)

If the exam expects forecast:

• Estimate at Completion (EAC) may use CPI:
  • Example formula: EAC = BAC / CPI (simple assumption).
• Estimate to Complete (ETC):
  • ETC = EAC − AC.

You should always state assumptions in your answer. EAC methods vary; examiners look for you not to treat EAC as magic.

Optimisation via performance variances: decision-making under constraints

Measurement alone does not optimise anything. You optimise by deciding what corrective action to take and where to apply effort.

Corrective action selection logic

When you detect negative SV or CV, you should ask:

1. Is the issue structural or temporary?

   • Temporary: recovery possible with minor re-planning.
   • Structural: requires baseline change or scope trade-off.

2. Which area drives the variance?

   • Work packages on critical path?
   • Specific suppliers causing delays?
   • Quality issues causing rework?

3. Are there controllable levers?

   • Add resources (if feasible)
   • Re-sequence work
   • Change procurement strategy
   • Improve defect prevention
   • Adjust acceptance criteria carefully (without reducing compliance)

4. What is the risk impact?

   • “Fixing schedule” may increase risk and cost.

Example decision framework for exams

Suppose a project is behind schedule (negative SV) and over budget (negative CV). A high-quality exam recommendation might be:

• Focus first on work packages feeding the critical path.
• Conduct a root cause analysis:
  • Are delays due to waiting on dependencies?
  • Are there procurement lead time issues?
  • Is quality causing rework and cost inflation?
• Apply targeted interventions:
  1. For procurement delays: adjust supplier plan or expedite shipping.
  2. For rework: implement stricter quality gates and testing.
  3. For staffing constraints: reallocate labour to critical deliverables.

You should explicitly state which corrective action changes the most critical driver.

Quality optimisation and risk-based acceptance

Optimisation in project delivery includes quality management. Quality failures can appear as schedule accelerations (because teams “push to finish”) but later manifest as rework cost and delays.

Risk-based quality gates

A robust exam answer may propose:

• Early quality planning tied to risk:
  • High-risk deliverables get stronger testing and review cycles.
• Acceptance criteria clarified up front:
  • Reduces late disputes and “scope creep through interpretation.”

Lessons learned integration

Control is not only about preventing failure; it’s about improving future decisions:

• Track which corrective actions worked.
• Capture lessons learned and update planning assumptions.

Scheduling, Resource Optimisation, and Stakeholder Management in Complex Projects

This section focuses on advanced but exam-friendly elements: scheduling trade-offs, resource allocation, dependency management, and stakeholder dynamics. It’s where optimisation becomes “human system + technical system” rather than only mathematical planning.

Resource optimisation: balancing capacity, skills, and cost

Resource constraints often define what is optimisable. A schedule is only as good as the capacity behind it.

Resource planning basics

In answers, show you understand resource types:

• Labour (specialists vs generalists)
• Equipment/machines
• Systems environments (e.g., test/staging)
• Supplier resources (external contractors)

Then relate these to planning outputs:

• Resource breakdown by work package
• Availability calendars
• Loading/unloading logic (who is available when)

Typical optimisation approaches

1. Resource smoothing

   • Reduces peaks and troughs in staffing.
   • May extend schedule but improves sustainability.

2. Resource leveling

   • Adjusts task start dates to respect capacity limits.
   • Often used in resource-constrained scheduling.

3. Crashing

   • Shorten the schedule by adding resources or using overtime.
   • Comes with added cost and sometimes risk.

4. Fast-tracking

   • Overlap phases where possible.
   • Requires risk management because rework may occur.

In an exam scenario, you need to justify which approach fits the constraint profile:

• If the project deadline is fixed and cost budget allows, crashing may be justified on critical path tasks.
• If cost is fixed but schedule can flex, resource smoothing/leveling may be better.
• If technical dependencies are rigid, fast-tracking might increase rework risk.

Stakeholder management as optimisation

Stakeholders are not “soft factors.” In optimisation, stakeholders influence scope decisions, approval speed, acceptance definitions, and risk tolerance.

Stakeholder analysis: practical exam method

1. Identify stakeholders:
   • Sponsors, project team, beneficiaries, regulators, suppliers, end-users.
2. Assess:
   • Influence (power)
   • Interest (impact on project success)
3. Determine engagement strategy:
   • Manage closely (high influence/high interest)
   • Keep satisfied
   • Keep informed
   • Monitor (low influence/low interest)

Optimisation through engagement cadence

A common exam scenario: approval delays cause project slippage. Optimisation includes:

• Identify approval lead times.
• Schedule reviews with realistic turnaround.
• Use pre-approvals or staged sign-offs where appropriate.
• Provide decision-ready materials to reduce rework.

Dependencies and critical chain thinking (exam-ready)

Complex projects have dependencies:

• External supplier delivery dependencies
• Regulatory review windows
• Internal decision approvals
• Training prerequisite completion

Even if the exam does not explicitly mention “Critical Chain,” answers can use the same logic:

• Protect the constraint (resource or dependency bottleneck).
• Manage buffers:
  • Project buffer for overall risk.
  • Feeding buffers for incoming dependencies.

Where students lose marks

Many students treat schedule as a simple chain and ignore:

• Review cycles
• Contracting lead times
• Training and change management as prerequisites
  These omissions create unrealistic plans.

A good answer highlights:

• Dependencies are scheduled with explicit dates and acceptance criteria.
• Buffering is justified using risk analysis (not arbitrary padding).

Procurement and vendor optimisation

Procurement can be a major source of schedule and cost variance.

Procurement planning elements

• Procurement strategy:
  • Make vs buy decisions (if relevant).
  • Contract type selection (incentives, fixed price vs time and materials).
• Supplier selection criteria:
  • Capability, track record, delivery reliability, compliance.
• Contract performance metrics:
  • SLA terms, delivery milestones, penalties, acceptance criteria.

Exam optimisation: avoiding “cheapest wins” thinking

A strong exam response argues:

• Optimisation includes total cost of ownership and delivery risk.
• A cheaper supplier with long lead time may harm schedule and cause higher indirect costs.
• The best option is the one with best risk-adjusted outcome.

Communications management and conflict resolution

Conflict can derail progress and create hidden costs. Optimisation includes preventing preventable conflicts.

Communication planning

A communication plan may include:

• Audience: steering committee, functional managers, project team, external stakeholders.
• Frequency: weekly status, monthly performance review, milestone-based governance.
• Medium: dashboards, written reports, meetings, workshops.
• Content: schedule status, risk changes, decisions needed.

Conflict handling in project settings

A typical exam scenario includes disagreements about scope or priorities. An excellent answer:

• Clarifies decision authority.
• Uses evidence: performance data, requirements, acceptance criteria.
• Proposes compromise options (alternatives).
• Applies change control if scope changes are required.

Case-style scenario you can reuse in answers (with consistent logic)

Scenario template (adaptable):
A university department launches an EPMO6808-aligned transformation project: implement an optimised workflow for student administration. Midway through implementation, a key stakeholder delays acceptance testing due to policy updates. Meanwhile, the project budget is trending above plan because rework is required.

Optimisation-focused answer elements:

1. Diagnose delay root causes (policy updates + testing readiness).
2. Update risk register for policy-driven acceptance delays.
3. Implement change control if acceptance criteria change.
4. Adjust schedule by resequencing test preparation tasks.
5. Provide “decision-ready” policy interpretation package to accelerate approvals.
6. Track quality and rework metrics to justify additional resources only if on the critical path.

This scenario demonstrates that optimisation is multi-dimensional: it includes schedule, risk, governance, and quality—exactly the themes typically assessed.

Exam Practice Toolkit for EPMO6808: Calculations, Framework Application, and Marking-Rubric Thinking

This section acts as a practical exam toolkit: how to approach calculations, structure long-form answers, and avoid common marking pitfalls. It includes ready-to-use frameworks, sample mini-answers, and consistency checks for quantitative reasoning.

How to handle calculations (when numbers appear)

Many project management exams include quantitative problems, such as:

• EVM with PV/EV/AC
• Cost forecasting using CPI
• Schedule variance interpretation
• Resource loading and basic schedule logic

A calculation workflow that prevents errors

1. Write down given values clearly
   • Example: PV = 500, EV = 450, AC = 520 (ZAR thousands, unless stated).
2. Confirm units
   • Money in ZAR, time in days, percentages as fractions, etc.
3. Compute variances and indices
   • SV = EV − PV; CV = EV − AC.
   • SPI = EV/PV; CPI = EV/AC.
4. Interpret results in words
   • Don’t stop at arithmetic—connect to management action.
5. State assumption-based forecast
   • If using BAC/CPI for EAC, say so and justify briefly.

Consistency check examples

If you calculate:

• CPI = EV/AC
  Then you must ensure:
• EV and AC correspond to the same time boundary (same “up to date” point).
  Examiners often detect mismatched time boundaries.

Example EVM mini-answer structure (what earns marks)

Suppose at a reporting point:

• PV = 800
• EV = 720
• AC = 760

Then:

• SV = EV − PV = 720 − 800 = −80 → behind schedule.
• CV = EV − AC = 720 − 760 = −40 → over budget.
• SPI = EV/PV = 720/800 = 0.90
• CPI = EV/AC = 720/760 ≈ 0.947

Interpretation:

• Schedule efficiency is 90% of plan.
• Cost efficiency is about 94.7% of plan.
  Decision:
• Investigate critical path tasks and identify whether delays causing overspend are structural.
• Apply corrective actions targeted to root cause: resequencing, supplier escalation, quality defect prevention.

Notice the pattern: calculation → interpretation → corrective action.

Framework selection: “matching tools to questions”

A frequent exam failure is selecting the wrong tool because the answer is generic. Use the matching principle:

• If the question is about scope control → WBS + scope baseline + acceptance criteria.
• If about schedule performance → critical path + baseline + variance interpretation.
• If about budget/cost control → cost baseline + EVM or variance analysis.
• If about stakeholder approvals → stakeholder management + engagement plan + governance and decision readiness.
• If about resource constraints → capacity planning + resource leveling/smoothing + crashing/fast-tracking justification.
• If about benefits → benefits realisation plan + KPIs + ownership + post go-live tracking.

Optimisation arguments: how to score high in “should we accelerate?” questions

Many exam questions ask you to recommend actions. Strong optimisation answers include:

• Identify the constraint (critical path task, procurement lead time, approval cycle, quality gate).
• Evaluate options:
  • crash / fast-track / rescope / accept risk / delay non-critical work
• Compare options using criteria:
  • impact on completion date
  • incremental cost
  • risk increase
  • effect on quality and compliance
• Provide a decision:
  • “Select option A because it reduces critical path risk with acceptable cost and risk exposure,” plus a fallback plan.

Avoid vague language:

• “We should optimise the schedule.”
  Instead say:
• “We will prioritise critical-path tasks for controlled crashing while maintaining quality gates to prevent rework.”

Long-form writing technique: structured paragraphs with “claim → evidence → implication”

For theory-heavy questions, use this structure:

1. Claim: e.g., “Change control protects the scope baseline and stabilises cost and schedule forecasting.”
2. Evidence: describe the process steps and impact assessment logic.
3. Implication: tie to optimisation outcomes like reduced variance and improved predictability.

This creates clarity and helps markers follow your reasoning.

Common pitfalls (and how to avoid them)

1. Confusing outputs with outcomes

   • Fix: always connect delivery to benefits and KPIs.

2. Treating risk as a list

   • Fix: show triggers, owners, response implementation, and how risk responses affect schedule/cost.

3. Ignoring governance

   • Fix: mention approval authority, escalation, steering committee decisions.

4. No trade-off discussion

   • Fix: present at least two options and explain why one is better.

5. Skipping baseline definitions

   • Fix: define baseline and clarify how variance triggers actions.

6. Arithmetic without interpretation

   • Fix: always convert results into managerial meaning and next steps.

Mini “exam pack” of reusable components (write these quickly in exams)

You can prepare short reusable blocks in your own words.

Component A: Project objectives & KPIs

• Objectives must be SMART.
• KPIs should cover scope, schedule, cost, quality, and benefits.
• Baseline values required for measurement.

Component B: Change control summary

• Request → impact assessment → approval decision → baseline update → implement → communicate.

Component C: EVM interpretation and corrective action

• Compute SV/CV/SPI/CPI.
• Diagnose root causes.
• Choose targeted corrective actions.
• Forecast EAC and adjust plan as needed.

Component D: Risk response planning

• Avoid/mitigate/transfer/accept.
• Define triggers and contingency actions.
• Assign owners and integrate responses into the schedule/cost baselines.

“Clustered” exam question mapping (so you can quickly plan your answer)

Use this mapping during revision:

• Governance questions → project charter, authority, reporting cadence, steering decisions.
• Planning questions → business case, WBS, schedule baseline, cost baseline, risk planning.
• Control questions → monitoring dashboards, variance analysis, change control, corrective actions.
• Optimisation questions → trade-off analysis (time/cost/risk/quality), resource constraints, benefits realisation.
• Scenario-based questions → diagnose root causes, choose interventions, justify with constraints.

Final Consolidation: One Integrated Optimisation Narrative (How to Answer Like a Professional)

To score at a high level in EPMO6808, you must demonstrate an integrated narrative rather than disconnected concepts. A professional project manager’s answer often reads like a connected storyline: strategy → planning → execution control → optimisation decisions → benefits and learning.

A coherent integrated flow for exam writing

When faced with any EPMO6808-style scenario, use this storyline:

1. Start with rationale

   • Business case and strategic alignment.
   • Define objectives and success metrics.

2. Plan with optimisation prerequisites

   • Build WBS for scope granularity.
   • Develop schedule baseline using dependencies and critical path logic.
   • Create time-phased cost baseline with contingency and reserves.
   • Conduct risk planning and integrate risk responses.

3. Operate governance and change control

   • Define decision authority and escalation routes.
   • Establish approval steps for scope/schedule/cost changes.
   • Use impact assessments and document updates.

4. Measure performance and trigger corrective action

   • Use KPIs and (if required) EVM metrics.
   • Interpret variances and identify drivers.
   • Choose targeted interventions based on where the constraint lies.

5. Optimise under constraints

   • Apply crashing, fast-tracking, resource leveling/smoothing as appropriate.
   • Manage dependency and stakeholder approval lead times.
   • Protect quality gates to avoid rework-driven schedule inflation.

6. Track benefits and learn

   • Define benefits KPIs with baselines.
   • Monitor benefits post go-live.
   • Document lessons learned and update future planning assumptions.

What examiners expect in the “why” behind recommendations

Recommendations must be more than “do X.” They must include:

• Why X is the best response to the scenario constraints.
• What impact X has on schedule, cost, scope, quality, risk.
• What governance will ensure X is controlled and approved correctly.
• What follow-up measurement confirms improvement (KPIs, variance trends, benefits metrics).

When you provide this, your answer demonstrates mastery of project management and optimisation as one discipline.

Smart revision strategy for the UFS EPMO6808 exam

Revision should combine:

• Framework recall (what each concept is for)
• Calculation practice (EVM and forecasting if used)
• Scenario drills (write short answers using the integrated narrative)
• Marking-rubric simulation (ensure your answer includes diagnosis, method, computation/logic, interpretation, and recommendation)

If you practise consistently with scenario-based writing, you will perform well because you are training the exam brain: quickly identify constraints, apply tools accurately, and justify decisions clearly.

End of EPMO6808 Exam Guide