MANCOSA PM5 – Project Management 5 Exam Pack (PM5): Study Notes, Past-Style Questions & Answers

Project Management 5 (PM5) is a core MANCOSA module that typically assesses your ability to plan, control and justify project decisions across the full project lifecycle—from initiation and governance through scheduling, cost control, procurement, risk, stakeholder management and reporting. This exam pack is written as comprehensive revision notes with worked examples, practical templates, and “exam-style” question-and-answer guidance aligned to what learners commonly face in South African higher education assessments (including MANCOSA-style case reasoning and structured answers).

These notes also connect the kinds of project-management thinking found across South African university modules such as Unisa’s project and operations management offerings (e.g., at undergraduate level in the broader Management Sciences domain) and CUT/other universities’ business project modules that emphasise planning, budgeting, risk, and evaluation. Expect frequent focus on: scope and work breakdown, scheduling logic, critical path thinking, cost control, earned value concepts, stakeholder and risk registers, procurement planning, and closing/benefits realisation.

Section 1: PM5 Foundations—Project Governance, Lifecycle, and Exam-Ready Planning

Project Management 5 usually assumes you already know the basics of project management, so the exam tends to test whether you can apply principles to real scenarios. A strong PM5 answer is not just theory: it is a structured plan that links objectives → scope → work → schedule → budget → risks → controls → reporting.

PM5 Project Lifecycle and Governance (What markers look for)

Most PM5 questions are built around a case study with a timeline, stakeholders, constraints and incomplete information. Your task is to propose a realistic approach.

A typical project lifecycle you should be able to describe (and apply) is:

1. Initiation / Concept
2. Planning / Design
3. Execution / Implementation
4. Monitoring & Controlling
5. Closing / Benefits Realisation

For PM5, “governance” matters: it’s how decisions are made and how performance is reviewed.

Common governance elements in exam scenarios:

• Project charter or authorization document: confirms purpose, high-level scope, authority and initial budget envelope.
• Project management plan: integrates subsidiary plans (scope, schedule, cost, risk, procurement, communications, quality).
• Stage-gate approvals: each stage is reviewed by a steering committee or sponsor before moving on.
• Change control: changes to scope, schedule or budget follow a formal process.
• Reporting cadence: e.g., weekly progress meetings, monthly steering committee packs.

Exam-style phrasing to use

Markers reward disciplined language. For example:

• “A stage-gate review will be used to confirm readiness before moving from design to implementation.”
• “A change request will be assessed for impact on scope, time and cost using agreed thresholds.”
• “Risk responses will be tracked on a risk register with owners and due dates.”

Defining the Project: Objectives, Success Criteria, and Scope Boundaries

A frequent PM5 trap is confusing objectives with deliverables. An objective is a desired outcome; a deliverable is tangible output.

A robust way to structure answers:

1. Project objective (why it exists)
2. Success criteria (how you know it worked)
3. Deliverables (what you will produce)
4. Constraints (what you must live with)
5. Assumptions (what you believe to be true)

Example scenario (used throughout these notes conceptually)

Imagine a mid-sized logistics company, Thandi Freight (Pty) Ltd, launching a new warehouse management system (WMS) to improve order accuracy and reduce dispatch delays. The sponsor wants a working system within 6 months and an initial budget ceiling of R3,200,000. The project team has limited vendor options and must comply with data security requirements.

Your exam answer should include:

• Objectives: improve accuracy, reduce delays, standardise processes.
• Success criteria: e.g., order accuracy > 98%, dispatch cycle time reduced by 20%, system user adoption rate above 90% (you can use relative numbers if provided).
• Deliverables: requirements document, configured WMS, interfaces, user training materials, go-live documentation.
• Constraints: deadline and budget envelope.
• Assumptions: availability of SME process owners for workshops, vendor availability for implementation slots.

Scope statements that score marks

Your scope statement should clarify what is included and excluded.

Included (example):

• Process mapping workshops
• Configuration and integration of WMS with existing systems
• Testing (unit, integration, user acceptance)
• Training and documentation

Excluded (example):

• Building a brand-new ERP (outside project boundary)
• Renovating the warehouse building (different project)
• Hiring additional permanent staff (handled by operations)

In PM5, you may be asked to identify scope risks or why unclear scope leads to cost overruns. Always tie your answer back to scope clarity and change control.

Work Breakdown Structure (WBS): Turning Scope into Deliverable-Based Planning

The WBS is one of the most testable tools in project management exams. In PM5, examiners may ask you to:

• build a WBS from a narrative scope,
• convert a WBS into activities,
• identify dependencies,
• estimate durations and costs,
• allocate responsibility (often with RACI).

A deliverable-based WBS is preferred (not task-based only).

Step-by-step: creating a WBS (exam-ready method)

1. Identify major deliverables.
2. Break each deliverable into manageable components.
3. Ensure each WBS element can be estimated and assigned.
4. Use a numbering scheme (e.g., 1.0, 1.1, 1.2…).

Example WBS for Thandi Freight’s WMS project (illustrative):

• 1.0 Project Initiation

  • 1.1 Project charter & approvals
  • 1.2 Stakeholder identification & engagement plan

• 2.0 Requirements & Design

  • 2.1 Business process mapping
  • 2.2 Functional requirements
  • 2.3 System architecture & interface design
  • 2.4 Data migration approach

• 3.0 Configuration & Build

  • 3.1 WMS configuration
  • 3.2 Interface build (orders, inventory)
  • 3.3 Data migration scripts

• 4.0 Testing

  • 4.1 Unit testing
  • 4.2 Integration testing
  • 4.3 User acceptance testing (UAT)

• 5.0 Training & Deployment

  • 5.1 Training sessions & materials
  • 5.2 Cutover plan
  • 5.3 Go-live support

• 6.0 Closure & Benefits Review

  • 6.1 Final documentation & handover
  • 6.2 Post-implementation review (benefits realisation)

Common WBS errors (and how to avoid them)

• Too high-level: WBS elements too vague to estimate.
• Too detailed too early: creates overhead; balance needed.
• Mixing deliverables and activities: keep hierarchy consistent.
• Missing management deliverables: e.g., project reporting, change control, risk management should appear as appropriate management work packages.

Planning the Schedule: Activities, Dependencies, and Milestones

PM5 schedule questions often require logic, not just “list tasks.”

You should be able to:

• derive activities from the WBS,
• sequence activities,
• identify dependencies (FS, SS, FF, SF),
• set milestones (zero-duration or event points).

Dependency types

Use the correct definitions:

• Finish-to-Start (FS): predecessor must finish before successor starts.
• Start-to-Start (SS): successor can start when predecessor starts (with conditions).
• Finish-to-Finish (FF): successor finishes when predecessor finishes.
• Start-to-Finish (SF): rare, successor finish depends on predecessor start (generally avoid unless explicitly given).

Milestones example for the WMS project

• M1: Requirements approved
• M2: Interface design sign-off
• M3: UAT passed
• M4: Go-live completed
• M5: Handover and closure accepted

In an exam, if milestones are requested, choose points that reflect decision readiness rather than “work completed” only.

Cost Planning Overview: From Budget to Cost Control

PM5 cost topics commonly connect:

• estimation methods (top-down vs bottom-up),
• cost baseline creation,
• contingency and management reserve,
• cost control mechanisms.

You should also be comfortable with budget categories:

• labour,
• materials/software licences,
• vendor costs,
• travel/training,
• contingency.

Budget baseline vs forecast

• Budget baseline: the approved plan.
• Cost forecast: estimated final cost based on performance.
• Contingency: risk-based allowance used for identified risks.
• Management reserve: budget held for unknown unknowns, typically approved by higher authority.

Risk Planning: From Risk Identification to Response and Controls

PM5 risk questions frequently test whether you can:

• identify risk causes and effects,
• classify risks (technical, schedule, cost, stakeholder, external),
• create responses (avoid, mitigate, transfer, accept),
• assign risk owners,
• track risks with review cadence.

Risk register essentials

A good risk register has:

• Risk ID (R1, R2…)
• Risk statement (cause + event + effect)
• Probability (P)
• Impact (I)
• Score (P×I) if using a numeric system
• Response strategy
• Owner
• Trigger indicators (what you watch)
• Contingency action (what you do if trigger occurs)
• Status and review date

Example risk for Thandi Freight (WMS)

• R3: Data migration delays
  • Cause: legacy data inconsistencies
  • Event: migration runs exceed planned effort
  • Effect: schedule slippage into UAT window
  • Response: mitigation via data cleansing plan, parallel test scripts, allocate additional analyst time; contingency: extend migration window with vendor support.

Communications and Stakeholders: The Difference Between Activity and Governance Communications

Stakeholder management is often the difference between average and high-scoring answers.

In PM5, stakeholders include:

• sponsor / steering committee,
• project team (internal),
• vendor / implementation partner,
• user departments,
• IT security/compliance,
• external regulators (if relevant).

Communication planning essentials

A communication plan specifies:

• audience,
• information needed,
• method (email, dashboard, meeting),
• frequency (weekly, monthly),
• owner (who sends),
• format (status report, steering pack).

Exam tip: If asked about stakeholder engagement, don’t only “identify stakeholders.” Provide actions:

• regular demos to users,
• training and change impact workshops,
• escalation paths for complaints,
• documented decisions and sign-offs.

Section 2: Scheduling, Critical Path, and Earned Value—Deep Application for PM5 Exam Questions

This section focuses on the numeric and logic-heavy parts of PM5. Many learners can describe planning; fewer can compute schedule implications and interpret performance data. Your goal in this exam pack is to be able to build a credible plan and justify decisions using methodical logic.

Building a Schedule: Network Logic and Estimating Durations

PM5 schedule questions typically include activity durations and predecessor relationships. You may be asked to:

• draw a precedence diagram conceptually,
• identify critical activities,
• compute earliest start/finish dates (or relative project duration),
• locate float (slack) and interpret it.

Activity duration estimation basics

When durations aren’t explicitly given, you may need to estimate using:

• expert judgement,
• historical data,
• analogous estimation,
• parametric estimation.

In many South African exam settings, the emphasis is less on the mathematics of estimation and more on showing that your estimate is:

• documented,
• supported by assumptions,
• realistic given constraints and dependencies.

Critical Path Method (CPM): What It Is and How It Is Used

Critical path is the longest sequence of dependent activities that determines the earliest project completion date. Activities on the critical path have zero or near-zero float.

Core computations (learn and reproduce)

For each activity:

• ES (Earliest Start)
• EF (Earliest Finish) = ES + Duration
• LS (Latest Start)
• LF (Latest Finish) = LS + Duration
• Float / Slack = LS − ES (or LF − EF)

The project duration is the maximum EF among terminal nodes.

Worked example: simple precedence network

Consider five activities for a WMS build (illustrative):

Activity	Duration (weeks)	Predecessor(s)
A: Requirements approved	2	—
B: Configuration	3	A
C: Interface build	4	A
D: Integration testing	2	B, C
E: UAT planning & test execution	3	D

Step 1: Forward pass

• A: ES 0 → EF 2
• B: ES 2 → EF 5
• C: ES 2 → EF 6
• D: ES = max(EF(B), EF(C)) = max(5,6)=6 → EF = 8
• E: ES 8 → EF 11

Project duration = 11 weeks.

Step 2: Backward pass
Terminal activity E finishes at 11, so:

• E: LF 11 → LS = 8
• D must finish so that E can start: D LF = LS(E)=8 → LS(D)=6
• C feeds into D, so C LF = LS(D)=6 → LS(C)=2
• B similarly feeds into D: B LF = LS(D)=6 → LS(B)=3
• A must precede both B and C, so A LF = min(LS(B), LS(C)) = min(3,2)=2 → LS(A)=0

Float

• A: LS 0 − ES 0 = 0 (critical)
• B: LS 3 − ES 2 = 1 (non-critical; has float)
• C: LS 2 − ES 2 = 0 (critical)
• D: LS 6 − ES 6 = 0 (critical)
• E: LS 8 − ES 8 = 0 (critical)

Critical path: A → C → D → E.

Exam interpretation

If a learner gets float but cannot explain its meaning, marks are lost. Use this statement:

• “Activities on the critical path directly control the project completion date; delays in those activities delay the whole project. Activities with float can slip without affecting completion, up to the float amount.”

Schedule Compression Options: Crashing vs Fast Tracking

PM5 may ask you to propose schedule solutions when delays occur.

• Crashing: reduce duration by adding resources (usually higher cost).
• Fast tracking: run activities in parallel that were originally sequential (increases risk, may reduce quality).

Example decision framing

If Thandi Freight’s UAT (Activity E) is at risk:

• You could crash by adding testers and reducing test documentation time (cost up, risk up if documentation quality suffers).
• Or fast track by starting UAT planning earlier while integration testing is ongoing (but ensure test environment readiness).

Your answer should compare:

• cost impact,
• risk impact,
• quality impact,
• feasibility (availability of people and systems).

Earned Value Management (EVM): The Most Testable Control Technique

Earned Value is a structured method to assess performance by comparing:

• Planned Value (PV): what you planned to spend/work by a point in time,
• Earned Value (EV): what work you have actually achieved (valued at the planned budget for that work),
• Actual Cost (AC): what you actually spent.

From these, compute:

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

Worked example: interpret a status report

Assume by week 6:

• PV = R1,200,000
• EV = R900,000
• AC = R1,050,000

Compute:

• SV = 900,000 − 1,200,000 = −R300,000 (behind schedule)
• CV = 900,000 − 1,050,000 = −R150,000 (over budget)
• CPI = 900,000 / 1,050,000 = 0.857
• SPI = 900,000 / 1,200,000 = 0.75

Interpretation:

• CPI < 1: each rand spent is buying less progress than planned (cost efficiency problem).
• SPI < 1: progress is slower than plan (schedule problem).

Forecasting (if your exam includes it)

A common extension is to forecast estimate at completion (EAC) using approaches like:

• EAC = AC + (BAC − EV) / CPI
  Where BAC is budget at completion.

If BAC is given, you must compute EAC consistently.

Applying EVM to the WMS case style

In exam questions, EVM usually sits inside a narrative:

• “The project is 40% complete but costs are 50% spent”
• “Actual cost is RX and earned value is RY”

Your job:

1. Identify PV, EV, AC from data.
2. Compute variances and indexes.
3. Write a control response: what action you take now and how you monitor.

Control response template (use in answers)

• Analyse root cause: Why is EV < PV (schedule) and/or EV < AC (cost)?
• Corrective action: staffing changes, re-plan critical tasks, revise vendor approach, improve testing discipline.
• Preventive action: update risk register, refine change control, improve estimation and monitoring.
• Update baseline if required: only with formal approval.
• Communicate to stakeholders: steering pack, mitigation plan, decision requests.

Quality and Schedule: Why PM5 Often Connects Them

Many schedule slips are actually quality-related:

• rework after test failures,
• defects discovered late,
• unclear acceptance criteria.

So if a question asks “what could explain the variance?” you can mention:

• test environment instability,
• unclear UAT sign-off criteria,
• interface errors requiring rework,
• change requests during development.

This is a high-scoring pattern: link EVM findings to potential causes and tie responses to quality management.

Section 3: Cost Management, Procurement, and Contracting—Turning Plans into Financial and Supplier Control

PM5 often blends cost and procurement because in real projects, vendor spending, procurement lead times and contract terms drive both budget and schedule outcomes. This section builds your ability to:

• plan procurement,
• choose contracting approaches,
• manage supplier performance,
• control costs through budgeting, forecasting and change.

Cost Control System: Baselines, Forecasts and Change Impacts

A cost control system is not just “track spending.” It includes:

• cost baseline,
• approval thresholds for variances,
• reporting frequency,
• mechanisms for dealing with changes.

Key concepts to master

• Cost baseline: planned distribution of costs over time.
• Control accounts: used to integrate scope, schedule and cost.
• Forecasts: updated estimates based on new performance data.

Variance handling approach (exam logic)

When you see a negative CV or forecast overrun:

1. Confirm whether it is a one-off timing issue (front-loading) or a true performance problem.
2. Identify which work packages caused it.
3. Assess whether schedule delays increased labour/vendor cost.
4. Examine scope creep through change requests (did unapproved scope expand work?).
5. Decide on corrective actions:
   • reduce scope within approved boundaries,
   • increase productivity if feasible,
   • renegotiate contract terms (if allowed),
   • delay non-critical activities.

Cost Estimation for Projects: Bottom-Up vs Top-Down

PM5 exam questions may not demand complex estimation math, but you must use the correct project management reasoning.

• Bottom-up estimation: add costs of work packages (more accurate, time-consuming).
• Top-down estimation: allocate budget based on overall categories (faster, less accurate early).
• Parametric: use known unit rates (e.g., cost per training seat, cost per interface endpoint, cost per testing cycle).
• Analogous: use past similar projects.

Example: bottom-up costing for WMS testing

Suppose testing includes:

• unit testing effort (analyst hours),
• integration testing effort,
• UAT facilitator hours,
• defect fixing buffer (contingency within testing).

A good exam answer might present a cost breakdown like:

• labour cost by role,
• vendor cost for test tools (if any),
• travel costs for training.

Even if exact numbers aren’t given, showing how you would build the estimate scores marks.

Procurement Planning: Make-or-Buy and Sourcing Strategy

Procurement is a planning and control function. A procurement plan includes:

• what to buy,
• when to buy,
• how to buy,
• selection criteria,
• contract structure,
• performance measurement approach.

Make-or-Buy analysis (what markers want)

You should compare:

• internal capability and capacity,
• cost comparison,
• time impact (lead times),
• quality risk,
• availability of skills,
• IP/security requirements.

In the Thandi Freight scenario, procurement might include:

• implementation partner (vendor),
• software licensing,
• integration specialists,
• managed hosting (if relevant).

Contract Types: Choosing the Right Risk Allocation

PM5 frequently tests whether you understand that contract type affects risk sharing.

Common contract types:

1. Fixed-price

   • Contractor bears most cost overrun risk.
   • Client bears scope definition risk (if scope changes, fixed-price can become expensive).

2. Cost-reimbursable (with fee)

   • Client bears more cost risk.
   • Requires strong controls, auditing and clear cost eligibility rules.

3. Time-and-materials

   • Useful when scope is uncertain but labour/material rates are defined.
   • Risk can shift to client if productivity drops without controls.

Exam-style recommendation

If requirements are stable and scope can be defined clearly, fixed-price or milestone-based contracts can work. If requirements evolve (e.g., early in WMS discovery), time-and-materials with caps or not-to-exceed amounts may be safer.

Procurement Process: Steps and Documents

A procurement process in exam questions often appears as a sequence:

1. Procurement needs identified in WBS.
2. Create procurement documentation: terms of reference, specs, evaluation criteria.
3. Source solicitation: RFQ/RFP.
4. Evaluate proposals: technical + commercial criteria.
5. Contract award and mobilization.
6. Contract execution and performance monitoring.
7. Acceptance and closure.

RFP evaluation matrix (example structure)

A typical structure:

• Technical capability (e.g., 40%)
• Experience in similar projects (20%)
• Proposed methodology (20%)
• Price (20%)

Even if you’re not asked to compute weights, show you know how procurement decisions are justified.

Supplier Performance Management: Deliverables, KPIs and Reporting

A high quality PM5 answer doesn’t stop at selecting a vendor. It includes performance management.

Supplier performance KPIs might include:

• delivery milestones met,
• defect rates during testing,
• response time to issues,
• adherence to change control,
• invoice accuracy and compliance.

Vendor reporting cadence

• weekly operational calls,
• monthly performance scorecards,
• milestone completion reports.

Contract controls

• service level agreements (SLAs),
• acceptance criteria,
• warranty/defect liability,
• escalation procedures.

Change Control in Procurement: Why It Drives Cost and Schedule

A major PM5 focus is how procurement and contracting interact with change management.

When scope changes:

• you assess impact on:
  • cost,
  • schedule,
  • resource plan,
  • risk exposure,
  • contract terms (e.g., variations, claims).

A strong exam answer includes:

• a variation order process,
• negotiation and approvals aligned with authority,
• evidence-based justification.

Financial Controls: Budgeting, Invoicing and Managing Cash Flow (conceptual)

Not every exam requires cash flow calculations, but it can ask about:

• invoice timing relative to work done,
• retaining amounts until acceptance,
• payment milestones tied to deliverables.

A common pattern:

• pay 30% mobilization,
• pay 40% on completion of design sign-off,
• pay remaining 30% after go-live acceptance.

This structure protects the client and ensures vendor incentives align with outcomes.

Section 4: Risk Management, Stakeholder Engagement, and Quality Assurance—Integrated PM5 Practice

This section synthesises risk, stakeholder and quality. In PM5 examinations, questions often present multiple issues at once—delays, budget pressure, resistance from users, quality failures. High-performing learners show integration: how stakeholders affect risk, how quality affects schedule, and how risk responses influence governance.

Risk Management Deep Dive: Techniques and Response Design

You already saw risk registers in Section 1. Here the focus is more on:

• analysing risks,
• prioritising and selecting response strategies,
• monitoring risk triggers,
• implementing contingency planning.

Risk analysis methods (how to discuss in answers)

• Qualitative analysis: probability/impact scoring, risk heat maps.
• Quantitative analysis: expected monetary value (EMV), simulation (if asked).
• Root cause analysis: “Why did this risk happen?” using cause-and-effect thinking (e.g., fishbone conceptually).

Even if exams don’t require calculations, you should describe what analysis achieves:

• improves decision quality,
• prioritises mitigation effort,
• provides justification for budgets and contingency.

Response strategies: avoid, mitigate, transfer, accept

• Avoid: change plan to eliminate risk.
  • Example: choose a different vendor due to security compliance concerns.
• Mitigate: reduce probability and/or impact.
  • Example: schedule extra data cleansing tests before UAT.
• Transfer: shift impact to another party.
  • Example: vendor warranty/penalties, insurance.
• Accept: acknowledge and prepare contingency.
  • Example: maintain spare resources for go-live week.

Choosing responses (exam logic)

Your answer should show the reasoning:

• If risk threatens the critical path, mitigation or avoidance is usually more appropriate.
• If risk is low impact but likely, mitigation may still be justified, but not at the expense of critical work.

Risk Monitoring and Trigger-Based Actions

A risk response plan without triggers is weak. PM5 answers should include “when to act.”

Example triggers for Thandi Freight WMS:

• Data migration risk trigger:
  • If migration tests exceed 80% of planned effort by week 4, activate contingency: additional analyst time and adjust migration schedule.
• Vendor mobilisation risk trigger:
  • If vendor team does not meet the mobilisation checklist by day 10, escalate to contract variation negotiation.

This adds realism and marks.

Stakeholder Management: Mapping, Influence, and Engagement Activities

Stakeholder engagement is not only about communication. It also involves managing expectations and enabling adoption.

Stakeholder mapping (basic but must be applied)

Common attributes:

• power/interest (or influence/impact),
• level of interest,
• current sentiment (supportive, neutral, resistant).

Engagement strategies by stakeholder type

• High power, high interest: steering committee briefings, frequent progress reporting, decision involvement.
• High power, low interest: periodic summaries, strategic updates, avoid overburdening.
• Low power, high interest: workshops, training, feedback loops.
• Low power, low interest: occasional updates.

Case-style example: user resistance during UAT

In WMS projects, users may resist new workflows if:

• the system changes daily routines,
• training is insufficient,
• acceptance criteria are unclear.

Risk link: user resistance is both a stakeholder risk and a quality risk.

• If users delay UAT feedback, integration defects are found late → rework → schedule and cost variance.

Exam response (what to propose)

1. Clarify UAT acceptance criteria early (governance).
2. Conduct short “train-and-try” sessions before UAT.
3. Provide a defect logging and prioritisation process.
4. Establish escalation for blocked users (e.g., missing access permissions).
5. Capture lessons learned in a post-UAT improvement plan.

Quality Assurance (QA): Preventing Defects and Rework

PM5 quality management often appears through acceptance criteria, testing, and continuous improvement.

Quality planning basics

A quality plan may include:

• quality objectives (e.g., data accuracy targets),
• standards and procedures,
• roles/responsibilities,
• test strategy and environment requirements,
• audit approach.

Quality assurance vs quality control

• Quality assurance (QA): processes to ensure quality is built in (training, checklists, coding standards).
• Quality control (QC): checking outputs (testing, inspections, audits).

In exam answers, explicitly differentiate QA and QC.

Integrating Quality, Risk and Schedule: Why Defects Are Schedule Risks

A strong PM5 theme: quality problems become schedule problems because they cause rework.

Example integration

If integration testing shows defect density above target:

• additional fix cycles are needed,
• which delays UAT,
• which moves acceptance and go-live.

Your answer should propose:

• root-cause analysis for defects (why they occur),
• adjust testing strategy (more early unit testing),
• enforce change control for late scope changes.

Reporting and Governance for Risk and Quality

PM5 exam questions often ask: “How would you report this to stakeholders?”

A high-scoring structure:

1. Current status: risks and quality metrics.
2. Impact: schedule/cost implications.
3. Trend: improving or worsening.
4. Decision required: escalation, approvals.
5. Next steps: actions and due dates.

Section 5: Exam Pack Practice—PM5-Style Questions, Model Answers, Templates, and Revision Checklists

This final section provides an extensive practice bank and exam-ready templates. It is designed to help you convert theory into structured answers that score marks in South African university and MANCOSA assessments—especially where case studies require calculations, prioritisation and justified recommendations.

How to Write a High-Scoring PM5 Answer (Structure That Works)

A consistent exam structure helps you score even when the question is unfamiliar.

Recommended answer framework

1. Restate the problem (1–2 lines)
2. Identify key constraints (time, cost, scope, resources)
3. Propose the plan using PM tools (WBS, schedule logic, risk register, governance)
4. If calculations are required, show:
   • formula/steps,
   • computed results,
   • interpretation in context
5. Provide recommendations (what you will do next and why)
6. Link to governance (reporting, approvals, change control)

Practice Question Set 1: Lifecycle, WBS and Scope Control

Question 1

A client wants to implement a new warehouse management system within 6 months with a maximum initial budget of R3,200,000. The scope is unclear in the early stage and user departments disagree on priorities.

Required:
a) Propose a project initiation and planning approach to clarify scope and set governance.
b) Provide a deliverable-based WBS outline for the project.
c) Explain how you would manage scope changes.

Model answer (condensed but exam-style)

a) Initiation and planning approach

• Develop a project charter with purpose, authority, high-level scope boundaries, initial budget envelope (R3,200,000), and the 6-month target.
• Conduct stakeholder mapping and hold discovery workshops to clarify requirements.
• Establish stage-gate governance:
  • Gate 1: approval of requirements baseline and UAT criteria.
  • Gate 2: sign-off of interface design and build plan.
  • Gate 3: readiness for go-live acceptance testing.
• Implement a change control process with:
  • change request logging,
  • impact assessment on scope/time/cost,
  • approval thresholds linked to sponsor/steering committee.

b) Deliverable-based WBS outline

• 1.0 Project initiation (charter, stakeholder engagement plan)
• 2.0 Requirements & design (process mapping, functional requirements, interface design, data migration plan)
• 3.0 Configuration & build (system configuration, interface build, migration scripts)
• 4.0 Testing (unit, integration, UAT)
• 5.0 Training & deployment (training materials, cutover plan, go-live support)
• 6.0 Closure & benefits review (handover, post-implementation review)

c) Managing scope changes

• Require a documented change request.
• Assess impact using agreed criteria.
• Use contingency for small risks; use management reserve or re-baseline only with approval.
• Maintain traceability from requirements to deliverables and acceptance criteria.

Practice Question Set 2: Critical Path and Schedule Interpretation

Question 2

The following activities exist in a project:

• Activity A: Duration 2 weeks (no predecessor)
• Activity B: Duration 3 weeks (predecessor: A)
• Activity C: Duration 4 weeks (predecessor: A)
• Activity D: Duration 2 weeks (predecessors: B and C)
• Activity E: Duration 3 weeks (predecessor: D)

Required:
a) Determine the project duration using critical path logic.
b) Identify the critical path.
c) Explain float for activities B and C.

Model answer

Forward pass

• A: ES 0, EF 2
• B: ES 2, EF 5
• C: ES 2, EF 6
• D: ES max(5,6)=6, EF 8
• E: ES 8, EF 11

Project duration = 11 weeks.

Critical path

• Since C determines D’s ES (C EF = 6 > B EF = 5), the critical path is A → C → D → E.

Float

• B’s EF is 5 but D can only start at 6, so B has 1 week of float.
• C is on the critical path, so float for C is 0.

Practice Question Set 3: Earned Value Calculations

Question 3

At a certain reporting date, a project has the following data:

• Planned Value (PV) = R1,200,000
• Earned Value (EV) = R900,000
• Actual Cost (AC) = R1,050,000

Required:
a) Calculate SV and CV.
b) Calculate CPI and SPI.
c) Interpret what these mean and recommend two corrective actions.

Model answer

a)

• SV = EV − PV = 900,000 − 1,200,000 = −R300,000
• CV = EV − AC = 900,000 − 1,050,000 = −R150,000

b)

• CPI = EV / AC = 900,000 / 1,050,000 = 0.857
• SPI = EV / PV = 900,000 / 1,200,000 = 0.75

c) Interpretation:

• SV negative: behind schedule.
• CV negative and CPI < 1: over budget for the work earned (cost inefficiency).

Corrective actions (examples):

1. Investigate causes: e.g., rework, defects, vendor delays; implement corrective quality processes and adjust staffing on critical tasks.
2. Re-plan the critical path: update schedule logic, prioritise remaining critical activities, and control change requests to stop scope creep.

Practice Question Set 4: Procurement and Contract Strategy

Question 4

A project requires a vendor to implement a system integration. The scope is partially uncertain early, but the project sponsor insists on a firm timeline. You must decide on a procurement approach.

Required:
a) Explain how you would conduct a make-or-buy decision.
b) Recommend a suitable contract type and justify your choice.
c) Describe two supplier performance measures you will include in the contract.

Model answer

a) Make-or-buy:

• Compare internal team capability and capacity vs vendor capability.
• Estimate costs (labour rates, internal overhead, training).
• Compare lead times and feasibility.
• Evaluate risk: security compliance, quality, delivery performance.

b) Contract recommendation:

• Because early scope is uncertain, prefer time-and-materials with not-to-exceed limits and milestone-based acceptance, or a cost-reimbursable structure with strict controls.
• Justification: reduces risk of fixed-price mismatch when scope evolves; timeline is managed through milestone schedules.

c) Supplier performance measures:

• Milestone delivery performance (on-time completion rate).
• Defect rate or responsiveness (e.g., severity 1 issues resolved within X days, or defect density thresholds during UAT).

Practice Question Set 5: Risk and Stakeholder Integration

Question 5

During user acceptance testing (UAT) for a new WMS, users report that training was insufficient and they are delaying sign-off. The project manager also notices late defect discovery is increasing rework.

Required:
a) Identify at least three risks triggered by stakeholder and quality issues.
b) Propose risk responses for each risk.
c) Outline what information you would include in a steering committee update.

Model answer

a) Three risks:

1. Stakeholder adoption risk: user resistance delaying UAT sign-off.
2. Quality risk: late defect discovery causing rework.
3. Schedule risk: UAT slippage affecting go-live and acceptance.

b) Responses:

1. Stakeholder response: schedule targeted training and “train-and-try” sessions; clarify acceptance criteria; establish a feedback/escalation channel.
2. Quality response: enforce structured defect logging, prioritise severity, introduce additional test cycles earlier (if feasible).
3. Schedule response: re-baseline UAT activity sequence if required; allocate extra resources to resolve critical defects quickly.

c) Steering committee update:

• Current status: % UAT completion, defect trends, sign-off progress.
• Variance impacts: time and cost implications (if known).
• Top risks: updated risk register entries with triggers and owners.
• Decisions requested: e.g., approval for additional training resources or schedule compression options.
• Next steps: dates for revised UAT milestones.

PM5 Templates: Copy, Adapt, and Use in Exams

Template 1: Risk Register (table structure)

Risk ID	Risk statement (cause → event → impact)	P	I	Score	Response (avoid/mitigate/transfer/accept)	Owner	Trigger	Contingency

Template 2: Change Control Record (structured bullet template)

• Change Request ID:
• Requestor:
• Description of change:
• Reason for change:
• Impact assessment:
  • Scope impact:
  • Schedule impact:
  • Cost impact:
  • Quality impact:
• Options considered:
• Recommended decision:
• Approval authority:
• Decision date:
• Implementation plan:

Template 3: Weekly Status Report (exam-mark friendly)

• Reporting period:
• Overall progress (% and milestone achieved):
• Completed work packages:
• Upcoming work packages:
• Issues & risks (top 3) with owner and due date:
• Schedule performance (qualitative):
• Cost performance (qualitative):
• Decisions required from sponsor/steering committee:

Revision Checklists: High-Frequency PM5 Topics

If a question asks about planning:

• WBS deliverables included
• schedule logic identified
• milestones and dependencies explained
• governance and change control mentioned

If a question asks about schedule control:

• critical path identified (with reasoning)
• float interpretation included
• corrective actions suggested (crashing/fast tracking with pros/cons)

If a question asks about cost control:

• cost baseline vs forecast described
• EVM computations: PV, EV, AC
• interpretation of CPI/SPI and variances
• corrective action suggestions tied to root causes

If a question asks about procurement:

• make-or-buy reasoning
• contract type justification
• supplier performance measures and acceptance criteria
• change impacts and variation handling

If a question asks about stakeholder and risk:

• stakeholder mapping and engagement actions
• risk register with triggers and owners
• integration: quality and schedule implications

Final Strategy: How to Use This Exam Pack Effectively

• Practise writing structured answers using the frameworks above.
• Rehearse the numeric patterns:
  • critical path ES/EF logic,
  • float interpretation,
  • PV/EV/AC and CPI/SPI and variances.
• Build confidence by running through the practice questions multiple times, each time improving:
  • clarity of assumptions,
  • realism of recommendations,
  • explicit linking of tools to governance and decisions.

This PM5 exam pack is designed to prepare you for both theory-heavy questions (governance, scope control, stakeholder management) and calculation-heavy ones (critical path, earned value). If you consistently produce answers that connect planning → measurement → corrective action → reporting, you align with what PM5 exam markers typically reward in South African university and MANCOSA-style assessments.