This week we look at our favourite answers for our fifth #DevOpsFriday5 question - Is Continuous Delivery the ultimate goal of DevOps? How do other 'Continuouses' contribute in a DevOps transformation?
What Attributes Constitute a Culture Embracing DevOps?
"People get hung up on this word Continuous. Why does something need to be continuous? What does it mean in our environment or business? Do we need to go to a 7 second release cycle? Do we need to go to a 7 second deploy (usage) cycle? Or instead, can we set aggressive targets and use these to continuously improve how we work? I prefer the approach of using the capabilities implied by continuous to drive improvement. I am happy for an organisation to then say we continuously deploy (creation thru delivery) every month." Daniel Breston
“Continuous Delivery is just one goal of DevOps. Continuous Deployment is one step further along the journey. Often it is better to achieve the various continuouses incrementally, but often all aren't needed. It is important to fit DevOps into your particular organisational environment. What works and is acceptable in one company may not work in another." Mike Dilworth
“The ultimate goal of DevOps is to create a precise and automated environment for integrated continuous development and delivery pipelines. This goal requires the environment to be accepted by all parties involved in the continuous pipeline from development, test, delivery, deployment and support. The goal is to have an environment that everyone can contribute to and use and be the basis for continuous improvements going forward." Marc Hornbeek
“The ultimate goal is to increase speed of deployment of new ideas to test the assumptions made at the beginning of the process. Software engineering is different to other forms of engineering because the artefacts created during the process are not as visible (unlike a bridge, car or other tangible object). The "Continuouses" are means to an end not the end itself. By using DevOps to achieve continuous delivery it provides faster feedback loops to test the assumptions (e.g. a customer will like/want this function/interface).” Keith Watson
“I'll refer back to the measures and metrics question - that really depends on the goals of the organisation in the first place. A business whose model is based on software and engagement would certainly benefit from continuous delivery, but there are plenty of organisations - particularly enterprises - for whom that model would be disastrous and overkill. Yet other continuous efforts - like testing and improvement - would be beneficial to those organisations. Any "continuous" that doesn't reach outside dev isn't really helping with the transformation because it doesn't rely on communication and collaboration. Similarly, if the efforts don't reach beyond ops into security and the network, it isn't fully affecting the organisational level of transformation needed to fully adopt and benefit from DevOps.” Lori MacVittie
“No, not at all. Organisations can embrace DevOps successfully without being 'continuous everything'. Speed is only one factor. For some, their customers make it an imperative. But for others, their industry does not demand speed as the highest priority. If your ultimate goal is to go faster, where are you heading? Have you maintained enough agility to adjust direction if needed? Quality, integrity, safety, security, and repeatability could all be goals of a DevOps mission. So could growth, profitability, and sustainable competitive advantage. So both “flow” and “feedback” become key based on the organisation. Remember, a twelve minute mile is just as far as a six minute mile. But how you get there...that can make all of the difference.” Derek E. Weeks
"No, continuous delivery is a capability of DevOps but is not the ultimate end goal from my perspective. It’s also important to define what continuous delivery means. It’s not just about releasing applications and features frequently and quickly. It’s about making sure that your release cadence is in line with the market and most importantly, customer needs. The ultimate goal for DevOps is to make the organisation fluid in relation to customer needs – to be able to change quickly plus respond, and this means that everyone in the organisation – business, development and operations must be able to work without friction". John Rakowski
"No, the end goal is more about what a business can achieve with IT. For some, that might be continuous delivery, but for others it might just be a faster route to a better quality product. From an IT perspective, continuous delivery is just a method". Toby Moore
Want to participate in the next round of #DevOpsFriday5 with a new set of questions? Do that here.