8CIOReview | | SEPTEMBER 2023To prepare for the future, you must understand the past. To understand the term DevOps, we must deep-dive into the original ideology behind it. When Patrick Debois first introduced the term "DevOps" in 2009, it was simply a re-arrangement of Development and Operations teams, to work towards common and non-conflicting goals. Since then, practising DevOps has evolved, and its implementation now addresses the entire software development lifecycle management. Still, nobody seems to agree on what DevOps means. As a conceptual and holistic approach, it's about culture, automation, lean, measuring and sharing (CALMS). The foundation for DevOps should start by establishing teams with full autonomy inside their domain to nourish the culture of ownership and innovation.DevOps emerged to streamline software development in both productivity of developers and the reliability of operations. Promoting a better understanding of service quality, security and foremost end-to-end accountability, it's not about creating new teams or roles, but rather a cultural shift that impacts the entire organization. However, what started well, some organizations have regressed by creating DevOps roles and teams and delegating responsibility for infrastructure, tools, and software delivery capabilities to someone else. Where did we go wrong?DevOps Delegation DownfallsA typical challenge is understanding that DevOps is not a position, a tool or even a process. For years, DevOps-TEAM IS A MYTHBy Niko Kivelä, Head of DevOps, SOK (S Group)Niko KiveläIN MY OPINION
< Page 7 | Page 9 >