The word “DevOps” was coined in 2009 by Patrick Debois, who became one of its gurus. The term was formed by combining “development” and “operations,” which provides a starting point for understanding exactly what people typically mean when they say “DevOps.” Notably, DevOps isn’t a process or a technology or a standard. Many devotees refer to DevOps as a “culture”—a viewpoint that New Relic favors. We also use the term “DevOps movement” when talking about topics such as adoption rates and trends for the future, and “DevOps environment” to refer to an IT organization that has adopted a DevOps culture.
This primer will have a great deal more to say about DevOps, but to get started, we need a serviceable definition. We like this one from "Gartner":
In short, the main principles of DevOps are automation, continuous delivery, and fast reaction to feedback.
You can find a more detailed explanation of DevOps pillars in the CAMS acronym:
Culture represented by human communication, technical processes, and tools
Automation of processes
Measurement of KPIs
Sharing feedback, best practices, and knowledge
Adherence to these principles is achieved through a number of DevOps practices that include continuous delivery, frequent deployments, QA automation, validating ideas as early as possible, and in-team collaboration.
Companies that incorporate DevOps practices get more done, plain and simple. With a single team composed of cross-functional members all working in collaboration, DevOps organizations can deliver with maximum speed, functionality, and innovation.
There are technical benefits:-
-Continuous software delivery
-Less complexity to manage
-Faster resolution of problems
There are cultural benefits:
-Happier, more productive teams
-Higher employee engagement
-Greater professional development opportunities
There are business benefits:
-Faster delivery of features
-More stable operating environments
-Improved communication and collaboration
-More time to innovate (rather than fix/maintain)