What good is it to learn DevOps

You can not “Do” DevOps, but you can ...

You cannot “do DevOps”, but you can, for example, align your teams along products and value streams. Before you do that (more on that later), you should ask yourself the question, WhyDevOps is relevant for your company at all. There are at least two good reasons for DevOps:

  • Your next toughest competitor could be a startup with a disruptive app. These companies are able to launch new and high-quality services on the market very quickly and to quickly test new ideas on the market. In this “Digital Ecomomy” it is not the big fish that eats the small fish, but the fast fish eats the slow one. And: no industry is spared. And of course this is not relevant for all of your products (bi-modal IT sends its regards).
  • The IT department in your company is split between developers and operations. Some want flexibility, others stability. Business wants both. Breaks and sprawled processes everywhere. Where is the value stream - end to end? It can not go on like this.


After you feel aboutYour "Why?" are clear and have set (and can also measure) appropriate goals for the areas where this is relevant, you can do the following:

  • Yours Identify value streams along products- from the vision, the requirements to the operation
  • Create cross-functional teams and align them accordingly and a Culture create with common goals (instead of flexibility vs stability)
  • The basics for Continuous delivery create, i.e.
    • Development and test platforms should be available quickly, the cloud (PaaS) is the basis for this. Up to "Infrastructure as a Code
    • Continuously Automation potential identify and use, e.g. automate tests, automate deployments
    • Fast Feedback loops build in to identify errors early
    • Ultimately one Deployment pipeline create
    • Create a "tool chain" along the deployment pipeline, without breaks (otherwise no continuous delivery)
  • A Create agile culture, now also with people from the company (who fought against it for a long time). As a first step, it can simply be a Kanban board, and then people learn to like it (because: Culture eats Strategy for Breakfast)
  • Continuously Value stream mappings carry out, Identify and eliminate bottlenecks


Here are a few examples, this list could be expanded to include many other successful “DevOps Practices”. It should also be clear that DevOps is not a one-time project, but a journey that never ends. Anything that helps to become faster (e.g. time to market) and better (e.g. service availability) is useful. And experimentation is an important part of this, as long as there are clear goals and a vision behind it. Does Kanban work for you? Don't know. Try it and you find out.

By Alex Lichtenberger