An Esfera Perspective on DevOps

Within the agile universe, there are strictly technical practices (such as TDD, BDD, test automation) and others focused on management (such as Scrum ceremonies). We can place DevOps in a space that cuts across both.

DevOps is an acronym for Development and Operations, referring to the integration of both areas to build software products.

Ignacio Raguet and Joaquín Moreno Fernandez—two Esféricos dedicated to implementing DevOps in organizations and training those who are interested—share their vision in this post on this way of conceiving software development. 

To define DevOps in simple terms, you could say it's a way of working or—the definition Ignacio and Joaquín find most fitting—a mindset (a way of thinking, a paradigm).

For Them, the Name "DevOps" Falls Short

Beyond Development and Operations, any agile software project involves other areas such as Security, Infrastructure, or Auditing. All of them must be aligned around the common goal of building products. However, it's also true that Development and Operations experience the most tension between them due to how they view their objectives: while maintaining stability is fundamental for Operations, Development proposes changes, new features, or enhancements that often put that stability at risk.

In a development project, it is essential that everyone involved pursues the same goals.

To achieve this, we need to move past the idea that there is one team for development, another for infrastructure, or another for security, and start thinking more in terms of a Product Team—one that encompasses all the roles required to successfully develop, test, and deploy the product.

🎯 DevOps is often thought of as a department within an organization. At Grupo Esfera, we propose considering it—and putting it into practice—as a mindset that spans technical practices, organizational structure, and people.