Case Study

20 Tickets Resolved. Developer Effort Cut by Up to 90%.

Australian Construction and Infrastructure Company

Challenge

A large organisation was managing a highly customised, complex legacy project management system with an ongoing stream of minor user requests and defects.

While these changes were often simple — from correcting typos and list ordering to fixing financial rounding — they followed the same development process as larger, more complex features. Each ticket required developer time to understand, implement, test, deploy and review.

As a result, smaller requests were frequently deprioritised in favour of higher-value feature work, creating a growing backlog and long-running support tickets.

The challenge was clear: how could the organisation accelerate minor changes without increasing headcount or taking developers away from more valuable work?

No items found.
PRocess

We designed an AI-enabled development workflow that allowed non-technical team members with strong product knowledge to use GitHub Copilot as a junior developer for clearly defined, low-risk changes.

Rather than introducing an entirely new technology stack, the approach built on the organisation’s existing GitHub infrastructure, Jira workflow and delivery processes.

We introduced dedicated pull request environments, supported by automated GitHub Actions workflows, allowing AI-generated changes to be deployed and verified independently before entering the standard development and QA pipeline.

Importantly, human oversight remained central to the process. Two human touchpoints were built into the workflow before any AI-generated code could progress, maintaining code quality and alignment with existing development standards.

This created a new pathway for simple changes: identify → AI develops → deploy → verify → developer reviews → release.

No items found.
Results

The results demonstrated how AI can significantly reduce the effort required to deliver smaller software changes.

  • Up to 90% reduction in developer effort per change, from approximately 1–2 hours to just 5–10 minutes of developer code review.
  • 20 tickets resolved across four release cycles, including long-running ServiceNow requests.
  • 10 tickets resolved in the latest release, up from just one in the first cycle as confidence in the process grew.
  • No regressions or issues introduced across the four release cycles.
  • No additional developers required to clear the backlog of smaller changes.
  • The success of the model led the client to expand from three to six dedicated pull request environments to support growing adoption.

Beyond the numbers, the workflow has changed how smaller improvements are prioritised and delivered. System analysts can now drive well-defined changes themselves, while developers remain focused on higher-value engineering work.

The project demonstrates that AI-enabled development doesn’t require a major transformation of existing systems or infrastructure. With the right processes, product knowledge, clear requirements and human oversight, organisations can introduce AI directly into their existing delivery cycles — and start turning long-standing backlogs into measurable progress.

No items found.
No items found.