Re: [AM] Article of Interest in CIO Magazine

[email protected] wrote:

> In a message dated 3/8/2004 4:47:10 AM Pacific Standard Time, 
> [email protected] writes:
> 
>     The Agile Manifesto describes this specifically, although indirectly.
> 
> As I thought. From a decision maker's perspecive, this can be a 
> difficult gap to bridge. It implies a reliance on the agile proponent to 
> describe the agile process  and the potential benefits clearly, which 
> could explain many of the criticisms from its detractors. Thank you.

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?
-- 
J. B. Rainsberger,
Diaspar Software Services
http://www.diasparsoftware.com :: +1 416 791-8603
Let's write software that people understand

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