The document discusses the dynamics of agile teams, including how they evolve and the factors affecting their performance. Key elements include the importance of individuals and interactions, environmental conditions, and team relationships, alongside various team structures from freelancers to large distributed teams. Challenges such as communication hurdles, cultural issues, and collective ownership in larger teams are highlighted, with an emphasis on the need for appropriate tools and practices to facilitate collaboration.

1. Agile Team DynamicsBhavinJaviaThoughtWorks, B’lorebhavin@thoughtworks.com© ThoughtWorks 201018th July 2010

2. AgendaHow teams become “Agile” ?Factors affecting Agile teamsEvolution of Team Dynamics Q & A© ThoughtWorks 20102

3. How teams become “Agile” ?© ThoughtWorks 20103

4. Agility© ThoughtWorks 20104

5. Manifesto of Agile Software Development© ThoughtWorks 20105Individuals and Interactions over Processes and ToolsWorking Software over Comprehensive DocumentationCustomer Collaboration over Contract NegotiationResponding to Change over Following a Plan“ while there is value in the items on the right, we value the items to the left more ”

6. Factors affecting Agile teams© ThoughtWorks 20106PeopleCustomersEnvironmentToolsDistancesTime zones

7. PeopleMost important factorSkillsCollective responsibilitySelf organizing teamRelationshipsAspirations© ThoughtWorks 20107

8. CustomersPartnersSponsors of innovationSponsors of growthRelationship affects team moralePart of the team© ThoughtWorks 20108

9. DistancesCreate hurdles forCommunicationCollaborationFeedbackRelationshipTeam work© ThoughtWorks 20109

10. Time zones24x7 work cultureAffects collaborationCultural issues © ThoughtWorks 201010

11. ToolsRight tool for the jobTools forced top downfail on the groundLet the team chooseShared toolset © ThoughtWorks 201011

12. EnvironmentOpen work environmentNo artificial barriersFreedom of expressionEncourage innovationEncourage “fail fast”Positive energy© ThoughtWorks 201012

13. Evolution of Team Dynamics© ThoughtWorks 201013

14. Agile Team Dynamics ? Challenges faced by the teamPractices and Processes evolved to solve challengesJust “ the way an agile team works ”FormingStormingNormingTuckman’s Group Development ModelPerformingAdjourning© ThoughtWorks 201014

15. FreelancerOne man armyCollaborates only with customer Independent decisionsSingle point of failure© ThoughtWorks 201015

16. Freelancer© ThoughtWorks 201016

17. A Dev PairMust be multi talented and multi functionalTeam building startsEasy collaboration with CustomerIntroduction of Agile practices starts e.g. Pair ProgrammingDecisions get discussed/challengedSense of collective responsibilityScaling issues begin to surface© ThoughtWorks 201017

18. A Dev Pair© ThoughtWorks 201018

19. Small Collocated TeamTeam Structure2 Dev pairs 1 BA 1 QA© ThoughtWorks 201019

20. Small Collocated TeamCollective ownership and responsibilityDirect collaboration with customerDistribution of workloadNo communication overheadsImmediate and direct feedbackOverlap of roles© ThoughtWorks 201020

21. Small Collocated Team© ThoughtWorks 201021

22. Small Distributed TeamTeam Structure1 Dev pair (onsite)1 BA (onsite)1 Dev pair (offshore)1 QA (offshore)© ThoughtWorks 201022

23. Small Distributed TeamOnsite team collaborates directly with CustomerOffshore team collaborates indirectly with CustomerWork gets done 24x7Collaboration challenges surfaceDivision of responsibilitiesLack of context begins to hurtCommunication overheads due to distance/time differencesFeedback cycles become largerCultural issues surface© ThoughtWorks 201023

24. Small Distributed Team© ThoughtWorks 201024

25. Large Collocated TeamTeam Structure8 Dev pairs2 BAs2 QAs1 IM/PM© ThoughtWorks 201025

26. Large Collocated TeamHigher capacity to deliverCollaboration with Customer gets indirectCollective ownership begins to hurtDifficult to roll out technical and process changesNeed for Managers become apparentNeed for Tracking tools felt© ThoughtWorks 201026

27. Large Collocated Team© ThoughtWorks 201027

28. Large Distributed TeamTeam Structure2 Dev pairs (onsite)1 BA (onsite)1 PM (onsite)6 Dev pairs (offshore)2 BAs (offshore)2 QAs (offshore)1 IM (offshore)© ThoughtWorks 201028

29. Large Distributed TeamCollaboration becomes difficultCustomer availability and feedback becomes scarceCollective ownership hurts moreScaling challenges peakHigh expectations from offshore teamCustomers may not realize all the challengesLocalized groups of expertise begin to formDifficult situations turn into ugly Blame GamesPeople become “email addresses” or “voices over phone”© ThoughtWorks 201029

30. Challenges and Solutions© ThoughtWorks 201030

31. Q & A© ThoughtWorks 201031

32. © ThoughtWorks 201032bhavin@thoughtworks.com