Think you’re a DevOps expert? Put your knowledge to the test and find out!
DevOps is all about breaking down the barriers between development and operations teams to foster collaboration and efficiency. It has evolved over the years, giving rise to various methodologies and practices. But how well do you really know the world of DevOps?
Back in 2009, Patrick DeBois organized the first DevOpsDay, laying the foundation for a new approach to software development and IT operations collaboration. Fast forward to today, and DevOps has become a buzzword, with numerous offshoots and related practices. From BizDevOps to DevOps 2.0, the DevOps landscape has expanded.
In this DevOps quiz, we’ll explore the different DevOps methodologies and concepts that have emerged over the years. Are you familiar with terms like HumanOps, HugOps, and even SnackOps? Time to test your DevOps knowledge and discover just how well-versed you are in this ever-evolving field.
Table of Contents
This is an approach to software development that encourages developers, operations staff and business teams to work together to be more responsive to user demand and ultimately maximize revenue.
D. DevOps 2.0
While folks often refer to DevOps 2.0 as BizDevOps, that doesn’t mean they’re right and that we’re just going to go along with it. DevOps 2.0 truly aims to expand DevOps style collaboration, not only to the business side, but also to quality assurance, security, HR and across the whole organization. DataOps is an approach that prioritizes a data analytics pipeline, so the data group can get involved and consistently monitor the pipeline. ProductDevOps is a great name, but it doesn’t exist … yet.
Some argue this methodology is redundant because security has always been a part of DevOps since the Phoenix Project.
Don’t let “DevBlackOps” fool you, DevSecOps is nearly as famous as DevOps itself. DevSecOps aims to integrate security through all aspects of software development lifecycle. Basically, continuous quality should be as important to you as continuous delivery. Sorry, SciOps — Scientific DevOps, i.e., DevOps practices applied to scientific computing to deliver scientific insights — and sorry, DevOpsIoT, better luck in next year’s DevOps quiz.
DevOps aims to cut inefficiencies, improve communication and develop collective empathy within an organization. This DevOps methodology emphasizes the empathy portion of the equation.
E. HugOps and HumanOps
E. HugOps and HumanOps
HumanOps and HugOps — one more of a Twitter movement and the other something you could actually pitch to your boss — assert that human health affects business health. Sometimes we forget that shipping software 24/7 means pushing real humans past normal working limits. HumanOps and HugOps are DevOps methodologies cut from the same cloth and work to develop processes that create a balanced workflow. DadOps, on the other hand, is less interested in developing empathy within your organization and more interested in telling you about the World War II book he just read. (If DadOps is new to you, it’s clear you needed to take our DevOps quiz.)
What happens when your DevOps process becomes so automated and abstracted that your infrastructure doesn’t even need a dedicated IT ops team? With the rise of IT automation and cloud computing, this methodology is quietly becoming a reality.
In this DevOps scenario, coined by Forrester Research, automated programs deploy and maintain developer code. NoOps faces considerable backlash from operations folks, understandably, and the idea has pivoted from “operations not allowed” to a more business and product-oriented focus. NoOps can mean an organization without any operations professionals at all, but product and PaaS vendors have adopted a more conservative form — with operations professionals residing in product teams — too. We’re not sure what ProtoOps is, but we liked the sound of it in our DevOps quiz.
This Agile movement takes the collaborative element of DevOps and applies it to the greater IT and tech community.
SnackOps is at it again, but it’s CoffeeOps that takes the cake here. This DevOps meetup can bring a diverse group of IT professionals — developers, ops folk, even recruiters — together to talk strategies for tackling particular DevOps issues. Part workshop, part therapy session, these DevOps meetups have sprouted across the country, most popularly in the Bay Area and Seattle. Most follow the lean coffee model and promote an anti-burnout culture.
This DevOps methodology strives to speed the production of applications running on big data processing frameworks, using an organization’s data in the most flexible, effective manner possible.
D. DevOps 2.0
If you saw “big data,” and thought “DataOps,” well, you didn’t outthink yourself on this DevOps quiz. As we’ve already explored, NoOps imagines a DevOps without operations. And DevOps 2.0 imagines DevOps applied throughout an organization — HR, legal, etc. DataOps, though, is an often overlooked DevOps methodology. In order to run multiple open source tools and frameworks all at once, your organization’s data architecture has to be both complex and flexible. If organizations want to do DataOps — and therefore DevOps — they have to break down silos between data engineers, developers and stakeholders.