Linked by Thom Holwerda on Mon 8th Aug 2005 13:45 UTC, submitted by cankles
Thread beginning with comment 15681
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.





Member since:
In my experience, improved quality is the key thing to come out of it (other than the book sales, yes). Things like pair-programming and test-driven development have a fair amount of up-front cost, but they do result in better code - both objectively as measured by defects found, and subjectively by anyone making subsequent changes.
As to why security doesn't appear in books on agile development, I'd not expect it to - it's something developers have to be aware of, but has nothing to do with the methodology used to develop it.