How to Score a High Distinction on a Postgraduate Project Management Group Report

A rubric-driven deep dive into what a High Distinction looks like across all seven required Content elements of a postgraduate PM group report, using the UniSA Zoo Relocation case study as the worked example throughout.

Why This Article Exists

Most postgraduate project management students approach a group report assessment the same way they approached essay writing at undergraduate level: they read the topic, do some research, divide the work among group members, write sections, stitch them together, and submit. The result is a report that clears the Pass band comfortably, lands in the Credit range with a bit of luck, and leaves the students wondering why it did not score higher.

The reason is that postgraduate PM reports are not essays. They are consultant-style deliverables that are graded against a detailed rubric with specific, non-negotiable content requirements. When the rubric says the report must analyse "5x Processes + methodologies, 9x Knowledge Areas, and Implementation Staging Plan," the marker is checking for each of those items specifically. A report that only implicitly covers the Knowledge Areas, or that buries the Staging Plan inside a conclusion, is leaving marks on the table regardless of how well-written the prose is.

This article decodes a representative postgraduate PM group report rubric — specifically the UniSA MPM411 Principles of Project Management Group Report marking guide — component by component, showing what HD-band performance looks like for each required element. The worked example throughout is the Zoo Relocation Project, a fictional but well-constrained case study used in MPM411. Students from other institutions with different case studies should still find the structure directly transferable: the seven Content elements are standard across virtually every postgraduate PM curriculum.

The Rubric, Reverse-Engineered

Before writing a single word of the report, the group must understand exactly how the marker will evaluate it. The UniSA MPM411 Group Report rubric allocates 100 marks across six components:

Two observations jump out immediately.

First, Content is 40% of the total mark, which is larger than any other component by a factor of two. A group that produces mediocre content but perfect grammar and citations cannot score above a P1 overall. Conversely, a group that produces HD-quality content with minor clarity or referencing issues can still land comfortably in the D range. Prioritise content first. Everything else is secondary.

Second, the Content component has seven named required elements:

1. Alignment with corporate strategy
2. Accountability & Responsibility
3. Organisation structure
4. 5x Processes + methodologies
5. 9x Knowledge Areas
6. Success measurement
7. Implementation Staging Plan

A report that omits any one of these will forfeit a substantial proportion of the Content marks no matter how well the remaining elements are covered. A report that covers all seven but only at the C or P1 level will finish in the C or P1 band for Content. HD-level Content requires HD-level treatment of all seven elements simultaneously.

The remainder of this masterclass walks through each Content element in detail, showing what HD-band treatment looks like using the Zoo Relocation case study.

---

Content Element 1: Alignment with Corporate Strategy

What the Rubric Is Really Asking

This element evaluates whether students understand that projects are strategy implementation vehicles. A project that cannot be traced back to a strategic objective is, by definition, organisational waste. The marker is looking for evidence that students can articulate the why of the project in terms that a board member would recognise as strategic logic, not operational logic.

What C-Band Looks Like

A typical Credit-level treatment says something like: "The project aligns with the Zoo's strategy to remain financially viable. The relocation will generate revenue and save costs." This is not wrong. It is also not analytical. It is a paraphrase of the CEO letter with the word "strategy" inserted.

What HD-Band Looks Like

HD-level treatment begins by articulating the strategic context in which the Zoo is operating. It draws on frameworks from strategic management literature to structure the analysis — PESTLE, Porter's Five Forces, SWOT, or resource-based view — and it explicitly maps the project to a named strategic objective.

For the Zoo project, an HD-level strategic alignment section might proceed as follows:

Strategic context. The Zoo operates in a discretionary-leisure market that has experienced structural decline in captive animal institutions over the past two decades (Carr & Cohen 2011), driven by changing public attitudes to animal welfare, competition from lower-cost entertainment alternatives, and the withdrawal of corporate sponsorship from animal-based tourism. The CEO's letter confirms that all three pressures are actively affecting the Zoo: declining visitor numbers, sponsor withdrawals, and loss of membership. These symptoms indicate a strategic failure of the existing business model, not merely a cash-flow problem.

Strategic response. The relocation project is the operational instrument through which a broader strategic reset is executed. The strategic objective is not "move the Zoo to a new site." The strategic objective is "re-establish the Zoo on a financial and geographic footing that permits long-term viability in the current market." The project converts a depreciating fixed asset (the existing site, which has development value exceeding its operational value) into the capital base for a repositioned operation.

Strategic criteria. This framing clarifies the project's success criteria. A successful project, in strategic terms, is one that not only delivers the new facility on time and on budget, but also positions the Zoo for ongoing operational solvency. The CEO letter's specification of a A$20M profit target is not a vanity metric — it is the strategic threshold below which the relocation does not achieve its strategic purpose.

This section does four things that the C-level treatment did not:

1. It uses external academic evidence (Carr & Cohen 2011) to ground the strategic claim.
2. It distinguishes between operational symptoms and strategic causes.
3. It reframes the project as a means to a strategic end, not an end in itself.
4. It explicitly links the success criteria to the strategic logic.

A powerful tool for visualising this linkage is the Strategy-to-Project alignment chain:

Vision — Zoo remains a viable — public institution — long-term

Strategic Objective — Re-establish sustainable — financial base

Strategic Initiative 1 — Relocate to lower-cost, — higher-visitor-draw site

Strategic Initiative 2 — Modernise visitor experience

Strategic Initiative 3 — Diversify revenue streams

Project — Zoo Relocation

Business Case: — A$20M profit

Benefits: — Sustainable operations

Benefits: — Retained institutional knowledge

Relationship details

From	Relationship	To
Vision — Zoo remains a viable — public institution — long-term	leads to	Strategic Objective — Re-establish sustainable — financial base
Strategic Objective — Re-establish sustainable — financial base	leads to	Strategic Initiative 1 — Relocate to lower-cost, — higher-visitor-draw site
Strategic Objective — Re-establish sustainable — financial base	leads to	Strategic Initiative 2 — Modernise visitor experience
Strategic Objective — Re-establish sustainable — financial base	leads to	Strategic Initiative 3 — Diversify revenue streams
Strategic Initiative 1 — Relocate to lower-cost, — higher-visitor-draw site	leads to	Project — Zoo Relocation
Project — Zoo Relocation	leads to	Business Case: — A$20M profit
Project — Zoo Relocation	leads to	Benefits: — Sustainable operations
Project — Zoo Relocation	leads to	Benefits: — Retained institutional knowledge

Including a diagram like this — even a simple one — immediately signals to the marker that the group has thought about strategic alignment structurally, not just rhetorically.

---

Content Element 2: Accountability & Responsibility

What the Rubric Is Really Asking

Every project has a governance structure. The rubric wants to see that students understand the difference between accountability (who is answerable for the outcome) and responsibility (who performs the work), and that they can articulate this structure formally.

What C-Band Looks Like

"The Project Manager is responsible for the project. The board is accountable." End of section. Technically correct, practically useless.

What HD-Band Looks Like

HD-level treatment introduces the RACI matrix (Responsible, Accountable, Consulted, Informed) or its close cousin the PARIS model, and uses it to map accountability explicitly across all major project decisions. It also distinguishes between the two concepts rigorously:

Definitions. Accountability is singular and ultimate — only one party can be accountable for any given decision. Responsibility is plural — multiple parties can share responsibility for delivering a task. Consultation implies two-way engagement before a decision is made. Information implies one-way communication after a decision is made. (Adapted from PMBOK Guide, 6th edn, Section 9.1.2.1.)

A worked RACI matrix for the Zoo project's major decisions might look like this:

The bolded A in each row identifies the single accountable party for that decision. Notice how accountability shifts between the Board, the CEO, the PM, and HR depending on the decision type. This is not arbitrary — it reflects legitimate authority structures and the principle of decision rights.

HD-level treatment also addresses organisational authority types — whether the PM holds line authority, functional authority, or matrix authority — and uses this to predict the project's organisational friction points. On the Zoo project, the PM has been given significant authority by the CEO but operates inside a functional organisation where specialist knowledge resides with department heads (curators, vets, HR). This is a classic weak matrix structure in PMBOK terminology, and the HD-level report names it as such and explains its implications for decision-making speed.

---

Content Element 3: Organisation Structure

What the Rubric Is Really Asking

The rubric wants to see that students can (a) describe the host organisation's structure, (b) describe the project organisation's structure, and (c) analyse the interaction between the two. PMBOK identifies several standard organisational structure types, and the marker will expect students to name the one they are analysing.

What C-Band Looks Like

"The Zoo has a functional organisation. The project will be managed by a team." A picture of an org chart with no analysis.

What HD-Band Looks Like

HD-level treatment explicitly classifies the host organisation using PMBOK's taxonomy, describes the project organisation using a named pattern, and analyses the interactions.

PMBOK organisational structure types:

For the Zoo project, the HD-level analysis would classify the existing Zoo as a functional organisation with a weak-to-balanced matrix overlay for the relocation project. The argument runs as follows:

The Zoo's day-to-day operations are organised functionally — curatorial departments (mammals, reptiles, birds, aquatic), operations (facilities, security, visitor services), and administrative functions (HR, finance, marketing) — each with a department head reporting to the CEO. The relocation project is superimposed onto this functional structure as a temporary matrix, with the Project Manager drawing specialist resources from the functional departments on a part-time or full-time basis depending on the phase.

This creates a balanced matrix specifically for the project: the PM holds direct authority over project-specific decisions and has explicit authorisation from the CEO to represent the project externally, but specialist staff (curators, vets, HR advisors) retain their functional reporting lines and must balance project demands against their business-as-usual responsibilities. The most likely friction points, as predicted by the matrix structure literature (Galbraith 1971; Ford & Randolph 1992), are competing demands for specialist time and ambiguity over performance evaluation authority.

The project's own structure can then be illustrated:

Zoo Executive Board

CEO (Project Sponsor)

Project Manager

Workstream 1 — Site & Construction — Construction Manager

Workstream 2 — Animal Relocation — Chief Curator

Workstream 3 — Finance & Sale — Finance Lead

Workstream 4 — Staff & HR Transition — HR Lead

Workstream 5 — Stakeholder & Comms — Comms Lead

Facilities Dept — (functional home)

Curatorial Dept — (functional home)

Finance Dept — (functional home)

HR Dept — (functional home)

Marketing Dept — (functional home)

Relationship details

From	Relationship	To
Zoo Executive Board	leads to	CEO (Project Sponsor)
CEO (Project Sponsor)	leads to	Project Manager
Project Manager	leads to	Workstream 1 — Site & Construction — Construction Manager
Project Manager	leads to	Workstream 2 — Animal Relocation — Chief Curator
Project Manager	leads to	Workstream 3 — Finance & Sale — Finance Lead
Project Manager	leads to	Workstream 4 — Staff & HR Transition — HR Lead
Project Manager	leads to	Workstream 5 — Stakeholder & Comms — Comms Lead

The dotted lines represent the workstream leads' continuing functional reporting relationships — they work on the project but remain employed by their functional departments. This visual captures the matrix structure in a way that prose alone cannot.

---

Content Element 4: Five Process Groups and Methodologies

What the Rubric Is Really Asking

The rubric explicitly requires analysis of the five PMBOK process groups — Initiating, Planning, Executing, Monitoring & Controlling, and Closing — and of the methodologies the project will use (PMBOK, PRINCE2, Agile, hybrid).

What C-Band Looks Like

A bullet list naming the five process groups with one sentence each, and a statement that "the project will use PMBOK methodology."

What HD-Band Looks Like

HD-level treatment does three things: (1) describes the five process groups with analytical rigour, (2) explains how they interact and overlap through the project lifecycle, and (3) justifies the choice of methodology with reference to the project characteristics.

The five process groups are often misunderstood as sequential project phases. They are not. They are groups of processes that run concurrently and iteratively throughout the project lifecycle, with different intensities at different times. This classic PMBOK diagram captures the relationship:

Project Lifecycle (Time →)

Initiating — Charter — Stakeholder ID

Planning — All Planning — Processes

Executing — Direct Work — Manage Team

Monitoring — & Controlling — Variance Analysis — Change Control

Closing — Administrative — Closeout

Relationship details

From	Relationship	To
Initiating — Charter — Stakeholder ID	leads to	Planning — All Planning — Processes
Planning — All Planning — Processes	leads to	Executing — Direct Work — Manage Team
Executing — Direct Work — Manage Team	leads to	Closing — Administrative — Closeout

For each process group, the HD-level report explains what the group contributes, which processes it contains, and how it applies to the specific project. For the Zoo project:

Initiating contains two processes: Develop Project Charter (4.1) and Identify Stakeholders (13.1). On the Zoo project, these processes transform the CEO's letter into a formally authorised project with a mapped stakeholder register, and their completion is marked by the board's formal approval of the charter.

Planning contains 24 processes spanning all ten knowledge areas. On the Zoo project, planning occupies approximately the first four months of the 18-month timeline and produces the scope baseline, schedule baseline, cost baseline, quality management plan, resource management plan, communications management plan, risk management plan, procurement management plan, and stakeholder engagement plan.

Executing contains 10 processes focused on carrying out the work defined in the project management plan. On the Zoo project, executing is the dominant activity from month 4 through month 16, including the staged animal relocation and construction activities.

Monitoring & Controlling contains 12 processes that run continuously from initiation through closure, including change control, scope control, schedule control, cost control, and quality control. On the Zoo project, monitoring and controlling is particularly intensive during the dual-site operational phase.

Closing contains one process (Close Project or Phase) that formally terminates the project. On the Zoo project, closing occurs in the final weeks after public opening.

Methodology choice. The HD-level report does not simply name PMBOK as the methodology. It compares alternatives and justifies the choice. For the Zoo project:

The recommendation for a PMBOK-PRINCE2 hybrid is justified by the project's characteristics: large scale, high governance requirements, well-defined deliverables, low tolerance for iteration, and the explicit fortnightly reporting mandate from the CEO. This analysis is what distinguishes HD-level from C-level treatment.

---

Content Element 5: Nine (or Ten) Knowledge Areas

What the Rubric Is Really Asking

The rubric refers to "9x Knowledge Areas" — this reflects PMBOK 4th Edition. PMBOK 5th and 6th Editions contain ten knowledge areas (Stakeholder Management was added in 5th Edition). HD-level treatment should use the ten-area framework while noting the historical context if appropriate.

The ten knowledge areas are:

What C-Band Looks Like

A table listing the ten areas with a generic one-line definition of each. No application to the case study.

What HD-Band Looks Like

HD-level treatment applies each knowledge area to the case study specifically, showing what the PM will actually do in that area and how the knowledge area interacts with the project's unique constraints. For the Zoo project, a condensed HD treatment might read as follows for each area:

Integration Management. The project integrates multiple specialist workstreams (construction, animal welfare, finance, HR, regulatory) whose timing and dependencies are non-trivial. The Project Management Plan will serve as the integration instrument, and the PM will chair a weekly integration meeting with all workstream leads.

Scope Management. The scope baseline comprises the Scope Statement, WBS, and WBS Dictionary (as discussed in Part 3 of the Zoo case study series). Scope control will be particularly important given the CEO's board-level interest, which typically generates mid-project scope additions.

Schedule Management. The 18-month operational deadline from public closure is a hard constraint. Critical path will run through regulatory approvals → construction → staged animal moves → commissioning. Schedule reserve of approximately 10% is recommended based on Monte Carlo analysis of comparable relocation projects.

Cost Management. The budget baseline derives from cost estimates at the work package level. Cost contingency of approximately A$4.2M (EMV-derived) is recommended. Earned Value Management will be the primary cost control technique with weekly CV and SPI reporting.

Quality Management. Quality management is structurally elevated on this project because of the zero-casualty animal welfare constraint. Quality planning includes welfare protocols subjected to independent veterinary review and regulatory approval, with quality control checkpoints at every animal movement.

Resource Management. Human resources are drawn from the Zoo's functional departments on a matrix basis. Physical resources include specialist animal transport vehicles (procured), temporary holding facilities (leased), and existing Zoo assets earmarked for reuse (salvaged).

Communications Management. The fortnightly board report mandated by the CEO is the backbone of the communications cadence. Additional communications include weekly CEO briefings, monthly stakeholder group communications, and crisis communications protocols for welfare incidents.

Risk Management. Risk management follows the PMBOK six-process framework with a customised impact scale that accommodates the zero-casualty welfare constraint (as discussed in Part 4 of the case study series). The top five risks drive specific mitigation actions integrated into the schedule and budget.

Procurement Management. Major procurements include the specialist animal transport contractor, the enclosure construction contractor(s), the veterinary consulting retainer, and the legal and planning advisors. Contract types will be primarily fixed-price for construction and cost-plus for specialist consulting. Procurement planning begins in month 2 to ensure suppliers are mobilised when needed.

Stakeholder Management. The Stakeholder Engagement Plan (discussed in Part 2 of the case study series) classifies stakeholders into the four Power/Interest quadrants and prescribes engagement strategies for each. The existing staff and the environment regulator are the two most sensitive stakeholder groups.

A summary diagram showing how the knowledge areas interact is valuable at HD level:

4. Integration — Holds it all together

5. Scope

6. Schedule

7. Cost

8. Quality

9. Resource

10. Communications

11. Risk

12. Procurement

13. Stakeholder

Relationship details

From	Relationship	To
4. Integration — Holds it all together	leads to	5. Scope
4. Integration — Holds it all together	leads to	6. Schedule
4. Integration — Holds it all together	leads to	7. Cost
4. Integration — Holds it all together	leads to	8. Quality
4. Integration — Holds it all together	leads to	9. Resource
4. Integration — Holds it all together	leads to	10. Communications
4. Integration — Holds it all together	leads to	11. Risk
4. Integration — Holds it all together	leads to	12. Procurement
4. Integration — Holds it all together	leads to	13. Stakeholder
5. Scope	leads to	6. Schedule
6. Schedule	leads to	7. Cost
7. Cost	leads to	11. Risk
11. Risk	leads to	8. Quality
9. Resource	leads to	7. Cost
13. Stakeholder	leads to	10. Communications
10. Communications	leads to	11. Risk

---

Content Element 6: Success Measurement

What the Rubric Is Really Asking

The rubric wants evidence that students understand how to measure project success, which is a deceptively hard question. Different stakeholders have different definitions of success, success is measured at different points in time, and success criteria interact with constraints in non-obvious ways.

What C-Band Looks Like

"Success will be measured by completing the project on time and within budget." The iron triangle, recited without analysis.

What HD-Band Looks Like

HD-level treatment distinguishes between at least three levels of success measurement:

1. Project management success — delivered on time, on budget, to scope and quality.
2. Project product success — the deliverable itself works and is accepted by the sponsor.
3. Project benefits success — the business case benefits are realised post-delivery.

These three levels are famously not the same. A project can be delivered on time and on budget, produce a functional deliverable, and still fail to realise its business benefits — this is the classic Iron Triangle success with business failure outcome.

For the Zoo project, the three-level measurement framework looks like this:

HD-level treatment also addresses the stakeholder dimension of success — different stakeholders have different success criteria, and a project can succeed for one stakeholder while failing for another. On the Zoo project:

• The Board defines success primarily by financial outcome (A$20M profit).
• The Staff define success primarily by employment continuity and workplace stability.
• The Animal Welfare Community defines success primarily by zero casualties and long-term survival.
• The Regulator defines success primarily by compliance with all permit conditions.
• The Community defines success primarily by continuity of access to a valued institution.
• The Project Team defines success primarily by meeting the PM-level criteria.

A truly successful project must satisfy most or all of these stakeholder definitions simultaneously. This is why the Stakeholder Engagement Plan (Content Element 3 above) is not cosmetic — it is the mechanism by which the PM manages competing success definitions.

HD-level treatment may also introduce the concept of success factors versus success criteria (Cooke-Davies 2002):

• Success criteria are the measures by which success is judged after the fact.
• Success factors are the conditions, circumstances, or events that contribute to the achievement of success.

Success criteria are outcomes. Success factors are inputs. On the Zoo project, a critical success factor is "early engagement with the environment regulator," which is not itself a measure of success but which significantly increases the probability that the regulatory compliance success criterion will be met.

---

Content Element 7: Implementation Staging Plan

What the Rubric Is Really Asking

The rubric specifically asks for an Implementation Staging Plan — this is not a generic schedule, it is a phased delivery strategy that answers the questions raised in Part 5 of the Zoo case study series: which deliverables are staged when, what are the entry and exit criteria for each stage, what are the rollback options, and how does the dual-operational period get managed.

What C-Band Looks Like

A Gantt chart with activities labelled by month. No stages. No gates. No rollback.

What HD-Band Looks Like

HD-level treatment produces a true staging plan with six components:

1. Staging criteria — how deliverables were classified into stages (weighted scoring model).
2. Stage definitions — what each stage does, with entry and exit criteria.
3. Stage gates — formal decision points with Go / Go-with-conditions / Hold / Stop outcomes.
4. Rollback options — what can be undone at each stage, at what cost.
5. Dual-operations protocols — how overlapping sites/systems are managed during transition.
6. Stage-level success criteria — how each gate review evaluates progress.

For the Zoo project, the full staging plan is developed in detail in Part 5 of the case study series. A condensed HD-level version in a group report might include:

Workstream	Activity	Type	Timing / dependency / duration
Stage 0	Planning & Site Acquisition	Activity	done · 2025-01-01 · 180d
Stage 0	Gate 1	Milestone	milestone · 2025-07-01 · 0d
Stage 1	Early Migration	Activity	2025-07-01 · 150d
Stage 1	Gate 2	Milestone	milestone · 2025-12-01 · 0d
Decision	Old Site Sale & Closure	Activity	crit · 2025-12-01 · 45d
Decision	Gate 3	Milestone	milestone · 2026-01-15 · 0d
Stage 2	Full Migration	Activity	crit · 2026-01-15 · 120d
Stage 2	Gate 4	Milestone	milestone · 2026-05-15 · 0d
Stage 3	Commissioning & Opening	Activity	2026-05-15 · 60d
Stage 3	Public Launch	Milestone	milestone · 2026-07-15 · 0d

Accompanied by a stage gate decision table:

---

Beyond Content: The Other Rubric Components

The four remaining rubric components (Logic, Clarity, Structure, Referencing) collectively account for 40% of the total marks. Content quality alone cannot score an HD — these components matter too.

Logic and Support (10%)

HD-level performance requires every major claim to be supported by either (a) evidence from the case study, (b) theory from the literature, or (c) both. The marker is specifically looking for argument development, not information recitation. A well-developed argument has a claim, supporting evidence, and a connection back to the project context. Weak arguments are evidence-free assertions; strong arguments chain claims, evidence, and implications together.

Clarity of Written Expression (10%)

HD-level performance requires business writing standards. Key principles: one idea per paragraph, topic sentences at the start of paragraphs, minimal passive voice, consistent terminology (do not switch between "Project Manager" and "PM" at random), no contractions, no rhetorical questions, no informal language. The report should read like a consulting deliverable, not a student essay.

Planning, Language & Grammar (10%)

HD-level performance requires the full report structure specified by the rubric: Cover Sheet, Title Page, Table of Contents, Introduction, Discussion, Staging Plan, Conclusion, References. The word count must be within 10% of the specified target (for MPM411, 1300 words per student). Spelling and grammar errors must be essentially absent.

Collaboration & Teamwork (20%)

This is worth almost as much as Content. HD-level performance requires highly equitable contribution — meaning not just that the work is divided equally, but that the quality of contribution is consistent across group members. Uneven drafts stitched together score poorly even if the total content is strong. Groups should allocate work by Content Element (each member owns one or more) but then cross-review each other's sections to ensure consistency of voice and quality.

Acknowledgement of Research (10%)

HD-level performance requires Harvard referencing done correctly: in-text citations with author, date, and page number; a reference list in alphabetical order; consistent formatting throughout; every in-text citation matched to a reference list entry and vice versa. Tools like Zotero or Mendeley are essentially mandatory — manual reference management at postgraduate level is a recipe for inconsistency.

---

Assembly: Putting the Seven Content Elements into a Coherent Report

The seven content elements are not a report structure — they are required topics. The actual report structure must organise these topics into a coherent narrative. A defensible HD-level report structure looks like this:

1. Cover Sheet (as required by rubric)
2. Title Page
3. Executive Summary (optional but valuable — one page, no more)
4. Table of Contents
5. Introduction (context, purpose, scope of the report)
6. Section 1: Strategic Alignment (Content Element 1)
7. Section 2: Governance and Organisation (Content Elements 2 & 3)
8. Section 3: Methodology and Process Framework (Content Element 4)
9. Section 4: Knowledge Area Application (Content Element 5)
10. Section 5: Success Measurement Framework (Content Element 6)
11. Section 6: Implementation Staging Plan (Content Element 7)
12. Conclusion
13. References
14. Appendices (RACI matrix, WBS, risk register extracts)

This structure covers all seven required elements while presenting them as a logical argument: strategic context → how the project is governed → how it will be managed → what knowledge will be applied → how success will be measured → how delivery will be staged. Each section flows naturally into the next.

Rubric Content Elements

Context and Objectives

Stakeholders

Scope Definition

Schedule and Phasing

Risk Management

Governance and Control

Benefits and Outcomes

Report Sections

Introduction

Project Context

Planning and Controls

Delivery Strategy

Risk and Governance

Benefits Realisation

Zoo Case Study Examples

CEO Letter and Mandate

Stakeholder Constellation

Exhibit Relocation Scope

Eighteen Month Transition

Operational and Safety Risks

Board and Change Control

Visitor and Revenue Benefits

Relationship details

From	Relationship	To
Context and Objectives	leads to	Introduction
Introduction	leads to	CEO Letter and Mandate
Stakeholders	leads to	Project Context
Project Context	leads to	Stakeholder Constellation
Scope Definition	leads to	Planning and Controls
Planning and Controls	leads to	Exhibit Relocation Scope
Schedule and Phasing	leads to	Delivery Strategy
Delivery Strategy	leads to	Eighteen Month Transition
Risk Management	leads to	Risk and Governance
Risk and Governance	leads to	Operational and Safety Risks
Governance and Control	leads to	Risk and Governance
Risk and Governance	leads to	Board and Change Control
Benefits and Outcomes	leads to	Benefits Realisation
Benefits Realisation	leads to	Visitor and Revenue Benefits

---

Common Failure Modes and How to Avoid Them

Even well-intentioned groups routinely lose marks in predictable ways. The following failure modes are observable in practically every cohort's submissions:

• Omitting one required Content element entirely. Usually Element 1 (Strategic Alignment) or Element 6 (Success Measurement), both of which feel "high-level" and get cut under word count pressure. Solution: allocate Content elements to group members with named ownership and cross-check before submission.
• Paraphrasing PMBOK without application. Writing generic definitions of the knowledge areas without connecting them to the case study. Solution: every knowledge area paragraph must contain the project name.
• Treating the Staging Plan as a Gantt chart. Drawing a schedule and calling it a staging plan. Solution: include explicit stage gates and rollback options.
• Undifferentiated RACI matrices. Assigning R/A/C/I values without thinking about which party is actually singular-accountable. Solution: each row has exactly one A.
• Unequal contribution visible in the prose. Different sections reading in different voices. Solution: appoint a single group member as final editor with explicit authority to harmonise voice.
• Bibliography of URLs only. Citing web pages without author, date, or publisher metadata. Solution: every reference list entry must have author, year, title, and source with full publication details.
• Wrong PMBOK edition for the unit. Citing 4th Edition (nine knowledge areas) when the historical unit and rubric are based on 6th Edition (ten knowledge areas and 49 processes). Solution: confirm which edition the unit is taught from and cite that course framework consistently; do not describe it as the current professional standard.
• Over-length executive summaries. Three-page executive summaries at the front of a 15-page report. Solution: one page maximum, or cut entirely if not required.
• No diagrams. Relying entirely on prose in a discipline where visual tools (WBS, org charts, network diagrams, Gantt charts) are core. Solution: include at least one diagram per major section.
• Submitting at the deadline. No time for final review. Solution: internal deadline at least 48 hours before submission to allow quality checks.

---

A Suggested Workflow

The single biggest determinant of report quality is when you start. A group that begins in the final week will score in the C or P1 band regardless of individual ability. A group that begins four weeks out, with a structured workflow, can score HD. The recommended workflow:

Week 1 — Read rubric — Divide elements — Outline sections

Week 2 — First drafts — of all sections — Research references

Week 3 — Cross-review — Integrate diagrams — Harmonise voice

Week 4 — Final edit — Reference check — 48h buffer

Relationship details

From	Relationship	To
Week 1 — Read rubric — Divide elements — Outline sections	leads to	Week 2 — First drafts — of all sections — Research references
Week 2 — First drafts — of all sections — Research references	leads to	Week 3 — Cross-review — Integrate diagrams — Harmonise voice
Week 3 — Cross-review — Integrate diagrams — Harmonise voice	leads to	Week 4 — Final edit — Reference check — 48h buffer

---

Key Takeaways

• The Content component is 40% of the mark — prioritise it over everything else.
• All seven required Content elements must be covered explicitly; omitting any one forfeits substantial marks.
• HD-level content applies concepts to the specific case study, not generically.
• Strategic Alignment requires linking the project to a named strategic objective using theoretical frameworks.
• Accountability & Responsibility are distinct concepts; a RACI matrix makes the distinction visible.
• Organisation Structure should be classified using PMBOK's taxonomy and analysed for friction points.
• The Five Process Groups run concurrently and iteratively, not sequentially; HD treatment makes this explicit.
• The Ten Knowledge Areas (not nine — PMBOK 5th and 6th Editions) must each be applied to the case study, not just defined.
• Success Measurement has three levels (PM success, product success, benefits success) and a stakeholder dimension.
• The Implementation Staging Plan is not a Gantt chart — it requires stage gates, rollback options, and dual-operations protocols.
• Collaboration and Teamwork are worth 20% — uneven group contribution is fatal.
• Start the report four weeks before submission, not one week.

---

References

• Carr, N & Cohen, S 2011, 'The public face of zoos: Images of entertainment, education and conservation', Anthrozoös, vol. 24, no. 2, pp. 175–189.
• Cooke-Davies, T 2002, 'The "real" success factors on projects', International Journal of Project Management, vol. 20, no. 3, pp. 185–190.
• Ford, RC & Randolph, WA 1992, 'Cross-functional structures: A review and integration of matrix organization and project management', Journal of Management, vol. 18, no. 2, pp. 267–294.
• Galbraith, JR 1971, 'Matrix organization designs: How to combine functional and project forms', Business Horizons, vol. 14, no. 1, pp. 29–40.
• Kerzner, H 2017, Project Management: A Systems Approach to Planning, Scheduling, and Controlling, 12th edn, Wiley, Hoboken, NJ.
• Office of Government Commerce 2017, Managing Successful Projects with PRINCE2, 6th edn, TSO, London.
• Project Management Institute 2017, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 6th edn, PMI, Newtown Square, PA.
• Turner, JR 2014, Handbook of Project-Based Management, 4th edn, McGraw-Hill, New York.
• University of South Australia 2015, MPM411 Principles of Project Management — Group Report Marking Guide, UniSA, Adelaide.
• University of South Australia 2015, MPM411 Principles of Project Management — Zoo Relocation Project Brief, UniSA, Adelaide.