Agile Development and Offshore/Dual-Shore/Multi-location development teams
Attendees: CarlErickson, EdCunningham?, ScottAmbler?, VinnieTeles?, AndrewMcKinlay?, SergeSimard?, MurthyPidaparthi?, JohnDonovan
Outsourcing to another country/culture/etc.
We started the session with some roundtable of people's interest in the topic. People at the table were developers, it managers, consultant principles involved in a mix of XP/Agile projects and offshore/dualshore development projects.
A couple of themes seemed to emerge:
Outsourcing works well if you have a long term relationship - this is especially true if outsource team is located in another timezone, country, etc.
Communication - is key (duh) and difficult - need to have some face-to-face to be successful. Phone, video, im, etc can help, but...
Cultural issues - recognized the difficuties of communications between people in different cultures (even if common language is used for project). Ex. development project for supermarket chain outsource to country without supermarkets?
Opinion - many offshore consulting shops are very good at CMM type projects. Cost issues allow for larger teams to accomplish tasks in the.
Know when it's appropriate for a "CMM-type" team based offshore to tackle a project vs. an agile team colocated with customer. BarryBoehm?'s book? others?
So a strategy for "on-shore" teams, consulting, etc -- is go agile - make sure you can sell the advantages, know the situation.
For someone looking to outsource - know the criteral to select one or the other approach.
Other Notes
AndrewMcKinlay? described a cases study with a team in India. Project consisted of 6 developers, 6 mo project. Andrew went India to setup the team. Most communication was offline (emial, postings, etc). Results were mixed - some agile techniques were used.
ScottAmbler? related a "pre-XP-era" project with - required partitioning the code base and making sure there was handoff for common areas. "Travellers" help with consistency at different sites. When things got humming, saw some "round the clock" coding velocity via 3 shifts.
MurthyPidaparthi? described similiar situation with large semiconductor that setup development center in India. Cultural immersion by some folks from the new office at "HQ".
JohnDonovan
FrontPage
RecentChanges
Attendees: CarlErickson, EdCunningham?, ScottAmbler?, VinnieTeles?, AndrewMcKinlay?, SergeSimard?, MurthyPidaparthi?, JohnDonovan
Outsourcing to another country/culture/etc.
We started the session with some roundtable of people's interest in the topic. People at the table were developers, it managers, consultant principles involved in a mix of XP/Agile projects and offshore/dualshore development projects.
A couple of themes seemed to emerge:
Outsourcing works well if you have a long term relationship - this is especially true if outsource team is located in another timezone, country, etc.
Communication - is key (duh) and difficult - need to have some face-to-face to be successful. Phone, video, im, etc can help, but...
Cultural issues - recognized the difficuties of communications between people in different cultures (even if common language is used for project). Ex. development project for supermarket chain outsource to country without supermarkets?
Opinion - many offshore consulting shops are very good at CMM type projects. Cost issues allow for larger teams to accomplish tasks in the.
Know when it's appropriate for a "CMM-type" team based offshore to tackle a project vs. an agile team colocated with customer. BarryBoehm?'s book? others?
So a strategy for "on-shore" teams, consulting, etc -- is go agile - make sure you can sell the advantages, know the situation.
For someone looking to outsource - know the criteral to select one or the other approach.
Other Notes
AndrewMcKinlay? described a cases study with a team in India. Project consisted of 6 developers, 6 mo project. Andrew went India to setup the team. Most communication was offline (emial, postings, etc). Results were mixed - some agile techniques were used.
ScottAmbler? related a "pre-XP-era" project with - required partitioning the code base and making sure there was handoff for common areas. "Travellers" help with consistency at different sites. When things got humming, saw some "round the clock" coding velocity via 3 shifts.
MurthyPidaparthi? described similiar situation with large semiconductor that setup development center in India. Cultural immersion by some folks from the new office at "HQ".
JohnDonovan
FrontPage
RecentChanges