Early in a project-management career, targeting project coordinator and project officer roles. I turn ambiguous briefs into scheduled, costed, de-risked plans, then present them so decision-makers actually follow them: interactive timelines, risk heat-maps and visual roadmaps in place of dense reports.
Hover, tap or arrow-key through the phases to explore each one.
A full delivery plan for a Victorian Government program to install 120 smart sensor and public Wi-Fi units across 57 council sites, part of the broader Connected Communities Victoria initiative. Built as a Master's capstone (Kingsford University) and graded High Distinction. Below, the project-management work it took to plan it. Hover any card for detail.
Ready 26 councils to run and maintain a smart sensor and Wi-Fi network, lift public digital services and open useful facility data.
A Director of Project Management over four zones, with zonal PMs sharing authority with functional directors.
Feasibility, a Level-3 WBS, an MS Project schedule, phase-wise budgeting, and a phased risk register.
Across the capstone I worked through the full project-management lifecycle, from feasibility to handover.
SWOT and PESTLE analysis (funding, hardware-cost falls, AS/NZS standards, digital-inclusion targets) to test whether the program was viable and worth taking on.
A balanced-matrix structure over four zones, with an urban and rural outsourcing and recruitment plan to staff dispersed sites.
A Statement of Work with AS/NZS acceptance criteria, plus a Level-3 WBS across five phases and their tasks.
The 310-day plan with dependencies, the critical path and slack analysis. See it below ↓
Phase-wise budget to $1.8M (labour ~77% of cost) using grassroots estimates and learning-curve assumptions.
An 18-risk register with a four-quadrant response, plus KPIs, 360° appraisals and a conflict-resolution matrix.
The program was scheduled in Microsoft Project: summary phases, task dependencies, and a critical path running Project Initiation, Regulatory Approvals, Contractor Engagement, Integration, System Testing and Handover. Toggle the highlight to see which tasks carry no slack.
Click any task, row or bar, to inspect its dates, predecessor and float.
Recreated depiction for interactive purposes. This schedule view has been rebuilt for the web from the actual Microsoft Project (.mpp) schedule produced for the CSWN plan. Dates, durations, critical path and slack reflect that plan.
Bar length is the share of the $1.8M budget. Installation and early planning carry the weight.
Initiation, Regulatory Approvals, Contractor Engagement, Integration, System Testing and Handover set the finish date; any slip here slips 07 Nov 25.
Site Assessments carries 39 days of float, Installation 28 days, Procurement 5. That flexibility smooths resourcing without risking the deadline.
Grassroots build-up estimates from vendor quotes, with learning-curve efficiencies across the repetitive multi-site installs.
Highest-rated risks, at a glance
Risk matrix · count by severity and phase (hover any cell for the risks behind it)
Severity here is recreated as a 1 to 5 numeric score (High = 5, Medium = 3, Low = 1) to show one way to quantify and depict risk on a project. The original CSWN register used a qualitative High / Medium / Low rating.
Full risk register · all 18 risks
| Risk event | Phase | Rating | Response strategy |
|---|---|---|---|
| Poor definition of project scope | P1 | High | Avoidance · clear scope documentation from the start |
| Delays in regulatory approvals | P1 | High | Avoidance · early regulatory engagement and tracking |
| Unavailable subject-matter experts | P1 | Medium | Mitigation · backup personnel and cross-training |
| Inaccurate feasibility studies | P1 | Medium | Mitigation · double-check studies and add contingencies |
| Inaccurate cost estimates | P2 | High | Mitigation · detailed cost analysis and research |
| Vendor selection delays | P2 | Medium | Acceptance · buffer time for selection |
| Contractor unavailability | P2 | Medium | Transfer · penalty clauses in contracts |
| Inadequate contractor expertise | P3 | High | Avoidance · select contractors with proven expertise |
| Material availability | P3 | High | Transfer · supplier contracts with late-delivery penalties |
| Technical integration issues | P3 | High | Mitigation · pre-installation compatibility testing |
| Regulatory compliance & safety issues | P3 | High | Avoidance · regular testing to ensure compliance |
| Site preparation delays | P3 | Medium | Acceptance · buffer time in the schedule |
| System testing failures | P4 | High | Mitigation · rigorous testing during integration |
| Staff availability for training | P4 | Medium | Acceptance · flexible schedules and multiple sessions |
| Training material development delays | P4 | Low | Mitigation · early development and clear deadlines |
| Poor quality assurance | P5 | High | Avoidance · consistent quality checks throughout |
| Unacceptable handover to stakeholders | P5 | High | Mitigation · involve stakeholders throughout |
| Cash flow problems | P5 | Medium | Acceptance · regular financial reviews and contingency funds |
Rebuilt for the web from the risk register in the CSWN report. Each risk carried a qualitative rating and a four-quadrant response (Avoidance, Mitigation, Transfer, Acceptance), with governance layered on top: KPI tracking, 360° appraisals, stakeholder surveys and a common code of ethics.
A multi-site operations and delivery role: I coordinate work, people and compliance across three high-volume venues, reporting to senior leadership. It is the day-to-day practice of the project-management disciplines above.
Direct ~50 staff across three sites: rostering, resource allocation, performance management and day-to-day delivery.
Built and maintained compliance frameworks, CAPA tracking and corrective-action registers across three sites.
Structured written briefings to senior leadership on compliance status, operational risk, project performance and financial outcomes.
Identified and implemented improvements cutting backend operating costs by over 35% through evidence-based consolidation.
Hover any tile for a real example.
Task breakdown, dependencies and timeline management.
Decomposing scope into deliverable, trackable tasks.
Finding the tasks that actually move the deadline.
Rating risks and assigning owned response strategies.
Phase budgeting and estimate methods.
Keeping delivery aligned to requirements and standards.
Decision-ready reporting to senior leadership.
Allocating effort across concurrent workstreams.
Evidence-based redesign of how work flows.