Most (all?) Agile methodologies are about striking a balance between allowing change, and managing the effect of those changes. As chromatic said, if you can make daily releases, it's not really a problem in and of itself. If you *have* to, because of bugs, or more to the point, business people changing their minds then it's a problem. (Believe it or not, I have seen business people try to distort the defintion of Agile to allow them to make changes in direction at least daily).
Scrum, for example, strongly discourages the product owner from interfering with the iteration while it's in progress (they can terminiate the sprint if they really have to, but this is an action of last resort). So there's really no need for the team to release anything until the end of the iteration, which is usally at least 2 weeks long.
-
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.
|