Transcending Cultures, Timezones and Countries

2,095 views
1,948 views

Published on

How to Scale with Distributed Agile?

During this presentation we'll take you through an exciting journey of key lessons learned from one of the largest agile projects executed at ThoughtWorks which will cover:

* Key agile principles
* What challenges comes along with the scale of up to 200+ people with added complexity of distributed location
* How is it different from other agile projects in terms of planning ahead, release plans, scope management, infrastructure
* Communication - The most important ingredient for large scale agile projects to be successful
* What kind of team structure would work best?
* How to stay focused? How to identify bottlenecks and work through them

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

  • Be the first to like this

No Downloads
Views
Total views
2,095
On SlideShare
0
From Embeds
0
Number of Embeds
78
Actions
Shares
0
Downloads
41
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcending Cultures, Timezones and Countries

  1. 1. Transcending Cultures, Timezones,and CountriesPresented by Mahesh BaxiPrepared by ChiragDoshi, NitinDhall & Mahesh BaxiJanuary 2010<br />1<br />
  2. 2. 2<br />
  3. 3. About Me<br />3<br />
  4. 4. About the Topic<br />4<br />Key Tenets of Agile<br />Something that can negatively impact the success of an agile project<br />Large scale development<br />Distributed development<br />Command-and-control<br />Forcing agile on teams<br />
  5. 5. What Does Scaling Mean?<br />Team Size Geographical Distribution Domain Complexity Technical Complexity Volumes DurationPerformance Release Planning Project Management DistributedMulti-Team Projects Functionality Stakeholders Integration Points <br />5<br />
  6. 6. Journey Through Agile Key Principles<br />6<br />Early and continuous delivery of valuable software<br />Welcome changing requirements<br />Deliver working software frequently<br />Collaboration<br />Face-to-face conversation<br />Maintain constant pace indefinitely<br />Attention to technical excellence and good design<br />Self-organizing teams<br />
  7. 7. What you don’t want<br />7<br />
  8. 8. Agility and Scale – It can work<br />8<br />Shared goal, vision and objectives<br />Team Organization<br />Planning<br />Communication<br />Bottlenecks<br />Implementing new ideas<br />Team rotations<br />Continuous Integration<br />Staying Focused<br />Importance of Toolsets<br />
  9. 9. Shared Vision, Goals & Objectives<br />9<br />
  10. 10. Shared Vision, Goals & Objectives<br />10<br />
  11. 11. Team Organization – Typical Agile Team<br />11<br />Installables<br />Continuous Integration<br />Code Repository<br />Cruise<br />
  12. 12. Team Organization – Scaled Agile Team<br />12<br />Installables<br />Continuous Integration<br />Code Repository<br />Cruise<br />
  13. 13. Planning<br />13<br />Inceptions<br />Across Teams<br />Roll-up Plans<br />Capacity & Schedule<br />Dependencies<br />
  14. 14. Planning – Watch out for<br />14<br />Story size and estimate baseline across teams<br />Story dependencies between teams<br />Individual team velocity not to be used for comparison<br />Story and feature level automation<br />
  15. 15. Agility and Scale – It can work<br />15<br />Shared goal, vision and objectives<br />Team Organization<br />Planning<br />Communication<br />Bottlenecks<br />Implementing new ideas<br />Team rotations<br />Continuous Integration<br />Staying Focused<br />Importance of Toolsets<br />
  16. 16. Communication<br />16<br />
  17. 17. Communication – Be Creative<br />17<br />Video conferencing<br />Scrum of scrums<br />Daily delivery catch-up<br />Information radiators<br />Release charts with key dates<br />Dependency charts<br />Program update meetings<br />Huddles<br />Knowledge sharing and maintaining shared context<br />
  18. 18. Bottlenecks / Constraints – put it in perspective<br />18<br />Story sign-offs<br />Automation / Regression<br />UAT<br />Release Planning<br />Builds<br />Check-ins / SVN / Branching<br />Capacity Planning<br />
  19. 19. Ideas – Ground-up, Keep it coming<br />19<br />Idea Wall<br />Larger Picture<br />High impact<br />Allocate Capacity<br />Communicate Innovation<br />
  20. 20. Team Rotations - Ownership<br />20<br />Collective Ownership<br />Financial Impact<br />Capacity Planning<br />Technical Excellence<br />Aspiration / Happiness<br />
  21. 21. Agility and Scale – It can work<br />21<br />Shared goal, vision and objectives<br />Team Organization<br />Planning<br />Communication<br />Bottlenecks<br />Implementing new ideas<br />Team rotations<br />Continuous Integration<br />Staying Focused<br />Importance of Toolsets<br />
  22. 22. Continuous Integration<br />22<br />Faster Feedback<br />Installers<br />Impact of broken builds<br />Single Build vs. aggregation<br />Conflict Resolution<br />Tool Selection<br />
  23. 23. Staying Focused<br />23<br />Executive<br />Dashboard<br />Programme Status<br />Work Steam Status<br />
  24. 24. Staying Focused<br />24<br />
  25. 25. Importance of Tools – Key Player<br />25<br />Scalability is important<br />Change is not easy<br />Easy to use / Intuitive<br />Flexibility<br />Reporting / Dashboarding<br />Should fit with architecture<br />
  26. 26. Scalable Agility across cultures, countries and Time zones <br />26<br /><ul><li>Early and continuous delivery of valuable software
  27. 27. Welcome changing requirements
  28. 28. Deliver working software frequently
  29. 29. Collaboration
  30. 30. Face-to-face conversation
  31. 31. Maintain constant pace indefinitely
  32. 32. Attention to technical excellence and good design
  33. 33. Self-organizing teams</li></li></ul><li>27<br />Thank you!<br />

×