Download as PDF, PPTX
Uploaded bySunil Mundra
Distributed Development Best Practices
The document discusses best practices for distributed development. It outlines challenges like barriers to communication when teams are in different time zones and lack of visibility into other teams' work. Recommended best practices include using tools like electronic story walls for transparency, having joint meetings and overlap hours to collaborate, and establishing cultural sensitivity. Adopting Agile practices can help by reducing risk through collaboration, overcoming communication barriers, and maintaining quality while scaling distributed teams. The key takeaways are that communication overhead is worthwhile, not all team members can be co-located, and transparency is important for distributed development success.
More Related Content
Similar to Distributed Development Best Practices
Distributed Development Best Practices
- 1. Distributed Development Best Practices September 7, 2012
- 2. Outline Why Distributed Development Challenges In Distributed Development Best Practices Role of Agile in Distributed Development Summary Q&A
- 3. Setting Expectations Takeaways Not Meant Sources of Agile Practices Challenges One Size Fits All Practical tips for Silver Bullet Best Practices Role of Agile in enabling Distributed Development
- 4.
- 5. BAU Cost Arbitrage Outsourcing
- 6. BAU Cost Arbitrage Outsourcing Proximity to Customers 24 X 7 Development Cycle Access to Talent/Experience
- 7.
- 8. Scenario 1 Development Teamis split between 2 vastly different time zones, say China and Brazil, and have never met each other. The teams communicate via emails and phone calls. Challenge: Barriers to Communication and Collaboration
- 9. Scenario 2 Client isin USA and Development is happening in Brazil, and client is communicating requirements via documents and phone calls. Challenge: Client Requirements Disconnect/Misunderstanding
- 10. Scenario 3 Product developmentis split between USA and India. USA Devs think India Devs are not good enough, and India Devs think their work is not getting appreciated in USA Challenge: Lack of Trust and Low Morale
- 11. Scenario 4 Product developmentis split between USA and India. India Devs ended their day with a broken build, resulting in USA Devs not being able to work on the latest build Challenge: Lack of Co-ordination
- 12. Scenario 5 Product developmentis split between USA and Philippines. On the release date, USA was ready with their features, but Philippines slipped Challenge: Lack of Visibility
- 13.
- 14. Additional Challenges Lack of Cultural Sensitivity
- 15. Additional Challenges Unforeseen Risks
- 16. Additional Challenges Lack of Common Ownership of Code
- 17. Additional Challenges Lack of ‘Big Picture’ View
- 18. Additional Challenges Finger Pointing on Slip Ups
- 19.
- 20. People Challenges Tools & Infrastructure Process
- 21.
- 22. People Proxy Product Owner
- 23. People Cross Pollination
- 24. People Cultural Sensitivity
- 25. People Optimize Team Around Effective Communicators
- 26. People Enable Personal Relationships
- 27. People Culture of Feedback
- 28.
- 29. Process Joint Meetings: Stand Ups Retrospectives
- 30. Process Showcases
- 31. Process Overlap Hours
- 32. Process Remote Pairing
- 33. Process Operational Documentation
- 34. Process Co-Located Meetings: Inception Release Planning
- 35. Process FunctionalityBased Structure
- 36. Process Daily Hand Offs
- 37.
- 38. Tools Electronic Info. Radiators: Story Wall Build Metrics Dashboard
- 39. Tools Communication and Collaboration Tools
- 40. Infrastructure Standard Team Rooms
- 41. Infrastructure Network Connectivity
- 42. Infrastructure Development and Testing Environments
- 43. Infrastructure Version Control System
- 44. Electronic Story WallExample
- 45. Tools Examples Speaker Phones Multi-View Webcams CI and Build Pipeline Messaging Tools Telepresence Wiki
- 46.
- 47. Agile and DistributedDevelopment Reduce Project Risk
- 48. Agile and DistributedDevelopment Maximize Collaboration
- 49. Agile and DistributedDevelopment Overcoming Communication Barriers
- 50. Agile and DistributedDevelopment Maximize Efficiency Through Engineering Practices
- 51. Agile and DistributedDevelopment Scale Without Sacrificing Quality
- 52.
- 53. To Summarize Communication and Travel Overheads Are Worth It
- 54. To Summarize Remember,Not Everyone Is In ‘The Room’
- 55. To Summarize Transparency Is Key
- 56. To Summarize Aim To Maximize ‘Intimacy’
- 57. To Summarize Maintain Discipline
- 58. To Summarize Leverage The Distance
- 59. Questions? Sunil Mundra sunilrm@thoughtworks.com Blog: http://suniltalksagile.wordpress.com/
- 60.