tag:blogger.com,1999:blog-21080042.post5423265952502628753..comments2024-03-17T17:03:47.760-07:00Comments on Agile World: Agile Offshore Development Tip 4: Involve Offshore into Scrum meetingsVenkatesh Krishnamurthyhttp://www.blogger.com/profile/11471239057569635943noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-21080042.post-17999756664987751092007-03-28T01:42:00.000-07:002007-03-28T01:42:00.000-07:00I have seen this pattern happening in Services com...I have seen this pattern happening in Services company especially if the offshore team is in India(as I work in India) and is "used" for development purposes.<BR/> The onsite team(US, Europe or some other place) members collect requirements, do a design and hand off these information to development team for coding and testing. Handoff by itself has lot of wastes associated with this, and in the above mentioned scenario, the development team would feel they are being used. This pattern needs to be avoided as much as possible. <BR/><BR/>My suggestion is to understand the capability of offshore teams and see if they are interested in participating in all key discussions. If offshore team does not know much, then the onsite team members can mentor the offshore teams !Venkatesh Krishnamurthyhttps://www.blogger.com/profile/11471239057569635943noreply@blogger.comtag:blogger.com,1999:blog-21080042.post-23751590137975220132007-03-27T12:31:00.000-07:002007-03-27T12:31:00.000-07:00In your experience does this happen often - i.e ag...In your experience does this happen often - i.e agile on-site and offshore teams not communicating properly?<BR/><BR/>Also, do you think it is better to structure the teams based on roles (requirements and design on-site, development and test offshore) or features (features a,b,c on-site, features d,e,f offshore)?Siddhihttps://www.blogger.com/profile/16893177345726416004noreply@blogger.com