News

We have a long history of using automation to enable teams to deliver regularly without drama. When we start a consulting relationship, one of our first steps is evaluating the process required to automate deployment of whatever we’re building for them. This process of thinking through how to simply and easily get our work out for testing and production usage pushes the team to think earlier about real value for real customers.

Your business isn’t generic, so why should your software be? Off-the-shelf tools are designed for the average use case, often the broadest audience, the safest assumptions, and the lowest common denominator. While they might work for a few months, they eventually reveal their limits through clunky workflows, rigid systems, hidden risks, and growth bottlenecks you didn’t plan for.

Brian Dukes, CTO, discusses how DevOps automation impacted the Account Center project with Consolidated Communications.

DevOps is an approach to creating software which works to reduce the gap between coding and deploying, allowing the same team which created the code to deploy and monitor the application, generally through automating much of that deployment and monitoring process. In order to achieve the strong outcomes associated with teams practicing DevOps, the DORA Core model highlights building capabilities in the following categories: Climate of Learning, Fast Flow, and Fast Feedback.