DevOps is a funny term that will sound very much like inside baseball for those outside of the technology industry. It is, however, a complex-sounding term for a simple movement. The idea of DevOps (itself a conjunction of the term developer operations) is that those who build applications should have an active role in, and an understanding of, the operational management of those apps. Looking at it from the other perspective, those who are responsible for the operation of applications should have a firm grasp on development approaches.
In traditional IT shops, developers and operations teams are distinct. Developers’ sole function is to “cut code.” They create the applications and then throw them over the wall to operations, whose task it is to make those applications actually run on the infrastructure at their disposal. This separate approach ends up being somewhat adversarial, with developers thinking of operations teams as smelly geeks down in the basement who don’t have a clue about what application users really want. Operations, for its part, thinks of developers as living on another planet with no real idea of what it takes to run a secure and high-performing IT shop.