I think there's a big caveat when using a model of deploying early and often. This approach can too easily lead to a culture where the early adopters of the "production" software are in reality just beta testers. There are reasons why the belief exists that you don't install new Microsoft products untill after SP1.

In the business world, people are trying to perform tasks, and want a stable environment to do it in. It's a thin tightrope to walk between being agile and responsive to business needs vs. getting something out just to say you've accomplished something. I've seen too many times in both in-house software development and comercial software where short term thinking and a desire to meet artificial dates rushed things into use that weren't ready. I think the real thing to take away from the referenced article is to keep the user community involved more, give people what they really need, and try to remember that quantity does not trump quality.