9.1 Project Scheduling, Network Analysis & Resource Management

Project Scheduling, Network Analysis & Resource Management

Capital expenditure projects and strategic transformations—such as enterprise software deployments, production line automations, and corporate reorganizations—represent major commitments of enterprise capital. For the strategic management accountant, project governance extends far beyond passive cost logging. It requires active participation in scheduling, network dependency analysis, critical path determination, and resource optimization to safeguard return on invested capital.

Flawed scheduling leads to schedule slippage, penalty clauses, opportunity costs from delayed commercial launches, and budget blowouts. Management accountants must therefore understand the quantitative tools that govern project duration, identify operational bottlenecks, and evaluate the financial trade-offs between project time and total cost.

---

The Work Breakdown Structure (WBS)

The foundation of all project scheduling, budgeting, and control is the Work Breakdown Structure (WBS). The WBS is a deliverable-oriented hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish project objectives and create required deliverables.

The 100% Rule

A foundational axiom of WBS design is the 100% Rule, which stipulates that the WBS must capture 100% of the scope defined by the project charter and approved specifications—including project management, testing, and regulatory documentation—and nothing more. The sum of work at each subordinate level must roll up precisely to 100% of the parent deliverable without overlap or omission.

Key Structural Components

• Control Accounts: Management control points positioned above work packages where scope, budget (Planned Value), and actual costs are integrated and compared against earned value for performance measurement.
• Work Packages: The lowest level of the WBS hierarchy. A work package represents a discrete deliverable with an identifiable owner, an estimated duration, and an assignable cost budget. As a standard rule of thumb, work packages should follow the "8/80 rule" (requiring no fewer than 8 hours and no more than 80 hours of effort) to ensure governance without micromanagement.
• WBS Dictionary: A detailed repository providing operational descriptions of each work package, including milestone dates, resource requirements, quality acceptance criteria, prerequisites, and cost account codes.

---

Project Scheduling Tools: Gantt Charts vs Network Diagrams

Once work packages are decomposed into discrete activities, project controllers construct scheduling models using two primary visual and analytical tools:

---

Critical Path Method (CPM) and Activity-on-Node (AON) Analysis

The Critical Path Method (CPM) is a deterministic scheduling algorithm that identifies the sequence of dependent activities determining the absolute minimum total project duration. In contemporary project management, CPM is modeled using the Activity-on-Node (AON) convention, where each node displays six fundamental scheduling values:

1. Early Start ($ES$): The earliest calendar point an activity can commence, given predecessor completions.
2. Early Finish ($EF$): The earliest calendar point an activity can complete ($EF = ES + \text{Duration}$).
3. Late Start ($LS$): The latest calendar point an activity can commence without delaying the total project deadline.
4. Late Finish ($LF$): The latest calendar point an activity can complete without delaying the total project deadline ($LS = LF - \text{Duration}$).
5. Activity Duration ($D$): Estimated working time required.
6. Total Float ($TF$): Permissible delay buffer.

Forward Pass Algorithm (Earliest Times)

The forward pass moves from project start to finish to establish the earliest possible timings:

• For the initial activity: $ES = 0$.
• For all subsequent activities: $ES = \max(EF_{\text{immediate predecessors}})$.
• For every activity: $EF = ES + D$.

Backward Pass Algorithm (Latest Times)

The backward pass moves from project completion back to the start to determine latest permissible timings:

• For the final activity: $LF = EF_{\text{project completion}}$.
• For all preceding activities: $LF = \min(LS_{\text{immediate successors}})$.
• For every activity: $LS = LF - D$.

The Critical Path

The Critical Path is the continuous chain of dependent activities connecting project initiation to completion that has the longest aggregate duration. Crucially:

• Activities on the critical path possess zero Total Float ($TF = 0$).
• Any delay in a critical path activity causes a day-for-day delay in final project completion.
• A project may have multiple critical paths of equal duration, which increases exposure to delay across more activities.

---

Float Analysis: Total Float vs Free Float

Float (or slack) represents the scheduling flexibility inherent in non-critical activities. Strategic management accountants distinguish rigorously between two types of float:

$$\text{Total Float (TF)} = LS - ES = LF - EF$$ $$\text{Free Float (FF)} = \min(ES_{\text{immediate successors}}) - EF$$

---

Program Evaluation and Review Technique (PERT)

While CPM is deterministic (assuming fixed durations), capital projects frequently face high technological or operational uncertainty. The Program Evaluation and Review Technique (PERT) addresses this by adopting a three-point probabilistic beta distribution for activity durations:

1. Optimistic Time ($o$): Minimum duration under ideal conditions.
2. Most Likely Time ($m$): Best estimate under normal operating circumstances.
3. Pessimistic Time ($p$): Maximum duration under adverse conditions (excluding extraordinary catastrophes).

Expected Duration and Variance Formulas

$$\mu = \frac{o + 4m + p}{6}$$ $$\sigma = \frac{p - o}{6}$$ $$\sigma^2 = \left(\frac{p - o}{6}\right)^2$$

Critical Path Aggregation & Central Limit Theorem

Under a simplifying approximation with independent activity durations and a fixed controlling path, the sum of expected durations along the critical path approximates a normal distribution. The overall project expected duration ($\mu_{\text{proj}}$) and variance ($\sigma_{\text{proj}}^2$) equal the sum of critical path values:

$$\mu_{\text{proj}} = \sum_{i \in \text{Critical}} \mu_i$$ $$\sigma_{\text{proj}}^2 = \sum_{i \in \text{Critical}} \sigma_i^2$$ $$\sigma_{\text{proj}} = \sqrt{\sigma_{\text{proj}}^2}$$

To calculate the probability of completing the project within a target deadline ($T$), compute the standard normal Z-score:

$$Z = \frac{T - \mu_{\text{proj}}}{\sigma_{\text{proj}}}$$

---

Resource Optimization: Leveling vs Crashing

Project managers must reconcile CPM network logic with finite labor, equipment, and cash resources.

Resource Loading and Resource Leveling

• Resource Loading: Tabulating the required quantities of specific labor, machinery, or technical skills across each calendar time period.
• Resource Smoothing and Leveling: Smoothing shifts activities within available float while preserving the completion date. Leveling changes activity dates to respect resource limits and may extend completion or change the critical path.

Project Crashing Economics

When commercial pressures dictate accelerating a project, management evaluates project crashing—shortening critical activity durations by deploying additional capital, overtime, or secondary equipment. Strategic management accounting evaluates crashing strictly through incremental cost-benefit analysis:

$$\text{Crash Cost per Unit Time} = \frac{\text{Crash Cost} - \text{Normal Cost}}{\text{Normal Time} - \text{Crash Time}}$$

Economic Crashing Principles:

1. Crash only critical path activities. Shortening a non-critical activity spends capital without reducing project duration.
2. Select the critical activity with the lowest crash cost per unit time.
3. Monitor secondary critical paths. As the critical path is compressed, non-critical paths will eventually become critical, requiring simultaneous crashing across multiple parallel paths.
4. Fast-Tracking Alternative: Overlapping sequential activities (e.g., commencing software coding before design sign-off). Fast-tracking may avoid the planned extra resource cost of crashing, but can add coordination costs and rework risk; it is not guaranteed to be free.

---

Corporate Application: Australasian Supply Chains Ltd (ASC)

Australasian Supply Chains Ltd (ASC) is constructing an automated regional fulfillment center with an approved baseline deadline of 28 weeks. The strategic management accountant evaluated the following 7 activities:

Forward and Backward Pass Network Computation

• Path 1 (Hardware): A $\rightarrow$ B $\rightarrow$ D $\rightarrow$ F $\rightarrow$ G = $4 + 6 + 5 + 4 + 3 = 22$ weeks.
• Path 2 (Software): A $\rightarrow$ C $\rightarrow$ E $\rightarrow$ F $\rightarrow$ G = $4 + 8 + 7 + 4 + 3 = 26$ weeks.

The Critical Path is Path 2 (A $\rightarrow$ C $\rightarrow$ E $\rightarrow$ F $\rightarrow$ G) with a project duration of 26 weeks.

Float Diagnostic: Notice Activity B has $TF = 4$ weeks, but $FF = 0$ weeks ($ES_D - EF_B = 10 - 10 = 0$). If Activity B slips by 2 weeks, it will not delay the 26-week project deadline, but it will immediately push Activity D's start date from week 10 to week 12.

PERT Probability Analysis

For the critical path activities, engineering supplied three-point estimates:

• Activity A: $o=2, m=4, p=6 \rightarrow \mu_A = 4.0, \sigma_A^2 = ((6-2)/6)^2 = 0.444$
• Activity C: $o=5, m=8, p=11 \rightarrow \mu_C = 8.0, \sigma_C^2 = ((11-5)/6)^2 = 1.000$
• Activity E: $o=4, m=7, p=10 \rightarrow \mu_E = 7.0, \sigma_E^2 = ((10-4)/6)^2 = 1.000$
• Activity F: $o=2.5, m=4, p=5.5 \rightarrow \mu_F = 4.0, \sigma_F^2 = ((5.5-2.5)/6)^2 = 0.250$
• Activity G: $o=1.5, m=3, p=4.5 \rightarrow \mu_G = 3.0, \sigma_G^2 = ((4.5-1.5)/6)^2 = 0.250$

$$\mu_{\text{proj}} = 4.0 + 8.0 + 7.0 + 4.0 + 3.0 = 26.0 \text{ weeks}$$ $$\sigma_{\text{proj}}^2 = 0.444 + 1.000 + 1.000 + 0.250 + 0.250 = 2.944 \text{ weeks}^2$$ $$\sigma_{\text{proj}} = \sqrt{2.944} = 1.716 \text{ weeks}$$

Probability of completing before the contract penalty deadline of 28.0 weeks:

$$Z = \frac{28.0 - 26.0}{1.716} = +1.166$$

Consulting standard normal probability tables, $P(Z \le 1.17) \approx 87.9\%$. The fixed-path normal approximation estimates about 87.9% on-time completion. Correlated durations and a different path becoming critical can change the result; simulation is useful where those effects matter.

Project Crashing Decision

If a retail tenant offers a $40,000 bonus to complete in 24 weeks (compressing 2 weeks):

• Critical path options: A ($15k/wk), C ($20k/wk), E ($12k/wk), F ($25k/wk), G ($20k/wk).
• Activity E has the lowest crash cost per week ($12,000) and can be crashed by up to 2 weeks.
• Crashing Activity E by 2 weeks reduces project duration to 24 weeks at an incremental cost of 2 × $12,000 = $24,000.
• The non-critical hardware path is 22 weeks, so Path 2 remains the critical path at 24 weeks.
• Net financial gain: $40,000 bonus - $24,000 crash cost = +$16,000.

---

Exam Traps to Avoid