5. Schedule Planning and Control

Introduction and Context

A project schedule translates scope into a time-based execution system. It shows what must be done, the order in which work should occur, the resources required, and the dates by which results are expected. In production and operations environments, scheduling is especially important because project activities compete for labour, equipment, materials, suppliers, production capacity, and management attention. A technically sound project can still fail when its schedule is unrealistic, poorly integrated, or not actively controlled.

Schedule planning is more than assigning dates to a list of tasks. It involves decomposing deliverables into activities, establishing logical relationships, estimating durations, allocating resources, identifying time-critical work, and creating a baseline against which performance can be measured. Schedule control then compares actual progress with the approved plan, explains deviations, forecasts completion, and supports corrective or preventive action.

The schedule is also a managerial communication instrument. It coordinates contractors, engineering teams, procurement, production, quality assurance, and customers. At postgraduate level, schedule management should therefore be understood as both a technical discipline and a decision-making process involving uncertainty, trade-offs, negotiation, and governance.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Define project activities and establish logical dependencies.

2. Construct and interpret precedence network diagrams.

3. Calculate critical path, float, and expected duration using CPM and PERT.

4. Develop resource-loaded schedules and explain resource constraints.

5. Apply critical-chain concepts, buffers, crashing, and fast tracking.

6. Monitor schedule performance using baseline, variance, and earned-value information.

7. Evaluate the use of scheduling software, analytics, and automation.

8. Recommend practical responses to schedule risk in production projects.

From Scope to Activities

The starting point for a credible schedule is the work breakdown structure (WBS). The WBS identifies deliverables and work packages; activity definition converts those work packages into executable units of work. An activity should be sufficiently specific to estimate, assign, monitor, and accept. “Install conveyor system” may be too broad if it includes foundations, delivery, assembly, electrical connection, testing, and operator training. These elements may need to become separate activities.

Activity definition normally considers the following information:

• the approved scope statement and WBS;
• technical specifications, drawings, and contractual milestones;
• resource calendars and production constraints;
• procurement lead times and supplier commitments;
• quality, safety, regulatory, and approval requirements; and
• historical data and lessons from comparable projects.

An activity register commonly records an identification code, description, predecessor and successor relationships, responsible owner, estimated duration, required resources, assumptions, constraints, and status. Milestones are significant events with zero duration, such as design approval, equipment arrival, trial production, or customer acceptance. They do not consume time but provide control points.

The distinction between effort and duration is essential. Effort is the amount of labour required; duration is the elapsed calendar time. Ten person-days of effort may require two days with five available workers, but this relationship is not always linear. Work may be constrained by equipment, sequence, learning, safety limits, or the availability of one specialist.

Dependency Analysis and Network Logic

Once activities are identified, their relationships are established. The most common relationship is finish-to-start (FS): activity B cannot start until activity A finishes. Other relationships are:

• Start-to-start (SS): B may start when A starts, possibly after a lag.
• Finish-to-finish (FF): B cannot finish until A finishes.
• Start-to-finish (SF): B cannot finish until A starts; this is relatively uncommon.

A dependency may be mandatory, discretionary, internal, or external. A mandatory dependency arises from the nature of the work, such as curing concrete before loading it. A discretionary dependency reflects a preferred sequence that could theoretically be changed. An external dependency depends on an outside party, such as a regulator or supplier.

Lags introduce waiting time between related activities; leads permit an activity to overlap with its predecessor. For example, painting may begin two days after plastering starts, represented as SS plus a lag. Leads should be used cautiously because they can obscure the true logic and make the schedule difficult to audit.

A network diagram represents activities and logical relationships. In activity-on-node notation, each node represents an activity and arrows represent dependencies. The diagram should flow from a clear start to a clear finish. Circular logic, unexplained open ends, excessive constraints, and relationships that merely reflect preferred dates are warning signs of poor schedule quality.

Critical Path Method

The Critical Path Method (CPM) assumes that activity durations can be estimated as single values. It identifies the longest path through the network and determines the shortest possible project duration, subject to the stated logic and constraints. The critical path is not necessarily the path containing the most activities; it is the path with the greatest total duration and normally has zero total float in the baseline schedule.

The forward pass calculates early dates:

• Early Start (ES): earliest time an activity can begin.
• Early Finish (EF): ES plus duration.

For an activity with several predecessors, its ES is the largest EF among those predecessors. The backward pass calculates late dates:

• Late Finish (LF): latest time an activity can finish without delaying the project.
• Late Start (LS): LF minus duration.

For an activity, total float is:

Total Float = LS − ES = LF − EF

Activities with zero total float form the critical path, although calendars, constraints, and multiple critical paths may complicate this interpretation. Free float is the amount of time an activity can be delayed without delaying the early start of its immediate successor. Total float belongs to the network logic, whereas free float reflects the immediate successor relationship.

Illustrative CPM Calculation

Consider the following simplified network:

| Activity | Duration (days) | Predecessor |

|---|---:|---|

| A: Design | 4 | — |

| B: Procure component | 6 | A |

| C: Prepare site | 5 | A |

| D: Install equipment | 4 | B and C |

| E: Test system | 3 | D |

The paths are A-B-D-E, with duration 17 days, and A-C-D-E, with duration 16 days. Therefore, the project duration is 17 days and A-B-D-E is critical. Activity C has one day of path float, assuming no other constraints. If procurement activity B slips by two days, the project finish slips by two days unless corrective action is taken. A one-day delay in C may consume its float without changing the project completion date.

The critical path is dynamic. A delay in a non-critical activity can consume float and make that activity critical. Similarly, crashing or resource changes can create a different critical path. Schedule analysis should therefore be repeated after significant changes.

PERT and Duration Uncertainty

CPM is useful when estimates are reasonably stable. The Program Evaluation and Review Technique (PERT) is designed for situations in which activity durations are uncertain. Three estimates are collected:

• optimistic time, a;
• most likely time, m; and
• pessimistic time, b.

The expected duration is calculated as:

te = (a + 4m + b) / 6

A commonly used activity variance is:

Variance = [(b − a) / 6]²

PERT gives greater weight to the most likely estimate but recognises the influence of favourable and adverse conditions. The expected duration of a path is the sum of expected activity durations, and path variance is often approximated by summing activity variances when activities are treated as independent. A normal approximation can then support an estimate of the probability of meeting a target date:

Z = (Target date − Expected project duration) / Standard deviation

PERT should not be treated as a guarantee. Estimates may be correlated, especially when several activities depend on the same supplier, technology, or approval. The method is most valuable as a way of making uncertainty visible and stimulating discussion about assumptions.

Resource Loading and Resource-Constrained Scheduling

A logically feasible schedule may be impossible when resources are limited. Resource loading assigns labour, equipment, materials, and cost information to activities. A resource histogram displays demand over time and reveals peaks, idle periods, and conflicts. For example, several installation activities may be logically independent but may all require the same commissioning engineer.

Resource smoothing adjusts activities within available float to reduce fluctuations while preserving the planned completion date. Resource levelling changes activity dates, and possibly the project completion date, to resolve over-allocation. A schedule that assumes unlimited resources is called resource-unconstrained; a schedule that reflects actual availability is resource-constrained.

Resource decisions should consider skill requirements, shift patterns, fatigue, learning curves, subcontracting, equipment setup time, and material availability. Simply adding people may reduce productivity when work areas are congested or communication becomes difficult. In production projects, resource loading should also be integrated with the master production schedule, maintenance windows, shutdown periods, and capacity plans.

Critical Chain and Buffers

Critical-chain project management extends network scheduling by considering both precedence and resource dependencies. The critical chain is the longest sequence of dependent activities after resource constraints are considered. It challenges the practice of embedding large safety margins in every activity estimate. Instead, protection is consolidated into strategically placed buffers.

A project buffer is placed at the end of the critical chain to protect the promised completion date. Feeding buffers protect the critical chain from delays on non-critical paths. Resource buffers provide alerts that a scarce resource will soon be needed. Buffer consumption is monitored as a control signal. A schedule may remain acceptable when activities are individually late if the delay has not consumed an excessive proportion of the relevant buffer.

Critical-chain methods can reduce local protection and multitasking, but they require disciplined prioritisation, reliable status reporting, and organisational support. Buffers should not be treated as hidden contingency to be spent casually; they are management reserves with a defined protective purpose.

Schedule Compression: Crashing and Fast Tracking

When a project must finish earlier, management may compress the schedule. Crashing adds resources, authorises overtime, uses premium suppliers, or applies more expensive methods to shorten activities. It should focus on critical-path activities. A useful decision measure is crash cost per unit of time saved:

Crash cost slope = (Crash cost − Normal cost) / (Normal duration − Crash duration)

The least-cost critical activity is normally considered first, but the analysis must be repeated because the critical path may change. Crashing can create quality problems, fatigue, coordination costs, and resource competition.

Fast tracking overlaps activities that were originally planned sequentially. For example, procurement may begin using an approved preliminary design while final detailing continues. Fast tracking increases rework and interface risk, particularly when changes are likely. It is more appropriate when deliverables can be divided into stable portions and communication is strong.

Crashing changes the cost-resource trade-off; fast tracking changes the risk and dependency structure. Neither method is automatically superior. The choice depends on the value of earlier completion, contractual commitments, safety, quality, and the reversibility of errors.

Schedule Baselines and Performance Control

After planning and approval, the time-phased schedule becomes the schedule baseline. It includes planned activity dates, milestones, logic, calendars, and often the time-phased budget. Control requires disciplined updating rather than informal date changes. Actual starts, actual finishes, remaining duration, physical progress, and approved changes should be recorded consistently.

Useful schedule-control measures include:

• milestone variance against baseline;
• activities started or completed late;
• critical-path movement;
• total and free float consumption;
• forecast completion date;
• percentage of activities with overdue status;
• constraint and dependency ageing; and
• schedule risk exposure.

Earned Value Management integrates schedule and cost. Planned Value (PV) is the authorised budget for work scheduled. Earned Value (EV) is the authorised budget for work actually completed. Schedule Performance Index is:

SPI = EV / PV

An SPI below 1.00 suggests that less value has been earned than planned, although earned-value results should be interpreted with the network schedule because a project may show an acceptable aggregate index while a key milestone is at risk. Schedule Variance is SV = EV − PV; it is expressed in monetary or budget units, not days.

Schedule control follows a repeated cycle: establish the baseline, collect reliable status data, analyse variance and causes, forecast outcomes, decide corrective action, implement approved changes, and communicate the revised outlook. Root causes may include inaccurate estimates, late decisions, supplier failure, design change, resource conflict, rework, safety stoppage, or unrealistic imposed dates. A professional scheduler reports causes and implications, not merely red and green indicators.

Software, Digital Tools, and Analytics

Scheduling applications such as Microsoft Project, Primavera P6, and comparable enterprise platforms support WBS development, dependency networks, calendars, baselines, resource loading, progress updates, and reporting. More advanced environments connect schedules with enterprise resource planning, procurement, building information modelling, manufacturing systems, and cost databases.

Digital scheduling is valuable only when the underlying data and logic are credible. Automated date calculations cannot correct missing dependencies, inappropriate constraints, or optimistic estimates. Common useful practices include version control, role-based approval, schedule health checks, automated alerts for float erosion, and dashboards showing milestone forecasts and resource conflicts.

Analytics and artificial intelligence can compare current patterns with historical projects, identify activities associated with delay, forecast completion dates, and detect unusual status updates. Such outputs should support—not replace—professional judgement. Data bias, poor coding of historical activities, confidentiality, explainability, and accountability must be considered. A project manager remains responsible for decisions made using analytical recommendations.

Illustrative Case: Expanding a Packaging Line

Background

A food manufacturer planned to add an automated packaging line during a six-week plant shutdown. The project included equipment delivery, foundation modification, electrical installation, software configuration, trial production, and regulatory approval. The shutdown date was fixed because restarting the existing line after the planned date would create major commercial disruption.

Situation and Problem

The initial schedule showed completion in 30 working days. However, it treated the electrical contractor and commissioning engineer as continuously available, although both were shared with another company project. Procurement also depended on final approval of a design drawing. Management wanted to know whether the deadline was genuinely achievable and what action would provide the greatest protection.

Analysis

The project team decomposed the work into activities and developed a precedence network. The initial critical path included design approval, equipment delivery, foundation modification, installation, software configuration, testing, and approval. Resource loading revealed that installation and software configuration competed for the same automation specialist. The resource-constrained critical chain extended the forecast by three days.

A PERT review showed considerable uncertainty in equipment delivery and regulatory approval. The project team also identified a hidden external dependency: the regulator required test records in a specified format before inspection could be booked. This had not appeared in the original schedule.

Approach and Solution

The team introduced an early design-review milestone, began procurement of long-lead standard components before final drawing approval, and divided installation into areas that could be released progressively. This represented controlled fast tracking rather than indiscriminate overlap. A second qualified electrician was engaged for the shutdown period, while the automation specialist’s work was protected through a resource buffer.

The project buffer was set at the end of the commissioning chain. Daily coordination meetings focused on completed physical work, emerging constraints, and buffer consumption rather than subjective claims of percentage completion. A baseline was approved, and all changes were recorded through change control.

Outcome

The line achieved mechanical completion before the shutdown deadline and entered trial production with two days of buffer remaining. The project avoided a costly extension of the shutdown, although additional specialist labour increased direct cost. The team concluded that the original 30-day schedule had been logically plausible but operationally unrealistic because it ignored resource dependencies and approval lead times.

Learning Points

The case demonstrates that schedule quality depends on more than arithmetic. Resource availability, external approvals, work packaging, uncertainty, and data quality must be integrated. Fast tracking is safer when stable portions of work are separated from work still subject to change. Finally, buffer and milestone information provides management with an early-warning system that a simple completion percentage cannot provide.

Risks, Governance, and Professional Practice

The most common scheduling errors are excessive detail without managerial value, missing dependencies, arbitrary constraints, unvalidated estimates, failure to update actual progress, and treating every activity as equally important. Another serious error is changing baseline dates to hide poor performance. This destroys trend information and weakens accountability.

Schedule governance should define who owns the schedule, who may approve changes, how progress is measured, how actual dates are evidenced, and how revised forecasts are communicated. Contractual schedules require particular care because dates may have legal and financial consequences. Claims analysis may depend on contemporaneous records, accepted baselines, delay notices, and proof of causation.

Ethically, schedulers should not manipulate logic or status data to create an appearance of control. Risks should be reported when they become credible, even when disclosure is uncomfortable. Safety, regulatory compliance, worker welfare, and product quality must not be sacrificed merely to preserve a date. When acceleration increases fatigue or bypasses inspection, the apparent schedule gain may create greater organisational risk.

Current Developments and Best Practices

Contemporary scheduling increasingly combines network logic with probabilistic risk analysis, rolling-wave planning, integrated cost and schedule controls, and near-real-time field data. Digital twins, sensor data, mobile progress capture, and four-dimensional models can improve visibility where data standards are consistent. Agile and hybrid approaches are also used where requirements evolve: near-term work is planned in detail while later work remains at a higher level.

Effective practice includes the following:

• begin with a deliverable-based WBS;
• make dependencies explicit and review them with technical specialists;
• distinguish effort, duration, and elapsed time;
• use realistic calendars and resource availability;
• analyse critical and near-critical paths;
• model uncertainty rather than hiding it in arbitrary dates;
• protect milestones through buffers and contingency where justified;
• baseline only after responsible stakeholders agree to the plan;
• measure physical progress using objective rules;
• investigate causes, not just symptoms, of variance; and
• preserve an auditable history of changes, forecasts, and decisions.

Chapter Summary

Schedule planning converts project scope into an executable time-based model. Activities must be defined at a useful level of detail, logically linked, duration-estimated, and assigned appropriate resources. CPM identifies the longest path and calculates early dates, late dates, and float. PERT incorporates uncertainty through optimistic, most likely, and pessimistic estimates. Resource loading reveals whether a logically feasible schedule can actually be executed, while critical-chain planning incorporates resource dependencies and uses project and feeding buffers.

When deadlines are threatened, crashing shortens critical activities through additional cost or resources, whereas fast tracking overlaps sequential work and increases coordination and rework risk. Schedule control depends on an approved baseline, reliable progress data, variance analysis, forecasting, and controlled change. Software and analytics strengthen scheduling only when logic, estimates, and governance are sound. Professional schedule management balances time, cost, quality, safety, resources, uncertainty, and ethical accountability.

Key Terms

Activity: A defined unit of project work with a duration and required resources.

Baseline: The formally approved version of the schedule used for performance comparison.

Buffer: Time deliberately placed to protect a project, critical chain, or feeding path from uncertainty.

Critical Chain: The longest sequence of logically and resource-dependent activities.

Critical Path: The longest duration path through a project network.

Crashing: Shortening schedule duration by adding resources or accepting additional cost.

Dependency: A logical relationship governing the order of activities.

Duration: Elapsed calendar time required to complete an activity.

Earned Value: Budgeted value of work actually completed.

Fast Tracking: Performing activities in parallel that were originally planned sequentially.

Float: Time by which an activity may be delayed without a specified adverse effect.

Lag: Waiting time inserted between related activities.

Milestone: A significant zero-duration event or decision point.

PERT: A probabilistic scheduling technique using three duration estimates.

Precedence Network: A diagram representing activities and their logical relationships.

Resource Levelling: Adjusting dates to resolve resource over-allocation.

Resource Smoothing: Adjusting activities within float to reduce resource variation without changing the completion date.

Schedule Performance Index: Earned Value divided by Planned Value.

Total Float: Delay available to an activity without delaying the project completion date.

Review Questions

Short Answer Questions

1. Distinguish between activity effort and activity duration.

2. What is the difference between total float and free float?

3. State the three duration estimates used in PERT.

4. Explain the purpose of a schedule baseline.

5. What is the difference between resource smoothing and resource levelling?

Long Answer Questions

1. Explain the process of converting a WBS into a precedence network and discuss common dependency errors.

2. Describe the forward-pass and backward-pass calculations used in CPM.

3. Compare CPM and PERT, including their assumptions, calculations, and appropriate uses.

4. Discuss critical-chain scheduling and the role of project, feeding, and resource buffers.

5. Explain how schedule performance should be controlled from baseline approval through corrective action.

Analytical / Application Questions

1. A project has two paths: A-B-D-E of 22 days and A-C-D-E of 20 days. Identify the critical path and explain what happens if activity C is delayed by one day.

2. A manager must reduce a project by five days. Compare crashing and fast tracking and recommend a method for a project involving safety-critical equipment installation.

3. A schedule reports an SPI of 0.92, but the customer acceptance milestone remains on its baseline date. Explain why both statements may be true and identify additional information the project manager should review.

22. Multiple Choice Questions with Answers

Question 1

Which statement best describes the critical path?

A. The path containing the greatest number of activities

B. The path with the longest total duration through the network

C. The path containing the most expensive activities

D. The path assigned to the largest project team

Correct Answer: B. The path with the longest total duration through the network

Question 2

An activity has an optimistic estimate of 4 days, a most likely estimate of 7 days, and a pessimistic estimate of 16 days. What is its PERT expected duration?

A. 7.0 days

B. 7.5 days

C. 8.0 days

D. 9.0 days

Correct Answer: C. 8.0 days

Question 3

Which relationship means that a successor cannot start until its predecessor has finished?

A. Finish-to-start

B. Start-to-start

C. Finish-to-finish

D. Start-to-finish

Correct Answer: A. Finish-to-start

Question 4

A non-critical activity has two days of total float. If it is delayed by one day and no other conditions change, what is the most likely immediate result?

A. The project finishes one day earlier

B. The activity becomes impossible to complete

C. The project completion date necessarily slips

D. One day of its total float is consumed

Correct Answer: D. One day of its total float is consumed

Question 5

What is the principal purpose of resource levelling?

A. To increase every activity's duration

B. To resolve resource over-allocation, even if the finish date changes

C. To eliminate all project uncertainty

D. To identify the cheapest supplier

Correct Answer: B. To resolve resource over-allocation, even if the finish date changes

Question 6

Which action is an example of fast tracking?

A. Adding a second work crew to one activity

B. Reducing inspection requirements

C. Overlapping equipment procurement with completion of stable design elements

D. Increasing the contingency reserve without changing activities

Correct Answer: C. Overlapping equipment procurement with completion of stable design elements

Question 7

In critical-chain scheduling, a project buffer primarily protects:

A. The final promised completion date

B. The procurement budget

C. The quality inspection team

D. Every individual activity from all variation

Correct Answer: A. The final promised completion date

Question 8

If Earned Value is 90 and Planned Value is 100, what is the Schedule Performance Index?

A. 0.90

B. 1.10

C. 10.00

D. 190

Correct Answer: A. 0.90

Question 9

Why should a crash-cost analysis be repeated after shortening an activity?

A. PERT estimates automatically become invalid

B. The critical path may change

C. All non-critical activities become critical

D. Resource calendars no longer matter

Correct Answer: B. The critical path may change

Question 10

Which practice most seriously undermines schedule governance?

A. Recording actual starts and finishes

B. Reviewing float erosion

C. Changing baseline dates to conceal poor performance

D. Using milestone forecasts in management meetings

Correct Answer: C. Changing baseline dates to conceal poor performance