CASE STUDY · EST. 2011 · APAC

Six major programs transitioned to remote delivery in two weeks. Sprints didn't miss a beat.

The Situation

The Australian Taxation Office engaged ZXM to lead the transition of six flagship delivery programs to fully distributed working — across a workforce of several hundred people.

ZXM was already embedded at the ATO. When this policy was introduced, the question was not whether the programs could move to remote delivery. It was about which Branches would struggle, how quickly any problems could be diagnosed, and whether the capability already in place would hold under the pressure of changes to work policies.

Three core outcomes were required:

rabbit-running

Rapid remote deployment

Move 100+ people to remove work with the least impact to delivery.

single-man-hierachy

Workforce effectiveness

Minimise productivity and delivery impacts.

direction-button-arrows

Resilience to change

Ensure the transition did not create change fatigue.

What the diagnostic found

Before any transition plan was designed, ZXM mapped capability maturity across all six programmes to identify which areas were at genuine risk of productivity collapse. The finding was structural: resilience to the remote shift was not evenly distributed, and it was not random.

Programmes that had progressed furthest in their capability development were adapting. Those where foundational practices — shared working agreements, visible backlogs, disciplined retrospectives — had not yet embedded were struggling. The constraint was not technology or willingness. It was the absence of the operating habits that make distributed work function.

That finding shaped what ZXM did next. The intervention was not a single remote-working guide issued to all six programmes. It was a differentiated response — targeted coaching intensity directed at the areas where the capability gap was greatest.

 

What changed

ZXM developed a remote delivery strategy within 48 hours of the transition decision, covering facilitation guides, virtual programme coordination practices, team working agreements, and tooling recommendations. Critically, the strategy differentiated by maturity level rather than treating all programmes as equivalent.

Scrum Masters in lower-maturity areas received direct one-on-one coaching. Programme-level retrospectives were run specifically to surface what was breaking in the remote context and to produce concrete improvements. Digital tooling practices were strengthened to make work visible in an environment where physical boards and shared spaces were no longer available. Disaster recovery protocols for connectivity and tooling failures were introduced to remove the disruption caused by technical incidents.

The ATO’s existing investment in delivery capability maturity meant the highest-maturity programmes needed little intervention. The coaching effort was concentrated where the structural gaps made remote delivery genuinely fragile.

What held

All six programs maintained continuity of delivery throughout the transition. Remote working guides were distributed within two weeks. Teams at risk were identified, prioritised, and supported before productivity degraded. No programme missed a delivery commitment due to the shift to distributed work.

Teams that received targeted coaching became more deliberate in their communication practices, more disciplined in backlog refinement, and more consistent in keeping work items visible to the rest of the program. The transparency improvements that the remote context demanded proved durable — they persisted after the acute transition period ended.

The ATO’s prior investment in delivery capability was the structural reason the transition held. Programs with stronger foundations adapted faster and required less intervention. The engagement confirmed a consistent pattern: capability maturity determines organisational resilience to operating-environment shocks, not planning for the shock itself.

6 programs delivered

All six flagship program maintained sprint and Programme Increment continuity through the transition.

Capability gap mapped

Maturity assessments identified which programmes were at risk before productivity degraded.

Practices sustained

Remote communication disciplines and backlog transparency persisted beyond the transition period.

search previous next tag category expand menu location phone mail time cart zoom edit close