tag:blogger.com,1999:blog-13831777.post8181966619302037722..comments2008-02-10T13:45:48.441-05:00Damon Poolehttp://www.blogger.com/profile/16561311551267979837noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-13831777.post-5082934306643514972008-02-10T13:45:00.000-05:002008-02-10T13:45:00.000-05:00Cool list, Im gonna share it with my Dev and QA leads. Our last project suffered a lot just by the fact that testers and developers met first time after 6 months of programming!Oscar Centenohttp://www.blogger.com/profile/04294807270100386744noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-89006363466586961042007-12-22T14:14:00.000-05:002007-12-22T14:14:00.000-05:00Guy,<BR/><BR/>Sort of! Getting to short iterations isn't easy, it often requires enabling practices such as timeboxing, continuous integration, and others. Anyway, short iterations and testing early (not necessarily full-on TDD) are two of my most highly recommended practices and I believe that's where most of the primary benefits of Agile are derived from.Damon Poolehttp://www.blogger.com/profile/16561311551267979837noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-60566969032630400802007-12-05T04:18:00.000-05:002007-12-05T04:18:00.000-05:00Most of the stated gains come from TDD and the others from short iterations. Gains from other agile techniques must be a long way down the list. So is a team that just does TDD in short iterations agile enough?Guy Rixonnoreply@blogger.comtag:blogger.com,1999:blog-13831777.post-77187697569213004602007-12-04T17:01:00.000-05:002007-12-04T17:01:00.000-05:00Good list.<BR/><BR/>On integrated dev and qa I agree with a caveat. The builds must be hands-off in a clean build environment that ensures everything in the build came from the SCM system and the QA environment must be separate from the Dev environment for the same reason. We live in SOX world...<BR/><BR/>MikeMike Coonhttp://www.blogger.com/profile/09264497793546775250noreply@blogger.com