This week we look at our favourite answers for our second #DevOpsFriday5 question - Can you describe what DevOps looks like when it’s ‘done’? Here's our round-up!
How would you describe the relationship between DevOps, Agile and ITIL?
“I have 5 things I’m currently talking to people about as high level goals of DevOps: - Deployment on demand - Eliminating technical debt and unplanned work - Failing smart/safe/fast - Looking outside-in - Measuring idea/feature value So I could posit that DevOps is ‘done’ when these 5 things are achieved. You can read more about my thinking on this here.” Helen Beal
“I don't think you are ever truly done, as there is always something new to do or try that adds value. This can be in tooling, process or methodology. It would be nice to think about having some base lines, such as infrastructure as code, CI/CD and introspection, monitoring and metrics.” Mike Dilworth
“Who said it was ever done? Seriously, I think DevOps is an ongoing process of constant improvement. There are always improvements to be made, lessons learned and continuous learning. However at some point you can look back and say we are operating at a much higher level now than we were at some point in the past and you can point to DevOps methodologies as being at least partly responsible for that. But I don’t think there is a “eureka” moment. I think it is something you recognize with hindsight. In the moment you are too involved in the here and now to take stock.”Alan Shimel
“DevOps is all about making processes precise, automated and continuous which themselves are continuously improving so in that sense DevOps is never really 100% done. Therefore it is more important to describe what DevOps looks like when a baseline DevOps has been accomplished sufficiently to be considered a functioning DevOps environment suitable for continuous improvement. A “complete” DevOps baseline is “up and running” when the development and operations teams have accepted to work together and are together using a mostly automated infrastructure which supports a continuous pipeline from integration through to delivery.” Marc Hornbeek
“Done is when you can deliver a solution which includes all artefacts in the stack (application code, user interfaces, infrastructure) to the real customers in a regular candence (e.g. daily, weekly). This enables feedback to the development teams whilst improving the relationships between those who develop the solutions (developers) and those who support the live services (Operations). There are different models of DevOps which go from separate teams to one team that does the development and operations (though this usually means the organisations are close to or at continuous delivery.” Keith Watson
“If someone finishes DevOps, please let me know ; ). If you are starting from ground zero, DevOps is so transformative that today will look nothing like tomorrow. Organisations will think differently, work differently, and interact differently. To fully embrace DevOps principles changes everything. While not attempting to provide an all encompassing answer, one of the great benefits that DevOps practices bring to the table is one of breaking down barriers or silos. The worst organisations I have worked for had erected tall, fortified silos around operational teams that really needed to work together. I still remember days after starting work at a huge company when a colleague explained that “we don’t work with that other software group over there.” I was astonished. We were both part of the same business unit. And we worked about 15 feet apart. Oh, how everyone enjoyed seeing the silos come down. When you all work under the same roof, it is so much more fun to work as “us” rather “us vs. them.” That is one huge cultural advantage of what DevOps practices bring to the table. There a thousand more examples out there.” Derek E. Weeks
“For me DevOps looks like a figure with many concentric circles. In the exterior I put DevOps Business Processes. DevOps Culture is on the next internal level. And in the middle I see Development and Operations Processes.” Liviu Faciu
“Well, DevOps is never done. It is an ongoing evolution of learning and continuously improving. When a company reaches a high level of DevOps maturity, that company usually becomes a high performing company. The Puppet Labs State of DevOps report does a great job of describing what that promised land looks like. Some of the highlights are happier customers, higher morale and less burnout, greater productivity, and even higher profitability.” Mike Kavis
“DevOps is a philosophy, not a standard or framework, so there is no "done" definition. However, a transformation could be called "done" (in the sense of "good enough") at a point in time, if business objectives in terms of agility requirements (idea-to-production, mean-time-to-repair) are met and additional benefits would not pay for further investments. It is also "done" at a point in time, if the bottleneck in the delivery pipeline shifts towards other (earlier) stages. "Done" today does not mean "done" tomorrow and cont. improvements, which are an inherent part of lean and agile, apply to DevOps either.” Michael Schmidt
“A good measure of DevOps 'done' is traceability. Can you point to a release of software running in production and then quickly and easily trace right back to the lines of code changed for that release and the change management tasks, requirements and business drivers ? Can you trace from a requirement to deliver functionality and identify exactly when that was released into production? Another measure of DevOps 'done' is the singular processes. Do you have a standard way to deploy each specific technology that is the same across all environments. Do you have a clear adit trail, a separation of responsibility and a security model that controls who can do what and when?” Mark Roberts
“I dont think its useful to compare DevOps in an analogous way with Agile's definition of 'done'. My perspective is that DevOps is well described as creating a purposeful activity system (Checkland) and that system can then be monitored to see if it is operating in an efficacious, efficient and effective way. So, lets define a system that DevOps creates.” Patrick Hyland
Want to participate in the next round of #DevOpsFriday5? Do that here.