Working With Augmented Distributed Agile Team In Legacy Application

1,355 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,355
On SlideShare
0
From Embeds
0
Number of Embeds
609
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Time Next slide
  • Working With Augmented Distributed Agile Team In Legacy Application

    1. 1. Working With Augmented Distributed Agile Team In Legacy Application- A Case Study<br /><ul><li>ShriKantVashishtha</li></ul>(http://svashishtha.wordpress.com/about/)<br />http://www.xebia.com<br />
    2. 2. Remember Those Old Photo Books?<br />
    3. 3. Augmented Team Model<br />http://www.xebia.com<br />9:00<br />12:00<br />13:00<br />14:00<br />15:00<br />16:00<br />17:00<br />18:00<br />10:00<br />11:00<br />9:00<br />12:30<br />17:30<br />10:00<br />11:00<br />13:30<br />14:30<br />15:30<br />16:30<br />18:30<br />Indian Team (Xebia)<br />Check nightly build results, fix broken build<br />Code Commit<br />Code new functionality<br />Stand up<br />Design Discussions<br />Pair Programming<br />Test cases<br />India<br />TIME LINE<br />Make New Tasks, Issues<br />Refactoring<br />Europe<br />Code Commit<br />Core Hours<br />Europe Team (Customer)<br />
    4. 4. Collocation<br />
    5. 5. Come to Know About Project<br />
    6. 6. Get to Know the Helicopter View<br />
    7. 7. Team Departs for Collocation<br />
    8. 8. Setup Project and Trust Building<br />
    9. 9. Collocation<br />
    10. 10. Knowledge Transfer of 2 Days<br />
    11. 11. No Single Point of Contact<br />
    12. 12. Incoherent Goals of Stay<br />
    13. 13. Finish Yet Another Sprint Successfully<br />
    14. 14. Knowledge Exchange Through Pair Programming<br />
    15. 15. … resulting in Vertical Knowledge Buildup<br />
    16. 16. The Way Team Work Agreement<br />
    17. 17. Points of Improvement?<br />
    18. 18. Define Goal of Stay<br />
    19. 19. Define Single Point of Contact<br />
    20. 20. Set the Clear and Right Expectations<br />
    21. 21. Team is Back to India…<br />
    22. 22. Project Got Changed<br />
    23. 23. Work Without Techno-Functional Knowledge<br />
    24. 24. The Project Outlook<br />
    25. 25. Initial Distributed Sprints<br />
    26. 26. Planning Meetings Like Shooting Arrows In Dark<br />
    27. 27. … resulting Drop in Mutual Trust<br />
    28. 28. After Effects<br />
    29. 29. Initial Sprints Failed<br />
    30. 30. False Sense of Productivity Loss<br />
    31. 31. Working Hard and Harder…<br />
    32. 32. Causing Burnouts<br />
    33. 33. Customer Threat to Pull the Plug<br />
    34. 34. Evolved Distributed Agile Practices<br />
    35. 35. Distributed Knowledge Sharing Sessions<br />
    36. 36. Distributed Pair Programming<br />
    37. 37. Introducing Local Retrospectives<br />
    38. 38. Pre-Planning Meetings<br />
    39. 39. Informal Distributed Communication<br />
    40. 40. Missing Links…<br />
    41. 41. Collocate for Each New Project<br />http://www.xebia.com<br />
    42. 42. Instead of Over Commit But Under Deliver…<br />
    43. 43. Under Commit and Over Deliver<br />
    44. 44. Focus on Knowledge Exchange<br />
    45. 45. References<br />http://blog.xebia.com/2009/06/02/knowledge-sharing-between-distributed-teams/)<br />http://blog.xebia.com/2009/05/21/augmented-distributed-agile-teams-the-need-of-local-retrospective/<br />http://blog.xebia.com/2008/08/14/preparing-for-agile-maintenance-knowledge-management/<br />http://xebee.xebia.in/2009/12/29/the-nutbolt-pattern-for-distributed-scrum-development/<br />http://www.xebia.com<br />
    46. 46. Questions???<br />http://www.xebia.com<br />

    ×