DevOps

DevOps is not a phase model, but a cry for help from the IT industry: against human exhaustion, burnt budgets and software that never reaches the customer. Instead of abstract process images, what is needed are four metrics, a culture of sharing and the realization that software testing does not take place in a vacuum - but in a value chain in which everyone depends on each other. Those who take DevOps seriously do not set up new dashboards, but ask themselves: What can I do today so that everyone suffers less tomorrow?

Podcast Episode: DevOps

Everyone associates DevOps with the symbol of the horizontal 8. In fact, this symbol is very common in marketing. Georgia doesn’t start much with it. For her, DevOps is a very practical way to make the way we work more effective. Collaboration and communication are crucial in software development, because what I produce today could affect someone else tomorrow. Or benefit from it - that would of course be the more desirable case. DevOps is very comprehensive and holistic, often without a lot of talking but with more: doing!

“DevOps is the (…) desperate cry of IT or the computer science industry for: It has to work better than it does right now” - Georgia König

Georgia König grew up in Baden-Württemberg with five siblings and studied computer science in Reutlingen, with a focus on DevOps in her bachelor’s and master’s theses. She has been working in IT practice since 2017, supporting customer projects in various industries and currently works at Novatec Consulting GmbH, where she designs webinars and training courses on Dev(Sec)Ops and Continuous Improvement. In addition, she teaches the subject “Current Challenges of IT Management (DevOps)” at Stuttgart Media University in some summer semesters.

Highlights der Episode

• DevOps is not a tool, but a battle cry against burnout, wasted money and a lack of standards.
• CALMS acronym concretizes DevOps: Culture, Automation, Lean, Measurement, Sharing - not just phase models.
• Four DORA metrics are enough: Deployment Frequency, Lead Time, Change Failure Rate, Mean Time to Recovery.
• DevOps success starts with the question: What can I automate today that will save me time tomorrow?
• The wall of confusion disappears when development and operations talk to each other instead of about each other.

DevOps: More than just a pipeline - A journey to improvement in IT

The true meaning of DevOps beyond the classic CI-CD pipeline and how it is revolutionizing the IT industry by addressing human and economic costs. DevOps can build a bridge between development and operations through practical approaches and the CALMS acronym.

DevOps as a concept and culture

Welcome to a world where DevOps is much more than just a figure eight that many immediately associate with CI-CD pipelines. I was pleased to welcome Georgia König today, who gave us a new perspective on DevOps. The discussion revealed that DevOps is a rallying cry for many in the IT industry - a desperate call for a better way of working. But what exactly does that mean? And why has this call become so urgent?

DevOps vs. agility: a battle for efficiency

For two decades, agility has been hailed as the savior for all problems in software development. But has it really delivered on all its promises? Georgia argues that DevOps differs from agile in that it has emerged directly from the experiences and needs of those working in the field. It’s about finding real solutions to real problems and sharing them within the community.

The heart of DevOps: the CALMS acronym

One of the centerpieces of the talk was the CALMS acronym, which stands for Culture, Automation, Lean, Measurement and Sharing. These five pillars form the basis of DevOps and show in a practical way how organizations can improve the way they work. These elements help not only to create more efficient processes, but also to promote a culture of collaboration and continuous learning.

Practical implementation of DevOps

What does the application of DevOps look like in practice? Georgia shares her experiences from teaching and consulting and emphasizes the importance of taking concrete steps to implement DevOps principles. From automating simple tasks to critically questioning existing processes, it’s about initiating short and long-term improvements.

Overcoming the wall of confusion

Another important topic was the so-called wall of confusion between development and operations. This metaphorical wall stands for misunderstandings and a lack of communication between the teams. By using DevOps principles, this barrier can be broken down so that both sides can work together more effectively.

A new look at DevOps

Georgia has shown that DevOps is much more than a method or a tool; it is a philosophy. A philosophy that aims to reduce both human and economic costs in IT. Through practical approaches and the pursuit of continuous improvement, DevOps can help create a healthier work environment while increasing business success.