Project and Operations Risk Management

Introduction and context

Operations managers increasingly deliver change through projects: implementing an enterprise resource planning system, expanding a warehouse, introducing automation, redesigning a service process, or recovering from a supply interruption. A project is temporary and produces a defined deliverable; operations are continuing activities that produce goods or services. The two are interdependent. A project must be planned so that its outputs can be operated safely, reliably and economically, while operational risks may determine whether the project succeeds.

Project management therefore involves more than preparing a schedule. It requires a coherent scope, work breakdown structure (WBS), network logic, resource plan, cost baseline, performance controls and risk responses. Risk management complements this planning by identifying uncertainty, assessing its consequences and preparing proportionate responses. Business continuity and resilience extend the analysis beyond a single project to the organisation’s ability to continue and recover from disruption.

Learning objectives

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

1. Distinguish projects, programmes and operations in an operational environment.
2. Construct a work breakdown structure and a logic-based project network.
3. Calculate critical-path dates, float and PERT expected duration.
4. Allocate constrained resources and evaluate schedule and cost performance using earned value.
5. Develop and maintain an operational risk register.
6. Apply FMEA to prioritise process and equipment risks.
7. Design practical business-continuity and resilience measures.
8. Evaluate governance, ethical, technological and implementation issues in risk management.

1. Project–operations integration

A project has a temporary organisation, a defined start and finish, and a unique or substantially changed output. Operations are repetitive or continuously managed activities. A programme coordinates related projects to obtain benefits that would not arise from managing them separately. In practice, an operations manager may be a project sponsor, subject-matter expert, process owner or future user of the project output.

The project life cycle commonly includes initiation, planning, execution, monitoring and control, and closure. These stages are not strictly linear: new information can require replanning. A useful governance distinction is:

A project should have a measurable business case. Typical benefits include lower unit cost, greater capacity, improved quality, faster response or regulatory compliance. Benefits should not be claimed merely because deliverables are completed; they must be measured after transition into operations.

2. Scope definition and the work breakdown structure

Scope describes what the project will and will not deliver. Weak scope definition creates scope creep, rework and disputes. A scope statement normally identifies the objective, deliverables, exclusions, assumptions, constraints, acceptance criteria and major milestones.

The WBS is a hierarchical decomposition of the total project scope. It breaks deliverables into progressively smaller work packages that can be estimated, assigned, scheduled and controlled. The WBS is deliverable-oriented rather than simply a list of departments or activities. The 100% rule states that the WBS should include all work required to produce the agreed scope, including project management and transition work, but should not include unapproved extras.

For example, a warehouse automation project might be decomposed into:

• 1.0 Warehouse automation project
• 1.1 Requirements and design
• 1.2 Supplier procurement
• 1.3 Site preparation
• 1.4 Equipment installation
• 1.5 Software integration
• 1.6 Testing and acceptance
• 1.7 Training and operational handover

A work package should have a clear output, responsible owner, estimated effort and cost, quality criteria, dependencies and completion evidence. A WBS dictionary records these details and reduces ambiguity. The WBS should be approved through change control; otherwise the schedule and cost baseline have no stable reference.

3. Scheduling: dependencies, critical path and float

Activities are connected by logical relationships. Finish-to-start means the successor cannot start until the predecessor finishes. Start-to-start, finish-to-finish and finish-to-start with leads or lags may be used when operationally justified. The network should reflect real work logic, not preferred departmental sequence.

For an activity with duration d, the forward pass calculates earliest start (ES) and earliest finish (EF):

For activities with several predecessors, ES is the largest predecessor EF. The backward pass calculates latest finish (LF) and latest start (LS):

For an activity with several successors, LF is the smallest successor LS. Total float is:

Here, d, ES, EF, LS and LF are expressed in consistent time units, such as working days. These calculations assume the network logic and activity durations are valid, resources are available as planned, and the schedule uses a stated calendar. Activities with zero total float form at least one critical path. Delaying a critical activity generally delays the project completion date, although alternative critical paths may emerge after changes.

Worked example: critical path

Consider the following activities, measured in working days:

Forward pass: A finishes at day 3. B finishes at day 7 and C at day 8. D finishes at day 14. E must wait for both B and D, so ES = 14 and EF = 18. F finishes at day 21. The project duration is therefore 21 working days. The controlling path is A–C–D–E–F, with duration 3 + 5 + 6 + 4 + 3 = 21 days. The path A–B–E–F is 14 days and has 7 days of path length difference, subject to detailed float calculation.

Critical-path analysis is a model, not a guarantee. Resource constraints, calendars, rework, approvals and uncertain durations may invalidate a purely deterministic result. Schedule risk analysis should therefore examine ranges and correlations rather than rely only on one critical path.

4. PERT and uncertainty

The Programme Evaluation and Review Technique (PERT) represents an activity using three time estimates: optimistic time a, most likely time m and pessimistic time b. The conventional beta-distribution approximation is:

The approximate activity variance is:

where te is expected duration and σ² is variance, in squared time units. The estimates should refer to the same work content and calendar. PERT is most useful when uncertainty is primarily duration uncertainty and estimates are made independently. It does not automatically model resource contention, scope changes or correlated delays.

If activities on a path are treated as independent, expected path duration is the sum of expected durations and path variance is the sum of activity variances:

The independence assumption is important. For correlated activities, variance cannot simply be added without considering covariance. In practice, simulation or structured expert review may be more credible than a false precision based on PERT.

For example, if an approval activity has a = 2, m = 5 and b = 8 days, its expected duration is (2 + 20 + 8) ÷ 6 = 5 days, and its standard deviation is (8 − 2) ÷ 6 = 1 day. A manager should communicate that 5 days is an expected estimate, not a promised completion date.

5. Resource allocation and schedule optimisation

A feasible schedule requires people, equipment, materials, information and facilities at the required time. Resource allocation assigns available capacity to activities. Resource loading shows demand over time; a resource histogram reveals peaks and periods of underuse.

When demand exceeds capacity, the manager may use resource levelling, which changes activity timing and may extend the project, or resource smoothing, which uses available float while preserving the completion date where possible. Other responses include changing work methods, adding shifts, outsourcing, cross-training, using alternative equipment or changing the sequence. Crashing adds resources to shorten duration, while fast-tracking overlaps activities that were previously sequential; both increase cost or risk and require quality controls.

Resource decisions should consider skill, fatigue, safety, learning curves, contractual restrictions and operational consequences. A mathematically shorter schedule may be inferior if it creates unsafe overtime, excessive handovers or an unmanageable commissioning risk.

6. Cost planning and earned value management

A time-phased cost baseline assigns approved budget to scheduled work. Earned value management (EVM) compares planned work, completed work and actual expenditure. The principal measures are:

• Planned Value (PV): authorised budget for work scheduled by a status date.
• Earned Value (EV): authorised budget for work actually completed by that date.
• Actual Cost (AC): cost incurred for the completed work by that date.

The schedule variance and cost variance are:

The schedule performance index and cost performance index are:

PV, EV and AC must use the same currency and status date. SV is a value-based schedule indicator, not a number of days; a positive SV does not prove that the completion date is safe. CPI below 1 indicates that more cost has been spent than the budgeted value of completed work.

If performance to date is expected to continue, a simple estimate at completion is:

where BAC is the budget at completion. This formula assumes current cost efficiency is representative of the remaining work. Other forecasts are appropriate when the initial variance was exceptional or when future work has been re-estimated. Estimate to complete is ETC = EAC − AC, and variance at completion is VAC = BAC − EAC.

Worked EVM example

At the reporting date, PV = £80,000, EV = £72,000, AC = £90,000 and BAC = £240,000. Therefore:

• SV = £72,000 − £80,000 = −£8,000.
• CV = £72,000 − £90,000 = −£18,000.
• SPI = 72,000 ÷ 80,000 = 0.90.
• CPI = 72,000 ÷ 90,000 = 0.80.
• EAC = 240,000 ÷ 0.80 = £300,000.

The project has achieved 90% of the budgeted progress planned by the date and is spending £1.25 for each £1 of budgeted value earned. If the trend persists, the forecast overrun is £60,000. Management should investigate causes rather than mechanically accept the forecast: late design information, inaccurate estimates, supplier claims and scope changes require different responses.

7. Operational risk management

Risk is the effect of uncertainty on objectives. An effect may be negative (a threat) or positive (an opportunity). An issue is a condition that has already occurred; it should not be hidden in a risk register as though it were still uncertain. Risk management is a continuous cycle of identification, analysis, response, monitoring and communication.

Risk identification methods include workshops, interviews, checklists, lessons learned, process mapping, assumptions analysis, supplier review, scenario analysis and analysis of incidents or near misses. Categories should be broad enough to expose systemic threats: strategic, commercial, financial, operational, technical, supply, legal, information-security, health-and-safety, environmental and reputational risks.

A risk register typically includes:

A qualitative matrix may classify probability and impact as low, medium or high. A quantitative expected-loss estimate is sometimes used:

where p is probability between 0 and 1 and I is the monetary impact. EMV is useful for aggregating certain financial exposures but should not be treated as the complete value of a risk. Safety, legal and reputational impacts may be unacceptable even when their expected monetary value is small. Probability and impact scales must be defined, calibrated and applied consistently.

Responses to threats include avoid, reduce, transfer or accept. Responses to opportunities include exploit, enhance, share or accept. Transfer does not remove responsibility: insurance, a contract or outsourcing may transfer financial exposure while leaving safety, ethical and reputational obligations with the organisation.

8. Failure Mode and Effects Analysis

FMEA is a structured, bottom-up method for examining how a product or process can fail. For each failure mode, the team records its effect, cause, existing prevention and detection controls, and proposed action. Traditional FMEA scores severity (S), occurrence (O) and detection (D), commonly on 1–10 ordinal scales, and calculates a risk priority number:

Higher RPN values indicate a prioritisation signal, not a probability or expected loss. Because the scales are ordinal, an RPN of 100 is not necessarily twice as serious as an RPN of 50. A high-severity failure should receive attention even if its RPN is moderate. Teams should document scoring criteria and consider action priority, legal requirements and detectability of catastrophic failures.

FMEA is strongest when conducted cross-functionally by people who understand design, operations, maintenance, quality and users. It can become ineffective when completed as a paperwork exercise, when controls are claimed without evidence, or when the team focuses on individual component failures and overlooks interactions and common causes. Fault-tree analysis, event-tree analysis and bow-tie analysis may complement FMEA for complex or high-hazard systems.

9. Business continuity and operational resilience

Business continuity management prepares an organisation to continue delivering important products and services during disruption. Resilience is broader: it includes anticipating, absorbing, adapting to and recovering from shocks while maintaining essential capabilities.

A business impact analysis (BIA) identifies critical activities, dependencies, consequences of interruption and recovery priorities. Important terms include:

• Maximum tolerable period of disruption (MTPD): longest period an activity can be unavailable before unacceptable harm occurs.
• Recovery time objective (RTO): targeted time to restore an activity or service.
• Recovery point objective (RPO): maximum tolerable period of data loss, expressed as time between the last recoverable copy and disruption.
• Minimum business continuity objective (MBCO): minimum acceptable level of service during disruption.

RTO should normally be shorter than MTPD, allowing time to stabilise and recover before the maximum is reached. Recovery strategies may include alternate sites, manual workarounds, cross-trained staff, dual suppliers, spare capacity, segmented information systems, backup power and tested data recovery. A plan that exists only in a document is not a capability. Exercises, maintenance, contact verification and post-exercise improvement are essential.

Resilience is supported by visibility and diversity. Single-source supply, common software dependencies, concentrated skills and just-in-time inventories may be efficient but create vulnerability. Resilience does not mean eliminating every risk; it means making important failure modes tolerable and recoverable at a justified cost.

10. Integrated risk, continuity and project control

Project risk controls should be linked to operational risk controls. A new automated line may have project risks involving installation and commissioning, followed by operational risks involving cybersecurity, maintenance skills and spare parts. The handover should transfer open risks, control owners, procedures, training evidence, maintenance requirements and emergency arrangements to the process owner.

A practical integrated cycle is:

1. Define objectives, scope, acceptance criteria and operational success measures.
2. Build the WBS and identify resources, dependencies and assumptions.
3. Develop the schedule, cost baseline and risk register together.
4. Analyse high-priority risks using FMEA, scenarios or quantitative methods where justified.
5. Assign owners and implement preventive, detective and recovery controls.
6. Monitor milestones, leading indicators, risk triggers, EVM and quality data.
7. Escalate changes through governance and protect the approved baseline.
8. Test continuity arrangements and complete a controlled operational handover.
9. Capture lessons and verify benefits after implementation.

Leading indicators may include overdue design decisions, supplier quality defects, safety observations, staff turnover, unresolved interface issues and declining preventive-maintenance compliance. Lagging indicators include incidents, missed milestones, downtime and customer complaints. A balanced dashboard uses both.

Illustrative case: Northbridge Medical Supplies distribution upgrade

Background

Northbridge Medical Supplies, a fictional regional distributor, planned a project to introduce barcode-directed picking and a new warehouse management system. The objectives were to increase order capacity by 30%, reduce picking errors and maintain uninterrupted delivery of urgent medical products.

Problem

The initial proposal focused on software installation and had a target completion date but no detailed WBS. The operations team identified risks that were absent from the first plan: inaccurate inventory data, dependence on a single network link, insufficient scanner training, supplier delay, and inability to process emergency orders during a system outage.

Analysis

The project team created a deliverable-based WBS covering data cleansing, configuration, interfaces, equipment, testing, training, cutover and contingency operation. A network analysis showed that interface testing and data validation controlled the planned go-live date. FMEA identified incorrect product-lot assignment as a high-severity failure, even though its occurrence was expected to be low. A BIA established that urgent-order processing had an MTPD of four hours, an RTO of two hours and an RPO of fifteen minutes for transaction data.

The risk register assigned owners and triggers. For example, “inventory accuracy below 99.5% during validation” triggered additional cycle counting; “network failover test unsuccessful” blocked go-live. The team planned a dual network connection, offline emergency-picking procedures, a read-only backup catalogue, supplier acceptance testing and staged training. A pilot was conducted in one warehouse zone before full deployment.

Outcome

The pilot revealed that a scanner interface failed when product labels contained an unexpected character. Correcting the interface before full deployment prevented a likely operational failure. The project started the final cutover with a tested rollback plan and a staffed manual process. Post-implementation measures showed improved picking accuracy and capacity, while continuity exercises demonstrated that urgent orders could be processed during a simulated system outage.

Learning points

The case illustrates that a schedule is not a risk plan, a completed installation is not an operational benefit, and a high-severity failure should not be overlooked because its numerical priority score is modest. Early user involvement, explicit acceptance criteria, realistic testing and operational continuity arrangements converted technical implementation into a controlled business change.

11. Governance, ethics and technology

Risk decisions must be transparent, proportionate and accountable. Managers should not suppress bad news to protect a milestone, manipulate probability scores to obtain approval, or transfer unacceptable hazards to contractors without effective oversight. Health and safety, environmental protection, accessibility, privacy and product integrity must be treated as objectives, not optional costs.

Regulatory requirements vary by sector and jurisdiction, but organisations should maintain a compliance register, identify responsible owners, preserve evidence and obtain specialist advice where necessary. Contractual risk allocation should be understandable and matched to the party able to control the risk.

Digital tools can support integrated schedules, dashboards, scenario modelling, sensor alerts and automated risk reporting. Artificial intelligence may assist with anomaly detection, text classification, forecast analysis and lessons-learned retrieval. However, AI outputs can reproduce biased historical data, confuse correlation with causation or conceal uncertainty. Human approval, data governance, access control, audit trails, cybersecurity and model validation remain necessary. Automation should not replace professional judgement for safety-critical or ethically significant decisions.

12. Limitations and best practice

No model predicts the future completely. Critical-path calculations depend on logic and estimates; PERT depends on assumptions about distributions; EVM can mislead when scope is unstable or progress is difficult to measure; FMEA scoring is subjective; and risk matrices can create artificial precision. These limitations are managed through triangulation, sensitivity analysis, scenario testing, independent challenge and frequent review.

Best practice includes:

• establish a clear scope and measurable operational benefits;
• use a deliverable-based WBS and maintain a WBS dictionary;
• integrate schedule, resources, cost and risk rather than managing separate spreadsheets;
• distinguish risks, issues, assumptions and changes;
• assign named owners with authority and due dates;
• prioritise high-severity and systemic risks, not only high numerical scores;
• use leading indicators and define escalation triggers;
• test continuity plans under realistic conditions;
• involve operators, suppliers, maintenance specialists and affected stakeholders;
• document assumptions, uncertainty and decision rationale;
• close the learning loop through benefits reviews and lessons learned.

Chapter Summary

Project and operations risk management integrates temporary change with continuing service delivery. Scope is controlled through a deliverable-based WBS, while network logic supports critical-path analysis, float calculation and realistic scheduling. PERT provides an uncertainty-aware estimate when its assumptions are understood. Resource allocation must balance capacity, cost, quality, safety and completion date. Earned value compares planned value, earned value and actual cost to identify performance trends, but its indicators require careful interpretation.

Risk management identifies uncertain events, assesses their effects, assigns owners and implements responses. Risk registers provide governance; FMEA analyses failure modes and controls, while severity must not be hidden by an aggregate score. Business impact analysis establishes continuity priorities through MTPD, RTO, RPO and minimum service objectives. Resilience depends on tested recovery capability, diversity, visibility and adaptation. Ethical governance, stakeholder involvement, cybersecurity and critical evaluation are essential when digital and AI tools support operational decisions.

Key Terms

Project: Temporary undertaking creating a defined deliverable or change.

Operations: Continuing activities that produce goods or services.

Work breakdown structure (WBS): Hierarchical decomposition of total project scope.

Work package: Manageable WBS component with defined output and control information.

Critical path: Longest controlling path through a project network.

Total float: Time an activity can be delayed without delaying the relevant project completion date.

PERT: Estimation technique using optimistic, most likely and pessimistic durations.

Resource levelling: Adjusting schedule timing to resolve resource over-allocation.

Crashing: Adding resources or cost to shorten activity duration.

Earned value (EV): Budgeted value of work actually completed.

Cost performance index (CPI): Earned value divided by actual cost.

Risk: Effect of uncertainty on objectives.

Risk register: Controlled record of risks, controls, owners and responses.

FMEA: Structured analysis of failure modes, effects, causes and controls.

RPN: Product of severity, occurrence and detection scores in traditional FMEA.

Business impact analysis: Assessment of disruption consequences and recovery priorities.

RTO: Target time to restore a service or activity.

RPO: Maximum acceptable period of data loss.

Operational resilience: Ability to anticipate, withstand, adapt to and recover from disruption.

Review Questions

Short Answer Questions

1. What distinguishes a project from an operation?
2. What is the purpose of a work breakdown structure?
3. Define total float and explain its relationship to the critical path.
4. What are PV, EV and AC in earned value management?
5. Distinguish RTO from RPO.

Long Answer Questions

1. Explain how a project manager can integrate scope, schedule, resources, cost and risk controls.
2. Describe the forward-pass and backward-pass methods for critical-path analysis, including their assumptions.
3. Explain PERT, including its three estimates, formulas and limitations.
4. Discuss how FMEA and a risk register complement one another in operational risk management.
5. Explain how a business impact analysis supports continuity and resilience planning.

Analytical / Application Questions

1. A project has PV = £120,000, EV = £108,000, AC = £135,000 and BAC = £360,000. Calculate SV, CV, SPI, CPI and the simple EAC forecast. Interpret the results and identify two management actions.
2. Construct a risk response for a single-source supplier whose disruption could stop a critical production line. Compare prevention, transfer, acceptance and recovery measures.
3. A hospital distribution system is being replaced. Develop a short WBS, identify two likely critical dependencies, propose three FMEA controls and specify suitable continuity objectives for urgent orders.

Multiple Choice Questions with Answers

Question 1

Which statement best describes a work breakdown structure?

A. A hierarchical decomposition of the total project scope

B. A list of employee salaries by department

C. A record of incidents that have already occurred

D. A forecast of annual sales demand

Correct Answer: A. A hierarchical decomposition of the total project scope

Question 2

An activity has ES = 6 working days and duration = 4 working days. What is its EF?

A. 2 days

B. 10 days

C. 24 days

D. 1.5 days

Correct Answer: B. 10 days

Question 3

Which activities normally form a critical path?

A. Activities with the highest individual cost

B. Activities assigned to the largest team

C. Activities with zero total float

D. Activities with the lowest risk score

Correct Answer: C. Activities with zero total float

Question 4

Using PERT, an activity has optimistic time 2 days, most likely time 5 days and pessimistic time 8 days. What is its expected duration?

A. 4 days

B. 5 days

C. 6 days

D. 8 days

Correct Answer: B. 5 days

Question 5

If EV = £72,000 and AC = £90,000, what is the CPI?

A. 0.80

B. 1.25

C. £18,000

D. £162,000

Correct Answer: A. 0.80

Question 6

Which EVM measure compares earned value with planned value?

A. CPI

B. CV

C. SPI

D. EAC

Correct Answer: C. SPI

Question 7

What is the primary purpose of a risk owner?

A. To guarantee that the risk cannot occur

B. To monitor the risk and ensure its response is managed

C. To approve every project invoice

D. To replace the project sponsor

Correct Answer: B. To monitor the risk and ensure its response is managed

Question 8

In traditional FMEA, RPN is calculated as:

A. Severity + occurrence + detection

B. Severity × occurrence × detection

C. Probability × schedule duration

D. Cost ÷ earned value

Correct Answer: B. Severity × occurrence × detection

Question 9

What does RPO measure?

A. The time required to train all staff

B. The maximum acceptable period of data loss

C. The longest project activity

D. The time before a supplier contract expires

Correct Answer: B. The maximum acceptable period of data loss

Question 10

Which statement about resource levelling is correct?

A. It resolves resource over-allocation and may extend the project

B. It always reduces total project cost

C. It eliminates the need for a risk register

D. It means adding resources to every activity

Correct Answer: A. It resolves resource over-allocation and may extend the project