Re: [AM] Article of Interest in CIO Magazine

[email protected] wrote:

> In a message dated 3/7/2004 9:48:49 PM Pacific Standard Time, 
> [email protected] writes:
> 
>     Is there a big difference between facilitating the implementation of
>     next week's requirements and facilitating the implementation of next
>     year's requirements?
> 
> Steven:
>  
> Objectively, no. My question is this (and if it turns out to be a 
> hair-splitter, I did not intend it to):
>  
> The Agile Manifesto has been criticized on occasion for being "mushy", 
> or too "touchy-feely", not enough substance, etc. How do you, and others 
> in this august group, address the issue of maintainability and 
> sustainability within the system design on occasions in which these 
> considerations are not explicitly part of the requirements? 

I encourage my programmers to maintain the system in a good state of 
(design) repair at all times, because that helps us add new more 
features more quickly. It also has the side effect of keeping the system 
  easier to maintain, so we generally do not need to do anything extra 
special to achieve maintainability. Since it is a side effect of Doing 
Good Work, it happens free of charge.

The Agile Manifesto describes this specifically, although indirectly.
-- 
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
--^----------------------------------------------------------------