Throughout this text, we have repeated that DevOps is a sum of practices and tools. However, its reason for existing, its original motivation, has its behavioral part as the slovenia mobile database important intangible element. As we said, the adoption of DevOps requires another form of integration between departments that originally had different interests.
Many responsibilities (and talents) that were previously typical of operations migrate to projects, which gain sovereignty to define various aspects of infrastructure in their own code – and with this autonomy also comes responsibility for any problems with their deliveries.
Let it be clear, therefore, that a change in culture is essential for the adoption of DevOps . In traditional IT, mechanisms of blame transfer and responsibility abandonment prevail, while in “post-DevOps” IT, responsibility for delivery is shared and everything possible is automated (mainly testing and delivery).