Questions 1–5 are multiple choice. Questions 6–7 are short-answer — work through your answer first, then reveal the model response.
Score tracker:0 of 5 multiple choice answered
Part A — Multiple Choice
Q1. What is the primary objective of Schedule Risk Analysis?
Explanation: The primary objective of SRA is to identify, quantify, and communicate the probability that a project will be delayed, and by how much. It produces a statistical distribution of possible completion dates rather than a single deterministic outcome — allowing programme managers to set defensible commitment dates and understand where their greatest risk exposure lies. Cost minimisation, communication planning, and resource assignment are separate disciplines.
Q2. Monte Carlo Simulation is used in SRA for:
Explanation: Monte Carlo simulation uses repeated random sampling — typically tens of thousands of iterations — to generate a statistical distribution of possible project completion dates. Each iteration randomly selects activity durations from their probability distributions, calculates the resulting critical path, and records the project end date. The accumulated results form the S-curve (cumulative probability distribution), which shows the probability of completing by any given date. Monte Carlo does not by itself identify the critical path (CPM does that), calculate budget variance (EVM does that), or develop mitigation plans (risk management does that).
Q3. Which of the following is NOT a technique used in Schedule Risk Analysis?
Explanation: CPM (Critical Path Method) is a deterministic scheduling technique — it calculates a single critical path based on fixed, single-point activity durations. While a valid CPM schedule is the essential foundation for a Monte Carlo SRA, CPM itself is not a risk analysis technique. PERT (Program Evaluation and Review Technique) uses three-point estimates, Sensitivity Analysis ranks which activities most influence the outcome, and Expert Judgment is central to collecting risk data in interviews and workshops — all are genuine SRA techniques. Note: CPM must be used as the underlying schedule model, but the risk analysis is performed on top of it using separate probabilistic methods.
Q4. What is the key difference between Schedule Risk Identification and Schedule Risk Assessment?
Explanation: Risk identification (Step 1 of the QSRA process) is the process of listing all events that could affect the schedule — brainstorming, SME interviews, risk register review. Risk assessment (Steps 2 and following) is the process of quantifying those risks — assigning probabilities of occurrence and impacts on schedule duration, and modelling them in the simulation. The terms are not interchangeable (B is wrong). D is partially true but oversimplified — identification can use quantitative historical data and assessment can involve qualitative expert judgment.
Q5. A project with substantial total float on its near-critical activities is generally considered:
Explanation: Total float acts as a buffer — near-critical activities with significant float can absorb delays without immediately affecting the project's finish date. A schedule with substantial float on near-critical paths is therefore less susceptible to schedule slippage. However, be cautious: merge bias means that when many near-critical paths converge at a milestone, the overall risk is greater than any individual path's float suggests — this is exactly why SRA is valuable even when the schedule appears to have adequate float.
Part B — Short Answer
Work through your answer before revealing the model response.
Q6. A construction project has identified a risk of material delivery delays that could impact several critical path activities. How would you approach this risk using SRA techniques? Briefly explain the steps involved.
Think through the QSRA process — from data collection to mitigation planning.
Model Answer:
1. Identify and document the risk. Add the material delivery delay risk to the project risk register as a named, defined threat. Identify which schedule activities are affected — in this case, all activities that depend on the delayed materials (concrete supply, steel delivery, mechanical equipment, etc.).
2. Quantify the risk (data collection). Interview the relevant SMEs — procurement manager, site superintendent, key subcontractors — to establish: (a) the probability that a material delay will occur, and (b) if it does occur, the range of possible delay duration (optimistic, most likely, pessimistic impact). Conduct interviews without authority figures present to avoid motivational bias.
3. Assign the risk driver to the affected activities. Using the risk driver approach, assign this risk to all affected schedule activities with its probability and impact distribution. This causes the risk to affect all assigned activities simultaneously in any iteration where it fires — naturally modelling the correlation between those activities.
4. Run the Monte Carlo simulation. Execute the simulation (typically 10,000+ iterations). Review the resulting S-curve to understand the probability of the project meeting its current completion date with and without the material delivery risk included.
5. Quantify the risk's contribution and develop mitigation. Remove the material delivery risk from the model and re-run the simulation. The difference in the P80 date between the full model and the model without this risk shows the risk's contribution to required contingency. If the contribution is significant, develop targeted mitigation — securing alternative suppliers, extending procurement lead times, increasing on-site buffer stock — and model the effect of mitigation on the SRA output.
Q7. Discuss the advantages and limitations of using Monte Carlo Simulation for Schedule Risk Analysis.
Aim for at least two advantages and two limitations. Think about data quality, complexity, and interpretation.
Model Answer:
Advantages:
Handles complexity. Monte Carlo can process a full programme schedule with hundreds or thousands of activities, multiple parallel paths, and complex logic — producing a probability distribution that accounts for merge bias and path convergence that simple hand calculations cannot capture.
Quantified confidence levels. Rather than a single deterministic date (which implies false precision), Monte Carlo delivers a range of possible outcomes with associated probabilities. Programme managers can select a commitment date at their preferred level of confidence (P70, P80, etc.).
Tests multiple scenarios simultaneously. By running thousands of iterations, Monte Carlo explores a far broader range of scenarios than any deterministic sensitivity analysis.
Supports prioritisation. Risk criticality indices and Tornado charts — derived from the simulation — identify which activities and risks contribute most to schedule overrun, enabling targeted mitigation.
Limitations:
Output quality is entirely data-dependent. Biased, inconsistent, or arbitrary input data produces misleading outputs. If interviewees provide compressed ranges due to motivational bias, the simulation will understate risk — creating false confidence.
Requires a valid, high-quality schedule model. If the underlying CPM schedule has poor logic, excessive constraints, or incomplete activities, the simulation will produce incorrect results. A flawed schedule produces a flawed risk model.
Complexity of interpretation. The S-curve, Tornado chart, and sensitivity indices are not self-explanatory to non-specialists. Misinterpretation of results by decision makers — particularly treating P50 as a safe commitment date — is a real risk.
Does not predict the future. Monte Carlo reflects only the risks and uncertainties that were identified and quantified. Events outside the model — unknown unknowns — are not captured. The results should be treated as inputs to decision-making, not as forecasts of how the project will actually unfold.
Module 6 — Quick Reference
P50
50% confidence — project likely as not to finish by this date. Not a commitment date.
P80
80% confidence — the common benchmark for infrastructure programme commitments.
Merge Bias
CPM underestimates programme duration because parallel paths converge — any path can slip and delay the merge event.
Contingency
P80 date − deterministic finish date. Held as a single activity before the finish milestone.