I’ve written before about the amazing financial impact of releasing more often. And I know from personal experience the positive impact that frequent releases have on learning and on product quality and value. So, I enjoyed this post on one company’s experience with continuous releases. Yes, you read that right; they release, on average, 50 times per day.

We call this process continuous deployment because it seemed to us like a natural extension of the continuous integration we were already doing. Our eventual conclusion was that there was no reason to have code that had passed the integration step but was not yet deployed.

Read the whole thing and consider what it would take in your organization to get to continuous deployment. How fast could you go? And what impediments would have to be resolved to make it happen?

Related posts:

1. Continuous Integration and the Bad Head Problem
2. Continuous Integration in Under an Hour
3. One Word Can Change Your Daily Scrum

It’s officially a series now. In this Short Answers video, I answer the question, “If my Scrum team could work on one thing in 2009, what should it be?”

Of course, adopting agile engineering practices and getting better at product management are often easier said than done. If you’d like help getting started with some of the practices I mentioned in the video, I’m running a New Year’s training and coaching special with 7 ways to get 2009 started right for less than $2,000.

Books I mentioned in the video:
The Goal by Eli Goldratt
It’s Not Luck by Eli Goldratt

Related posts:

1. Short Answers #1: When Stories Are Larger Than Planned
2. New Benjamin Zander Video – “How Fascinating!”
3. One Word Can Change Your Daily Scrum