[no subject]

> -----Original Message-----
&gt; From: ale-bounces at ale.org [<a  rel="nofollow" href="mailto:ale-bounces";>mailto:ale-bounces</a> at ale.org] On Behalf Of
John
&gt; Wells
&gt; Sent: Thursday, January 27, 2005 2:44 PM
&gt; To: ale at ale.org
&gt; Subject: [ale] OT: Scrum and Extended Development
&gt; 
&gt; All,
&gt; 
&gt; I know there's a few Scrum guys on the list.  I've been researching
Scrum
&gt; for possible implementation in our organization, but have read (and
&gt; sensed, to a certain extent), that Scrum is better suited for new
product
&gt; development (&quot;Both Scrum and Sashimi are suited best to new product
&gt; development rather than extended development&quot; --
&gt; <a  rel="nofollow" href="http://www.controlchaos.com/about/how.php";>http://www.controlchaos.com/about/how.php</a>).

Wow.  I'd never seen that before, and there it is in the first line of
that page.

I don't know what is meant by that line.  What does &quot;extended
development&quot; mean in this context?  I would have used it to mean &quot;a
development project over an extended period of time&quot; in which case,
scrum is ideal.  I guess they mean &quot;development extending earlier,
non-scrum, development&quot; in which case they recommend against it.  I
think that all processes are best used ab initio, and that scrum is no
worse than any other for starting in the middle.

&gt; My company works on a large ERP system.  It's core functionality is
there
&gt; and we mainly do bug fixes and enhancements.  We are in the midst of a
&gt; conversion from Progress 4GL to Java, so the app is changing, but it's
&gt; still 80% functionally complete (at least).
&gt; 
&gt; So...my question: is anyone actually using Scrum in an extended
&gt; development environment?  If not, what agile alternatives might you
&gt; suggest?

I'd like to see why they make that claim.  I think scrum is great for
coming in and clearing logjams in projects.

Scrum sounds to me like a really good thing to use on your project.
After each iteration you are supposed to have &quot;shippable code&quot;.  It
should be fully tested and running--no &quot;demo ware&quot;.  For a conversion
project, this seems like a good thing.

Scrum only works if you have real management buy-in on it.  If you adopt
it, will management let you proceed?  Will they let you not change
requirements except between iterations?  Will they let you have fixed
length iterations?  If not, then I wouldn't bother adopting it.

Good luck,

Michael



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="01214" href="msg01214.html">[ale] OT: Scrum and Extended Development</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Christopher Fowler)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg01211.html">[ale] Why Ruby? [was Pyhon syntax]</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg01213.html">[ale] Getting Linux OS to boot</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg01206.html">[ale] OT: Scrum and Extended Development</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg01214.html">[ale] OT: Scrum and Extended Development</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#01212"><strong>Date</strong></a></li>
<li><a href="threads.html#01212"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>