The Burgess Group is a leader in medical claims modeling and reimbursement. At the intersection of healthcare and finance, their Operations team works hard to thread the needle of regulatory compliance. At the same time, they have been growing rapidly to meet the needs of their clients, forcing them to become more efficient in their management of configuration drift.
The Burgess Group has doubled in size in the past year and looks to double again. Having more people both increases the size of each release and introduces new possible points of miscommunication. In order to maintain the quality of the product delivered to the end user, Jeffrey Friedman, Director of IT at Burgess, started using UpGuard to detect configuration drift.
Burgess was already using Octopus Deploy to automate part of the release process. But, as Jeffrey Friedman and others have found, automation is not the same as validation. After reading Jez Humble's Continuous Delivery, Friedman saw clearly that he needed separate mechanisms to for deployment and confirmation.
The comprehensive scans that UpGuard runs out of the box gave a baseline for existing drift. That validated further investigation with UpGuard's custom policy toolbelt. With support from the UpGuard team, Friedman built up a library of UpGuard policies to test incoming builds for unexpected configuration changes, preparing his team to handle massive growth without compromising on quality.