DevOps and agile development practices have been—and continue to be—hot topics in the development world. How are they similar and how are they different? Is it really DevOps versus agile, or is it DevOps as well as agile, or even agile then DevOps? Knowing more about both philosophies and methodologies can help you determine which of both can be of the most help to your development teams. Thankfully, there is a plethora of resources out in the blogosphere. Here's a look:
He expands on this, leading deeper into the entire app lifecycle. "DevOps strives to focus on the overall service or software fully delivered to the customer instead of simply 'working software.' It emphasizes breaking down barriers between developers and operations teams, and getting them to collaborate in a way where they benefit from combined skills. Agile teams used automated build, test automation, Continuous Integration and Continuous Delivery. With DevOps that extended further to "Infrastructure as Code", configuration management, metrics and monitoring schemes, a toolchain approach to tooling, virtualization and cloud computing to accelerate change in the modern infrastructure world. So you see DevOps is not a separate concept, but a mere extension of Agile to include operations as well in the definition of cross-functional Agile team, collaborate together and work as one team with an objective to delivery software fully to the customer." The Buddha has spoken.
He hammers home the point that DevOps is not a thing or a product you can buy, but a philosophy, a style of working together more closely and cooperatively. "DevOps stresses on effective collaboration and communication between the two departments within a culture that enables optimized release cycles of high-quality and thoroughly-tested end-products."
Posted by Lafe Low on 09/19/2017 at 12:54 PM