DevOps Teams and Liaisons
In the last 20 years, software development has been undergoing a transformation. We’re all familiar with the disciplines of software development, quality assurance, and IT operations — developers would write code, kick it over the net to QA for testing, and then when it was ready, hand it off to IT for deployment. This model worked fine when software was shipped on CDs and releases were on an annual or bi-annual schedule.
Today, companies need to respond to a constantly-changing marketplace, and have largely adopted the software-as-a-service model, which allows them to provide near-immediate updates and bug fixes to their web applications. The old way of compartmentalizing software development roles doesn’t work well in this scenario, as team hand-offs can be inefficient and slow when different teams’ goals don’t sync with each other.
DevOps is the intersection of each of these roles — a blending of responsibilities that enhances communication and collaboration. Developers find themselves writing tests, performing builds, and deploying to dev test environments. QA personnel find themselves writing code for test harnesses and deploying to QA test environments. The DevOps team increasingly deploys to the cloud, rather than to physical servers managed by a local IT team, so DevOps needs to become its own IT team. With so much happening, the role of DevOps Liaison has arisen to keep all the other roles working together smoothly.
An experienced HOS DevOps liaison can facilitate communication among all DevOps team members, and provide administrative support and training to help your team meet its objectives.
HOS can also supply resources for any of the following roles:
- DevOps Evangelist
- Release Engineer
- Automation Architect
- Developer Test Writer
- UX Tester
- DevOps Engineer