RE: [AM] The Spiral Model

Exactly.  

And there have been several discussions here why RUP in theory approaches agility, but very few real world instantiations of it are actually as agile as most instantiations of XP, Scrum, and other agile methodologies.  

If I recall, I came away from those discussions concluding that what makes RUP not agile in practice are:
- the huge menu of practices to choose from makes it difficult to start from a small enough set of practices to stay lightweight.
- the accompanying document-centric tool set also makes it hard to stay lightweight.
- the first phase is devoted to determining an architecture given the initial requirements, thus not delivering any business functionality early enough the customer to prime the requirement refinement pump.  This increases the cost of change, thus discouraging the requirement refinement pump from ever becoming more than a trickle compared to true agility.

-----Original Message-----
From:	Barr Bill P [mailto:[email protected]]
Sent:	Fri 2/13/2004 6:42 AM
To:	'[email protected]'
Cc:	
Subject:	RE: [AM] The Spiral Model

>If you take Spiral to the extreme that you build some new business
functionality every few weeks, then you would be approaching agility.  This
would end up forcing us to focus on only a few features.  The requirements, 

Doesn't this pretty much describe the RUP's implementation of the Spiral
model?

For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com

For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com
--^----------------------------------------------------------------
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h
Or send an email to: [email protected]

TOPICA - Start your own email discussion group. FREE!
http://www.topica.com/partner/tag02/create/index2.html
--^----------------------------------------------------------------