tag:blogger.com,1999:blog-1328514867467683594.post4889767365467583729..comments2009-03-12T18:42:14.524-07:00Aaron Schniederhttp://www.blogger.com/profile/13203827771563617211noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1328514867467683594.post-64968239260372967922009-03-12T18:42:00.000-07:002009-03-12T18:42:00.000-07:00Well said. Another key aspect and challenge of delivering successful software is planning the deployment. Its like being on a sports team and practicing the plays - you still need to run through the scenarios when you new plays don't fall through. That seems to be the place where I see most stress happen. When the developing is complete and looks awesome, but nobody tests properly or discusses implementation and something blows up, it is really a challenge to see who/what/when/where/why it will get fixed and prevented in the future.Kiyoshihttp://weblogs.asp.net/kiyoshi/noreply@blogger.comtag:blogger.com,1999:blog-1328514867467683594.post-71594195139905384692009-03-04T06:18:00.000-08:002009-03-04T06:18:00.000-08:00Good to see a software developer/engineer identify good requirements as one the keys.<BR/><BR/>And a high volume can be produced in a short time, see www.iag.biz .David Wrightnoreply@blogger.com