in reply to
An interesting rebuttal of "agile"
Most (all?) Agile methodologies are about striking a balance between allowing change, and managing the effect of those changes. As chromatic said, if you can make daily releases, it's not really a problem in and of itself. If you *have* to, because of bugs, or more to the point, business people changing their minds then it's a problem. (Believe it or not, I have seen business people try to distort the defintion of Agile to allow them to make changes in direction at least daily).
Scrum, for example, strongly discourages the product owner from interfering with the iteration while it's in progress (they can terminiate the sprint if they really have to, but this is an action of last resort). So there's really no need for the team to release anything until the end of the iteration, which is usally at least 2 weeks long.