Re: [AM] Article of Interest in CIO Magazine

In a message dated 3/7/2004 7:22:47 PM Pacific Standard Time, [email protected] 
writes:
Incidentally, I’ve never been satisfied with how development methodologies 
address the issue of promoting design quality. Does anyone have any thoughts on 
this?
Actually, that was one of the points I had intended to address in my post, 
and I apologize for not explaining it more clearly or thoroughly. (I think I 
just ran out of steam at the time!). 

One of the "unclarities" I have regarding virtually all of the agile 
methodologies pertains to  system design, as in: "How do we build complex systems "in 
the agile way" that are maintainable and sustainable, when we know up front 
that we are looking at what might be a very small subset of the requirements 
that the system might ultimately be called upon to satisfy?" 

While the purists among us might suggest that we disregard those things that 
are not known, because there is some likelihood that whatever work we do on 
them may ultimately be unnecessary, and therefore a waste of resources, the 
"impurists" might suggest that to do nothing in the face of seemingly 
incontrovertible evidence that the system will require some level of post-deployment 
maintenance or modification is irresponsible, derelict, or worse. 

Now, 'fess up, boys: How many of you design systems in a manner that 
facilitates post-deployment modification, even though this might not be strictly in 
accordance with either the system requirements or the spirit of agility? I do! I 
admit it! Go ahead, drag me down to the plaza in downtown Los Gatos, where 
everyone will  laugh at my clothes! (supposedly, the depths of Silicon Valley 
ignominy).

Hey, I'm kidding, at least the part about Los Gatos. They don't actually 
laugh, they smirk! (I'm told: this is second-hand hearsay). Actually, I suspect 
that this is the point at which the immovable object meets the irresistible 
force. (Hey, it's a phrase from my youth; stuff like that is in my genes!), In 
this case, it's experience versus dogma. 

I may be making too much of this, but it seems to come up often enough in 
this forum (and others in which agile methodologies are diiscused). It is, 
however, a topic that I've wondered about at times, and would appreiate the counsel 
of the Elders on it.

Regards,

Pete

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
--^----------------------------------------------------------------