Projects are temporary systems established to create a unique product, service, capability, or change. Unlike repetitive operations, which emphasize stability, projects operate under a defined beginning and end, a specified scope, constrained resources, and an intended outcome. Examples include implementing an enterprise-resource-planning system, constructing a plant, launching a product, relocating a distribution centre, developing a software platform, and executing a major maintenance shutdown.

Project management is therefore a central concern of production and operations management. It converts strategic intentions into coordinated work while balancing scope, time, cost, quality, risk, resources, and stakeholder expectations. Temporary operations management extends this perspective to the design and control of short-lived operating systems, such as event operations, emergency response, commissioning, turnaround maintenance, and transformation programmes.

A project is not simply a large task list. It is a socio-technical system involving interdependent activities, decision rights, information flows, suppliers, users, regulators, and organizational learning. Effective managers must plan sufficiently to provide direction while remaining adaptable when assumptions change.

Learning Objectives

1. The Nature of Projects and Temporary Operations

A project may produce a deliverable, whereas a programme coordinates related projects to obtain benefits that individual projects cannot achieve independently. A portfolio contains projects, programmes, and operational work selected to support organizational strategy. Governance determines how these entities are authorized, controlled, and reviewed.

Temporary operations share project characteristics but usually emphasize the design and operation of a temporary service or capacity. For example, a sports event requires temporary facilities, workforce rosters, safety controls, ticketing, transport, and contingency arrangements. The event is temporary, but its operational performance must be managed in real time.

The traditional “iron triangle” of scope, time, and cost is useful but incomplete. Quality, safety, benefits realization, sustainability, resilience, and stakeholder legitimacy may be more important than finishing cheaply. A project can be delivered on time and within budget yet fail if customers do not adopt its output or if the expected benefits do not materialize.

2. Project Life Cycle and Delivery Logic

A generic life cycle comprises initiation, planning, execution, monitoring and control, and closure. These are not always strictly sequential. Agile projects revisit planning and execution repeatedly, while regulated projects may require formal stage gates.

Initiation

Initiation establishes the business need, sponsor, high-level scope, expected benefits, constraints, assumptions, and authority to proceed. The business case should identify alternatives, costs, benefits, risks, and the consequences of not acting. A project charter converts this rationale into a formally authorized mandate.

Planning

Planning defines deliverables, work packages, activities, dependencies, estimates, resources, procurement, quality criteria, communications, risks, and baselines. Planning is not a one-time administrative exercise; it is a mechanism for exposing uncertainty before resources are committed.

Execution and control

Execution produces deliverables. Control compares actual performance with approved baselines, manages changes, resolves issues, forecasts outcomes, and protects quality and safety. A baseline is a formally approved reference plan; changes should be traceable rather than silently absorbed.

Closure and transition

Closure confirms acceptance, transfers the output to the operating owner, closes contracts, releases resources, captures lessons, and evaluates whether benefits are likely to be realized. Operational readiness is especially important: training, maintenance, data migration, support, and ownership must be in place before handover.

3. Work Breakdown Structures

A work breakdown structure (WBS) is a hierarchical decomposition of the total project scope into progressively smaller components. The lowest useful components are work packages. A WBS is deliverable-oriented: it describes what must exist, not merely the departments that will perform the work.

A sound WBS follows the 100-percent rule: the hierarchy should represent all approved project scope, and each lower level should collectively represent the complete scope of its parent. Work should not be counted twice, and exclusions should be explicit.

Level	WBS element
1	Warehouse automation project
2	Design; equipment; software; facility preparation; training and launch
3	Under equipment: conveyors; sensors; controls; testing
4	Under testing: factory acceptance; site acceptance; performance trial

A work package should have a clear owner, deliverable, acceptance criteria, estimate, planned start and finish, dependencies, and budget. The WBS should be linked to a responsibility assignment matrix, often a RACI matrix: responsible, accountable, consulted, and informed. The WBS, schedule, cost plan, risk register, and procurement plan should use consistent codes so that performance can be integrated.

Common WBS errors include organizing only by organizational departments, omitting project management work, decomposing to excessive detail, mixing deliverables and activities at the same level, and failing to include transition or benefits activities.

4. Network Scheduling and the Critical Path Method

A network diagram represents logical relationships among activities. In an activity-on-node representation, each node is an activity and arrows show precedence. Typical relationships are finish-to-start, start-to-start, finish-to-finish, and start-to-finish, although finish-to-start should not be used automatically when overlap is operationally possible.

The critical path method (CPM) uses deterministic activity durations. For each activity, the forward pass calculates earliest times:

where ES_i is the earliest start of activity i, EF_i is its earliest finish, and d_i is its duration. For an activity with predecessors, its earliest start is the maximum earliest finish of its immediate predecessors:

where j represents each immediate predecessor. The project duration is the earliest finish of the final activity or the maximum earliest finish among terminal activities.

The backward pass calculates latest allowable times without delaying the project:

For an activity with successors, its latest finish is the minimum latest start of its immediate successors:

Activities with zero total float form at least one critical path. Criticality can change when durations, logic, calendars, or constraints change. A critical activity is not necessarily the most important activity; safety-critical or legally constrained work may have substantial float but still require close control.

Worked example: CPM

Activity	Duration (days)	Immediate predecessor
A	3	—
B	4	A
C	5	A
D	2	B
E	3	C
F	2	D, E

The paths are A-B-D-F = 3 + 4 + 2 + 2 = 11 days and A-C-E-F = 3 + 5 + 3 + 2 = 13 days. Therefore, the project duration is 13 days and the critical path is A-C-E-F. Activity B-D has two days of path slack relative to the critical path. This result assumes the stated dependencies, uninterrupted work, fixed calendars, and unlimited availability of the required resources.

CPM is valuable because it reveals schedule sensitivity and supports what-if analysis. Its limitations include deterministic durations, difficulty representing resource constraints, and the risk that managers focus narrowly on the calculated path while ignoring emerging risks and near-critical paths.

5. PERT and Schedule Uncertainty

The Program Evaluation and Review Technique (PERT) models uncertain activity duration using three estimates: optimistic a, most likely m, and pessimistic b. The expected duration is:

Here, σ² is variance in squared time units. PERT is based on a beta-like approximation and assumes the three estimates are meaningful, the activity’s uncertainty is represented by them, and dependencies are correctly specified. It should not be treated as a guarantee or as proof that project duration is normally distributed.

For a path, expected duration is the sum of expected activity durations. If activity durations are treated as independent, path variance is the sum of activity variances:

and path standard deviation is σ_path = √(σ²_path). A rough probability that a path will finish by deadline D can be estimated using a normal approximation:

where μ_path is expected path duration. This approximation becomes unreliable when paths merge, activity durations are strongly correlated, or the critical path changes under uncertainty. Simulation, such as Monte Carlo analysis, is preferable for complex schedules.

Suppose an activity has a = 2, m = 5, and b = 8 days. Its expected duration is (2 + 4×5 + 8) ÷ 6 = 5 days, and its variance is ((8 − 2) ÷ 6)² = 1 day². The estimates are useful only if the optimistic and pessimistic values reflect credible operating conditions rather than arbitrary optimism and pessimism.

6. Time–Cost Trade-offs and Crashing

Crashing reduces activity duration by applying additional resources, overtime, alternative methods, or premium suppliers. It should be considered only when the activity lies on the current critical path or when the reduction creates a strategically valuable outcome. Crashing a non-critical activity may produce no project-level benefit.

Cost slope = (Crash cost − Normal cost) ÷ (Normal time − Crash time)

The units are cost per unit of time saved. The usual procedure is to identify the critical path, select the lowest-cost crashable activity on that path, reduce its duration within feasible limits, recalculate the network, and repeat until the target is met or further crashing is uneconomic or infeasible.

Suppose an activity normally takes 10 days and costs $40,000; it can be reduced to 7 days at $52,000. Its cost slope is ($52,000 − $40,000) ÷ (10 − 7) = $4,000 per day saved. This calculation assumes a reasonably linear cost-duration relationship between the stated normal and crash points. In real projects, overtime may create nonlinear costs, rework, fatigue, safety exposure, or quality loss.

A rational decision compares incremental crash cost with the value of earlier completion, contractual damages avoided, capacity released, or strategic benefit gained. Crashing should never bypass safety, regulatory approval, testing, or quality acceptance.

7. Resource Allocation and Resource-Constrained Scheduling

A time-feasible schedule may be resource-infeasible. If two activities require the same scarce engineer, machine, or specialist at the same time, precedence logic alone does not solve the conflict. Resource management includes capacity planning, skills analysis, procurement, cross-training, leveling, smoothing, subcontracting, and prioritization.

Resource smoothing adjusts activities within available float to reduce peaks while preserving the target completion date. Resource leveling resolves over-allocation even when the completion date must move. Managers should distinguish a genuine capacity constraint from a planning assumption that can be changed through hiring, outsourcing, shift design, or technology.

Useful heuristics include prioritizing activities with low float, high downstream impact, safety significance, or contractual importance. However, heuristic decisions should be tested against the whole network because locally efficient choices can increase total makespan. Resource-constrained project scheduling is computationally difficult for large networks, so optimization software, simulation, and expert judgment are commonly combined.

Resource allocation also has a behavioural dimension. Excessive multitasking increases switching costs, hides delays, and reduces throughput. A focused team with explicit priorities may deliver faster than a nominally larger team whose members are continuously interrupted.

8. Earned-Value Management

Earned-value management (EVM) integrates scope, schedule, and cost. At a measurement date, three quantities are required:

Schedule variance SV and cost variance CV are expressed in monetary value, not calendar time. SPI < 1 indicates less earned work than planned at the measurement point, while CPI < 1 indicates cost inefficiency. These indices are dimensionless because the numerator and denominator use the same value units.

This assumes current cost efficiency will continue. Other forecasts may use actual cost plus a revised estimate of remaining work:

where ETC is the estimate to complete. The appropriate formula depends on whether past variance is expected to recur, whether scope has changed, and whether remaining work has been independently re-estimated.

Worked EVM example

The project is behind the planned value curve and spending $1.33 for every dollar of budgeted work earned. The forecast is not a certainty; management should investigate scope definition, accounting timing, productivity, procurement, and quality-related rework before accepting it.

9. Predictive, Agile, and Hybrid Delivery

Predictive approaches define substantial scope and sequence before execution. They are appropriate when requirements are stable, interfaces are known, change is costly, and regulatory or contractual evidence is required. Stage gates, design reviews, baselines, and formal change control are prominent.

Agile approaches deliver small increments, obtain frequent feedback, and reprioritize a transparent backlog. Scrum, Kanban, and related methods emphasize collaboration, short feedback cycles, visual flow, and adaptation. Agile is not an absence of planning: product goals, release planning, capacity, architecture, quality criteria, and governance remain necessary.

A hybrid approach combines predictive and adaptive elements. For example, a pharmaceutical facility may use predictive controls for validation, construction, and regulatory submissions while using agile teams for software configuration and user-interface development. The key question is not whether one method is fashionable, but which elements of scope, uncertainty, risk, and compliance require which control logic.

Agile metrics must be interpreted carefully. Velocity is a local planning indicator, not a universal productivity measure. A team should not inflate story points to appear faster. Flow measures such as cycle time, work-in-progress, throughput, and blocked time often provide more useful operational insight.

10. Risk Management and Uncertainty

A risk is an uncertain event or condition that may affect objectives positively or negatively. An issue is a condition that has already occurred. Risk management is a continuous process:

Threat responses include avoid, mitigate, transfer, and accept. Opportunity responses include exploit, enhance, share, and accept. Contingency reserves address identified risks, whereas management reserves are held for unforeseen work subject to governance authority.

A probability–impact matrix is useful for screening but can create false precision. A risk rated “high” because of a multiplied score may deserve less attention than a low-probability event with catastrophic safety consequences. Quantitative analysis may use expected monetary value:

where p_i is the probability of outcome i and impact_i is its monetary impact. EMV supports portfolio decisions under uncertainty but should not be interpreted as a guaranteed financial result. Safety, legal, human, and reputational impacts should not be reduced to money alone.

Risk owners must possess authority and resources. A risk register without actions, triggers, dates, and accountable owners is merely a list. Common risk sources include immature requirements, optimistic estimates, supplier failure, integration defects, cyber threats, labour shortages, regulatory change, weather, stakeholder resistance, and benefits that depend on behaviour after handover.

11. Project Governance, Ethics, and Control

Project governance defines who decides, who is accountable, what information is required, and how exceptions are escalated. A practical governance structure may include a sponsor, project manager, steering committee, product or business owner, technical authority, assurance function, and operational owner.

Ethical project management requires truthful reporting, protection of workers and users, fair procurement, respect for privacy, avoidance of conflicts of interest, and willingness to stop unsafe work. “Green” claims should be supported by evidence, and artificial schedule optimism should not be used to secure authorization. Governance should create psychological safety so that team members can report defects, risks, harassment, or misconduct without retaliation.

Digital dashboards and artificial intelligence can support estimating, anomaly detection, document search, schedule risk analysis, resource forecasting, and predictive maintenance. However, data may be incomplete, biased, commercially sensitive, or generated under inconsistent definitions. AI outputs should be explainable enough for the decision context, checked by competent professionals, and governed for privacy, cybersecurity, intellectual property, and accountability. Automation should strengthen—not replace—responsible judgment.

12. Contemporary Practice and Best Practices

Projects increasingly operate in volatile environments characterized by supply disruption, climate exposure, geopolitical uncertainty, distributed teams, and rapid digital change. Useful contemporary practices include modular design, scenario planning, digital twins, integrated planning tools, collaborative contracting, product operating models, and benefits tracking after delivery.

Best practice is less about applying every tool than about maintaining coherence among objectives, scope, schedule, resources, risk, and governance. Managers should:

13. Illustrative Case: Regional Hospital Digital-Operations Project

Background

A regional hospital decides to replace paper-based medication administration with an integrated electronic medication-management system. The project includes software configuration, barcode devices, wireless upgrades, pharmacy integration, staff training, data migration, clinical testing, and a controlled launch.

Problem

The hospital initially proposes a six-month deadline. Clinical leaders want rapid implementation, while the information-technology team identifies uncertain interfaces and limited availability of nurses for testing. A supplier offers an accelerated configuration at additional cost, but the safety team warns that insufficient user testing could create medication errors.

Analysis

The project team constructs a deliverable-oriented WBS. The network schedule shows that wireless upgrades, interface testing, clinical validation, and training are linked. Although software configuration has a short nominal duration, interface testing is on the critical path. Resource analysis reveals that the same senior nurses are needed for clinical validation and training development. The team therefore levels the schedule rather than assuming unlimited clinical capacity.

A risk workshop identifies risks involving data-quality defects, downtime, user resistance, cyber compromise, supplier delay, and unsafe workarounds. The highest-priority risk is not given a monetary score alone: medication safety requires mandatory clinical acceptance criteria and a go/no-go decision by the clinical governance committee.

The project adopts a hybrid model. Predictive controls govern cybersecurity, procurement, validation evidence, and the hospital-wide cutover. Agile teams configure screens and workflows in short iterations with pharmacists and nurses. A pilot ward provides feedback before wider deployment.

Approach and solution

The sponsor approves a revised nine-month plan. The project uses a WBS-linked schedule, weekly risk review, two formal stage gates, a change-control board, and EVM for cost monitoring. The team establishes acceptance criteria: barcode scanning reliability, interface accuracy, response time, training completion, incident thresholds, and downtime procedures. A contingency plan allows rollback to the previous process if safety indicators deteriorate.

Outcome

The pilot launches two weeks later than the original target but meets the revised clinical acceptance criteria. Early EVM reporting identified configuration rework and prevented premature expansion. Post-launch measurement shows improved medication-record completeness and reduced transcription errors, while benefits ownership remains with hospital operations rather than the temporary project team.

Learning points

The case illustrates that schedule acceleration is not automatically valuable; safety and readiness may dominate calendar objectives. Critical-path analysis must be combined with resource analysis. Hybrid delivery is effective when different work components have different uncertainty and compliance needs. Finally, project success includes safe adoption and benefits realization, not merely technical installation.

Challenges and Limitations

Project methods can create an illusion of control. A precise schedule may conceal uncertain estimates; a risk matrix may conceal severe but rare events; and EVM may report favourable performance when scope has been reduced or quality has been deferred. Network models also simplify human relationships, negotiation, learning, and political behaviour.

Projects may fail through weak sponsorship, unstable requirements, fragmented accountability, poor integration, unrealistic deadlines, inadequate operational ownership, or incentives that reward reporting good news rather than solving problems. Standard methods must therefore be adapted to organizational maturity, industry regulation, project complexity, and stakeholder capability. Methodological discipline is valuable, but professional judgment remains indispensable.

Chapter Summary

Project and temporary operations management coordinates unique, time-bounded work under constraints while protecting value, quality, safety, and stakeholder interests. The WBS defines complete scope through deliverables and work packages. Network scheduling and CPM identify precedence, earliest and latest times, float, and critical paths. PERT incorporates duration uncertainty, while crashing evaluates the cost of reducing activity durations. Resource allocation recognizes that a logically feasible schedule may be impossible with available people or equipment.

Earned-value management integrates scope, cost, and schedule through PV, EV, AC, variances, performance indices, and forecasts. Predictive, agile, and hybrid approaches should be selected according to uncertainty, compliance, interfaces, and the cost of change. Risk management requires active owners, response strategies, triggers, and escalation, not merely a register. Governance establishes authority, assurance, change control, ethical conduct, and benefits accountability. Contemporary project leadership combines analytical tools with transparency, safety, learning, stakeholder engagement, and responsible use of digital and AI technologies.

Key Terms

Project: A temporary endeavour undertaken to create a unique deliverable, service, or result.

Temporary operation: A short-lived operating system designed to deliver a service or capability.

Programme: Related projects and activities managed together to realize broader benefits.

Portfolio: Projects, programmes, and operational investments aligned with strategy.

Work breakdown structure: Hierarchical decomposition of total project scope.

Work package: The lowest manageable WBS component with defined scope, owner, and estimate.

Critical path: The longest-duration path through a schedule network, determining minimum project duration under stated assumptions.

Float: Time an activity may be delayed without violating a defined schedule constraint.

PERT: A technique using optimistic, most-likely, and pessimistic duration estimates.

Crashing: Shortening activity duration by applying additional or more costly resources.

Resource leveling: Adjusting a schedule to resolve resource over-allocation, potentially changing completion date.

Earned value: Budgeted value of work actually completed by a measurement date.

Hybrid delivery: Combination of predictive and adaptive management practices.

Stage gate: Formal decision point at which continuation, revision, or termination is considered.

Project governance: Framework of authority, accountability, controls, and decision processes.

Review Questions

Short Answer Questions

Long Answer Questions

Analytical / Application Questions

Multiple Choice Questions with Answers

Question 1

A. A hierarchy of the total project scope into manageable deliverables and work packages

Correct Answer: A. A hierarchy of the total project scope into manageable deliverables and work packages

Question 2

For an activity with ES = 6 days and duration = 4 days, what is its earliest finish?

Question 3

Which activities form the critical path in the worked network example in the chapter?

Question 4

Using PERT, if a = 2, m = 5, and b = 8 days, what is the expected activity duration?

Question 5

An activity has a normal cost of $40,000 for 10 days and a crash cost of $52,000 for 7 days. What is its cost slope?

Question 6

Correct Answer: A. Moving activities within available float to reduce resource peaks

Question 7

Question 8

Question 9

Correct Answer: B. It combines predictive and adaptive practices according to the work context

Question 10

Correct Answer: B. It is calculated as EV − PV and is expressed in value units

Chapter 13 Project and Temporary Operations Management

Project and Temporary Operations Management

Introduction and Context