DevOps Culture “without Bullshit”
Have you ever googled DevOps and tried to find an answer beyond bullshit bingo? No? Wonderful, then you’ve come to the right place. “Without bullshit” is, after all, exactly the buzzword we use to live DevOps for our customers and also for ourselves. And summarized in one sentence, it means: a mix of the right culture and the right tools.
To explain a bit more what we mean by this, let’s briefly look together (promised – very briefly!) at our understanding of DevOps, which is based on the 3-way principle.
Dev Ops – Systems Thinking
The 1st way describes the “flow” of the value creation process – sounds highfalutin, but means nothing else than, for example, the entire process from the idea to the finished software running productively.
To improve the performance of this flow, it is important to use the right tools. This starts with the appropriate programming language and continues with packaging, pipelines, tests and deployments. Obviously, sensible automation and standardization is the be-all and end-all here.
DevOps – Feedback loops
To make the flow of the 1st way sustainable, the 2nd way describes the introduction of feedback loops. If there is a problem somewhere, it should be solved as soon as possible. Communication between departments can solve problems that might not have arisen in the first place or might be a thing of the past in the future. Feedback creates an iterative process for regular improvement.
DevOps – Culture
And finally, the entire process must be enriched with the right culture. Constant learning and experimentation must be just as natural as a functional error culture and knowledge exchange.
Our DevOps Approach
But now back to the question of what makes our DevOps approach different or special. On the one hand, we not only offer consulting, but also have our own software product, orcharhino. In this respect, we know from our own experience what is important for a functional DevOPs approach, where the shoe could pinch and what can help to alleviate it.
In short, in all 3 ways, optimizations can usually be found that we have already experienced in the same way or at least very similarly.
We have also learned from various customer projects what is especially important in the initialization phase of DevOps – the creation of cross-departmental lighthouse projects.
This can be one of our customized trainings, a joint design workshop, or something else entirely. The main thing is that there is healthy communication. We are just as happy to talk to techies about the final implementation of a Kubernetes network model as we are to talk to department heads about process design issues.
In general, however, it is most important for us to talk to you about your concrete questions and problems instead of boring you with generalities.
That’s why we offer you a free DevOps “Expert Discussion”, which is exclusively about your topics.
All you have to do is to provide us with your contact detailshere.
We’ll get back to you, and hopefully soon we’ll be able to convince you in person that we have the right DevOps approach for you.
And if you would like to hear a story or two from real “DevOps” life, our colleagues Jonas Trüstedt and Bernhard Hopfenmüller are looking forward to your “virtual visit” at their IT-Tage talk on Wednesday, 08 Dec 2021 from 10:00 – 10:45 am CET. The talk will be held in German. Dez 2021 from 10:00 – 10:45 am CET!
Latest posts by Bernhard Hopfenmüller (see all)
- Ansible Automation Platform - 25. May 2022
- DevOps Culture “without Bullshit” - 24. November 2021