It was half-baked because we felt the urge to release often. I consider this experience very positive, we learned a lot but meanwhile, our product had to fail and now, we have to resurrect it.

But that's not what release often means. If you've got a half-baked idea, then it's half-baked regardless of when and how often you release.

Releasing often has lead us to stop seeing the bigger picture. I think the danger when you release often is to rush the releases... and in the end transform what was a great idea into a half-baked product. I don't want to say that this statement is always wrong, because it certainly isn't, but I think people should approach it with care and stop applying it like it was a God commandement.

> ... but I think people should approach it with care and > stop applying it like it was a God commandement. Isn't that the case with _any_ guideline ?

Guidelines like 'Release early, release often' are just that, guidelines. Take any guideline to its extremes and it will just collapse. They are just there to 'guide' your _thinking_, and that's something no-one else can do for you.