Project and Program Delivery Management

Introduction

Infrastructure assets are delivered through projects, but their value is usually realized through programs and portfolios. A project may construct a bridge, implement a utility-control system, or upgrade a railway station. A program coordinates related projects so that their combined outputs produce strategic outcomes—for example, improved mobility, lower emissions, and safer operations. Effective delivery management therefore extends beyond completing individual work packages. It requires integrated control of scope, time, cost, quality, resources, interfaces, risk, change, assurance, and benefits.

Infrastructure delivery is particularly demanding because projects are capital-intensive, long-lived, geographically distributed, regulated, and dependent on many organizations. Design decisions affect construction; construction decisions affect operations; and operational benefits may not appear until years after handover. The delivery manager must therefore establish a controlled management system while preserving enough flexibility to respond to uncertainty.

This chapter presents an integrated approach based on governance, stage gates, baseline management, earned value, change control, assurance, and benefits realization.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Distinguish projects, programs, portfolios, products, outputs, outcomes, and benefits.
2. Establish integrated baselines for scope, schedule, cost, and quality.
3. Apply stage-gate governance and assurance proportionately.
4. Interpret earned value measures and forecasts.
5. Manage resources, interfaces, dependencies, risks, and changes.
6. Design benefits-realization arrangements across the program life cycle.
7. Evaluate delivery performance and recommend corrective action.

1. Projects, Programs, and the Delivery System

A project is a temporary endeavor undertaken to create a unique product, service, or result. A program is a coordinated group of related projects and change activities managed to obtain benefits that would not be available from managing them separately. A portfolio is a collection of projects, programs, and operational work selected and governed to achieve strategic objectives.

The distinction is consequential. A project manager may optimize a station construction package by minimizing its local cost, while a program manager may authorize a more expensive design because it reduces whole-life maintenance costs across the network. Project success is commonly judged by delivery against approved scope, time, cost, quality, and safety requirements. Program success additionally depends on strategic alignment, adoption, capability creation, and sustained benefits.

A useful chain is:

Inputs → Activities → Outputs → Outcomes → Benefits → Strategic objectives

For example, funding and land access enable design and construction activities. These produce a completed bus rapid-transit corridor. The corridor enables faster and more reliable journeys. The resulting benefits may include reduced travel time, increased public-transport use, and lower emissions. Strategic objectives might include economic inclusion and climate resilience.

Outputs are under the delivery team’s direct influence; outcomes depend on users, operators, regulators, and external conditions. Benefits should therefore have named owners, measures, target values, and realization dates rather than being treated as automatic consequences of project completion.

Delivery roles and accountability

Typical roles include:

• Sponsor: owns the business case, funding, strategic alignment, and major decisions.
• Project or program manager: integrates planning, execution, control, reporting, and escalation.
• Project board or steering committee: provides governance and authorizes gates.
• Design authority: protects technical integrity and configuration coherence.
• Commercial manager: manages contracts, procurement, claims, and supplier performance.
• Assurance function: independently tests whether governance, controls, and technical decisions are adequate.
• Operations and asset owners: define maintainability, operational readiness, and benefits requirements.
• Stakeholders and affected communities: contribute requirements, constraints, legitimacy, and acceptance criteria.

Accountability should be explicit. A responsibility assignment matrix, often called a RACI matrix, identifies who is Responsible, Accountable, Consulted, and Informed for significant decisions and deliverables. One person should normally be accountable for each decision, even when many parties are responsible for execution.

2. Integrated Scope and Requirements Management

Scope defines what the delivery system will and will not produce. Weak scope definition creates ambiguity, uncontrolled growth, disputes, rework, and benefits failure. Scope management includes requirements elicitation, analysis, validation, decomposition, acceptance, and control.

A sound hierarchy is:

1. Strategic objectives and investment outcomes.
2. Program capabilities and benefits.
3. Project products and acceptance criteria.
4. Work breakdown structure (WBS) elements.
5. Activities, resources, and cost accounts.

The WBS decomposes the total deliverable into manageable components. It should be deliverable-oriented rather than merely an organizational list. Each work package should have a defined owner, scope statement, assumptions, interfaces, acceptance criteria, schedule logic, budget, and evidence requirements.

Requirements should be traceable from stakeholder need to design, verification, validation, and operational acceptance. A requirements traceability matrix can expose missing tests or requirements that have no implemented solution. Requirements should also be classified—for example, functional, performance, safety, regulatory, environmental, information, maintainability, and accessibility requirements.

Scope control requires a baseline. A baseline is an approved version against which performance and proposed changes are assessed. It is not immutable; it can be changed through authorized configuration and change-control processes. Informal additions are scope creep, even when individually small.

3. Schedule, Dependencies, and Criticality

The schedule converts scope into a time-based delivery strategy. Planning begins with activities, logic relationships, durations, calendars, constraints, resources, and milestones. Common relationships include finish-to-start, start-to-start, finish-to-finish, and start-to-finish, although finish-to-start should not be used automatically when it misrepresents the work.

The critical path is the longest logical path through a network under stated assumptions. Activities on it have little or no total float, so delay to them can delay the project unless corrective action changes the network. Criticality is dynamic: resource constraints, approved changes, and progress can move the critical path. A schedule should therefore be periodically recalculated and reviewed rather than treated as a static diagram.

Schedule quality depends on more than a visually detailed plan. Useful checks include:

• every activity has defined predecessors and successors where appropriate;
• durations are credible and based on productivity, quantities, or historical evidence;
• constraints are visible rather than hiding logic problems;
• calendars reflect possessions, weather, holidays, and working-time rules;
• commissioning, approvals, procurement, and handover are included;
• interfaces and decision dates are represented;
• the schedule has a clear data date and update procedure.

For uncertain work, deterministic dates may be supplemented by three-point estimates. If optimistic, most-likely, and pessimistic durations are represented by a, m, and b, a commonly used beta-weighted estimate is:

Here, all durations use the same unit. This estimate assumes the three-point judgment reasonably represents uncertainty and that the beta-shaped weighting is appropriate; it is not a guarantee of actual duration. For a simple three-point range, an approximate standard deviation is:

These expressions support planning judgments but should not substitute for empirical data or risk analysis.

4. Cost, Baselines, and Earned Value Management

Cost management includes estimating, budgeting, funding control, commitments, accruals, forecasting, and financial reporting. Estimates should distinguish direct costs, indirect costs, contingency, escalation, taxes, financing effects, and whole-life costs where relevant. A project budget is not simply a contractor price: it must also reflect design, land, supervision, testing, commissioning, risk, and organizational costs.

The cost baseline is the time-phased authorized budget for planned work. Management reserve may be held outside the performance measurement baseline for unforeseen in-scope work, subject to governance rules. Contingency and reserve terminology varies by organization, so definitions must be explicit.

Earned value concepts

Earned value management (EVM) integrates scope, schedule, and cost. At a given status date:

• Planned Value (PV): authorized budget for work scheduled to be completed.
• Earned Value (EV): authorized budget for work actually completed.
• Actual Cost (AC): cost actually incurred for completed work.

The principal variances and indices are:

Schedule variance (SV) and cost variance (CV) are expressed in budgetary currency, not calendar time. A positive SV means more budgeted work has been earned than planned; it does not mean the project is a specific number of days ahead. SPI and CPI are dimensionless. Values above 1.00 generally indicate favorable performance, while values below 1.00 indicate unfavorable performance, subject to data quality and baseline assumptions.

If BAC is the budget at completion, a simple estimate at completion is:

This assumes current cost efficiency will continue. If remaining work is re-estimated independently, then:

where ETC is the estimate to complete. The estimate at completion should be selected based on the cause of variance, remaining risk, and quality of the forecast—not by mechanically applying one formula.

Worked example

Suppose a work package has BAC = $1,000,000. At the status date, PV = $600,000, EV = $500,000, and AC = $550,000. Then:

• SV = $500,000 − $600,000 = −$100,000.
• CV = $500,000 − $550,000 = −$50,000.
• SPI = $500,000 ÷ $600,000 = 0.833.
• CPI = $500,000 ÷ $550,000 = 0.909.

The package has earned less work than planned and has spent more than the value of the work achieved. If the cost efficiency continues, EAC = $1,000,000 ÷ 0.909 ≈ $1,100,000. This forecast is indicative, not definitive; management should investigate whether the variance is temporary, caused by approved change, or evidence of a systemic productivity problem.

EVM has limitations. It may reward physical progress measures that are poorly defined, conceal quality problems, and treat schedule as a cost-based proxy. It should therefore be combined with milestone evidence, critical-path analysis, safety, quality, risk, and stakeholder measures.

5. Stage-Gate Governance and Assurance

Stage gates are formal decision points at which authorized decision-makers determine whether work should proceed, be redirected, paused, or stopped. A typical infrastructure life cycle includes:

1. Strategic need and option identification.
2. Feasibility and outline business case.
3. Definition, design development, and procurement strategy.
4. Detailed design and authorization to construct.
5. Construction and integration.
6. Testing, commissioning, and operational readiness.
7. Handover, benefits realization, and post-implementation review.

A gate should not be a ceremonial presentation. Evidence should be specified in advance, such as an updated business case, design maturity assessment, risk exposure, land and consent status, cost estimate, schedule confidence, safety case, procurement status, and benefits plan. Gate decisions may be “proceed,” “proceed with conditions,” “rework,” “pause,” or “terminate.”

Assurance is an evidence-based, independent challenge of whether the delivery system is fit for purpose. It may examine governance, technical design, commercial strategy, information management, safety, cybersecurity, environmental compliance, or benefits. Assurance is distinct from management: the delivery team manages risks and performance; assurance tests whether its controls and judgments are credible.

Assurance should be proportionate. Excessive review can delay delivery and encourage compliance theater, while insufficient independence can allow optimism bias and conflicts of interest. Findings should have owners, due dates, severity ratings, and closure evidence.

6. Change, Configuration, and Interface Management

Change is inevitable in infrastructure delivery. The objective is not to prevent all change but to ensure that changes are understood, authorized, prioritized, implemented, and verified.

A change request should describe:

• the proposed change and reason;
• affected requirements, drawings, specifications, and assets;
• impacts on scope, schedule, cost, quality, safety, environment, operations, and benefits;
• affected contracts and interfaces;
• alternatives and consequences of doing nothing;
• funding source and approval authority;
• implementation, testing, and communication arrangements.

A change-control board may authorize changes within delegated limits, while material changes to the business case require sponsor or board approval. Emergency changes need a documented expedited route and retrospective review.

Configuration management establishes identification, status accounting, change control, and verification for baselined items. It is essential where multiple designers, contractors, operators, and suppliers work on connected systems. Without configuration control, teams may construct obsolete drawings, test incompatible versions, or hand over incomplete asset information.

Interface management addresses boundaries between organizations, disciplines, systems, contracts, and life-cycle stages. An interface register should identify the parties, inputs and outputs, owner, required date, acceptance condition, and unresolved issues. Interfaces are often where technically correct components fail as a system.

7. Resources, Quality, and Risk

Resource management covers people, equipment, materials, facilities, information, and specialist capability. Resource loading can reveal unrealistic schedules, but leveling may extend completion dates or change the critical path. Managers must distinguish resource shortage from productivity loss and address both capacity and competence.

Quality management has three complementary dimensions:

• Quality planning: defining standards, acceptance criteria, inspection and test plans, and responsibilities.
• Quality assurance: evaluating whether processes are suitable and followed.
• Quality control: inspecting and testing outputs against requirements.

Quality should be built into design and process control rather than inspected only at the end. Nonconformities require containment, root-cause analysis, corrective action, and verification of effectiveness. A defect-free handover is not sufficient if the asset is difficult to operate or maintain.

Risk management is a continuous process of identifying uncertainty, analyzing likelihood and consequence, selecting responses, assigning owners, and monitoring triggers. Responses include avoid, reduce, transfer, accept, exploit, enhance, or share, depending on whether the uncertainty is a threat or opportunity. Risk registers should not become static lists; they should connect to schedule activities, cost allowances, contracts, design decisions, and gate evidence.

8. Benefits Realization in Programs

Benefits management begins with a benefits map or theory of change. Each benefit should have:

• a clear definition and baseline;
• an accountable benefit owner;
• one or more measures and data sources;
• a target and realization date;
• dependencies and assumptions;
• dis-benefits and unintended effects;
• actions required from operations, users, or policy teams.

Benefits may be financial, service-related, social, environmental, safety-related, or capability-based. Some are difficult to monetize and should not be excluded merely because they resist monetary valuation. Multi-criteria analysis can make trade-offs explicit, provided weights and evidence are transparent.

Program governance should maintain a benefits register and review benefits at gates and after transition. A project can be delivered on time and within budget while failing to achieve its benefits if demand assumptions were wrong, users were not trained, operating procedures were not changed, or complementary projects were delayed.

9. Integrated Reporting and Decision-Making

A useful delivery dashboard combines leading and lagging indicators. Leading indicators include unresolved design interfaces, overdue decisions, safety observations, procurement exposure, risk response completion, and schedule logic quality. Lagging indicators include actual cost, defects, incidents, missed milestones, and realized benefits.

Reports should explain causality rather than merely display red, amber, and green status. For each material variance, the manager should state its cause, consequence, trend, response, owner, and decision required. Data definitions must be consistent across contractors and organizational systems. Automated dashboards can improve timeliness, but automation does not resolve poor baseline quality or inconsistent measurement rules.

Illustrative Case: Metro Extension Program

Background

A metropolitan authority established a program to extend a rail line by 18 km, construct three stations, upgrade signaling, and introduce an integrated operating model. The program contained civil works, systems, rolling-stock compatibility, land acquisition, and customer-information projects.

Problem

The civil works project reported 92% completion, but systems integration was only 65%. Several station structures had been designed without final equipment-room requirements. The program was showing acceptable expenditure against budget, yet the opening date was at risk. Benefits depended on synchronized completion of track, signaling, rolling stock, staffing, and passenger-information systems.

Analysis

An independent assurance review found that each project had a credible local schedule, but the integrated schedule lacked interface milestones. EVM was being reported using inconsistent rules: one contractor earned value from physical quantities, while another used invoice milestones. The benefits register had no owners in the operating organization. A change to fire-and-life-safety requirements had been approved within a project but had not been assessed for program-wide effects.

Approach

The program established a common WBS and calendar, standardized EVM rules, and introduced an interface register owned by the program integration manager. A recovery schedule focused on the critical path through equipment-room design, signaling software, integrated testing, and operational readiness. The stage-gate board required evidence for design maturity and system integration before authorizing further station fit-out.

A change-control board assessed the safety change, approved additional design and testing budget, and recorded the effect on the opening date. Operations appointed benefit owners for journey-time reliability, passenger adoption, and safety performance. A transition rehearsal tested staff competence, emergency procedures, asset information, and passenger communications before opening.

Outcome

The opening was delayed by six weeks but occurred with completed integrated testing and approved operational procedures. The final cost exceeded the original project baseline but remained within the program’s authorized tolerance after approved safety and integration changes. The post-implementation review found that early interface ownership and operational involvement would have reduced rework substantially.

Learning points

The case demonstrates that local project progress can conceal program-level failure. Integrated baselines, common measurement rules, independent assurance, and benefits ownership are necessary where outputs are interdependent. A controlled delay may be preferable to opening an unsafe or operationally immature asset.

10. Contemporary Practice, Technology, and Ethics

Digital twins, common data environments, model-based systems engineering, mobile field inspection, and predictive analytics can improve coordination and evidence. AI may assist with schedule-risk detection, document classification, defect recognition, and forecast analysis. However, AI outputs require validated data, explainable assumptions, human accountability, cybersecurity controls, and protection of commercially sensitive information. An algorithm should not approve a safety-critical change without accountable professional judgment.

Ethical delivery includes fair procurement, anti-corruption controls, respect for labor and community rights, transparent treatment of affected landowners, accessibility, environmental responsibility, and honest reporting. Pressure to conceal variance or manipulate earned-value measures is a governance failure, not a performance strategy. Regulators and professional institutions may impose duties concerning safety, competence, records, conflicts of interest, and public interest.

Climate adaptation and decarbonization increasingly affect scope, design standards, procurement, and benefits. Delivery decisions should consider embodied carbon, resilience, maintainability, climate scenarios, and future flexibility rather than focusing exclusively on initial capital cost.

Best-Practice Principles

1. Align every project with a clearly articulated program outcome and benefit.
2. Baseline scope, schedule, and cost only when requirements and assumptions are sufficiently mature.
3. Use stage gates for decisions, not merely reporting ceremonies.
4. Integrate technical, commercial, operational, and stakeholder interfaces.
5. Apply EVM consistently and interpret it with critical-path, quality, risk, and safety evidence.
6. Make change visible, traceable, and proportionate to its consequences.
7. Give assurance sufficient independence and ensure findings are closed with evidence.
8. Involve operators and maintainers before design is frozen.
9. Assign benefit owners outside the delivery team when benefits depend on operational change.
10. Preserve truthful records, challenge optimism bias, and escalate bad news early.

Chapter Summary

Project and program delivery management integrates the production of infrastructure outputs with the realization of strategic benefits. Projects create defined products; programs coordinate interdependent projects and change; portfolios select investments for strategic value. Effective delivery depends on traceable requirements, deliverable-oriented work breakdown structures, credible schedules, cost baselines, quality controls, resource planning, risk management, and interface ownership.

Stage gates provide evidence-based authorization to proceed, while assurance independently tests the adequacy of governance and technical controls. Earned value connects scope, schedule, and cost through PV, EV, AC, variances, indices, and forecasts, but it must be interpreted alongside critical-path, quality, safety, and risk information. Change and configuration management protect approved baselines without preventing justified adaptation. Finally, benefits registers, accountable owners, measures, and operational transition arrangements ensure that completion is not confused with value realization.

Key Terms

Project: Temporary endeavor creating a unique product, service, or result.

Program: Coordinated group of related projects and activities managed to realize benefits.

Portfolio: Collection of investments governed to achieve strategic objectives.

Output: Direct product or deliverable produced by project work.

Outcome: Change enabled by one or more outputs.

Benefit: Measurable advantage resulting from an outcome.

Baseline: Approved reference used to measure and control performance.

Work breakdown structure: Hierarchical decomposition of total deliverable scope.

Critical path: Longest logical path through a schedule network under stated assumptions.

Stage gate: Formal decision point authorizing continuation, redirection, pause, or termination.

Assurance: Independent evidence-based examination of delivery fitness and controls.

Earned value: Budgeted value of work actually completed.

Planned value: Budgeted value of work scheduled to be completed.

Actual cost: Cost incurred for work performed.

Configuration management: Control of identified products and their approved changes.

Interface: Boundary where organizations, disciplines, systems, or life-cycle stages interact.

Change control: Formal assessment and authorization of proposed changes.

Benefits owner: Person accountable for realizing and measuring a benefit.

Operational readiness: Evidence that people, processes, systems, and assets can safely operate.

Review Questions

Short Answer Questions

1. Distinguish a project from a program.
2. What is the purpose of a work breakdown structure?
3. Define planned value, earned value, and actual cost.
4. Why is configuration management important in infrastructure delivery?
5. What evidence might be required at a stage gate?

Long Answer Questions

1. Explain how scope, schedule, cost, quality, and risk baselines should be integrated.
2. Discuss the strengths and limitations of earned value management.
3. Explain how assurance differs from project management and why independence matters.
4. Describe a robust change-control process for a major infrastructure program.
5. Analyze why benefits may fail even when a project is delivered within its approved budget.

Analytical / Application Questions

1. A project has PV = $4.0 million, EV = $3.2 million, and AC = $3.5 million. Calculate SV, CV, SPI, and CPI, and recommend two management actions.
2. A station project is on schedule, but its signaling supplier is six weeks late. Explain how the program should assess interfaces, criticality, change, risk, and operational readiness.
3. Design a stage-gate evidence pack for authorization to construct a complex transport facility. Justify the inclusion of each major item.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a program from a project?

A. A program has no defined objectives.

B. A program coordinates related work to realize benefits.

C. A program is always shorter than a project.

D. A program excludes operational change.

Correct Answer: B. A program coordinates related work to realize benefits.

Question 2

If PV = $600,000, EV = $500,000, and AC = $550,000, what is the CPI?

A. 0.833

B. 0.909

C. 1.091

D. 1.200

Correct Answer: B. 0.909

Question 3

What does a negative schedule variance in EVM indicate?

A. The project is necessarily late by a specific number of days.

B. Actual cost is below budget.

C. Less budgeted work has been earned than was planned.

D. Quality requirements have failed.

Correct Answer: C. Less budgeted work has been earned than was planned.

Question 4

What is the primary purpose of a stage gate?

A. To eliminate all project risk.

B. To authorize continuation based on evidence.

C. To replace detailed planning.

D. To calculate contractor invoices.

Correct Answer: B. To authorize continuation based on evidence.

Question 5

Which item is most directly associated with configuration management?

A. Controlling approved versions and changes to technical products.

B. Selecting annual tax rates.

C. Assigning employee holidays only.

D. Forecasting inflation without a baseline.

Correct Answer: A. Controlling approved versions and changes to technical products.

Question 6

Who should normally be accountable for realizing a program benefit?

A. An identified benefit owner.

B. Only the quantity surveyor.

C. The document controller in every case.

D. No one, because benefits are automatic.

Correct Answer: A. An identified benefit owner.

Question 7

Which is a limitation of earned value management?

A. It cannot combine scope and cost information.

B. It always predicts the completion date exactly.

C. It may conceal quality problems if progress measures are weak.

D. It requires no baseline.

Correct Answer: C. It may conceal quality problems if progress measures are weak.

Question 8

What is the main purpose of an interface register?

A. To record boundaries, dependencies, owners, and required exchanges.

B. To replace the risk register entirely.

C. To authorize every payment automatically.

D. To list only completed activities.

Correct Answer: A. To record boundaries, dependencies, owners, and required exchanges.

Question 9

Using EAC = BAC ÷ CPI, what is EAC when BAC = $1,000,000 and CPI = 0.8?

A. $800,000

B. $1,080,000

C. $1,200,000

D. $1,250,000

Correct Answer: D. $1,250,000

Question 10

Which practice best supports operational readiness?

A. Excluding operators until after opening.

B. Testing only construction quantities.

C. Verifying staff, procedures, systems, maintenance information, and emergency arrangements.

D. Treating handover documents as optional.

Correct Answer: C. Verifying staff, procedures, systems, maintenance information, and emergency arrangements.