Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Should DevOps Be a Title?

DZone's Guide to

Should DevOps Be a Title?

· DevOps Zone
Free Resource

The Nexus Suite is uniquely architected for a DevOps native world and creates value early in the development pipeline, provides precise contextual controls at every phase, and accelerates DevOps innovation with automation you can trust. Read how in this ebook.

There has been a lot of talk around whether or not DevOps can be used as a job title or a prescriptive requirement for a job position. Some opponents to DevOps titles say DevOps, like Agile, is a methodology and no one uses “Agile Engineers” as a title. They’re just called developers. Others argue that DevOps is too nascent of a process to expect people to have resume-qualifying experience in. We believe the main point revolves around speedy implementation of DevOps, but is there a right way to do it?

Rajat Bhargava, CEO here at JumpCloud, opens up the subject for debate in an article posted on DevOps.com. He concludes explaining how time will tell how the terminology culminates in industry, but until then, if someone uses it as a title to gain traction in their firm, that could work on a case-by-case basis. He gives some opinions expressed at the DevOps State of the Union event in Boston – one being that there is a self-defeating notion involved in DevOps being a title because it stands for a cultural movement being incorporated throughout the firm. Damon Edwards eloquently highlights this in a post stating that there are inherent dangers in creating a DevOps title because it makes it someone else’s problem, therefore, creating a title out of DevOps pigeon holes the true potential of it really taking hold. At the same time, some people in industry are fervent believers that titles should describe day-to-day duties of an employee. Thus, DevOps Engineers is used to describe the ideal candidate.

When it comes down to it, we can safely say that we all want simply DevOps implemented as fast as possible, but the discussion around the protocols for this implementation is valuable to have when trying to create a community. We want to hear from you so feel free to email us and let us know how we help you deploy DevOps in your organization. For now,  here are some questions and thoughts on DevOps:

Does using DevOps in a title create barriers to incorporating the methodology as a culture across the firm?

In what circumstances could you make the argument that it’s better to use DevOps as a title or requirement? When do you think it’s unnecessary?

What other cultural and professional movements could we identify in history with synergies to the DevOps movement?

The DevOps Zone is brought to you in partnership with Sonatype Nexus.  See how the Nexus platform infuses precise open source component intelligence into the DevOps pipeline early, everywhere, and at scale. Read how in this ebook

Topics:

Published at DZone with permission of Topher Marie, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}