Delivery Leadership
Planning, prioritisation, dependencies, risk management, release coordination and outcome-focused execution across business and technology teams.
Programme overview
Australian Unity needed to improve daily care-worker rostering while migrating customer and workforce capabilities from a legacy platform into Salesforce. Because both initiatives depended on the same operational data, the rostering solution, migration programme and business-readiness activities had to progress together.
01
Business Need
Smarter daily rostering
Provide an effective scheduling solution for care workers and customers, balancing service requirements, worker availability and operational cost.
Legacy-to-Salesforce transformation
Migrate customer and care-worker capabilities across clinical and non-clinical service categories while retaining the required rostering functionality.
02
My Role
Delivery leadership
- Worked across operations, product owners, SMEs, engineering, integration teams and the external rostering vendor.
- Coordinated migration validation, system testing, BAT, UAT and dress-rehearsal activities.
- Led Jira and Zephyr workshops, reviewed scenarios and evidence, managed defects and supported business sign-off.
- Maintained programme artefacts, traceability and reporting through Jira, Confluence and consolidated Excel reporting.
Hands-on contribution
- SQL stored procedures, automated CSV extraction and SQL Agent scheduling.
- Python file processing, secure SFTP workflows and operational reprocessing.
- Tableau data-quality, availability and KPI dashboards.
- Salesforce functional validation, QuerySurge comparisons and migration checks.
03
Building the Rostering Data Flow
Australian Unity engaged Biarri to support workforce rostering. I validated the business requirements and designed the data-supply process required to feed the solution from the legacy SQL Server environment.
I replaced the existing master extraction procedure with a customised stored procedure that returned only the data required for rostering. The output was generated as CSV files through Python and scheduled through SQL Server Agent to run each morning at 6:00 am.
Legacy SQL Server→
Custom Stored Procedure→
Python CSV Processing→
SQL Agent→
SFTP→
Biarri
I coordinated the secure SFTP setup between Australian Unity and Biarri so that input files could be transferred for processing and completed output files returned for downstream use.
04
Turning Poor Data into Trusted Data
When the scheduling outcomes were inconsistent, I did not treat the problem as an optimisation-engine defect. I traced the issue back through the data flow and identified widespread source-data quality problems.
Missing mandatory data
Incorrect source values
Wrong field mappings
Incomplete onboarding records
I developed Tableau dashboards that exposed these issues directly to operations teams so that records could be corrected in the source system as part of an ongoing process rather than through one-off cleansing.
I also recommended updates to the onboarding standard operating procedures for new customers and care workers. This reduced recurring data gaps and improved the quality of information supplied to the rostering solution.
05
Operational Automation Across 24 Branches
Returned Biarri files arrived as compressed outputs. I created Python and SQL Agent processes to extract the files, reprocess them, add protected health information that was intentionally excluded from the vendor input, refresh dashboard datasets and place the final outputs into a controlled reprocessed location.
I then coordinated with the WebMethods team to automate delivery of the reprocessed files into the relevant SharePoint location for each branch.
24Branches supported
3Run frequencies
Daily · Weekly · FortnightlyScenario-based processing
Biarri Output→
Python Extraction→
PHI Reprocessing→
Dashboard Refresh→
WebMethods→
Branch SharePoint
06
Salesforce Transformation
While the rostering solution supported the legacy platform, Australian Unity was also migrating care-worker and customer capabilities into Salesforce. The non-clinical service category needed to retain the Biarri scheduling model after migration, even though Salesforce provided its own scheduling engine.
I contributed to source-to-target mapping and coordinated with Biarri and internal teams to prepare the rostering integration in parallel with the Salesforce migration.
01Requirements & mapping
Reviewed migration and scheduling requirements and supported source-to-target alignment.
02System testing
Briefed offshore testers, reviewed test cases and evidence, and triaged defects with development teams.
03Integration validation
Validated connectivity, configuration and Biarri scheduling outcomes within the Salesforce landscape.
04UAT & BAT
Facilitated Jira workshops, scenario development, review, execution, sign-off and test-summary reporting.
05Dress rehearsals
Managed Jira execution cards and dashboards to provide clear progress visibility across end-to-end scenarios.
I also acted as the business-analysis lead for end-to-end BAT across scheduling and service-delivery modules, working with product owners and SMEs to create migration scenarios for dress rehearsals. Testing was managed through Jira and Zephyr, with supporting artefacts maintained in Confluence.
07
Business Impact
The programme established an automated workforce-rostering data flow supported by improved source quality, operational monitoring and repeatable branch-level processing.
It also enabled the rostering capability to progress alongside the Salesforce migration, supported business readiness through structured BAT and UAT, and provided management visibility through Jira, Tableau and consolidated status reporting.
08
Technology
SQL ServerStored ProceduresPython
SQL Server AgentTableauSalesforce
SFTPWebMethodsSharePoint
JiraZephyrConfluence
QuerySurgeExcelBiarri
View the vendor's published home-care scheduling case study ↗
Key learning
Enterprise transformations succeed when technology, operational processes, data quality and stakeholder alignment improve together.