InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Presentation: Reaching Hyper-Productivity with Outsourced Development Teams

Posted by Abel Avram on Nov 11, 2008

Sections
Process & Practices
Topics
Agile Techniques ,
Agile
Tags
Distributed Teams ,
agile2008 ,
XP ,
Scrum

 In this presentation filmed during Agile 2008, Jeff Sutherland, co-creator of Scrum, and Guido Schoonheim, CTO of Xebia, present an actual case of reaching hyper-productivity with a large distributed team using XP and Scrum.

Watch: Jeff Sutherland: Reaching Hyperproductivity with Outsourced Development Teams (29 min.)

Usually, the general advice is: don't use distribute teams. The Dutch company Xebia has tried going distributed and has succeeded, according to Jeff and Guido. They started by creating a common "mindspace", bringing together the members of both teams, the Dutch and the Indian one, in order to achieve:

• Shared ownership
• Shared context
• Personal relationships
• Team culture and standards
• Shared Agile value system

After some time, they sent the offshore team back home continuing development by practicing Scrum and XP. The results were remarkable, according to Jeff and Guido. They benefited both from the local talent and offshore cost reductions, and recommend fully distributed Scrum as the best development solution.

Whole team issues by Sasha Milenkovic Posted
  1. Back to top

    Whole team issues

    by Sasha Milenkovic

    About ScrumMasters/Coaches in teams. Did you have two of them per team or one per team, or there was no specialy ScrumMaster role in team?

    Did you had real product owner in team or proxies? Is it neaded to have more product owners when you have multiplied teams?

    What can be the ideal situation with product owners/proxies for product made by Fully Distributed Scrum?

Educational Content

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?

Wrap Your SQL Head Around Riak MapReduce

Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.