14.2 Scope, Schedule, and Cost Management

13.2 Scope, Schedule, and Cost Management

Quick Answer: Lock scope baseline (scope statement + WBS + dictionary). Build AON/PDM networks; critical path = longest path (float ≈ 0). Fast track = overlap (risk↑); crash = add resources (cost↑). Know cost types and EVM: CPI = EV/AC, SPI = EV/PV.

Section 13.1 gave the framework. Most Domain F quantitative-style reasoning lives here: what will be delivered (scope), when (schedule), and for how much (cost). On chemical plant and EPC projects in Qatar, these three baselines are what owners track in weekly reports—and what exam writers use for crisp MCQs.

Scope management essentials

Product scope describes features of the product (for example, a distillation train meeting capacity and purity). Project scope describes the work required to deliver that product (engineering, procurement, construction, commissioning support). Both must be clear.

Scope baseline

The scope baseline is the approved version of:

1. Project scope statement — description, deliverables, acceptance criteria, exclusions, constraints, assumptions
2. Work Breakdown Structure (WBS) — hierarchical decomposition of the total scope of work
3. WBS dictionary — detailed descriptions of WBS elements (boundaries, owners, acceptance)

Changes to the scope baseline go through integrated change control—not informal hallway agreements. Uncontrolled growth is scope creep.

WBS principles

• 100% rule: The WBS includes all project scope and only the project scope—no gaps, no extra work.
• Decompose until work packages are assignable, estimable, and controllable.
• WBS is deliverable-oriented, not a random org chart (though org structure may inspire coding).
• Do not confuse WBS with a schedule network: WBS answers “what,” network answers “in what order and when.”

Deliverables vs activities (exam favorite)

A stem that asks for a WBS element usually wants a deliverable-oriented package (“Reactor foundation complete”), not a vague ongoing verb without a product (“Think about safety”). Activities appear in the schedule after decomposition and sequencing.

Validate vs control scope (awareness)

• Validate scope: formal acceptance of completed deliverables with the customer/sponsor.
• Control scope: monitor status and manage scope baseline changes.

Schedule management: networks, critical path, float

After defining activities from the WBS, you sequence them with logical relationships and estimate durations, then analyze the network.

AON / PDM networks

Precedence Diagramming Method (PDM) with Activity-on-Node (AON) is the standard exam model: boxes (nodes) are activities; arrows are dependencies.

Activity-on-Arrow (AOA), also called the arrow diagramming method, is the older alternative you should be able to recognise because it appears by name in the published UPDA project-management topic list. In AOA the arrow is the activity and the node is an event (a moment in time when preceding activities finish and following ones may start), and because AOA supports only finish-to-start logic it needs dummy activities—zero-duration dashed arrows—to express dependencies the geometry cannot otherwise show.

Critical-path logic is identical in both notations: the critical path is the longest path through the network and carries zero total float. Only the drawing convention changes.

Lead accelerates a successor (negative lag); lag inserts waiting time (concrete cure, vendor fabrication wait).

Critical path method (CPM)

• Perform forward pass (earliest start/finish) and backward pass (latest start/finish).
• Total float (slack): time an activity can slip without delaying the project end date.
• Critical path: the path with least float (classically zero total float); its length equals the minimum project duration for that network.
• Delay on the critical path delays the project (unless float is created by crashing/fast-tracking or scope change).

Worked concept (qualitative)

Path A: Engineering → Long-lead order → Install → Commission (28 weeks)
Path B: Civil → Structural → Pipe racks (22 weeks)
If these are the only parallel paths, Path A is critical. Improving civil productivity alone does not finish the project earlier unless Path A shortens or logic changes.

Fast tracking vs crashing

When the schedule must compress:

Exam traps:

• Crashing non-critical work wastes money without helping the end date.
• Fast tracking is not free; quality and safety risk can soar on brownfield plant work.
• “Work overtime forever” is a form of crashing with fatigue/safety costs—not a magic free lunch.

Cost management essentials

Cost types

Projects also speak of CAPEX (capital expenditure for the asset) versus owner OPEX impacts after startup—exam stems usually stay with project cost control language.

Contingency versus management reserve

Section 13.3 covered estimate classes and how capital estimates are built and escalated. The project-control point here is the reserve vocabulary, which stems test directly: contingency addresses known-unknowns and sits inside the cost baseline, while management reserve, where it is used, addresses unknown-unknowns and sits outside the baseline at sponsor level. Spending contingency is a project-manager decision; releasing management reserve is not.

Cost baseline

The cost baseline is the approved time-phased budget used for measurement (often excluding management reserve). Control costs compares actuals and performance to that baseline and manages changes formally.

Earned value management (EVM) at exam level

EVM integrates scope, schedule, and cost performance using three cornerstone values:

Core indices and variances

Mini numerical intuition

At a status date: PV = 200, EV = 180, AC = 210.

• SV = 180 − 200 = −20 → behind schedule in EV terms
• CV = 180 − 210 = −30 → over budget
• SPI = 180/200 = 0.90 → 90% of planned earning rate
• CPI = 180/210 ≈ 0.86 → only 0.86 currency units of value per 1 spent

Forecast awareness (light): Estimate at Completion often uses EAC ≈ BAC / CPI when current cost efficiency is expected to continue (BAC = budget at completion). Know the idea that poor CPI drives higher EAC; detailed forecasting variants are beyond typical UPDA depth.

EVM traps

• Confusing PV with AC (plan vs spend).
• Thinking SPI > 1 always means “critical path is fine”—SPI is value-based, not a substitute for network float analysis on the true critical path.
• Using EVM without a clear measurement of percent complete on work packages.

Triple constraint and trade-offs

Scope, schedule, and cost (with quality and risk) trade against each other. Expanding scope without time or budget change stresses the project. Compressing schedule often raises cost or risk. Domain F items often ask which technique or metric fits the trade-off described.

Section synthesis

Build scope baseline with a proper WBS, schedule with PDM/critical path, compress with fast tracking vs crashing knowingly, classify costs sensibly, and read EVM indices without panic. Section 13.3 adds risk, quality, and stakeholder management—the human and uncertainty layers that decide whether those baselines survive contact with a live plant project.