PJM4A11 Project Management 4A (Civil Engineering) Past Papers — Exam Notes (University of Johannesburg)

PJM4A11 (Project Management 4A for Civil Engineering) is a core module that tests your ability to plan, schedule, cost, and control civil engineering projects using standard project management tools. This study guide is designed around the kind of questions that typically appear in past papers—especially the mixture of theory, calculations, and short-argument problem-solving. It also aligns with what you’ll see in many South African university assessments: structured answers, clear assumptions, and disciplined use of project management frameworks.

This guide is written specifically for students in the University of Johannesburg (UJ) Project Management Exam Resources (College of Business & Economics) collection, focusing on the PJM4A11 exam style and the expected competencies in civil engineering project contexts.

Section 1: Understanding PJM4A11 Exam Requirements — How Past Papers Test Your Project Management Thinking (UJ Civil Engineering)

What PJM4A11 Typically Assesses

In PJM4A11, you’re not only expected to “know definitions”—you’re expected to apply project management methods to realistic civil engineering scenarios. Past-paper style questions often test:

Project initiation and definition: identifying stakeholders, clarifying scope, and setting project objectives that can be measured.
Work breakdown and scope control: turning a project description into deliverables and work packages.
Scheduling and time management: using critical path concepts, sequencing logic, and sometimes activity time/cost trade-offs.
Cost estimation and budgeting: building an estimate, justifying assumptions, and interpreting cost breakdowns.
Risk and quality management: identifying risks, assessing likelihood/impact, and proposing responses.
Monitoring and control: using performance measures to judge schedule and cost status (often with formulas and interpretation).

Because PJM4A11 is “Project Management 4A,” the exam usually expects intermediate-to-applied competence. That means: show methods, compute carefully, and interpret results—not just state the method.

How Civil Engineering Context Changes the Questions

Civil engineering adds specific “flavour” compared with general project management modules. You may see scenarios involving:

Roadworks, bridges, buildings, water and sanitation infrastructure
Earthworks, concrete curing periods, foundation activities
Procurement lead times for materials such as cement, rebar, structural steel
Constraints like access restrictions, inspections, safety requirements, and environmental compliance

These features affect scheduling, risk, and cost control. For instance:

Some tasks have durational dependencies (e.g., concrete cannot proceed to the next stage without curing time).
Weather affects earthworks more strongly than indoor activities.
Procurement delays influence the earliest possible start dates.

Past papers often exploit these dependencies by giving a network diagram or precedence table and asking you to calculate:

Earliest Start (ES) and Latest Finish (LF)
Float/Slack
Critical path
Project duration and sometimes “time impact” of changes

Common Past Paper Question Formats (UJ Style Patterns)

While different past papers vary by lecturer and year, there are recurring patterns:

Short theory questions (5–10 marks)
- Example: “Explain the difference between scope and deliverables.”
- Expected response: structured bullet points, with an applied civil example.
Calculations using formulas (10–20 marks)
- Example: “Given activities and predecessors, compute the critical path and total project duration.”
- Expected response: show the forward pass and backward pass (or equivalent), then explain what “critical” means.
Mixed scenario questions (20–30 marks)
- Example: a project description plus a schedule and budget data, then ask for both:
  - risk register entries (qualitative/quantitative)
  - performance interpretation (e.g., schedule/cost variance)
- Expected response: combine calculation with a narrative interpretation.
Best-practice justification
- Example: “Propose a mitigation plan for a procurement delay. Justify your plan.”
- Expected response: link mitigation measures to the risk’s cause, and reflect feasibility in civil works.

Your “Answer Structure” for High Marks

Past-paper success often comes from disciplined formatting. A reliable structure for PJM4A11 answers:

Define the concept (one sentence)
State the method (two short sentences: what you do and why)
Compute clearly (show steps; do not skip arithmetic)
Interpret the result (what it means for decision-making)

Civil engineering project management also rewards clarity in assumptions:

If a question does not specify overtime policy, state a reasonable assumption (e.g., normal working days only).
If a question provides a cost per day, confirm whether you’re expected to use it for crash calculations (if those appear).

Quick Orientation: Essential Tools You Must Be Comfortable With

A PJM4A11 exam is usually manageable if you are fluent with the following tools:

Work Breakdown Structure (WBS) and deliverable-based thinking
Activity sequencing / precedence in a network model
Critical path method (CPM) calculations:
- ES/EF (earliest start/finish)
- LS/LF (latest start/finish)
- Float (total and sometimes free float)
Cost estimation basics:
- direct vs indirect costs
- contingency logic
Risk management cycle:
- identify → analyze → plan responses → implement → monitor
Monitoring & control:
- performance measurement interpretation using standard variance logic

This section sets the foundation. The following sections move into the tools and calculations that commonly appear in PJM4A11 past papers—especially those that students typically struggle with.

Section 2: Work Breakdown Structure, Scope Definition, and Scheduling Logic in Civil Projects (PJM4A11 Past Paper Skills)

Work Breakdown Structure (WBS): From Project Brief to Work Packages

A Work Breakdown Structure converts a project into manageable components. In civil engineering projects, the best WBS is usually deliverable-based (what you will produce), not just task-based.

Deliverable-Based WBS Example (Civil Engineering)

Consider a simplified project: construction of a small bridge.

A deliverable-based WBS might look like:

Project Management
- Project office & reporting
- Safety management coordination
Design & Approvals
- Concept design
- Detailed drawings
- Environmental approvals coordination
Site Establishment
- Mobilization
- Site access and security
Foundations
- Piling/substructure works
- Foundation concrete works
Superstructure
- Steel/RC elements fabrication/installation
- Deck slab works
Finishing & Safety
- Bearings and expansion joints
- Road surfacing tie-in
Commissioning & Close-Out
- Final testing/inspections
- Handover documentation

Within each branch, you create work packages—small units that are:

clearly described,
assignable to a responsible party,
measurable for progress.

Why Past Papers Emphasize WBS

Past-paper questions often assess whether you understand:

Scope boundaries (what’s included vs excluded)
Level of detail (not too high-level, not overly microscopic)
Consistency (WBS should match scope statements)

A common exam trap: students make a WBS that is only a list of activities. That can still help scheduling, but it weakens scope control because deliverables are missing. Civil engineering projects require strong scope traceability due to approvals and handover documentation.

Scope Definition and Stakeholder Alignment

In civil projects, “scope” must align with stakeholders such as:

client/owner,
consulting engineer,
contractors,
regulatory authorities,
community representatives.

Scope Statement Elements (Short Exam Answers)

When asked to define scope, your answer should include elements such as:

Project objectives (measurable outcomes)
Deliverables (what will be handed over)
Boundaries (what’s included/excluded)
Assumptions (e.g., access road availability)
Constraints (e.g., working hours, site limitations)
Acceptance criteria (what quality and documentation are required)

Example of “Acceptance Criteria” in Civil Works

For a road segment, acceptance criteria might include:

compaction test results (minimum %),
surface smoothness measurements,
drainage functionality (no ponding),
as-built drawings and certification.

Past papers sometimes ask: “Why acceptance criteria matter?” The civil answer: because they prevent disputes at close-out and they guide quality control during execution.

Activity Sequencing: Precedence Logic and Network Models

Scheduling depends on correct precedence relationships.

Common Precedence Types

When you see activity networks in past papers, the activities usually have relationships such as:

Finish-to-Start (FS): Activity B cannot start until A finishes.
Start-to-Start (SS): B starts when A starts (less common in basic exams).
Finish-to-Finish (FF): B finishes when A finishes (also less common in basic introductory sections).
Lag/Lead: time between activities (e.g., curing time).

In civil engineering, FS with lags is extremely common:

After foundation concrete pour finishes, there is a curing period before placing columns.

Critical Path Method (CPM): Forward and Backward Pass

A typical PJM4A11 past paper question provides a set of activities, durations, and predecessors, then asks you to compute ES/EF, LS/LF, float, and critical path.

A Worked Example (Style-Compatible)

Suppose a simplified civil project has these activities:

Activity	Duration (days)	Predecessor(s)
A	3	—
B	4	A
C	2	A
D	5	B, C
E	3	D

We calculate:

Forward Pass (earliest times)
- Start of A: ES(A)=0, EF(A)=0+3=3
- B: ES(B)=EF(A)=3, EF(B)=3+4=7
- C: ES(C)=EF(A)=3, EF(C)=3+2=5
- D depends on both B and C, so ES(D)=max(EF(B), EF(C))=max(7,5)=7, EF(D)=7+5=12
- E: ES(E)=EF(D)=12, EF(E)=12+3=15
- Project duration = EF(E) = 15 days
Backward Pass (latest times)
- Set LF(E)=project duration = 15, LS(E)=15-3=12
- D predecessor of E: LF(D)=LS(E)=12, LS(D)=12-5=7
- B and C precede D; their LF is LS(D)=7
  - LS(B)=LF(B?) Actually for backward pass:
    - LF(B)=LS(D)=7, LS(B)=7-4=3
    - LF(C)=LS(D)=7, LS(C)=7-2=5? Wait: if LF(C)=7 then LS(C)=7-2=5
- A precedes B and C:
  - LF(A)=min(LS(B), LS(C))=min(3,5)=3
  - LS(A)=3-3=0
Float/Slack
- Total float TF = LS – ES (or LF – EF)
- A: LS 0 – ES 0 = 0 → critical
- B: LS 3 – ES 3 = 0 → critical
- C: LS 5 – ES 3 = 2 → non-critical
- D: LS 7 – ES 7 = 0 → critical
- E: LS 12 – ES 12 = 0 → critical

Critical path: A → B → D → E
Non-critical activity: C has 2 days of float.

Why This is a Past-Paper Favorite

Past papers love CPM because:

it tests method,
it tests attention to precedence,
it punishes calculation errors and missed max/min logic.

Civil engineering scenarios often include parallel tasks (e.g., piling and excavation) followed by a dependent task (e.g., concrete placement). That’s exactly the kind of structure that creates float.

Time–Cost Implications in Scheduling (Intro Level)

Some PJM4A11 past papers include “what happens if we reduce duration?” questions. Even if full crashing is not required, you must understand the logic:

Activities on the critical path have zero float, so reducing their duration reduces total project time.
Non-critical activities with float may be reduced without affecting project duration—unless the reductions remove the float.

To score well, you should explicitly state:

“Because activity C has float of 2 days, reducing C by 2 days would still not change the overall project duration. Only beyond that would the critical path change.”

That type of interpretation demonstrates exam-grade understanding.

Scope vs Schedule: Avoiding Two Common Errors

Two common student mistakes in past papers:

Treating WBS as a schedule
- WBS organizes deliverables; schedule sequences work.
- They overlap but are not identical.
Confusing precedence with availability
- Precedence dictates logical ordering.
- Availability considers resources and constraints, which may require additional modelling (not always detailed in basic exams).

To improve marks:

If asked for precedence, focus on predecessors and logical dependencies.
If asked for “resource constraints,” then discuss procurement, labour, and plant availability.

This section gave you the core building blocks for exam-style CPM and WBS questions. Next, you’ll apply these ideas in cost estimation, budgeting, and monitoring—where past papers often include numeric P&L-style or variance interpretations.

Section 3: Project Costing, Budgeting, and Monitoring & Control for Civil Engineering Projects (PJM4A11 Past Papers)

Cost Estimation Foundations

In civil engineering project management, cost is not just “materials plus labour.” It includes design, approvals, temporary works, risk allowances, and overhead structures.

Direct vs Indirect Costs

A good exam answer distinguishes:

Direct costs: costs that can be traced to specific work activities
- concrete materials, rebar, labour hours for a specific pour
Indirect costs: costs that support the project but aren’t directly traceable to one activity
- site supervision overhead, site security, project management staff

Contingency and Risk Allowances

Past papers often want to see that you understand the difference between:

Contingency: budget reserve for identified risks or known uncertainty
Management reserve: reserve for unknown unknowns (depending on how your course frames it)

In civil engineering, uncertainties include:

underground conditions,
weather delays,
regulatory delays,
productivity variation due to site constraints.

Budgeting Structure in Exam Scenarios

Budgeting typically follows a logic such as:

Estimate costs per work package/activity
Aggregate costs into cost accounts
Plan expenditure over time (cash flow)
Include contingency or risk allowances (as instructed)

Example: Simple Cost Aggregation (Civil Works)

Assume a small site works package with activities:

Earthworks: R 120,000
Concrete: R 85,000
Reinforcement: R 60,000
Finishing: R 45,000
Project overhead allocation: R 30,000

Total base estimate:

120,000 + 85,000 + 60,000 + 45,000 + 30,000
= R 340,000

If the exam adds contingency of 10%:

Contingency = 0.10 × 340,000 = R 34,000
Total budget = 340,000 + 34,000 = R 374,000

A high-mark answer will show arithmetic clearly. Another key exam skill: interpret what contingency means—i.e., not a “use whenever,” but tied to risk triggers or approved changes.

Earned Value Style Monitoring (If Included in Your Past Papers)

Some project management courses (and past papers) use earned value concepts even if not always labelled “EV.” You might see variables like:

Planned Value (PV)
Earned Value (EV)
Actual Cost (AC)

Even if the course uses simplified monitoring language, many exams still resemble EV logic.

EV Relationships You Must Know

If EV concepts apply:

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

These indicators allow interpretation:

SV < 0: behind schedule
CV < 0: over budget
CPI < 1: cost efficiency below plan

A Worked Example (Full Numeric Consistency)

Assume at a reporting date:

PV = R 200,000 (planned value of work that should be completed)
EV = R 175,000 (earned value of work actually completed)
AC = R 210,000 (actual cost spent)

Compute:

SV = EV − PV = 175,000 − 200,000 = −R 25,000
CV = EV − AC = 175,000 − 210,000 = −R 35,000
SPI = EV / PV = 175,000 / 200,000 = 0.875
CPI = EV / AC = 175,000 / 210,000 ≈ 0.833

Interpretation:

SV negative and SPI < 1 ⇒ project is behind schedule.
CV negative and CPI < 1 ⇒ project is over budget for the work earned.

In a civil engineering context, this might reflect:

productivity loss due to site constraints,
rework because of quality issues,
delays causing extended overhead.

If your past paper asks “what should management do?”, your answer should link:

behind schedule + over cost ⇒ investigate root causes and implement corrective actions.

Monitoring & Control: From Reporting to Corrective Action

Monitoring and control in project management is often presented as a loop:

Measure actual performance
Compare to plan/baseline
Analyse variances (why did it happen?)
Take corrective actions (what will fix it?)
Update forecasts and re-baseline if allowed

Example Corrective Actions (Civil Engineering)

If the project is behind schedule:

resequence non-critical activities,
increase resource allocation (if available),
add overtime (if permitted),
address constraints causing productivity loss (access, approvals, material availability).

If the project is over budget:

verify quantities and measurement accuracy,
check labour productivity and procurement unit pricing,
control variations/change orders,
review contingency usage rules.

Past papers sometimes ask for a “justification” of corrective action selection. Your answer should:

identify the likely cause,
choose an action that addresses that cause,
consider feasibility and risk impacts.

Quality Management as a Cost Driver

Quality is not just “technical.” In civil engineering, poor quality becomes costly:

rework,
delays due to failed inspections,
wasted materials,
disputes at handover.

A good exam narrative links quality control to cost and schedule:

If concrete compressive strength tests fail, cure time and redo works push schedule.
Delays then raise overheads (site facilities, supervision time).

Thus, monitoring & control is inseparable from quality and risk management.

Change Control: Why Variations Matter in Civil Projects

Civil projects often encounter scope changes due to:

client design changes,
unforeseen ground conditions,
service relocations (utilities),
compliance updates.

Past papers often test your ability to propose a change control process. A standard approach includes:

Raise a change request with description of what changed
Assess impacts:
- scope impact
- time impact
- cost impact
Evaluate risk and compliance implications
Approve/reject through the appropriate authority
Update baseline documents (schedule, cost estimate, contract documents)

In an exam scenario, if asked for “impacts,” you should mention at least:

effect on critical path (if applicable),
effect on resource plan,
whether contingency is sufficient or requires re-budgeting.

This section built your competence in cost estimation and monitoring logic. Next, you will tackle risk and stakeholder management—topics that are common in PJM4A11 past papers, often asked with applied civil scenarios.

Section 4: Risk Management, Stakeholders, and Procurement/Contract Interfaces in Civil Engineering Projects (PJM4A11 Past Papers)

Stakeholder Management: Identifying Power, Interest, and Influence

Stakeholders in civil engineering include:

client/owner,
engineers/consultants,
contractor,
subcontractors,
regulatory authorities,
communities and end-users,
suppliers and transport operators.

A common exam approach is the power–interest matrix:

High power / high interest: manage closely
High power / low interest: keep satisfied
Low power / high interest: keep informed
Low power / low interest: monitor with minimal effort

Applied Example

In a road rehabilitation project:

Regulatory authorities may have high power (approvals, compliance).
Communities might have high interest (access disruptions) but possibly lower formal power.
Suppliers might have low–moderate interest but can strongly affect schedule through lead times.

Your exam answers should show that you can map stakeholders to appropriate engagement methods:

meetings, reporting lines, inspection schedules, and communication plans.

Risk Management Cycle: From Identification to Monitoring

Risk management is usually assessed as a process. Your exam answer should show:

Identify risks
Analyse/assess (likelihood and impact)
Plan responses
Assign ownership
Implement and monitor

Typical Civil Engineering Risks in Past Papers

Examples include:

Construction risks: productivity lower than planned, rework due to quality failures
Technical risks: design errors, incorrect assumptions about soil conditions
Procurement risks: late delivery of steel, cement, or specialized components
Environmental risks: weather, rainfall, erosion control compliance issues
Safety risks: incidents affecting work stoppage
Legal/regulatory risks: permit delays, inspection failure

Risk Register and Scoring (Likelihood–Impact)

Many past papers expect you to create or interpret a risk register. A typical risk register table includes:

Risk description
Category (technical, schedule, cost, safety, environment)
Likelihood (e.g., Low/Medium/High or 1–5)
Impact (e.g., Low/Medium/High)
Risk rating (could be L×I)
Risk response strategy
Owner

Example Risk Register Entry (Roadworks)

Risk: Late delivery of reinforcement bars due to supplier lead time
Likelihood: Medium (3)
Impact: High (5)
Risk rating: 3×5 = 15
Response:

place early orders,
qualify alternative suppliers,
use buffer stock for critical items,
adjust sequencing (if possible) to avoid idle labour.

This kind of entry is exactly the type of “apply concept to scenario” marksheet expects.

Risk Response Strategies: Avoid, Mitigate, Transfer, Accept

Past papers test both the definition and the logic of responses.

Avoid: change plan to eliminate the risk
Mitigate: reduce likelihood or impact
Transfer: shift impact via insurance or contract terms
Accept: acknowledge risk and plan contingency

In civil projects:

Transfer might involve contractual clauses (e.g., penalties for late delivery).
Mitigate might involve procurement scheduling or alternative methods.

If a question asks which strategy is best, your answer should justify based on:

severity,
controllability,
cost of mitigation vs cost of risk.

Procurement and Contract Interfaces (Civil Engineering Reality)

Even in “project management” modules, civil engineering exams often connect procurement and scheduling:

procurement lead times,
contract milestones,
variation approvals,
subcontractor management.

Procurement as a Schedule Driver

If a task cannot start until materials arrive, then procurement becomes part of scheduling logic:

It creates implicit predecessors (e.g., reinforcement delivery precedes concrete placement).

Past papers may provide:

lead times,
delivery constraints,
documentation requirements.

Your answer should explicitly link:

how procurement lead time affects ES/Ef of construction activities,
how delays create float consumption (or critical path shifts).

Contract/Change Interface: Risk and Cost Implications

Contract changes (variations) affect:

cost (materials, labour, overhead),
time (rework or resequencing),
risk (unknowns that require additional approvals).

A strong exam response for “change control and risk” combines:

schedule impact analysis (critical path implications),
cost impact logic (what items change and why),
documentation and approval pathway.

Integrating Risk and Quality: Preventing Costly Rework

Quality failures often cause schedule delays and cost overruns, turning quality risk into project performance risk.

For example:

If concrete curing is interrupted due to weather management failure, the result can be:
- structural performance risk,
- rework,
- inspection retest delays.

Thus, risk management should incorporate preventive quality controls:

curing plans,
inspection schedules,
material testing,
procedures for weather contingency.

This section covered stakeholder management and risk management applied to procurement and civil delivery realities. Next, you’ll tackle advanced scheduling interpretation—especially float, critical path shifts, and scenario analysis that past papers commonly test.

Section 5: Scenario-Based Past Paper Mastery — CPM Modifications, Time/Cost Trade-offs, and Exam-Ready Problem Solving (PJM4A11)

Building Past-Paper Confidence with a “CPM Modification” Method

Many PJM4A11 problems don’t just ask you to compute a critical path once. They may change an activity duration, add a lag, or insert a new task and ask you to recompute the outcome.

A reliable procedure when the network changes:

Recompute forward pass to get new earliest finish times.
Recompute backward pass from the new project end time.
Recalculate float for each activity.
Identify:
- the new critical path,
- whether project duration changes,
- which activities become critical.

Students lose marks when they try to adjust “by intuition” without recalculating max/min logic correctly.

Example: Reduce a Non-Critical Activity and Check Duration Impact

Use the earlier network:

A (3)
B (4) after A
C (2) after A
D (5) after B and C
E (3) after D

Original:

Project duration = 15 days
Critical path = A–B–D–E
Activity C float = 2 days

Scenario Change

Suppose activity C duration is reduced from 2 days to 1 day.

Recompute forward pass:

ES(A)=0 EF(A)=3
B: ES=3 EF=7
C: ES=3 EF=4
D depends on B and C: ES(D)=max(EF(B), EF(C))=max(7,4)=7 → EF(D)=7+5=12
E: ES=12 EF=15

Project duration remains 15 days.

Interpretation:

Because C’s reduction is within its float (original float = 2 days, reduction = 1 day), it does not affect the critical path or total duration.

Past papers often award marks for:

showing computation,
stating clearly that total duration is unchanged,
explaining why (float concept).

Example: Reduce a Critical Activity and Show New Duration

Now reduce activity B from 4 days to 3 days.

Original critical path included B. So we expect reduced project duration.

Recompute forward pass quickly:

A: ES 0 EF 3
B: ES 3 EF 3+3=6
C: ES 3 EF 5
D depends on B and C: ES(D)=max(EF(B), EF(C))=max(6,5)=6 → EF(D)=6+5=11
E: ES=11 EF=11+3=14

New project duration = 14 days.

Interpretation:

Since B is on the critical path, its duration reduction shortens the chain A–B–D–E.

A high-quality exam response includes both:

updated duration,
explanation that critical path changed or remained critical with different length.

Example: Insert a Lag (Civil Curing Time)

Civil engineering often includes lags. Suppose after D (which includes foundation/concrete related work), the project requires a 2-day inspection/curing buffer before E can start.

Then modify precedence:

E depends on D with a 2-day lag: E starts 2 days after D finishes.

In the original network:

EF(D)=12 → ES(E)=12+2=14 → EF(E)=14+3=17

Project duration becomes 17 days.

Past papers might ask:

“How does lag affect critical path?”
Your answer:
the critical path remains conceptually tied to the chain into D, but the total duration increases because the lag delays E.

Time/Cost Trade-offs: Conceptual “Crash Decision” Logic

Some past papers ask you to discuss whether to crash (shorten) an activity and how to choose. Even if the question doesn’t provide crash slope rates, you should know the logic:

Crashing critical activities yields schedule reductions.
Crashing non-critical activities might not reduce project duration until float is exhausted.
Crashing increases cost—so you compare:
- cost to reduce duration vs benefits (e.g., reduced overhead, earlier completion penalties/bonuses).

A civil context includes:

earlier completion reduces closure risks, community disruption costs, and prolonged site overhead,
but crashing may raise quality risk if crews rush curing or reduce testing time (which can be dangerous).

So, exam answers should balance:

schedule urgency,
safety/quality constraints,
financial trade-offs.

Correct Assumptions in Scenario Questions

Past papers frequently leave some details unspecified. To score well:

state a clear assumption,
keep it consistent throughout the calculation.

Examples of assumptions you might state (only if needed):

working days only (no weekends) unless specified otherwise,
resources are sufficient (or if constrained, mention that schedule compression requires resource reallocation),
cost rates apply uniformly (if a per-day cost is provided, use it for the relevant time change only).

Exam-Ready “Quality Checklist” for Numeric Work

When solving CPM and time/cost questions, check:

Did you apply max when an activity has multiple predecessors in forward pass?
Did you apply min when setting latest times (backward pass)?
Did you compute project duration as the final EF/LF properly?
Did you compute float as LS − ES (or LF − EF) consistently?
When durations change, did you recompute both forward and backward passes?

Civil engineering problems punish errors because one wrong float or wrong max/min ripples through.

A Full Scenario Practice (Civil-Style Narrative + CPM + Interpretation)

Consider a civil project with the following activities:

A: Site establishment (2 days), no predecessor
B: Excavation (4 days), predecessor A
C: Foundation concrete (3 days), predecessor B
D: Rebar installation (2 days), predecessor B
E: Concrete pour for columns (4 days), predecessor C and D
F: Curing and QA inspection (3 days), predecessor E with no lag

We ask:

Determine earliest start/finish and project duration.
Determine critical path and float for all activities.
If activity D is reduced by 1 day, determine new project duration.

Step 1: Forward Pass

ES(A)=0 → EF(A)=0+2=2
B after A: ES(B)=2 → EF(B)=2+4=6
C after B: ES(C)=6 → EF(C)=6+3=9
D after B: ES(D)=6 → EF(D)=6+2=8
E after C and D: ES(E)=max(EF(C), EF(D))=max(9,8)=9 → EF(E)=9+4=13
F after E: ES(F)=13 → EF(F)=13+3=16

Project duration = 16 days

Step 2: Backward Pass

LF(F)=16 → LS(F)=16−3=13
E precedes F: LF(E)=LS(F)=13 → LS(E)=13−4=9
C and D precede E:

For C: LF(C)=LS(E)=9 → LS(C)=9−3=6
For D: LF(D)=LS(E)=9 → LS(D)=9−2=7
A precedes B:
B has to feed C and D; backward determines:
LF(B)=min(LS(C), LS(D))=min(6,7)=6 → LS(B)=6−4=2
A:
LF(A)=LS(B)=2 → LS(A)=2−2=0

Now float TF = LS − ES:

A: LS0 − ES0 = 0
B: LS2 − ES2 = 0
C: LS6 − ES6 = 0
D: LS7 − ES6 = 1
E: LS9 − ES9 = 0
F: LS13 − ES13 = 0

Critical path = A → B → C → E → F
Activity D has float 1 day.

Step 3: Reduce D by 1 day

Original D duration = 2 → new duration = 1.

Recompute forward pass:

A EF = 2
B EF = 6
C unchanged: EF(C)=9
D new: ES(D)=6 → EF(D)=6+1=7
E ES = max(EF(C), EF(D))=max(9,7)=9 → EF(E)=9+4=13
F EF = 13+3=16

New project duration remains 16 days.

Interpretation:

D had float 1 day; reduction used exactly that float and did not change which predecessor constrained E (C remained the controlling path because EF(C)=9 > EF(D)=7).

This practice demonstrates the exact type of reasoning past papers expect: compute, interpret, and link float to duration impact.

How to Write Answers That Look Like Past Paper “Marking Scheme” Winners

A final exam strategy linked to past paper outcomes:

Use tables for ES/EF/LS/LF when networks are involved.
Keep float values visible; explicitly label critical activities.
When asked “explain,” connect your explanation to the calculated numbers (e.g., “float = 1 day, so reduction by 1 day does not change project duration”).
For risk questions:
- include a risk owner,
- propose a response strategy,
- mention monitoring (how you track whether the response works).

Bringing It All Together: A Unified PJM4A11 Exam Skillset

Across WBS, scheduling, costing, risk, and control, PJM4A11 past papers reward the same core competencies:

Structured decomposition (WBS into deliverables/work packages)
Logical sequencing (precedence relationships)
Correct CPM calculations (max/min logic, forward/backward passes)
Sound cost and budget logic (direct/indirect, contingency, assumptions)
Variance interpretation (what the numbers mean operationally)
Risk and stakeholder alignment (practical responses in civil contexts)
Clear, defensible problem-solving writing

Master these patterns, and your exam performance will improve because each new past-paper question becomes a variation of a method you already know how to execute.

Final Note on Exam Preparation Practice (Integrated, Not a Warning)

To prepare specifically for PJM4A11 past-paper style questions, prioritize:

2–3 sets of CPM network questions (calculations + interpretation),
1–2 integrated scenarios combining cost and schedule,
1–2 risk register drafting questions with likelihood/impact scoring,
short theory answers that include a civil engineering example.

If you work through at least a few complete past-paper sets in timed conditions, you’ll develop the speed and accuracy the exam demands—especially in CPM, where one arithmetic slip can affect critical path identification.

End of PJM4A11 Project Management 4A (Civil Engineering) Past Papers — Exam Notes (University of Johannesburg, College of Business & Economics).