Anatomy of the Zoo Relocation Case Study

The Zoo Relocation brief is a 400-word letter that contains roughly 30 distinct project management constraints, assumptions, and implied requirements. This Format A deep dive dissects the case study word by word and maps every element to the relevant PMBOK knowledge area.

Why This Article Exists

The Zoo Relocation Project Brief used in university project is, on its surface, a short fictional CEO letter — under 450 words, one page, deliberately colloquial in tone. On its surface, it is easy to read in three minutes and then put aside.

This is a mistake. The brief is not a casual introduction. It is a densely engineered pedagogical artefact in which nearly every sentence encodes a distinct project management constraint, assumption, stakeholder obligation, or implied requirement. Students who read the brief once and move on inevitably produce assessment work that misses half of what the brief is actually asking for.

This article treats the brief the way a senior PM would treat a real executive-level Statement of Need: as a forensic object requiring sentence-by-sentence decomposition. The goal is to produce an exhaustive inventory of everything the brief contains — explicit and implicit — and to map each element to the relevant PMBOK knowledge area and the relevant Content element of the group report rubric.

This is a companion piece to the three rubric decoder articles (Participation, Group Report, Exam) and to the six-part Zoo Relocation case study walkthrough series. Together they form a complete reference set for any student working on the MPM411 assessments.

Section-by-Section Dissection

The brief consists of a subject line, a congratulatory opening, and nine substantive paragraphs. We will walk through each in order.

Paragraph 1 — The Congratulations

"Congratulations on your recent appointment as Project Manager for the Zoo Relocation Project."

This looks like boilerplate. It is not. Three facts are encoded:

1. The PM has already been appointed. This is not a bid or proposal scenario. The PM is walking into an existing authority structure. The charter will be signed shortly.
2. The appointment is recent. The PM has no prior context with this project and must build understanding from scratch in the first weeks.
3. The letter is the first official communication. The PM should treat it as the anchor document for initiation but must not mistake it for the charter itself.

Knowledge Area mapped: Integration Management (4.1 Develop Project Charter). Rubric Content Element mapped: Accountability & Responsibility (the authority hierarchy begins with this appointment).

Paragraph 2 — The Strategic Context

"As you are aware, the Zoo has faced increased financial pressure over the last five years due to a decline in the average number of visitors, the withdrawal of key sponsors and lack of membership from the public. To offset the growing debt, the Zoo must sell off its current site, which has been earmarked to become a high-density residential precinct."

This is the strategic context paragraph. It establishes why the project exists — which is the single most important input to Content Element 1 (Strategic Alignment).

Constraints and context encoded:

Analytical insight. The phrase "growing debt" is significant. The Zoo is not cash-rich pursuing expansion — it is cash-constrained pursuing survival. This dramatically affects risk tolerance: a cash-rich organisation can accept a higher probability of cost overrun; a cash-constrained one cannot. The risk management plan must reflect this.

Knowledge Areas mapped: Integration Management; Cost Management (the underlying financial constraint drives all cost decisions). Rubric Content Element mapped: Alignment with Corporate Strategy (Element 1); Success Measurement (Element 6).

Paragraph 3 — The Funding Mechanism

"The funds from the sale will be used to lease one of several inner-city sites on crown land that have been offered by the government."

This sentence contains four discrete elements:

1. Funding mechanism — sale proceeds fund the relocation. No external capital is assumed beyond the government grant mentioned later.
2. Lease, not purchase — the new site is a lease, which has major implications for long-term asset strategy. Leasehold improvements cannot be depreciated the same way as owned-land improvements.
3. Crown land — government ownership introduces additional regulatory and political considerations.
4. "One of several" sites — site selection is a real decision, not predetermined. Selection criteria must be defined.

Knowledge Areas mapped: Cost Management; Procurement Management; Stakeholder Management (government as stakeholder). Rubric Content Element mapped: Success Measurement (the leasehold versus freehold distinction affects long-term financial metrics).

Paragraph 4 — The Project Scope Outline

"The project will involve the sale of the existing site, selection and acquisition of the new site, relocation of the Zoo's assets and re-establishment of the Zoo's business operations in the shortest possible timeframe. Most importantly, the project must generate $20 million profit to sustain its ongoing future in the current market conditions."

This paragraph establishes scope at the highest level and introduces the first hard financial target.

The four-part scope is implicitly:

1. Sale of existing site
2. Acquisition of new site
3. Relocation of assets
4. Re-establishment of operations

Each of these becomes a natural top-level branch of the Work Breakdown Structure. A WBS that cannot trace each of its level-1 elements back to this sentence has either missed scope or added unauthorised scope.

The A$20 million target is the first quantified success criterion. Note the phrasing: "must generate," not "should aim to generate." This is absolute language, and the charter must treat it as a baseline acceptance criterion rather than a stretch target.

Knowledge Areas mapped: Scope Management; Cost Management; Integration Management. Rubric Content Element mapped: Strategic Alignment (Element 1); Success Measurement (Element 6); Staging Plan (Element 7).

Paragraph 5 — The Human and Welfare Constraints

"Importantly, a focus will need to be placed on the needs of the Zoo's large existing staff with an emphasis on achieving maximum staff retention. Furthermore, it is imperative that all current exhibits are successfully relocated with welfare of the animals placed as the highest priority. Every creature must be transported with a zero-percent casualty rate with long-term survival a critical success factor."

This paragraph is the most operationally consequential in the entire brief. It introduces two of the project's three most demanding constraints:

1. Maximum staff retention. The language is not "high staff retention" or "target 80% retention." It is "maximum." This implies either 100% (which is practically impossible given normal turnover) or an instruction to treat retention as an optimisation target with no upper bound. The charter must negotiate this into a measurable figure with the sponsor.

2. Zero-percent casualty rate. This is the phrase that reshapes the entire risk management framework. Welfare becomes a binary constraint rather than a variable. "Accept" is functionally eliminated as a risk response strategy for any welfare-impact risk.

3. Long-term survival as a critical success factor. This extends the welfare constraint past project closure and into benefits realisation. The project cannot be declared successful at opening day; success requires ongoing confirmation months or years later.

Analytical insight. The phrase "highest priority" for welfare is in tension with the A$20M profit target from the previous paragraph. Both cannot simultaneously be the highest priority in all decisions. The charter must resolve this explicitly — typically by establishing welfare as the absolute constraint (a floor that cannot be violated) and profit as the primary objective (a target to be maximised subject to the constraint). This is a classic hierarchical constraint structure used in defence procurement, where safety is treated as an absolute and performance-to-cost ratio as the objective.

Knowledge Areas mapped: Quality Management; Risk Management; Resource Management (staff); Stakeholder Management. Rubric Content Element mapped: Success Measurement (Element 6); Knowledge Areas (Element 5); Staging Plan (Element 7 — welfare drives staging sequencing).

Paragraph 6 — The Reuse Requirement

"It will be necessary to retain and reuse as much of the existing enclosures and exhibits as possible to minimise the cost in establishing them in the new locations. This extends to trees, vegetation and existing structures. Supplies and equipment will also need to be transported safely and in some cases will require careful planning and quality assurance to ensure that perishables and delicate apparatuses are not compromised during transit."

This paragraph introduces a cost-driven scope constraint (reuse) and a quality-driven transport constraint (perishables).

Elements encoded:

Analytical insight. The reuse requirement conflicts with the 18-month deadline. Reusing existing assets requires a dismantle → transport → inspect → refurbish → re-erect cycle that is typically longer than new construction. A PM who takes the reuse requirement at face value and sizes the schedule on greenfield assumptions will blow the deadline. The staging plan must either (a) carefully identify which assets are genuinely cheaper to reuse than to replace, or (b) accept that the reuse target must be negotiated downward with the sponsor. This is exactly the kind of trade-off that HD-level exam answers should identify explicitly.

Knowledge Areas mapped: Scope Management; Cost Management; Quality Management; Procurement Management (salvage logistics). Rubric Content Element mapped: Strategic Alignment (cost driver); Success Measurement; Staging Plan.

Paragraph 7 — The Time Constraints

"It has been forecasted that current finances will sustain the Zoo's operations for another 12 months, at which the sale of the current site must be finalised in order to fund the relocation. This will allow for the planning phase of the project and the acquisition of the new site. It will be advantageous to acquire the site as soon as possible so that a staged relocation can commence. The Zoo accepts that some exhibits may be shut down and relocated prior to the closure of the Zoo to the public."

This paragraph contains the project's hardest deadlines and the explicit permission for phased delivery.

Analytical insight. The permission for staged relocation is worth entire paragraphs of the group report. Without this permission, the project would be a big-bang delivery — which is infeasible given the 18-month deadline. With this permission, the project becomes a phased delivery with dual-site operations during the overlap. The entire Implementation Staging Plan (rubric Content Element 7) depends on this single sentence.

Knowledge Areas mapped: Schedule Management; Cost Management; Integration Management; Stakeholder Management (the early closure permission pre-resolves a stakeholder conflict). Rubric Content Element mapped: Staging Plan (Element 7 — this is the core source material for the entire staging plan).

Paragraph 8 — The Grant and the Final Deadline

"A government grant has been approved for the relocation and will sustain full closure for a short period of time whilst the new site is being established. From closure of the Zoo to the public, the new Zoo must be substantially operational within 18 months so that it can be officially opened and generating income."

Two distinct constraints:

1. Government grant. Provides bridging finance during the full-closure period. Amount not specified — this is an assumption the PM must validate. Duration also not specified ("a short period of time") — also requires validation.
2. 18-month operational deadline. Measured from public closure of the old site, not from project start. This is the most frequently misread element of the brief. Students routinely treat the 18 months as the total project duration, which is wrong — the 18 months is the post-closure window only.

Analytical insight. The phrasing of the deadline as "substantially operational" rather than "fully operational" gives the PM a small amount of scope flexibility. "Substantially" can be reasonably interpreted as "operating with the majority of exhibits open and the major systems functional," allowing some minor exhibits to open slightly later. This is a negotiable parameter the PM should discuss with the board early.

Knowledge Areas mapped: Cost Management (grant assumption); Schedule Management (deadline); Integration Management. Rubric Content Element mapped: Success Measurement; Staging Plan.

Paragraph 9 — Governance and Authority

"You will report directly to the Zoo's Executive board and submit a formal project report on a fortnightly basis. You will be responsible for appointing your project team, which should include external consultants and experienced internal staff members."

This paragraph establishes the governance structure and the PM's authority:

Analytical insight. Direct board reporting is unusual authority for a PM and should be read as a deliberate signal from the CEO that the project is strategically critical. The fortnightly reporting cadence is very short for a multi-year capital project and indicates an expectation of active board engagement. The requirement to mix internal and external team members is an explicit acknowledgment that neither the Zoo's existing staff nor external consultants alone can deliver this project — it needs both.

Knowledge Areas mapped: Resource Management; Communications Management; Stakeholder Management; Integration Management. Rubric Content Element mapped: Accountability & Responsibility (Element 2); Organisation Structure (Element 3).

Master Constraint Inventory

Consolidating the analysis above, the brief encodes the following inventory of constraints, assumptions, requirements, and implied obligations:

Zoo Relocation Brief — ~450 words

Financial

Temporal

Scope

Quality / Ethics

Human Resources

Governance

Stakeholder

A$20M profit target

Growing debt context

Site sale funds relocation

Government grant — bridging

Cost minimisation via reuse

12 months — sale deadline

12 months — planning/acquisition window

18 months — post-closure operational deadline

Short full-closure period

Sell existing site

Select and acquire new site

Relocate assets

Re-establish operations

Reuse enclosures, trees, structures

Transport supplies and equipment

Staged relocation permitted

Zero casualty rate — absolute

Long-term survival — benefits-realisation criterion

Perishables safely transported

Delicate apparatuses protected

Maximum staff retention

Team mix — internal + external

PM authority to appoint

Direct board reporting

Fortnightly formal reports

CEO as sponsor

PM already appointed

Executive Board

CEO

Government (lessor)

Government (grant funder)

Existing staff

Public / members

Site buyer / developer

Relationship details

From	Relationship	To
Zoo Relocation Brief — ~450 words	leads to	Financial
Zoo Relocation Brief — ~450 words	leads to	Temporal
Zoo Relocation Brief — ~450 words	leads to	Scope
Zoo Relocation Brief — ~450 words	leads to	Quality / Ethics
Zoo Relocation Brief — ~450 words	leads to	Human Resources
Zoo Relocation Brief — ~450 words	leads to	Governance
Zoo Relocation Brief — ~450 words	leads to	Stakeholder
Financial	leads to	A$20M profit target
Financial	leads to	Growing debt context
Financial	leads to	Site sale funds relocation
Financial	leads to	Government grant — bridging
Financial	leads to	Cost minimisation via reuse
Temporal	leads to	12 months — sale deadline
Temporal	leads to	12 months — planning/acquisition window
Temporal	leads to	18 months — post-closure operational deadline
Temporal	leads to	Short full-closure period
Scope	leads to	Sell existing site
Scope	leads to	Select and acquire new site
Scope	leads to	Relocate assets
Scope	leads to	Re-establish operations
Scope	leads to	Reuse enclosures, trees, structures
Scope	leads to	Transport supplies and equipment
Scope	leads to	Staged relocation permitted
Quality / Ethics	leads to	Zero casualty rate — absolute
Quality / Ethics	leads to	Long-term survival — benefits-realisation criterion
Quality / Ethics	leads to	Perishables safely transported
Quality / Ethics	leads to	Delicate apparatuses protected
Human Resources	leads to	Maximum staff retention
Human Resources	leads to	Team mix — internal + external
Human Resources	leads to	PM authority to appoint
Governance	leads to	Direct board reporting
Governance	leads to	Fortnightly formal reports
Governance	leads to	CEO as sponsor
Governance	leads to	PM already appointed
Stakeholder	leads to	Executive Board
Stakeholder	leads to	CEO
Stakeholder	leads to	Government (lessor)
Stakeholder	leads to	Government (grant funder)
Stakeholder	leads to	Existing staff
Stakeholder	leads to	Public / members
Stakeholder	leads to	Site buyer / developer

This single diagram contains roughly 30 distinct project elements extracted from a 450-word brief. That is one constraint or requirement per 15 words — a remarkable density that is typical of well-crafted executive-level briefs.

Mapping to the Group Report Rubric

Every rubric-required Content element can be traced back to specific sentences in the brief:

A group report that traces each of its Content sections back to these specific paragraphs will be structurally complete by design. Conversely, a group report that cannot trace each section back to brief text is either importing generic material or missing brief content.

Mapping to the PMBOK Knowledge Areas

Every PMBOK knowledge area is invoked by at least one element of the brief:

This is why the Zoo brief is such a strong pedagogical case study: it exercises every knowledge area simultaneously, unlike narrower case studies that touch only a subset.

Mapping to the Six-Part Case Study Series

The six case study walkthrough articles in this publication each draw on specific paragraphs of the brief:

Every sentence of the brief is referenced by at least one article in the series, and most sentences are referenced by multiple articles. This is the kind of referential density that makes a case study rich enough to sustain a full postgraduate unit.

Reading the Brief Like a Senior PM

The difference between a student reading and a senior PM reading lies in what each notices. A student notices the explicit facts. A senior PM notices:

• What is not said. The brief does not specify the Zoo's location, the number of staff, the number of animals, the size of the government grant, the identity of the environment regulator, or the timeline for site selection. These are all items the PM must clarify before the charter can be completed.
• The implicit hierarchy of priorities. Profit is mentioned once as "must generate." Zero casualties is mentioned as "imperative" with welfare as "highest priority." These are not equal priorities; zero casualties is absolute while profit is relative.
• The political subtext. "Focus will need to be placed on the needs of the Zoo's large existing staff" is not a casual observation — it is a pre-emptive warning that staff relations are sensitive and will require executive attention.
• The permissions that enable scope. The early exhibit closure permission is the single most consequential sentence in the brief because it unlocks staged delivery.
• The governance signals. Direct board reporting on a fortnightly cadence is unusual — it signals that the board has chosen to stay very close to this project, which both empowers and constrains the PM.
• The commercial hints. The mention of "key sponsors" withdrawing suggests that sponsor recovery might be a benefits-realisation lever. The mention of high-density residential on the old site suggests the sale is likely to be oversubscribed (because residential development is typically high-margin).

A senior PM reading this brief for the first time would spend perhaps 30 minutes extracting all of the above, would then meet with the CEO for 90 minutes to validate assumptions and clarify unknowns, and would leave that meeting with perhaps another 20–30 questions for written response. The brief is input to that process, not a substitute for it.

Pitfalls for Students Using This Brief

• Treating the brief as complete. It is not. It is the starting input for stakeholder engagement, not the final statement of requirements.
• Ignoring the implicit constraints. Every paragraph contains elements that are not stated directly but that follow logically — these are fair game for assessment and must be addressed.
• Misreading the 18-month timeline. The 18 months runs from public closure, not from project start. Confusing these produces a completely incorrect schedule.
• Underweighting the zero-casualty constraint. This is the single hardest constraint in the brief and must dominate risk, quality, and staging decisions.
• Forgetting the reuse-vs-speed tension. Reuse takes longer than replacement. A schedule that ignores this tension is not defensible.
• Treating "maximum staff retention" as 100%. This must be negotiated with the sponsor into a specific figure.
• Not tracing assessment work back to brief sentences. Every claim in the group report or exam should be traceable to a specific brief element. If it cannot be traced, it is probably generic rather than case-applied.

Key Takeaways

• The Zoo Relocation brief is a deliberately densely-engineered pedagogical artefact containing roughly 30 distinct PM elements in under 450 words.
• Every sentence of the brief encodes one or more constraints, assumptions, or requirements — explicit or implicit.
• The brief exercises every PMBOK knowledge area simultaneously, which is why it is such a strong teaching case study.
• Strategic framing comes from paragraphs 2 and 4; scope from paragraph 4; welfare constraints from paragraph 5; reuse constraints from paragraph 6; timeline from paragraphs 7 and 8; governance from paragraph 9.
• The 18-month operational deadline runs from public closure of the old site, not from project start.
• The zero-casualty welfare constraint is absolute and reshapes the entire risk management approach.
• The staged-relocation permission in paragraph 7 is the single most consequential sentence, enabling the entire Implementation Staging Plan.
• Students should trace every assessment claim back to specific brief sentences. If it cannot be traced, it is probably generic rather than case-applied.
• A senior PM reads this brief in about 30 minutes and leaves with 20–30 follow-up questions for the sponsor. Students should aim to develop the same reading discipline.

---

References

• Project Management Institute 2017, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 6th edn, PMI, Newtown Square, PA.
• Kerzner, H 2017, Project Management: A Systems Approach to Planning, Scheduling, and Controlling, 12th edn, Wiley, Hoboken, NJ.
• Turner, JR 2014, Handbook of Project-Based Management, 4th edn, McGraw-Hill, New York.
• University of South Australia 2015, MPM411 Principles of Project Management — Zoo Relocation Project Brief, UniSA, Adelaide.
• University of South Australia 2015, MPM411 Principles of Project Management — Group Report Marking Guide, UniSA, Adelaide.