I’m not gonna lie: as our project grows, we find we need to invite new members into our team, members with more specific roles who will help us evolve. We’re talking about specialists in user experience, quality analysts who focus on test automatization and, of course, as the title of the article suggests, DevOps.
When we include a new role in our team, we start a process of rethinking and improving what we have been working on. It’s not really okey to say that without a DevOps, everything the team did before is wrong. What we can say is that by including this role, we’re able to invigorate our team and empower it with new perspectives.
Including DevOps in the Team
When we invite a DevOps into the team, the transformation that takes place is quite interesting and goes through different stages.
Let’s take a look at them in detail.
When a DevOps is included in the team, they firstly need to understand the processes, spot their deficiencies and the areas to be improved or enhanced. The team also needs to understand why it’s necessary to include a DevOps. Once we all understand this, we can start investigating.
During this time, you should all take all the time needed, and any doubt for the DevOps should be solved as a team. At all times and from the beginning, the DevOps has to get deeply involved with the whole team.
In this part of the plan, the team members should be all working together. This could very well be a crucial stage in the whole process, since we need the team to pitch in on topics that are generally delegated to the infrastructure and development processes areas. This is why the DevOps should always suggest ways in which the processes can be improved and facilitated, and how to add value to the business. Needless to say, the rest of the team should support the DevOps suggestions. We’ll be able to create a working plan if the whole team and the client are involved in the proposals and planning.
This stage involves training the DevOps and the team too. It’s a continuous learning process to leave the comfort zone. It doesn’t just have to do with the technical parts: it’s deeply connected to the human side of everything and with the processes as well. The goal is for everyone to understand what each role can contribute and the responsibilities everyone’s got in the business.
In this stage, we assess and analyze the areas in which we’ve failed in order to try to improve. We plan again and we define goals. It’s vital to try and continuously improve. The role of the DevOps in any team aims at simplifying the development processes, empowering the team, being the bridge between the team and the infrastructure. Short to medium term, you’ll be able to see the benefits of this continuous improvement, since processes will be simplified.
So, do you think you need a DevOps?
In my experience, we need to know that, even if we’re specifically talking about including one person as a DevOps, the whole DevOps culture is not their sole responsibility, it must be fostered and the whole team must internalise it. Now that I think about it, rather than referring to the “DevOps role”, we should say “enabler of DevOps culture”. Responsibilities about infrastructure should always be shared and, for that, we need the whole team to be 100% involved.