DevOps Frequently Asked Questions

What is DevOps & Why Should You Care?

DevOps Diagram

DevOps is the centerpiece between Software Engineering, Quality Assurance, and Technology Operations, leading to crossover IT roles and a unified approach to development, infrastructure procurement, and product deployment. Essentially, it is the process of applying agile and lean approaches to improve communication, collaboration, and integration within an IT department to enhance the entire service lifecycle.

The primary value is creating communication between the Operations Team and the Development Team, which enables faster development and more supportive, predictable application releases. The focus shifts from “working the software” to the overall service provided.

A typical Operations team is under constant demand. They take care of everything data center driven, including planning for all IT infrastructure deployments, managing a budget, lifecycles of equipment, resources to manage that equipment, support for legacy and current applications, monitoring and maintaining system performance, support for internal and external clients, and maintaining uptime. They receive and troubleshoot end user issues and maintain security procedures as well. The Operations Team mindset is very different from the Software Development Team.

Software developers work in a fast paced and dynamic environment that has very specific responsibilities; they manage full lifecycle application development from designing, coding, and debugging applications to implementing performance tuning and integrating software with other systems. They are very technically focused on code, but not on IT infrastructure. The Software Development Team wants to make sure the system is accessible to their clients and are less concerned with the security of that system.

The normal response in an environment where there are no DevOps methodologies, meaning very little communication or interaction, is typically the counter-offensive project delay. Long procurement times lead to the long project cue time, and future projects enter the queue based on importance or critical nature, which pushes lower priority issues to the bottom of the list causing them to see longer solution times.

Bringing the Software Development Team together with the Operations Team helps to create more sound and secure developments, while eliminating some FUD (fear, uncertainty, doubt) factors. The Operations Team has better insight and experience working with the infrastructure, while the Software Team knows how their code works. Together they can create a secure platform for the software to reach the customer in a streamlined process, which increases time to value (TtV).