Gitlab hero border pattern left svg Gitlab hero border pattern right svg

What a DevOps platform team can do for your organization

Adopting a DevOps platform won’t just improve release times – it also provides an opportunity to rethink traditional roles, particularly on the ops side. Our 2020 Global DevSecOps Survey shows that all DevOps roles are changing, but that was especially true in operations. Ops pros told us they were taking on new responsibilities including cloud and infrastructure management, while devs were busy provisioning and maintaining their own environments. Some organizations are going further and creating a DevOps platform team to help with the unique challenges of advanced DevOps.

Here’s a look at why, and how this cutting-edge team could fit into a DevOps organization.

Start with the DevOps platform

Less is certainly more when it comes to a DevOps platform; it brings all the steps necessary to build, release, and secure software together in one place and ends the toolchain “tax.” The platform can serve up advanced technologies from Kubernetes to microservices and infrastructure as code (IaC), and as such, it needs an owner. In the past, a site reliability engineer (SRE) might have been tasked with some of those responsibilities, but today some organizations are looking to hire DevOps platform engineers in order to create a DevOps platform team.

Not every company with a DevOps platform will need a team, however. An organization without legacy systems might not need this level of focus on infrastructure, while one with both cloud and on-premises data centers will likely want extra help supporting all the moving parts.

If you’re not sure, ask this simple question: Do you have a system for hosting websites? If the answer is no, a DevOps platform team might be the right choice for you.

What a DevOps platform team can do

At its heart, a DevOps platform team will free ops (and devs for that matter) from the complex and sometimes messy struggle to support the infrastructure. The goal is, of course, to offer as much self-service as possible for dev and ops, which means a streamlined and less touchy experience. A DevOps platform team can “tame the beast,” making it possible for devs to do push-button deployments without any extra involvement.

A DevOps platform team will likely take full advantage of infrastructure as code so manual interventions aren’t required. Devs will benefit from an API-interface that will allow them to do their jobs without actually having to understand how the infrastructure is created.

For some organizations, a DevOps platform team is a way to maximize engineering efficiency, and for others it allows for a focus on best practices, an end to ad-hoc platform “volunteer managers” who won’t have a broad view of team goals, and an increase in business agility.

It’s not platform engineer vs. DevOps

A platform engineering team is an extension of a DevOps team, not a replacement for it. Some practitioners warn of the risks of accidentally creating a secondary DevOps team while trying to create a platform team.

Also, it’s important to keep in mind that a platform engineering team needs a broad set of skills ranging from security to Linux to Kubernetes and of course soft skills like communication and collaboration. A DevOps platform team should be laser focused on infrastructure, not product development.

Done correctly, a highly-skilled DevOps platform team will allow the DevOps team to be more efficient.

Read more about DevOps:

The Benefits of DevOps

Future-proof your developer career

Axway aims for elite DevOps status

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license