InfoQ Homepage Presentations Continuous Delivery Sounds Great But It Won’t Work Here
Continuous Delivery Sounds Great But It Won’t Work Here
39:50
Summary
Jez Humble presents some of the highlights and lowlights of the past six years listening to people explain why continuous delivery won’t work, and what he has learned in the process.
Bio
Jez Humble is co-author of the Jolt Award winning Continuous Delivery, published in Martin Fowler’s Signature Series, and Lean Enterprise, in Eric Ries’ Lean series. He is currently researching how to build high performing teams, and helping to create a cloud platform for government. He works at 18F, teaches at UC Berkeley, and is co-founder of DevOps Research and Assessment LLC.
About the conference
Agile Australia was founded in 2009 as an annual Conference. Since then, not only has the Conference grown to welcome over 1,200 delegates each year as well as high-profile speakers from around the country and the world, but Agile Australia has also become much more than a Conference. AgileAus is a hub for the Australian agilist community and those interested in better ways of working.
Sep 17, 2017
Community comments
Change mindset, deliver continuously
by Andrea Mussap,
Chicken & Egg
by Mark Ingram,
Change mindset, deliver continuously
by Andrea Mussap,
Your message is awaiting moderation. Thank you for participating in the discussion.
In this quite funny video, Jez Humble talks about four reasons/excuses ppl give to explain why continuous delivery won't work. For each reason, he presents examples of how companies such as Amazon, HP, and NUMMI overcame their issues and became more profitable. The takeaway of the presentation is that no matter the practice you're going to try in your company, if you don't change culture and mindset to invest in people and innovation, then you may be right: continuous delivery won't work for you.
Chicken & Egg
by Mark Ingram,
Your message is awaiting moderation. Thank you for participating in the discussion.
Quoting John Shook, Jez suggests that we should focus on changing behaviour first and that will lead to a change in culture. Later he goes onto cite the example of GM where they copied the practices (the behaviours?) but not the culture and thus didn't reap the benefits. I'm obviously misunderstanding but I found this bit of the presentation confusing.
In my experience, I agree that simply copying practices isn't enough. When the practitioners experience a positive benefit from the change, that's the spark that ignites and causes the continuously increasing change/improvement/making more awesome.