Zoo Relocation Project—Part 4: Risk Management

The Zoo project has a zero-casualty mandate. That single constraint reshapes every risk decision — from how risks are identified, to how they are scored, to what responses are acceptable.

Series recap. Parts 1–3 produced the Charter, Stakeholder Plan, Scope Baseline, WBS, and Schedule. Part 4 applies risk management across the project using PMBOK's six-process framework, aligned to ISO 31000:2018.

The Challenge

Most project risk registers are exercises in probability-times-impact arithmetic the sponsor quietly ignores. The Zoo project does not permit this luxury. One sentence from the CEO's letter reshapes everything:

"Every creature must be transported with a zero-percent casualty rate with long-term survival a critical success factor."

Zero. Not "minimise casualties." Not "best practice welfare." Zero.

This phrase converts animal welfare from a quality concern into quality-as-constraint — failure is defined absolutely, not relatively. It forces all welfare risks to the top regardless of calculated probability. And it narrows the universe of acceptable responses: "Accept" is rarely an option for any welfare-impact risk.

The defence parallel is exact. When a submarine program includes "zero loss of life" for sea trials, every risk response is designed against a tolerance of zero, which cascades through design margins, procurement specifications, testing protocols, and governance.

The PM Framework Applied

PMBOK's Risk Management Knowledge Area (Chapter 11) contains six processes performed in order:

11.1 — Plan Risk — Management

11.2 — Identify — Risks

11.3 — Qualitative — Analysis

11.4 — Quantitative — Analysis

11.5 — Plan — Responses

11.6 — Monitor — Risks

Relationship details

From	Relationship	To
11.1 — Plan Risk — Management	leads to	11.2 — Identify — Risks
11.2 — Identify — Risks	leads to	11.3 — Qualitative — Analysis
11.3 — Qualitative — Analysis	leads to	11.4 — Quantitative — Analysis
11.4 — Quantitative — Analysis	leads to	11.5 — Plan — Responses
11.5 — Plan — Responses	leads to	11.6 — Monitor — Risks

The feedback loop from Monitor back to Identify is not cosmetic — new risks emerge continuously. Risk management is the only Knowledge Area whose processes run continuously from start to close.

Step 1: Plan — customised scoring scale

The critical early decision is the scoring scale. The Zoo requires customisation because welfare impact has a zero-tolerance ceiling:

Level 5 welfare is defined as a mandate breach, not a specific count. One casualty equals ten in this scheme because the CEO's letter does not distinguish.

Step 2: Identify — Risk Breakdown Structure

Zoo Project Risks

Technical

External

Organisational

Project Management

Welfare Protocol Failure

Transport Equipment Failure

Enclosure Design Defect

Salvaged Asset Unfit

Regulatory Delay

Site Sale Delay

Media Welfare Incident

Weather During Transport

Key Staff Resignation

Industrial Action

Funding Gap

Scope Creep

Estimation Error

Contractor Non-Performance

Relationship details

From	Relationship	To
Zoo Project Risks	leads to	Technical
Zoo Project Risks	leads to	External
Zoo Project Risks	leads to	Organisational
Zoo Project Risks	leads to	Project Management
Technical	leads to	Welfare Protocol Failure
Technical	leads to	Transport Equipment Failure
Technical	leads to	Enclosure Design Defect
Technical	leads to	Salvaged Asset Unfit
External	leads to	Regulatory Delay
External	leads to	Site Sale Delay
External	leads to	Media Welfare Incident
External	leads to	Weather During Transport
Organisational	leads to	Key Staff Resignation
Organisational	leads to	Industrial Action
Organisational	leads to	Funding Gap
Project Management	leads to	Scope Creep
Project Management	leads to	Estimation Error
Project Management	leads to	Contractor Non-Performance

Red is Technical because technical risks contain the welfare catastrophe pathway.

Step 3: Qualitative analysis — score and rank

Why R-001 scores "only" 10. Probability is 2 (Low) because welfare protocols, specialist transport procurement, and regulatory approvals are specifically designed to drive it toward zero. If probability were higher, the project should not proceed until pre-mitigation were applied.

Step 4: Quantitative analysis

Expected Monetary Value:

$$EMV = \sum_{i=1}^{n} P_i \times C_i$$

Summed across the register, EMV feeds the cost contingency reserve (illustratively ~A$4.2M for the Zoo).

Monte Carlo schedule simulation — thousands of iterations with randomised activity durations estimates the probability of meeting the 18-month deadline. Output: e.g., 62% probability — a far more useful input for the board than a simple pass/fail.

Step 5: Plan Responses

Threat responses per PMBOK: Avoid, Transfer, Mitigate, Accept.

"Accept" appears nowhere for welfare-impact risks. The zero-casualty mandate has removed acceptance as a legitimate response for this category.

Step 6: Risk Register structure

Reviewed fortnightly. Top ten risks by score appear in every board report by default.

Probability × Impact Matrix

Low

Medium

High

Extreme

Top 10 Risks

1. Supplier Delay

2. Design Rework

3. Cost Escalation

4. Resource Shortage

5. Compliance Failure

Risk Count Over Time

Jan

Feb

Mar

Apr

May

Relationship details

From	Relationship	To
Jan	leads to	trend
trend	leads to	Feb
Feb	leads to	trend
trend	leads to	Mar
Mar	leads to	trend
trend	leads to	Apr
Apr	leads to	trend
trend	leads to	May
May	leads to	trend
Probability × Impact Matrix	leads to	Top 10 Risks
Top 10 Risks	leads to	Risk Count Over Time

The Result

Three controlled artefacts: Risk Management Plan, Risk Register, Risk Response Plan. Each feeds back into other plans: schedule reserves from Monte Carlo; budget contingency from EMV; crisis comms in the communications plan; risk-driven work packages integrated into the schedule.

The Pitfalls

• Scoring probability too low out of optimism. The single most common error. The board wants an accurate forecast, not optimism.
• "We will be careful" as a mitigation. Not a mitigation. A mitigation is something you will actually do that credibly reduces probability or impact.
• Forgetting the trigger column. Without triggers, risks sit in the register indefinitely. Triggers transform the register from static document to operational early-warning system.
• Treating the register as the PM's private document. Team members encounter indicators in daily work that never reach the PM's desk otherwise.
• Omitting positive risks. PMBOK explicitly includes opportunities. Managing upside is part of mature risk management.
• Confusing risks with issues. A risk has not happened yet. An issue has. Separate documents.

Knowledge Check

1. Rewrite R-001 as a cause-event-effect statement ("As a result of [cause], [event] may occur, leading to [effect]").
2. Six months in, a structural inspection reveals 70% of enclosures cannot be safely dismantled for reuse. Which risks are affected, and what does the PM do first?
3. The board asks you to remove R-008 because "talking about it makes it more likely." How do you respond?

Key Takeaways

• Risk management runs continuously from start to close.
• The six PMBOK processes must be performed in order with continuous feedback from monitoring back to identification.
• The scoring scale must be tailored — welfare impact on the Zoo has a zero-tolerance ceiling that reshapes the entire response strategy.
• The Risk Breakdown Structure organises risks by source category.
• Quantitative analysis (EMV, Monte Carlo) converts qualitative scores into numbers that feed contingency reserves.
• Acceptance is rarely legitimate for welfare-impact risks under a zero-tolerance mandate.
• Risks are not issues.

---

References

• Project Management Institute 2017, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 6th edn, PMI, Newtown Square, PA.
• Project Management Institute 2019, The Standard for Risk Management in Portfolios, Programs, and Projects, PMI.
• International Organization for Standardization 2018, ISO 31000:2018 Risk management — Guidelines, ISO, Geneva.
• Hillson, D & Simon, P 2020, Practical Project Risk Management: The ATOM Methodology, 3rd edn, Berrett-Koehler.
• Chapman, C & Ward, S 2003, Project Risk Management: Processes, Techniques and Insights, 2nd edn, Wiley, Chichester.
• University of South Australia 2015, MPM411 Zoo Relocation Project Brief, UniSA, Adelaide.