The authors of The Agile Manifesto I think agree more with you than with many of the process zealots selling books and classes about agile development. There has been a follow-up saying they never intended the formalization of their people over process rant into such strict processes, which makes sense.
The actual processes are largely inspired by Japanese manufacturing techniques. They get labeled "agile" mainly because that's the hot word and the original manifesto authors didn't trademark the word to sell books and classes.
I'm still unsure what part of any of this situation encourages you to keep saying that people who do test-first development or who have daily fifteen-minute status meetings are absolutely and definitely replaceable cogs who can't develop code and need to "code by numbers". That seems like one hell of an unsupported claim.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|