The document discusses the challenges faced by an augmented distributed agile team working on a legacy application, highlighting issues such as incoherent goals, lack of techno-functional knowledge, and false productivity. It suggests improvements like clearly defining goals, establishing a single point of contact, and enhancing knowledge exchange through practices like pair programming and local retrospectives. The case study emphasizes the importance of collocation for new projects to foster trust and effective collaboration.

1. Working With Augmented Distributed Agile Team In Legacy Application- A Case StudyShriKantVashishtha(http://svashishtha.wordpress.com/about/)http://www.xebia.com

2. Remember Those Old Photo Books?

3. Augmented Team Modelhttp://www.xebia.com9:0012:0013:0014:0015:0016:0017:0018:0010:0011:009:0012:3017:3010:0011:0013:3014:3015:3016:3018:30Indian Team (Xebia)Check nightly build results, fix broken buildCode CommitCode new functionalityStand upDesign DiscussionsPair ProgrammingTest casesIndiaTIME LINEMake New Tasks, IssuesRefactoringEuropeCode CommitCore HoursEurope Team (Customer)

4. Collocation

5. Come to Know About Project

6. Get to Know the Helicopter View

7. Team Departs for Collocation

8. Setup Project and Trust Building

9. Collocation

10. Knowledge Transfer of 2 Days

11. No Single Point of Contact

12. Incoherent Goals of Stay

13. Finish Yet Another Sprint Successfully

14. Knowledge Exchange Through Pair Programming

15. … resulting in Vertical Knowledge Buildup

16. The Way Team Work Agreement

17. Points of Improvement?

18. Define Goal of Stay

19. Define Single Point of Contact

20. Set the Clear and Right Expectations

21. Team is Back to India…

22. Project Got Changed

23. Work Without Techno-Functional Knowledge

24. The Project Outlook

25. Initial Distributed Sprints

26. Planning Meetings Like Shooting Arrows In Dark

27. … resulting Drop in Mutual Trust

28. After Effects

29. Initial Sprints Failed

30. False Sense of Productivity Loss

31. Working Hard and Harder…

32. Causing Burnouts

33. Customer Threat to Pull the Plug

34. Evolved Distributed Agile Practices

35. Distributed Knowledge Sharing Sessions

36. Distributed Pair Programming

37. Introducing Local Retrospectives

38. Pre-Planning Meetings

39. Informal Distributed Communication

40. Missing Links…

41. Collocate for Each New Projecthttp://www.xebia.com

42. Instead of Over Commit But Under Deliver…

43. Under Commit and Over Deliver

44. Focus on Knowledge Exchange

45. Referenceshttp://blog.xebia.com/2009/06/02/knowledge-sharing-between-distributed-teams/)http://blog.xebia.com/2009/05/21/augmented-distributed-agile-teams-the-need-of-local-retrospective/http://blog.xebia.com/2008/08/14/preparing-for-agile-maintenance-knowledge-management/http://xebee.xebia.in/2009/12/29/the-nutbolt-pattern-for-distributed-scrum-development/http://www.xebia.com

46. Questions???http://www.xebia.com