RE: [AM] Article of Interest in CIO Magazine

Trying to directly address this problem in the technical and process domain generally creates a weight that impedes agility, adds costs, and masks the real underlying problem - communication and cooperation.  The result is everyone's ass is covered, but solutions are still produced that are difficult to maintain, integrate, and adapt.
 
My understanding of the Agile Manifesto is that it advocates simplifying and emphasizing the lines of communication instead of trying to create process that ameliorates the need for communication by directly addressing the common symptoms of poor communication.
 
In other words, we should be communicating and learning with the people who will be using and maintaining the systems we build, not just the people paying for it and their subject matter experts. This communication should include eliciting the requirements necessary to make the system maintable, integratable, and adaptable.  The communication with the people paying for the system should include making sure they understand these additional requirements sufficiently to properly prioritize them.
 
A process that has us guessing these additional requirements, their priorities, and then implementing them without this communication and cooperation is likely to miss the mark anyway.
 
Steven Gordon
http://sf.asu.edu

	-----Original Message----- 
	From: [email protected] [mailto:[email protected]] 
	Sent: Mon 3/8/2004 7:00 AM 
	To: [email protected] 
	Cc: 
	Subject: Re: [AM] Article of Interest in CIO Magazine
	
	
	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 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.
	 
	Regards,
	 
	Pete
	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
--^----------------------------------------------------------------