tag:blogger.com,1999:blog-30978416.post8569090508076950859..comments2023-04-05T15:22:55.100-07:00Comments on Agile Advocate: Productivity of distributed teamsBrad Swansonhttp://www.blogger.com/profile/03081884860431841622noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-30978416.post-64042437711845517762008-11-29T16:19:00.000-08:002008-11-29T16:19:00.000-08:00Sure, depending on your definition of productive. ...Sure, depending on your definition of productive. A distributed team (or large teams for that matter) require a more structured development environment. Im talking about things like more explicit requirements, testing frameworks etc. If you are comfortable investing in that level of infrastructure you are already willing to give up being truly productive.<BR/><BR/>If you are seeking top productivity in a project, you have to be willing to abandon this in favor of tiny teams of the best people you can get and give them constant access to the customer (which is usually impossible from a distributed sense). And if you think your project is too big to do this, its just like the 500 line function - its probably not granular enough.<BR/><BR/><BR/>just my .02Anonymousnoreply@blogger.com