There is a lot of talk about devops right now, but how many people work in a real devop way? It’s not just about acquiring tools, but also about adopting new, and perhaps frightening, strategies for organizing teams and shared responsibilities.
Here, IDG Nyheter suggests three sure signs that you can really work in a devop team.
1. Product-based teams
A true devotional organization usually organizes its IT teams around the products it delivers. This means that one must abandon the old silo strategy that has been prevalent for several decades. Sometimes there is talk of “value streams” instead of products. It is a term that can be translated as “product family” or any other description of related solutions.
A product-based devop team includes roles such as product manager, developer, infrastructure experts, system administrators and everyone else who needs a product to become a reality. This may not mean that all experts must be in every team. For example, you can have an expert in network infrastructure who is part of several product-based teams.
It can also be a good idea for people from several teams who have a certain role, such as developing, to gather to get an overall picture of new technologies, experiences and the like.
2. Fails nicely
Genuine devopsteams do not try to avoid failures by slowing down the pace of change. Instead, they work fast and rely on the team’s ability to fix a failure quickly. By using products during short, controlled iterations, you know that many changes that are made in each iteration are minimal. This means that risks are minimized and that it is faster to recover from failures.
Devopsteam sees failures as valuable experiences. Thanks to automated supply chains (pipelines) and unit tests, each failure becomes a new test that is incorporated into the construction process. I set out to rely on institutionalized knowledge to avoid mistakes being repeated, so everything is coded in processes, so that failures are automated away in the future.
This requires that an organization must be possible, in terms of the attitude to failure, and abolish and culture that is about blaming others.
Obsessed with automation
In a true devop team, it is known that human error is the main source of failure in all processes. I think the team loves automation, both because it can be consistent solutions and because it goes fast. From rules for checking in code and starting test environments, to efficient unit testing and production start-up, teams know that automation is the only way forward.
A really efficient devop team has no favorites when it comes to tools and techniques for automation. They focus on choosing the right tool for a task. They are willing to abandon one tool for another, if it provides and better solution. This can be a major challenge for an established organization where there are strong ties to certain platforms and growth practices.
Devops is not synonymous with no-ops, but an obsession with automating as much of IT operations as possible.
For companies that dislike and try to make changes, that rely on manual deployment, that focus on manual quality control processes, and that have a departmental structure based on professional roles, devops may seem strange, even crazy. But many of today’s most agile and agile companies are embracing devotional ideas to ensure that their customers receive more new products than ever before.