When thinking of how organizations implement DevOps, a church is generally not the first prospect that comes to mind. Callibrity worked with Crossroads, a Cincinnati based church organization, to help establish a national presence. Crossroads’ digital product team worked alongside Callibrity to create software solutions that can support Crossroads’ large and expanding user base. With the support of Callibrity, Crossroads embraced modern, scalable approaches such as DevOps from ideation to deploying code to production.

In Part 1 of this series we took a look at some common symptoms of organizations that could benefit from the adoption of DevOps principles. In this post we’ll dig a little deeper into DevOps and answer questions like: Where did DevOps originate? How does DevOps define itself? And what are some of DevOps core tenants?

The development team finished the product 3 weeks ago, but it’s still not in production. You released a new feature and half the website went down. A significant amount of your day is spent dealing with production outages or issues. No matter what your role is, if you work in a technology organization, chances are you’ve heard the term DevOps. If any of the above problems sound familiar, chances are your company could benefit from adopting DevOps practices.