By: Romnick Acabado
DevOps Institute has released the “2020 Upskilling: Enterprise DevOps Skills Report” earlier this year. For part one of my two part blog series, let’s look at the differences between the 2019 and 2020 studies and the team topologies.
Here are the interesting statistics about upskilling IT professionals and employees who are working in an organization with planned or ongoing DevOps adoption:
These are all eye-openers and insightful for our leaders and DevOps enthusiasts. Now, let’s go through the notable differences between the 2019 and 2020 study. We found that:
This is enough for us to recognize the value of the humans of DevOps and their skills which are important to make a successful DevOps adoption. Last year, we learned about I-Shaped, T-Shaped (coined by IDEO chief executive Tim Brown) and now E-Shaped professionals:
The goals of the leaders is to guide and upskill their people from being simple specialists to being the Next-Gen specialists that can give them limitless possibilities.
Also, based on my experience, humans’ flexibility and resilience are important in order to adapt to more complex demand of business which is not an easy task for leaders.
It is important that in hiring or introducing new personalities to a team, we immediately set the expectations and the norms about collaboration, interpersonal skills, problem solving, sharing and knowledge transfer and flexibility. Otherwise, it can be complicated when you’ve got the people who do not fit your team’s vision and values.
As described by experts in topology, there are different team structures which inhibit or accelerate the success of a DevOps team. We found three different models which are currently used. The one which is leveraged the most is the DevOps team silo or DevOps Advocacy model where there is a separate DevOps team between Dev and Ops. The second most used is the DevOps collaboration model where DevOps is everyone’s job, and the third most deployed team structure is that of the DevOps tool team where the DevOps team is responsible for tooling required.
This is very insightful and helpful to validate our experiences. From my side, my experience is mostly related to DevOps Team silo or DevOps Advocacy model and so far it is working. Through it, you are able to ensure that you have people who can bridge the expertise, experience, execution and exploration between Development and Operations. At the same time, you are able to keep the quality of service. Of course, there is no “one-size fits all approach” for DevOps and I believe that the customer’s goals, project’s complexity and the maturity of DevOps adoption have significant influence for the design and structure.
Download the 2020 Upskilling: Enterprise DevOps Skills Report here: https://lnkd.in/ftzZjxY