CELE Construction Management & Methods — Project Planning and Scheduling (CPM/PERT)Misconception Buster
Avoid the most common Project Planning and Scheduling (CPM/PERT) mistakes made by CELE reviewers. Each misconception here has been pulled from real CELE Construction Management & Methods questions where Professional Regulation Commission (PRC) — Board of Civil Engineering used it to separate strong reviewers from weak ones. Learn these before your next mock.
Exam context
The Civil Engineer Licensure Examination is conducted by Professional Regulation Commission (PRC) — Board of Civil Engineering and is scheduled for May and November 2026. The Construction Management & Methods subtest is marked as "Core" in the official pattern, and Project Planning and Scheduling (CPM/PERT) appears in position 2nd of 5 in the CELE Construction Management & Methods review rotation. Passing mark: 70% weighted average, no sub-test below 50%. Recent CELE 2026 papers have drawn roughly a meaningful share of questions from this subject.
Project Planning and Scheduling (CPM/PERT) - Misconception Buster
In the PRC Civil Engineer Licensure Examination, CPM/PERT problems are among the most frequently tested topics in Construction Management and Methods. These problems appear deceptively straightforward, yet a majority of examinees lose marks not because they lack knowledge, but because they carry specific misconceptions that lead them to choose the wrong answer confidently. This guide identifies the exact wrong beliefs that trip up Filipino CE reviewees — from confusing the critical path with the shortest path, to misapplying the PERT formula weights, to mixing up total float and free float. Each misconception is paired with a trap question modeled after actual board-exam style questions. Mastering where you go wrong is just as important as mastering what is correct. Study each item carefully: if you would have chosen the 'wrong answer' for any trap question, that misconception needs your immediate attention before exam day.
Summary
The most exam-critical misconceptions in CPM/PERT can be grouped into four categories. First: the critical path is ALWAYS the longest path — never the shortest. This single error invalidates all float, duration, and crash calculations. Second: PERT uses a weighted average t_e = (a + 4m + b)/6, not a simple mean; project variance sums ONLY critical path activity variances; and standard deviations are NEVER directly addable — always sum variances first, then take the square root. Third: the forward pass uses MAX (not min) of predecessor EF values for each activity's ES, while the backward pass uses MIN (not max) of successor LS values for each activity's LF — these max/min rules are mirror images of each other and both are commonly reversed by examinees. Fourth: float has two distinct definitions — total float concerns the project deadline while free float concerns the immediate successor — and these give different numerical values; zero float means criticality, not delay. Finally, for crashing: only critical path activities matter, but the critical path can SHIFT after each crash iteration, requiring re-evaluation at every step. Mastering these eight specific points — longest path, PERT weights, variance summation, variance (not σ) summation, max for forward pass, min for backward pass, two types of float, and path shifting in crashing — will eliminate the majority of avoidable errors in CPM/PERT board examination questions.
Misconceptions
The critical path is the SHORTEST path through the network.
Tags
- conceptual_gap
- common_error
- critical_path
Topic
Critical Path Identification
Severity
critical
Exam Impact
Students who hold this misconception will identify the wrong path as critical, compute the wrong project duration, and assign zero float to the wrong activities — resulting in multiple wrong answers from a single flawed premise. This can cost 3–5 marks in a single problem set.
The Reality
The critical path is the LONGEST path (in duration) through the network. It determines the minimum project completion time. A project cannot finish earlier than its longest chain of dependent activities. Shortening any non-critical path has zero effect on project duration; only shortening the critical path reduces the project duration. This is the fundamental theorem of CPM.
Trap Question
Question
A project network has three paths: Path X = 10 days, Path Y = 14 days, Path Z = 11 days. What is the minimum project duration and which path is critical?
Explanation
The minimum project duration equals the duration of the longest path. All activities on Path Y must be completed sequentially with no flexibility; they have zero float. Path X has 14 - 10 = 4 days float; Path Z has 14 - 11 = 3 days float. Shortening Path X or Z does nothing to the project finish date.
Wrong Answer
The project duration is 10 days and Path X is critical because it is the shortest (most restrictive) route.
Correct Answer
The project duration is 14 days and Path Y is critical because it is the LONGEST path.
Misconception Id
M1
Correct Vs Incorrect
Correct Approach
The critical path is Path B = 12 days because it is the LONGEST path. The project cannot complete in less than 12 days regardless of how fast Path A is completed. Path A has 12 - 8 = 4 days of float.
Incorrect Approach
Network has Path A = 8 days and Path B = 12 days. Student selects Path A (8 days) as critical because it is the 'fastest' route and assumes 'critical' means time-sensitive.
Why Students Believe It
Students confuse 'critical' with 'urgent' or 'fast'. They reason that the shortest path is the most efficient route, and since critical activities are urgent, the shortest path must be critical. This is a linguistic trap — the word 'critical' does not mean 'shortest' in project scheduling.
In the PERT formula, all three time estimates (a, m, b) are weighted equally, so t_e = (a + m + b) / 3.
Tags
- formula_confusion
- common_error
- PERT
Topic
PERT Expected Duration
Severity
critical
Exam Impact
Every PERT expected duration question will be answered incorrectly. Since t_e feeds into project duration and probability calculations, all downstream computations are also wrong. This single misconception can cascade into multiple wrong answers.
The Reality
The PERT expected time formula is t_e = (a + 4m + b) / 6, which is a weighted beta-distribution approximation. The most likely estimate m is given weight 4, while a and b are each given weight 1, for a total weight of 6. This reflects the reality that project durations tend to cluster near the most likely estimate. Using (a+m+b)/3 will almost always give a different (wrong) answer.
Trap Question
Question
An activity in a building construction project has optimistic duration a = 3 days, most likely duration m = 6 days, and pessimistic duration b = 15 days. What is the PERT expected duration?
Explanation
The PERT formula weights the most likely duration m by a factor of 4 because the beta distribution used in PERT places greater probability mass near the mode. The denominator is 6 (= 1 + 4 + 1). The simple average of 8 is incorrect and does not appear as an answer choice in well-written board exams — but (3+4×6+15)/6 = 7 does.
Wrong Answer
t_e = (3 + 6 + 15) / 3 = 8 days
Correct Answer
t_e = (3 + 4×6 + 15) / 6 = (3 + 24 + 15) / 6 = 42 / 6 = 7 days
Misconception Id
M2
Correct Vs Incorrect
Correct Approach
t_e = (a + 4m + b) / 6 = (4 + 4×6 + 14) / 6 = (4 + 24 + 14) / 6 = 42 / 6 = 7 days. The most likely estimate m = 6 gets weight 4; the denominator is 6, not 3.
Incorrect Approach
a = 4, m = 6, b = 14. Student computes t_e = (4 + 6 + 14) / 3 = 24 / 3 = 8 days.
Why Students Believe It
Students recall that PERT uses three estimates and instinctively apply a simple arithmetic mean. The formula (a + m + b)/3 looks like a standard average and feels mathematically natural. Many students memorize 'average of three estimates' without memorizing the specific weights.
Total float and free float are the same thing.
Tags
- conceptual_gap
- formula_confusion
- float
Topic
Float Analysis
Severity
major
Exam Impact
Questions specifically asking for 'free float' will be answered with TF values and vice versa. Since FF ≤ TF, the numerical answers differ and wrong choices will be selected.
The Reality
Total Float (TF) = LS - ES = LF - EF: how much an activity can be delayed without delaying the ENTIRE PROJECT. Free Float (FF): how much an activity can be delayed without delaying any of its IMMEDIATE SUCCESSORS. FF ≤ TF always. An activity can have large TF but zero FF (meaning it can slide within the project without harm, but if delayed even slightly, its successor is impacted). These are different questions: TF asks about the project; FF asks about the next activity.
Trap Question
Question
Activity E has ES = 6, EF = 9, LS = 11, LF = 14. Its only successor, Activity F, has ES = 10. What is the free float of Activity E?
Explanation
Total float of Activity E = LF - EF = 14 - 9 = 5 days (or LS - ES = 11 - 6 = 5 days). But free float measures how much E can slip before hitting its successor F. Since F starts at day 10 and E currently finishes at day 9, E has only 1 free day. Using TF = 5 as the free float would be wrong.
Wrong Answer
Free float = LS - ES = 11 - 6 = 5 days (same as total float)
Correct Answer
Free float = ES(F) - EF(E) = 10 - 9 = 1 day
Misconception Id
M3
Correct Vs Incorrect
Correct Approach
TF = LS - ES (uses late start of the activity itself). FF = ES(successor) - EF(current activity). These formulas reference different endpoints. TF concerns the project end; FF concerns the successor's early start. The values will often differ.
Incorrect Approach
Student reads 'what is the float of Activity D?' and computes TF = LS - ES = 5 days. When asked 'what is the free float of Activity D?' they again answer 5 days, treating both as identical.
Why Students Believe It
Both are called 'float' and both measure scheduling flexibility. Students who have not deeply studied network scheduling treat them as synonyms or assume one is just a subset abbreviation of the other. Textbooks that briefly introduce float without contrasting examples reinforce this confusion.
Activities NOT on the critical path can be ignored or delayed indefinitely without risk.
Tags
- conceptual_gap
- common_error
- float
Topic
Float and Project Impact
Severity
major
Exam Impact
Students make errors in crashing problems by continuing to crash activities on the original critical path after a path shift, and in resource leveling by incorrectly extending non-critical activities beyond their float limits.
The Reality
Non-critical activities can only be delayed up to their total float value. Delaying beyond TF extends the project. Furthermore, if resources are shared among activities, delaying non-critical activities can starve critical activities of resources. Also, crashing the critical path can cause the critical path to shift — what was non-critical becomes critical — and students must re-check float after every crash iteration.
Trap Question
Question
A project has a critical path duration of 20 days. Activity G is not on the critical path and has a total float of 4 days. If Activity G is delayed by 6 days due to material delivery problems, what is the new project duration?
Explanation
Float is the maximum allowable delay without affecting the project. Any delay beyond TF = 4 days directly extends the project. A 6-day delay = 4-day float consumed + 2-day overrun. The new project duration = 20 + 2 = 22 days. The path containing Activity G is now critical (TF = 0).
Wrong Answer
Still 20 days, because Activity G is not on the critical path.
Correct Answer
22 days. The delay of 6 days exceeds the float of 4 days by 2 days, extending the project by 2 days.
Misconception Id
M4
Correct Vs Incorrect
Correct Approach
The activity can only be delayed by exactly 3 days (its total float). Delaying it by 5 days means it exceeds its float by 2 days, which will delay the project by 2 days and make this activity (or its path) part of the new critical path.
Incorrect Approach
Project has critical path = 15 days. A non-critical activity has TF = 3 days. Student assumes this activity can be delayed by 5 days without problem since it is 'non-critical'.
Why Students Believe It
Students reason that since critical path activities have zero float and non-critical activities have some float, non-critical activities are 'safe' and can always be pushed back. They forget that float has a finite value and that delaying beyond the total float converts a non-critical path into a new critical path.
Crashing any activity on the critical path by 1 day always reduces the project duration by 1 day.
Tags
- common_error
- crashing
- multi-path
Topic
Crashing and Time-Cost Trade-off
Severity
major
Exam Impact
Students will continue crashing along the original critical path past the point where another path becomes critical, computing wrong time savings and wrong crash costs. Multi-path crashing problems will be entirely miscalculated.
The Reality
After one or more crashing iterations, the critical path may shift — a previously non-critical path becomes critical (or co-critical). Once two or more paths are simultaneously critical, you must crash activities that are on ALL critical paths simultaneously to gain further project time reduction. Crashing only one path when multiple paths are critical yields 0 days of project savings, not 1 day.
Trap Question
Question
A project has two paths: Path 1 (A-C) = 14 days, Path 2 (B-C) = 12 days. Activity A can be crashed at Php 5,000/day, Activity B at Php 4,000/day, Activity C at Php 8,000/day. What is the minimum cost to reduce the project by 2 days?
Explanation
After the first crash of A, the critical path shifts. Students who do not re-evaluate after each crash step will make errors in multi-step crashing. The key insight is: once two paths are co-critical, an activity that belongs to only one path cannot shorten the project.
Wrong Answer
Crash Activity A by 2 days = 2 × Php 5,000 = Php 10,000. Project goes from 14 to 12 days.
Correct Answer
Crash A by 1 day (cost Php 5,000): Path 1 = 13 days, Path 2 = 12 days. Project = 13 days. Then both paths: crash A again (Path 1 = 12) OR crash C (affects both paths). Crash A again by 1 day (cost Php 5,000): Path 1 = 12, Path 2 = 12, project = 12 days. Total cost = Php 10,000. Project is now 12 days, a reduction of 2 days. But verify: if we crash C instead after first step, cost = Php 8,000 and project goes to 12 days in one more crash. Total = Php 5,000 + Php 8,000 = Php 13,000 > Php 10,000. Optimal: crash A twice = Php 10,000.
Misconception Id
M5
Correct Vs Incorrect
Correct Approach
After crashing A by 1 day: A-C = 11 days = B-C = 11 days. Both paths are now critical. To crash further, you must crash Activity C (common to both) or crash both A and B simultaneously. Crashing only A further gives A-C = 10 days but the project is still 11 days (B-C controls).
Incorrect Approach
Original critical path A-C = 12 days. Non-critical path B-C = 11 days (float = 1 day). Student crashes Activity A by 2 days (A-C becomes 10 days), then concludes the project is now 10 days without realizing Path B-C = 11 days is now longer.
Why Students Believe It
Students correctly understand that shortening the critical path shortens the project. They then incorrectly generalize this to mean that every 1-day crash always yields exactly 1 day of project time savings, regardless of how many iterations of crashing have been performed.
The PERT project variance equals the SUM of variances of ALL activities in the network.
Tags
- formula_confusion
- PERT
- variance
Topic
PERT Variance and Probability
Severity
major
Exam Impact
Students will include non-critical path activity variances and compute an inflated project standard deviation. This leads to wrong Z-values and wrong probability-of-completion answers.
The Reality
The project duration variance in PERT is the sum of variances of activities ON THE CRITICAL PATH only. Non-critical path activities are not included because the project duration is determined solely by the critical path. Using all activity variances will overestimate project uncertainty and give a wrong standard deviation.
Trap Question
Question
A PERT network's critical path passes through Activities P, Q, R with variances 1, 4, and 1 respectively. Activity S (non-critical) has variance 9. What is the standard deviation of the project duration?
Explanation
Project duration variance in PERT = sum of variances of CRITICAL PATH activities only = 1 + 4 + 1 = 6. Activity S is non-critical and is excluded. σ = √6 ≈ 2.45 days. Including Activity S gives the wrong answer of 3.87 days.
Wrong Answer
σ = √(1 + 4 + 1 + 9) = √15 = 3.87 days
Correct Answer
σ = √(1 + 4 + 1) = √6 = 2.45 days
Misconception Id
M6
Correct Vs Incorrect
Correct Approach
Only critical path variances are summed: project variance = 4 + 1 + 4 = 9. Project standard deviation σ = √9 = 3 days. The non-critical activity variance of 2 is excluded.
Incorrect Approach
Network has critical path activities with variances 4, 1, 4 and non-critical activity with variance 2. Student computes project variance = 4 + 1 + 4 + 2 = 11, project σ = √11 = 3.32 days.
Why Students Believe It
Students hear 'sum the variances' and apply it globally to all activities without restriction. It seems logical that all activities contribute to overall project uncertainty. Some textbooks present the formula without clearly stating the restriction to the critical path only.
The Late Finish (LF) of the last activity always equals the Early Finish (EF) of the last activity.
Tags
- conceptual_gap
- backward_pass
- imposed_dates
Topic
Backward Pass and Late Times
Severity
minor
Exam Impact
Problems specifying a contractual deadline or imposed finish date will be miscalculated if students default to LF = EF without reading problem conditions carefully.
The Reality
By default in CPM, we set LF of the terminal activity equal to EF (the calculated project duration). This means the project is set to be completed exactly at the earliest possible time — a standard assumption for network analysis. However, if a problem specifies a DEADLINE different from the computed project duration, the LF of the last activity is set to that deadline, not EF. This changes all LS/LF values and float calculations throughout the network.
Trap Question
Question
A project's forward pass gives a project EF = 22 days. The client contract specifies completion within 25 days. What is the Late Finish (LF) assigned to the terminal activity for the backward pass?
Explanation
When a problem imposes a target or deadline different from the computed project duration, the backward pass starts at that deadline. Setting LF = 25 means all critical path activities will have TF = 25 - 22 = 3 days, not zero. The network still has a 'critical path' (the longest path), but all activities have some float relative to the imposed date.
Wrong Answer
LF = 22 days (equal to EF, since the project ends at day 22)
Correct Answer
LF = 25 days (the contractual deadline as specified by the problem)
Misconception Id
M7
Correct Vs Incorrect
Correct Approach
LF of last activity = 18 days (the imposed deadline). Backward pass uses LF = 18 as the starting point. All activities now have positive float (minimum TF = 3 days for critical path activities). The project has 3 days of total float built in.
Incorrect Approach
Problem states 'the contract requires completion in 18 days' and the computed project duration (EF of last node) = 15 days. Student sets LF of last activity = 15 (EF) and proceeds with backward pass.
Why Students Believe It
Students assume that in a proper network, the project is always planned to finish exactly on time, so LF = EF at the project end. This is true only when the project target date equals the calculated project duration — which is the default assumption but may not always hold in exam problems that set a different target date.
An activity with zero float is always causing a problem or delay in the project.
Tags
- conceptual_gap
- float
- interpretation
Topic
Critical Path and Float Interpretation
Severity
minor
Exam Impact
Conceptual questions about the meaning of zero float and what critical path activities imply will be answered incorrectly. Students may also misinterpret scenario questions about project status.
The Reality
Zero total float simply means the activity is ON the critical path — it must start and finish exactly on schedule for the project to complete on time. Zero float is the NORMAL condition for critical path activities; it does not indicate a delay has occurred or that there is a problem. It is a planning state, not an alarm condition. An activity has zero float because of where it sits in the network, not because anything has gone wrong.
Trap Question
Question
A project manager reviewing the CPM schedule notes that Activity L has a total float of 0 days. What does this definitively indicate?
Explanation
Total float = 0 is the defining characteristic of a critical path activity in a planned schedule. It indicates scheduling sensitivity, not an existing delay. Delays are determined by comparing actual progress against the schedule, not by reading float values from the original plan.
Wrong Answer
Activity L is currently delayed and is the cause of project schedule slippage.
Correct Answer
Activity L is on the critical path and must be completed on schedule; any delay in Activity L will directly delay the project completion date.
Misconception Id
M8
Correct Vs Incorrect
Correct Approach
Activity K has TF = 0, which means it is on the critical path. This is a planning characteristic, not an operational problem. It means Activity K must be completed on schedule; any delay in K will delay the project. No delay has necessarily occurred yet.
Incorrect Approach
Student reads 'Activity K has TF = 0' and answers 'Activity K is currently delayed and is causing a project delay.' They interpret zero float as evidence of an ongoing problem.
Why Students Believe It
Zero sounds like 'nothing left' or 'no room', which students associate with a problem or deficit. The word 'float' sounds like spare time, so zero float = no spare time = something is wrong or delayed.
In the forward pass, an activity's Early Start (ES) equals the EF of any ONE of its predecessors (whichever finishes first).
Tags
- formula_confusion
- common_error
- forward_pass
Topic
Forward Pass — Multiple Predecessors
Severity
critical
Exam Impact
The entire forward pass and all EF, LS, LF, TF values will be wrong for any activity that has multiple predecessors. This cascades through the entire network calculation.
The Reality
In a finish-to-start dependency network (standard CPM), an activity can only start when ALL of its predecessors have finished. Therefore, the ES of an activity = the MAXIMUM EF among all of its predecessors. Using the minimum EF (earliest finishing predecessor) will give an ES that is too early, causing all downstream times to be wrong.
Trap Question
Question
Activity F has three predecessors: Activity P (EF = 5 days), Activity Q (EF = 9 days), Activity R (EF = 7 days). Activity F has a duration of 4 days. What is the Early Finish (EF) of Activity F?
Explanation
Activity F requires all three predecessors to be complete. The last predecessor to finish is Activity Q at day 9. Therefore ES(F) = 9. EF(F) = ES + duration = 9 + 4 = 13 days. Using the minimum EF (5 days) would mean starting Activity F before Activities Q and R are done — a logical impossibility in a standard finish-to-start dependency.
Wrong Answer
ES(F) = min(5, 9, 7) = 5; EF(F) = 5 + 4 = 9 days
Correct Answer
ES(F) = max(5, 9, 7) = 9; EF(F) = 9 + 4 = 13 days
Misconception Id
M9
Correct Vs Incorrect
Correct Approach
ES(D) = max(EF of all predecessors) = max(8, 12) = 12 days. Activity D cannot begin until BOTH Activity B and Activity C are complete. Using ES = 8 is wrong because Activity C has not finished yet.
Incorrect Approach
Activity D has two predecessors: Activity B (EF = 8) and Activity C (EF = 12). Student sets ES(D) = 8 (the minimum EF, 'as soon as the first predecessor finishes').
Why Students Believe It
Students think that as soon as any predecessor finishes, the successor can start. This seems logical — why wait for the last predecessor if an earlier one already finished? In resource terms, this might even seem efficient.
In the backward pass, an activity's Late Finish (LF) equals the LS of any ONE of its successors (whichever starts latest).
Tags
- formula_confusion
- common_error
- backward_pass
Topic
Backward Pass — Multiple Successors
Severity
critical
Exam Impact
All LF, LS, and TF values for activities with multiple successors will be wrong. Float values will be overestimated, causing some critical activities to appear non-critical.
The Reality
In the backward pass, an activity's LF = the MINIMUM LS among all of its successors. This is because the activity must be done before ALL of its successors can begin. Using the maximum LS would incorrectly allow the activity to finish later than at least one successor needs it to — a logical impossibility.
Trap Question
Question
Activity T has a duration of 5 days. It has two successors: Activity U with LS = 18 days and Activity V with LS = 15 days. What is the Late Start (LS) of Activity T?
Explanation
Activity T feeds into both U and V. V needs T done by day 15 at the latest. Even though U can tolerate T finishing as late as day 18, V cannot. Therefore LF(T) = 15 (the most restrictive constraint). LS(T) = 15 - 5 = 10 days. Using max(18,15) = 18 would incorrectly allow T to run until day 18, violating Activity V's start constraint.
Wrong Answer
LF(T) = max(18, 15) = 18; LS(T) = LF - duration = 18 - 5 = 13 days
Correct Answer
LF(T) = min(18, 15) = 15; LS(T) = 15 - 5 = 10 days
Misconception Id
M10
Correct Vs Incorrect
Correct Approach
LF(M) = min(LS of all successors) = min(14, 10) = 10 days. Activity M must complete before Activity Y starts at day 10 — it cannot extend to day 14, even though Activity X doesn't need it until day 14.
Incorrect Approach
Activity M has two successors: Activity X (LS = 14) and Activity Y (LS = 10). Student sets LF(M) = max(14, 10) = 14 days (thinking 'the latest start gives the most time').
Why Students Believe It
This is the mirror-image error of M9. Students apply the wrong direction of comparison. Since the backward pass goes from end to start, students sometimes take the maximum LS of successors instead of the minimum.
The PERT standard deviation formula is σ = (b - a) / 6, and this is the PROJECT standard deviation.
Tags
- formula_confusion
- PERT
- statistics
Topic
PERT Project Standard Deviation
Severity
major
Exam Impact
Students will either skip the variance-summing step and incorrectly add standard deviations directly (wrong), or they will apply (b-a)/6 once using total project range values (wrong). Both produce incorrect project σ values.
The Reality
σ_activity = (b - a) / 6 is for ONE activity only. The PROJECT standard deviation is computed by: (1) finding σ² for each critical path activity using [(b - a)/6]², (2) summing all critical path variances: σ²_project = Σσ²_i, and (3) taking the square root: σ_project = √(Σσ²_i). Standard deviations are NOT directly addable — variances are addable.
Trap Question
Question
A project's critical path has four activities with standard deviations of 1, 2, 1, and 2 days respectively. What is the standard deviation of the project duration?
Explanation
Standard deviations are NOT additive. You must first square each σ to get variance, sum the variances, then take the square root. √10 ≈ 3.16 days. Adding the σ values directly (6 days) is a fundamental statistical error that will always overestimate the project uncertainty.
Wrong Answer
σ_project = 1 + 2 + 1 + 2 = 6 days
Correct Answer
σ_project = √(1² + 2² + 1² + 2²) = √(1 + 4 + 1 + 4) = √10 = 3.16 days
Misconception Id
M11
Correct Vs Incorrect
Correct Approach
σ² for each = 2² = 4. Sum of variances = 4 + 4 + 4 = 12. σ_project = √12 = 3.46 days. Always sum VARIANCES, then take the square root.
Incorrect Approach
Three critical path activities each have σ = 2 days. Student adds: σ_project = 2 + 2 + 2 = 6 days. This is WRONG — standard deviations cannot be directly added.
Why Students Believe It
Students correctly memorize σ = (b - a) / 6 but forget this formula gives the standard deviation of a SINGLE activity, not the whole project. When asked for the project standard deviation, they directly apply this formula using the overall project's a and b values (if given) instead of computing individual activity variances and summing them along the critical path.
A network with more activities always has a longer project duration than one with fewer activities.
Tags
- conceptual_gap
- network_logic
- parallel_activities
Topic
Network Fundamentals and Project Duration
Severity
minor
Exam Impact
Conceptual questions about project duration and network characteristics will be answered incorrectly. Students may misjudge the impact of adding or removing activities from a project plan.
The Reality
Project duration depends only on the LENGTH of the critical path, not the total number of activities. Many activities can be executed in parallel. A project with 20 activities where 15 are parallel to the critical path may have a shorter duration than a simpler-looking project with 8 activities all in series. Adding parallel non-critical activities does not increase project duration; it may even provide resource flexibility.
Trap Question
Question
Project X has 6 activities all in series with durations 2, 3, 2, 4, 3, 2 days. Project Y has 15 activities, with a critical path of 3 activities each taking 5 days, and the remaining 12 activities all running in parallel with the critical path. Which project has the longer duration?
Explanation
Project duration = critical path length. Project X has all 6 activities in series: 16 days. Project Y's critical path has only 3 activities × 5 days = 15 days. Despite having 15 activities, Project Y finishes faster because most activities run concurrently. More activities ≠ longer duration.
Wrong Answer
Project Y, because it has more activities (15 vs 6).
Correct Answer
Project X has duration = 2+3+2+4+3+2 = 16 days. Project Y duration = 5+5+5 = 15 days. Project X has the LONGER duration.
Misconception Id
M12
Correct Vs Incorrect
Correct Approach
Project A duration = 15 days (all series). Project B duration = 9 days (only the critical path A→B matters; the 10 parallel activities do not extend it). Project B is SHORTER despite having more activities.
Incorrect Approach
Project A has 5 activities all in series: each 3 days = 15 days total. Project B has 12 activities but 10 run in parallel with the critical path of A(4) → B(5) = 9 days. Student assumes Project B is longer because it has more activities.
Why Students Believe It
Students intuitively think more work = more time. If a project has 20 activities and another has 8, the 20-activity project must take longer. This common-sense reasoning ignores the role of parallel execution in project networks.
Quick Self Check
The critical path is the LONGEST path. Its length equals the minimum project duration. All critical path activities have zero total float.
Statement
The critical path is the path with the shortest total duration in a project network.
This is the correct PERT beta-distribution weighted average formula. The most likely estimate m receives weight 4; the optimistic a and pessimistic b each receive weight 1; the denominator is 6.
Statement
The PERT expected duration formula is t_e = (a + 4m + b) / 6, where m is the most likely estimate.
Free Float ≤ Total Float always. Total Float measures slack relative to the project end; Free Float measures slack relative to the successor's early start. The project-level constraint is always at least as restrictive as the successor-level constraint.
Statement
An activity's Free Float can be greater than its Total Float.
Only the variances of critical path activities are summed. Non-critical path activities do not determine project duration and are excluded from the project variance calculation.
Statement
The project variance in PERT is computed by summing the variances of ALL activities in the network.
In a standard finish-to-start network, all predecessors must be complete before a successor can begin. Therefore ES = max(EF of all predecessors) — the activity waits for the LAST predecessor to finish.
Statement
When an activity has multiple predecessors, its Early Start equals the maximum Early Finish among all predecessors.
Standard deviations are NOT directly additive. You must sum VARIANCES (σ²), then take the square root of the total variance. Directly adding σ values overestimates project uncertainty.
Statement
Standard deviations of critical path activities can be directly summed to obtain the project standard deviation.
Only activities on the critical path control project duration. Crashing non-critical path activities shortens those paths but has no effect on project duration unless those paths become the new critical path.
Statement
Crashing an activity on a non-critical path is an effective way to reduce the project duration.
Zero total float means the activity is on the critical path and has no scheduling flexibility. It does not indicate an existing delay — it is a planned characteristic of critical path activities. Delays are assessed by comparing actual progress against the baseline schedule.
Statement
An activity with zero total float is always experiencing a delay.
Previous chapter
Construction Estimates and Quantity Surveying
Next chapter
Construction Methods, Equipment and Operations
Ready to practise for the CELE 2026?
Super Tutor's AI review plan adapts to your weak areas and builds a weekly practice schedule around your target CELE exam date.