Re: [AM] Article of Interest in CIO Magazine

In a message dated 3/8/2004 6:25:45 AM Pacific Standard Time, 
[email protected] writes:
I don't understand this: Agile has a problem because it has to be explained?

> I like to think that I develop software with the same objectives as 
> everyone in this group, and it is somwhat often difficult to describe 
> the agile process and benefits in a way that satisfies the reluctance of 
> potential clients to employ it.

But clients don't employ Agile programming techniques. Clients employ 
programmers who might use Agile programming techniques. Clients employ 
planning/requirements/communication techniques that may or may not be 
Agile-minded. What would it take for clients to be clients and let 
programmers be programmers?
As far as I recall, there has not been a single time in my consulting 
experience that a potential client has not inquired as to the major details of the 
process to be employed, and these details play a significant role in their 
decisions regarding vendor selection. (I'm referring primarily to business 
applications here). If agile mehodologies were not the radical departure from 
traditional development methodologies that they are perceived to be, and might provide 
the substantial benefits with which they are credited, this might not be the 
case. However, the rapidly increasing importance of software, and the 
increasing reliance on software to facilitate virtually every facet of commerce, makes 
the development methodology to be employed an important factor. Further, 
while clients are still clients, and programmers are still programmers, the 
reported benefits in productivity and quality that are purported to accrue when they 
are combined in an agile manner substantially exceed those that accrue when 
the relationship is based upon a more traditional model. Is it, in fact, 
possible for clients and programmers to remain in their traditional roles and expect 
the results of their union to be any different than they have been in the 
past thirty-some years? If it is, what benefits do the agile methodologies bring 
to the table? If the potential paths from start to finish of a development 
project are visualized as a triangle (ABC), agile methodologies are perceived to 
provide a way to go straight from A to C, without taking the longer path 
through B (relative to the development of "working software", not distance). 

BTW, my postings in this thead are intended to elicit comments from agile 
practitoners more experenced that I that might serve to answer some of the 
criticisms that have been posted in this forum and elsewhere regarding the benefits 
of the agile methodologies and the issues to which they pertain. It is clear 
from these postings that some clarity would be both welcome and useful. No 
offense is intended. 

Comments/Opinions/Enlightenment, please.

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