Like everything else, there has to be a "point of balance". In this case, someone (the author of the quotation) acts as arbiter between what the end users want and what the "system" can or should provide. The ability to release new software daily does indeed reflect flexibility and agility. The question is how much flexibility and/or agility should be exercised?

Too much of these qualities expend resources that can never be reclaimed and will kill the organization. Insufficient flexibility/agility will kill the system, because: the users simply won't use it; or the organization will die because it could not adapt to the real functional needs it was designed to satisfy.