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.

In reply to Re: An interesting rebuttal of "agile" by DBAugie
in thread An interesting rebuttal of "agile" by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.