DevOps has been instrumental in transforming IT responsiveness to business, as is evident by the fact that we have enterprises from all walks of life
DevOps has been instrumental in transforming IT responsiveness to business, as is evident by the fact that we have enterprises from all walks of life including Banks adopting DevOps. It’s certainly not a thing that hip web companies do now. However, with this rush to “do” DevOps comes the noise associated with it and hence, the confusions. I’ve been asked quite a bit off late we’re practicing Lean Kanban already how would DevOps help us? or even Do we need to do DevOps when we’re practicing lean? This blog is an attempt at two things, at showing how DevOps borrows Lean principles and it’s really not an either/or equation between these practices as they complement each other. DevOps While there are many definitions of DevOps the one I like to stick to is: "A cultural and professional movement that stresses communication, collaboration and integration between software developers and IT operations professionals while automating the process of software delivery and infrastructure changes". While there wasn’t necessarily anything more to DevOps than an observe and solve sort of cycle initially. Over the years we’ve had a more formalised way of working in DevOps. I’d still say most of it is common sense but then creating a structure or nomenclature does help majority of human beings to identify better. DevOps therefore has certain principles that make up most of what we know as DevOps today. Lean Most of us would know Lean well enough; the classic definition in IT industry context is "Lean IT applies the key ideas behind lean production to the development and management of IT products and services". And to know more about Lean Production you can start from here. Let’s look at the lean principles before I elaborate on this blog’s theme. 1. Define value precisely from the perspective of the end customer 2. Identify the entire value stream for each service, product or product family and eliminate waste 3. Make the remaining value-creating steps flow 4. As flow is introduced, let the customer pull what the customer wants when the customer wants it 5. Pursue perfection














