DASA – the leading DASA organizational culture provider – shared a set of antipatterns, based on myths, which strongly oppose DevOps adoption and adaption. In my practice I often meet “devops engineers” and “we implemented devops, because we have ci/cd”. Let’s understand, what’s difference, and why DevOps culture first and precedes any technical tools, and why tools cannot create devops (rather they can be helpful locally).
DevOps Antipatterns: However, in practice, DevOps has different meanings for different people. Due to this confusion, organizations don’t realize the benefits of DevOps. Here are some antipatterns.
Agile is for development teams, and DevOps is for the downstream teams: Wrong. DevOps is about building end-to-end product teams, who own the product and are responsible for it throughout its lifecycle. These are the teams Amazon and Spotify popularized: the two pizza teams with build-and-run responsibilities.
The DASA DevOps team competency model illustrates the skills and knowledge areas of an end-to-end responsible DevOps team.
DevOps is a CI/CD pipeline: Another common antipattern is to confuse a CI/CD pipeline with DevOps. DevOps is more than implementing a CI/CD pipeline. It is about embracing the technical and cultural practices that enable the smooth flow of small batches of work from development to operations, getting continuous feedback across the delivery pipeline, including from operations, and continually improving the process and the product based on feedback.
The mythical DevOps engineers: This antipattern is widely prevalent and perhaps the most stressful for the unlucky person. Instead of the entire organization owning the improvement of software delivery performance, a person is responsible for it. Predictably, this doesn’t work. Instead of DevOps breaking silos, organizations create another silo and a bottleneck – the stressed-out DevOps engineer.”
IT startup mentoring framework 