[AccessD] Lazy, or Agile: that is the question... - Was Re:When to Use a JunctionTable

Hi Eric

Thanks for the clarification. That list of principles makes sense. Indeed as that is how we've always (which is since 1993) operated.

That said, I think most of the discussion on agile programming relates to large projects where the "old method" was to use years in writing specifications involving users in endless meetings on something they could only imagine; then years was used to program the project using old technology. In the end the project was finished - typically with a major delay and a serious budget increase - but it was outdated from the first day as the real world, of course, had moved during the build of the project.

/gustav

>>> ebarro at verizon.net 07-05-2007 17:35 >>>
Shamil,

I think that if you were to check with the principles of Agile Development
you will note that the goal is rapid application development (RAD) but not
at the expense of technical excellence and good design.

http://en.wikipedia.org/wiki/Agile_software_development 

Specifically... 

Some of the principles behind the Agile Manifesto are:

    * Customer satisfaction by rapid, continuous delivery of useful software
    * Working software is delivered frequently (weeks rather than months)
    * Working software is the principal measure of progress
    * Even late changes in requirements are welcomed
    * Close, daily, cooperation between business people and developers
    * Face-to-face conversation is the best form of communication
    * Projects are built around motivated individuals, who should be trusted
    * Continuous attention to technical excellence and good design
    * Simplicity
    * Self-organizing teams
    * Regular adaptation to changing circumstances

--Eric