The main motivation of the DevOps movement is fast and good cooperation between operation and development areas. The requirements are elementary, which means the DevOps culture is currently on fertile ground, where modern development methods with short iterations and daily retroperspectives make the close interaction between development and operations indispensable. The priority of DevOps is to ensure quality and promote change without discriminating against any of the groups during the fulfillment of their mission.
Mutual interaction between development and operations is essential for the fulfillment of project and day-to-day business within IT organizations. Unfortunately, a fundamental conflict of objectives often causes frictional losses, which cannot be resolved without overarching rules and flexible processes: The task of the development area (implementing change) conflicts with the task of the operations area (ensuring availability). In the worst case, more energy is invested in a "blockade" mentality and mutual recriminations than in a mutual search for solutions. One reason for this can be found in the type of collaboration. Years ago, inflexible and rigid procedures were preferred ("waterfall model" and long, complex iteration cycles), but today a dynamic, flexible approach is favored. DevOps is neither a standard nor a certification.
Instead: it is a common framework of values in which tunnel vision is abolished and focus is placed on communication and interaction with a view to a shared perspective. At COVIS, this involves a high degree of automation, which allows us to quickly generate reproducible results with the ability to apply corrections. This includes a healthy "error culture," which allows trial and error based on measurable information and a clear product view. Functionality takes precedence over technical shortcomings.