From the course: DevOps Foundations: Lean and Agile

What is DevOps?

- When we've talked about Lean and Agile, we've said the words software development a lot, and that's how those two methodologies were introduced into tech through developers. - But you need more than software to deliver value to a customer, right? The days of just using software that run it entirely in your PC are pretty much over. Tech solutions run at least on a server and usually over the internet nowadays. - And that means that the network, servers, and other infrastructure that these solutions run on are part of the value stream. That's the core inside of DevOps. - Here's how we define DevOps. - [Instructor 1] DevOps is the practice of operations and development engineers participating together in the entire service lifecycle from design through the entire development process, all the way to deployment and production support. - DevOps is also characterized by operation staff making use of the same techniques as developers for their systems work and development staff, creating applications designed to work well in an operational environment. - That's right, as software depends more on infrastructure, and as infrastructure has become more automatable, these two groups can't separate responsibilities and do their work entirely differently, as was common in the olden days. - The word DevOps is a combination of developers and operations. It was coined by Belgian engineer Patrick Debois after a discussion at an Agile conference about Agile infrastructure. - [Instructor 1] In fact, Tom Limoncelli, author of "The Practice of Cloud System Administration" says simply that DevOps is the application of Agile methodology to system administration. - [Instructor 2] DevOps also explicitly incorporates Lean as a part of its core values. CAMS was the initial acronym for the four main values of DevOps: culture, automation, measurement, and sharing. - But Lean as It came originally from the world of real machines on manufacturing lines had a lot of wisdom built up around relevant concepts like intelligent automation. - [Instructor 2] So very quickly the community added Lean to the mix, making it CLAMS instead of CAMS. This quickly gained acceptance as one of the standard models for understanding DevOps. - I think they prefer to call it CALMS. - Well, I just really like shellfish. - At this point, you may be a little confused about how all three of these concepts: Lean, Agile, and DevOps fit together. Matthias Marschall summed it up the best in his diagram of the relationship between the three. He shows the combination of Agile development, Lean product management, and operations, all as part of DevOps. - [Instructor 2] He then shows how the Lean principles of flow inform the entire path of the software development process from product conception through development to operations. - Thus, product development and operations are phases in the pipeline that originates with an idea and ends with something that provides value to your customer. Lean is more of a mindset that occurs across all of these phases. - That's the idea anyway. Next, let's dig into DevOps practices more to see how they help us produce results in concert with Agile and Lean.

Contents