Portfolio, programme and project management

We don’t just advise. We take the delivery.

Portfolio, programme and project management for the transformations that cannot be allowed to fail.

Twenty-three years delivering complex P3M engagements across some of the most demanding sectors in the market. We operate client-side and embedded – accountable for delivery outcomes, governance quality and stakeholder confidence from initiation through to business-as-usual transition. Our 40+ senior P3M professionals hold the outcome, not just the plan.

How we work Selected engagements

Delivering complex programmes

Senior P3M professionals

Programmes under management

How we work

We don’t just advise. We deliver.

We operate client-side and embedded – accountable for delivery outcomes, governance quality and stakeholder confidence from initiation through to business-as-usual transition. The distinction that matters is whether the person holding the plan is also holding the outcome.

Structured, then fast

Governance with an agile cadence

Structured delivery governance combined with agile execution cadences allows pace without sacrificing quality, compliance or stakeholder confidence – provided the governance is designed for the delivery model rather than inherited from a template.

At any scale

One project, or a whole portfolio

The same disciplines run a single project and a multi-stream, multi-vendor portfolio spanning tens of billions in capital investment. What changes with scale is the governance layering and reporting cadence, not the standard applied.

Capability, then handover

Measured beyond project close

Every engagement is anchored to building client-side capability and embedding repeatable governance frameworks. The measure is whether the outcomes endure after the programme closes and we have gone.

The delivery lifecycle

Eight stages, and the same standard at every scale.

From business case through to benefits realisation. Select any stage to see what we do inside it, what it produces, and the question we hold it to.

01 – Initiation and business case

Establish what is being bought, what it is worth, and who is accountable for it.

02 – Planning and mobilisation

Build the plan, the controls and the team – in that order.

03 – Execution and delivery

Run the work across streams, vendors and functions that do not report to each other.

04 – Change control and dependency management

Absorb change without stopping the pipeline – which is where most programmes fail.

05 – Testing and quality assurance

Prove it works before the business finds out that it doesn’t.

06 – Data migration and cutover

Govern data migration as a standalone workstream, with extraction, cleansing, validation and reconciliation evidence completed before any cutover.

07 – Transition to BAU

Deployment is not the outcome – an internally supported, operable service in steady operation is.

08 – Benefits realisation

Prove what the investment returned, measured against what the business case originally claimed.

Selected engagements

Where the programme could not be allowed to fail.

Each engagement is described in the terms the organisation measured it by. Where a client is identified by sector rather than name, that is by agreement.

Critical infrastructure

Six years bridging engineering standards and digital delivery

Six-year management of a $30M application portfolio supporting a domestic capital works programme. A core team of 14 absorbed 350+ scope variations, bridged engineering and digital governance regimes, and maintained 50+ system interfaces across four concurrent programmes.

Higher education

A $70M programme, governance built from nothing

$70M, five-year technology transformation for a university community of 30,000. Built the governance framework from nothing before delivery commenced, then ran six concurrent projects under a ten-role accountability model – absorbing a mid-programme funding reduction without derailing any project.

Enterprise services

Five HCM modules, three countries, eleven months

Greenfield cloud HCM platform delivered across Australia, New Zealand and the Philippines in eleven months. Five modules in parallel, 18+ integrations live at go-live, 5,000+ employees transitioned with zero payroll disruption in all three jurisdictions.

Service domains

Seven domains, from portfolio down to cutover.

Organised around what organisations ask us to take on. Three commitments run through all of them.

Accountable for delivery

We operate client-side and embedded, holding the outcome — not reporting on it from a governance seat with no authority to change anything.

Governance sized to the work

Structured delivery governance with agile execution cadences, layered up for a portfolio and stripped back for a project, without changing the standard applied.

Capability left behind

Repeatable frameworks, change playbooks and integration standards embedded and transferable — so the next programme starts from something.

Seven domains — select any one to see the detail.

“Every programme director tells me theirs is the priority. I have no portfolio-level view that lets me arbitrate between them on anything other than volume.”

We establish portfolio governance, benefits realisation and investment prioritisation frameworks, then the multi-programme visibility that makes them usable — consolidated registers and dashboards giving a portfolio-wide position rather than a stack of project reports. Where two governance regimes collide, we design the connective layer that reconciles them at process level instead of escalating the tension.

Services
Portfolio governance, benefits realisation and investment prioritisation frameworks Multi-programme visibility dashboards and consolidated scope variation registers Application portfolio management across enterprise platforms and interfaces Dual governance models bridging engineering standards and digital programme delivery Portfolio-level benefits tracking against business case commitments Baseline and target measures reported into portfolio governance
Frameworks and tooling
MoP PRINCE2 MSP Portfolio dashboards and consolidated registers
Delivery Model

Portfolio management leadership, portfolio governance framework establishment, and independent review of a portfolio already running.

“We have six projects, four vendors and a steering committee, and no single person who can tell me whether the programme as a whole is going to land.”

We provide programme leadership that holds the outcome — establishing the operating model, running the controls, coordinating cross-functional teams across IT, HR, finance, operations and third parties, and carrying the executive relationship. Where no programme governance exists, we build it before delivery starts rather than assembling it while things are already moving.

Services
End-to-end programme leadership from governance design to BAU transition Programme operating model design and executive-level approval Cross-functional delivery teams spanning IT, HR, finance, operations and third parties Risk, issue and dependency management — RAID logs, escalation protocols and controls Executive steering committee reporting and stakeholder confidence management Coordination of multiple senior project managers under unified programme controls
Frameworks and tooling
MSP: Managing Successful Programmes PRINCE2 and PRINCE2 Agile SAFe Agile at Scale PMI PMBOK
Delivery Model

Programme director and programme manager engagements, PMO establishment, and embedded programme leadership into a client-led initiative.

“We need this delivered — not governed, not advised on, delivered — and we need whoever does it to still be here at cutover.”

We deliver across the full project lifecycle: initiation, planning, execution, monitoring and closure. The delivery model is matched to the project’s context and risk profile rather than to a house preference, which in practice means agile where discovery dominates, waterfall where compliance does, and hybrid more often than either.

Services
Full project lifecycle delivery: initiation, planning, execution, monitoring, closure Agile, waterfall and hybrid delivery models matched to context and risk profile Sprint cadences aligned to integration and testing milestones Schedule, budget and scope accountability at project level Project board reporting and escalation into programme governance Project closure, lessons capture and handover
Frameworks and tooling
PRINCE2 PMI PMBOK Agile, waterfall and hybrid JIRA, Confluence, Asana
Delivery Model

Project management engagements, delivery team augmentation, and recovery of a project already in difficulty.

“Every variation stops something. And when delivery slips, each vendor can point at another one and we cannot prove who is right.”

We run integrated change control with structured triage, impact assessment across cost, schedule, compliance and dependency, and an audit-ready trail from request to artefact. Vendors are governed inside the model rather than alongside it — SLA frameworks, unified performance dashboards and milestone-based accountability, so delivery performance is evidenced rather than argued.

Services
Integrated change control with structured triage and impact assessment Consolidated change registers giving cross-programme visibility Release scheduling that batches compatible change and protects critical milestones Audit-ready traceability from variation request to system and engineering artefact Vendor performance management with SLA accountability across subcontractors Unified vendor performance dashboards and regular governance reviews
Frameworks and tooling
ITIL Service Management SLA and contract governance frameworks Consolidated change registers
Delivery Model

Change control framework establishment, vendor governance, and programme-level change management on a live portfolio.

“We are told the build is complete. Nobody can tell me whether the data will reconcile or whether payroll will run on the Monday.”

System testing governance and data migration are run as first-class workstreams with their own evidence trails, not as tasks inside a build plan. That means SIT and UAT governance with defect tracking through to closure, statutory compliance checkpoints inside every testing cycle, and migration frameworks covering extraction, cleansing, validation and parallel reconciliation before anyone approves a cutover.

Services
System testing governance — SIT, UAT, defect tracking, resolution and optimisation Statutory and compliance checkpoints embedded in every testing cycle Data migration planning, governance, validation and parallel reconciliation Integration governance with a master integration register and end-to-end flow validation Cutover planning, rehearsal and go/no-go decision support Post go-live defect management, hypercare and optimisation planning
Frameworks and tooling
ISO/IEC/IEEE 29119 Master integration registers JIRA and ServiceNow Parallel reconciliation frameworks
Delivery Model

Test and cutover governance, data migration workstream leadership, and independent go-live readiness assessment.

“The last programme went live and the support model arrived three months later. By then the delivery team had gone and nobody internally knew how it worked.”

Transition is designed as a deliverable rather than a phase that happens if there is time — support models, escalation pathways, internal system administration capability and role-specific training, all operating before hypercare concludes. Benefits are then tracked against what the business case actually claimed, into portfolio governance.

Services
Transition to BAU: support models, capability uplift, training and continuous improvement Internal system administration capability established before hypercare concludes Escalation pathways and operational support model design Post go-live adoption monitoring and optimisation planning Benefits realisation maps, plans and measurement against business case commitments Repeatable governance frameworks and playbooks transferred for reuse
Frameworks and tooling
ITIL Service Management PROSCI Change Management Benefits realisation maps and plans
Delivery Model

Transition and hypercare leadership, capability uplift programmes, and independent benefits realisation review.

“Our assurance reviews are point-in-time, expensive and always arrive after the decision they should have informed.”

We apply AI-enhanced assurance modelling across all three levels — portfolio, programme and project. It draws on the governed method library that carries the recognised standards for each domain inside it, so an assurance position is produced consistently and every finding traces back to the source it came from rather than to the reviewer who happened to be available.

Services
Portfolio assurance modelling — AI-enhanced assurance services Programme assurance modelling — AI-enhanced assurance services Project assurance modelling — AI-enhanced assurance services Evidence-linked findings scored consistently against a defined rubric Traceability from every finding back to its originating source document Independent assurance ahead of a gate, rather than after it
Frameworks and tooling
StepChange method library PRINCE2, MSP and MoP embedded in the method Evidence traceability matrices
Delivery Model

Independent assurance engagements, assurance retainers across a portfolio, and point-in-time review ahead of a governance gate.

Start a conversation

Some programmes cannot be allowed to fail.

Whether it is a portfolio without a single view, a programme that lacks the governance to run it, a fixed-window delivery, or a recovery that needs someone accountable rather than advisory – talk to the people who would do the work.

Email us +61 8 9324 1020