Trility helped reduce labor expenses at all retail locations for this client by providing architectural guidance and continuing to secure and automate accounting and finance processes from legacy systems to a cloud-based solution using CI/CD technology.
This growing retail client sought to reduce accounting labor expenses by automating accounting workflow from 265+ retail locations by integrating its current reporting systems to a cloud-based solution. Accounting and finance teams needed a secure way to streamline how financial information was sent and fed into Enterprise reporting systems.
The client also wanted to improve the capabilities of their existing engineering team members through coaching and paired programming – ensuring the team is positioned to continue to simplify and automate workflows for this area of businesses and other ones.
In addition to providing architectural guidance, Trility identified where technical debt was blocking or slowing down the developers. Many of the issues were solved by building a code repository and using Infrastructure as Code (IaC) to build CI/CD pipelines to further automate testing and deployments, as well as writing the tests to expedite the amount of time it was taking the team to troubleshoot and resolve failed tests.
As Trility improved and eliminated duplicate code with a repository and created CI/CD pipelines, they actively worked with the client's team members and trained them on how to build and test the pipelines with both pair and mob programming. The team also produced documentation, Readme files, how-to videos, and tools that support markdown and linking in order to set them up for success at project end. This information always spotlighted the Why, How, and What the intended results.
The accounting and finance departments reduced labor costs for reporting across all locations.
Eliminated redundant and duplicate code in the building and testing of the application through the creation of a code repository and CI/CD pipelines.
Tests were written in a consistent manner with the frontend UI tests so a Javascript developer could easily support the frontend and backend testing. If a test failed, the team also had relevant information to reference to troubleshooting and fixing issues that previously could take 20 minutes, now took seconds.
The developers were able to deliver new features and improve existing ones due to the increase in automated processes and workflows and leveraging reusable code patterns.
