tag:blogger.com,1999:blog-6149953344722382854.post5297856764782157887..comments2010-02-12T18:52:59.387-06:00AABhttp://www.blogger.com/profile/07464006705601227120noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6149953344722382854.post-43845361616565514362010-02-12T18:52:59.387-06:002010-02-12T18:52:59.387-06:00Roger - <br /><br />That is precisely my viewpoint as well. I think Agile and LEAN practices are absolutely required in certain parts of Development Life Cycle. In my view, capability-based analysis, and our internal method (TIMM) is an effective way to make that happen. Once chaos is organized, it&#39;s easy to pick out small pieces and apply Agile practices or processes and apply LEAN. I just think that each of these has to be done in moderation, rather than go overboard.<br /><br />AABAABhttp://www.blogger.com/profile/07464006705601227120noreply@blogger.comtag:blogger.com,1999:blog-6149953344722382854.post-49678734698653997062010-02-11T20:15:40.214-06:002010-02-11T20:15:40.214-06:00I can&#39;t argue with requirements gathering. The only issue is when it the appropriate time to do so. Of course, I believe that requirements gathering takes second place (and occurs after) complexity has been addressed.<br /><br />- RogerRoger Sessionshttp://www.blogger.com/profile/16946430426943308823noreply@blogger.com