I think these two lines are perhaps the truest things I've read about software development or anything else all day.

Dogmatically applying any set of guidelines as inflexible rules is both silly and against the definition of "agile" as a word and as the original movement. A team should make as much or as little use of a methodology or a mix of methodologies as works best for that team. Anything written in a book or taught in a class is just a starting point for a new team and shouldn't be an end goal.

In reply to Re^4: Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship (useful) by mr_mischief
in thread Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship by eyepopslikeamosquito

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.