So you're building in small pieces with frequent feedback and rapid adjustments? I hate to tell you this, but that is very similar to bespoke agile development.
I don't think you are against the goals of "agile" or against the principals espoused by the writers of The Agile Manifesto. It seems you share mostly the same goals, and dislike the pomp, ritual, zealotry, and rapacious consulting fees of the training coaches. Well, that's true I think of most people.
As a method for estimating work and protecting developers from marauding stakeholders outside the team, I think having a company-wide buy-in to Scrum for example is a good thing. It's not going to make your developers produce better software. It just gets them clearer specs and more chance to focus on delivery. They can still deliver utter crap if that's what they are capable of producing and what your customers accept.
-
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.
|