Agile Team Dynamics


Published on

My presentation on Agile Team Dynamics given at Agile NCR 2010 conference at Gurgaon, India

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Introduction:Sr Consultant at ThoughtWorks for 6+ yearsFounding member of ASCI, organized various Agile India conferencesWorked on more than 16 Agile ProjectsTenure from 2 weeks to 1 yearTeam sizes 3-60+India and abroadTalk to introduce the evolution of team dynamics in an agile team
  • Nothing can replace face to face collaborationDistances create hurdles for communication, collaboration, relationships, team work
  • Work gets done 24x7Collaboration gets hitCultural issues
  • Availability of the right tool for the job at the right timeTools introduced Top Down fail to address ground realitiesShared toolset does wonders to team productivity
  • Open work environment a mustArtificial barriers negate benefits of collocationFreedom of expression
  • Agile Team Dynamics

    1. 1. Agile Team Dynamics<br />BhavinJavia<br />ThoughtWorks, B’lore<br /><br />© ThoughtWorks 2010<br />18th July 2010<br />
    2. 2. Agenda<br />How teams become “Agile” ?<br />Factors affecting Agile teams<br />Evolution of Team Dynamics <br />Q & A<br />© ThoughtWorks 2010<br />2<br />
    3. 3. How teams become “Agile” ?<br />© ThoughtWorks 2010<br />3<br />
    4. 4. Agility<br />© ThoughtWorks 2010<br />4<br />
    5. 5. Manifesto of Agile Software Development<br />© ThoughtWorks 2010<br />5<br />Individuals and Interactions over Processes and Tools<br />Working Software over Comprehensive Documentation<br />Customer Collaboration over Contract Negotiation<br />Responding to Change over Following a Plan<br />“ while there is value in the items on the right, we value the items to the left more ”<br />
    6. 6. Factors affecting Agile teams<br />© ThoughtWorks 2010<br />6<br />People<br />Customers<br />Environment<br />Tools<br />Distances<br />Time zones<br />
    7. 7. People<br />Most important factor<br />Skills<br />Collective responsibility<br />Self organizing team<br />Relationships<br />Aspirations<br />© ThoughtWorks 2010<br />7<br />
    8. 8. Customers<br />Partners<br />Sponsors of innovation<br />Sponsors of growth<br />Relationship affects team morale<br />Part of the team<br />© ThoughtWorks 2010<br />8<br />
    9. 9. Distances<br />Create hurdles for<br />Communication<br />Collaboration<br />Feedback<br />Relationship<br />Team work<br />© ThoughtWorks 2010<br />9<br />
    10. 10. Time zones<br />24x7 work culture<br />Affects collaboration<br />Cultural issues <br />© ThoughtWorks 2010<br />10<br />
    11. 11. Tools<br />Right tool for the job<br />Tools forced top down<br />fail on the ground<br />Let the team choose<br />Shared toolset <br />© ThoughtWorks 2010<br />11<br />
    12. 12. Environment<br />Open work environment<br />No artificial barriers<br />Freedom of expression<br />Encourage innovation<br />Encourage “fail fast”<br />Positive energy<br />© ThoughtWorks 2010<br />12<br />
    13. 13. Evolution of Team Dynamics<br />© ThoughtWorks 2010<br />13<br />
    14. 14. Agile Team Dynamics ? <br />Challenges faced by the team<br />Practices and Processes evolved to solve challenges<br />Just “ the way an agile team works ”<br />Forming<br />Storming<br />Norming<br />Tuckman’s <br />Group Development Model<br />Performing<br />Adjourning<br />© ThoughtWorks 2010<br />14<br />
    15. 15. Freelancer<br />One man army<br />Collaborates only with customer <br />Independent decisions<br />Single point of failure<br />© ThoughtWorks 2010<br />15<br />
    16. 16. Freelancer<br />© ThoughtWorks 2010<br />16<br />
    17. 17. A Dev Pair<br />Must be multi talented and multi functional<br />Team building starts<br />Easy collaboration with Customer<br />Introduction of Agile practices starts e.g. Pair Programming<br />Decisions get discussed/challenged<br />Sense of collective responsibility<br />Scaling issues begin to surface<br />© ThoughtWorks 2010<br />17<br />
    18. 18. A Dev Pair<br />© ThoughtWorks 2010<br />18<br />
    19. 19. Small Collocated Team<br />Team Structure<br />2 Dev pairs <br />1 BA <br />1 QA<br />© ThoughtWorks 2010<br />19<br />
    20. 20. Small Collocated Team<br />Collective ownership and responsibility<br />Direct collaboration with customer<br />Distribution of workload<br />No communication overheads<br />Immediate and direct feedback<br />Overlap of roles<br />© ThoughtWorks 2010<br />20<br />
    21. 21. Small Collocated Team<br />© ThoughtWorks 2010<br />21<br />
    22. 22. Small Distributed Team<br />Team Structure<br />1 Dev pair (onsite)<br />1 BA (onsite)<br />1 Dev pair (offshore)<br />1 QA (offshore)<br />© ThoughtWorks 2010<br />22<br />
    23. 23. Small Distributed Team<br />Onsite team collaborates directly with Customer<br />Offshore team collaborates indirectly with Customer<br />Work gets done 24x7<br />Collaboration challenges surface<br />Division of responsibilities<br />Lack of context begins to hurt<br />Communication overheads due to distance/time differences<br />Feedback cycles become larger<br />Cultural issues surface<br />© ThoughtWorks 2010<br />23<br />
    24. 24. Small Distributed Team<br />© ThoughtWorks 2010<br />24<br />
    25. 25. Large Collocated Team<br />Team Structure<br />8 Dev pairs<br />2 BAs<br />2 QAs<br />1 IM/PM<br />© ThoughtWorks 2010<br />25<br />
    26. 26. Large Collocated Team<br />Higher capacity to deliver<br />Collaboration with Customer gets indirect<br />Collective ownership begins to hurt<br />Difficult to roll out technical and process changes<br />Need for Managers become apparent<br />Need for Tracking tools felt<br />© ThoughtWorks 2010<br />26<br />
    27. 27. Large Collocated Team<br />© ThoughtWorks 2010<br />27<br />
    28. 28. Large Distributed Team<br />Team Structure<br />2 Dev pairs (onsite)<br />1 BA (onsite)<br />1 PM (onsite)<br />6 Dev pairs (offshore)<br />2 BAs (offshore)<br />2 QAs (offshore)<br />1 IM (offshore)<br />© ThoughtWorks 2010<br />28<br />
    29. 29. Large Distributed Team<br />Collaboration becomes difficult<br />Customer availability and feedback becomes scarce<br />Collective ownership hurts more<br />Scaling challenges peak<br />High expectations from offshore team<br />Customers may not realize all the challenges<br />Localized groups of expertise begin to form<br />Difficult situations turn into ugly Blame Games<br />People become “email addresses” or “voices over phone”<br />© ThoughtWorks 2010<br />29<br />
    30. 30. Challenges and Solutions<br />© ThoughtWorks 2010<br />30<br />
    31. 31. Q & A<br />© ThoughtWorks 2010<br />31<br />
    32. 32. © ThoughtWorks 2010<br />32<br /><br />