Comments for Continuous Delivery

Comment on Release Management White Paper and Assessment by The Morning Brew - Chris Alcock » The Morning Brew #674

The Morning Brew - Chris Alcock » The Morning Brew #674 — Fri, 27 Aug 2010 07:33:38 +0000

[...] Release Management White Paper and Assessment – Jez Humble shares a white paper “Agile Release Management: Towards Frequent, Low-Risk Releases” and multichoice assessment looking at the release management process based in part on the content of his book ‘Continuous Delivery’ [...]

Comment on Continuous Delivery vs Continuous Deployment by Tim Coote

Tim Coote — Sun, 22 Aug 2010 22:00:06 +0000

Nice post.

Have you looked at the value to the business in being able to decouple the application from the underlying technology?

Most enterprise apps are stuck on the platforms that they were first implemented on because the cost of migration is too high. Since the average life of an app is 7 years and most IT shops overprovision, this is a big (if largely hidden) cost.

Comment on Continuous Delivery by Pierluigi Vernetto

Pierluigi Vernetto — Sat, 21 Aug 2010 14:16:46 +0000

Hey Jez, I am progressing with your book and it’s really a gold mine of precious advice. I have corrected my post on http://www.javamonamour.org . You guys rock!
I would suggest also selling a podcast of the book that one can listen on IPod…
pierre

Comment on Continuous Delivery vs Continuous Deployment by Michael Hüttermann

Michael Hüttermann — Tue, 17 Aug 2010 16:05:24 +0000

great article.

“Continuous delivery is about putting the release schedule in the hands of the business, not in the hands of IT.” — what is a release (respectively its schedule) that is not driven by business?

Comment on Continuous Delivery vs Continuous Deployment by Andrew Spencer

Andrew Spencer — Tue, 17 Aug 2010 08:32:26 +0000

Thanks for an interesting and helpful article. How about some links to Amazon UK, FR, DE etc? I may well buy the book, and I’m sure I’m not the only European who’d be happy to earn you some commission.

Comment on Continuous Delivery Talks 2010 by Revue de Presse Xebia | Blog Xebia France

Revue de Presse Xebia | Blog Xebia France — Tue, 17 Aug 2010 05:48:15 +0000

[...] livre donnera lieu a un grand nombre de présentations en conférence, qui, si ce n’est déjà fait, devrait vous donner envie d’en faire votre livre de [...]

Comment on Continuous Delivery vs Continuous Deployment by Jonathan Nieto

Jonathan Nieto — Mon, 16 Aug 2010 19:13:07 +0000

What’s the point on having a user story ready to be used if it is not going to be used, isn’t it a loss of resources?

Nice article!

Comment on Continuous Delivery vs Continuous Deployment by Guilherme Silveira

Guilherme Silveira — Mon, 16 Aug 2010 18:36:00 +0000

One of the other good reasons one might not want to deliver a new version of the product is the cost-of-change in the mindset of its users. They might not be able to cope with a fast pace on changes in its UI or features. While some groups adapt themselves better with a steady pace of delivery in new features, others react better to batch updates.

Either way, deployment should be subject to business, as you mentioned: in the end, our job is to deliver what our business need, not the other way around.

Great post…

Just a note, when using a limited WIP, one might be able to start a new story in order not to waste effort while waiting for some answers/tests in another one, so can’t one change to the next story if the story is approved to come into play, but did not yet due to a business restriction? (e.g. waiting for the right marketing time, a monday morning)

Comment on Continuous Delivery vs Continuous Deployment by A Smattering of Selenium #23 « Official Selenium Blog

A Smattering of Selenium #23 « Official Selenium Blog — Mon, 16 Aug 2010 11:27:45 +0000

[...] Se plays a large part in Continuous Deployment setups, but what I am really interested in is Continuous Delivery. Jez (who literally wrote the book on it) explains the difference between the two. [...]

Comment on Agile Tokyo 2010 by jez

jez — Mon, 16 Aug 2010 07:59:01 +0000

Update: this article made it to Slashdot Japan Google Translate for Japanese is pretty crap, but this comment caught my eye: Waterfall - Japanese-style choices 1, make desperate efforts 2, work hard for Dear Life 3, (in short) and adding staff, work hard until they die