3. What is a Distributed Team?
consulting.ciklum.com
4. Why Distributed Teams?
Some reasons to do Distributed Development:
• “Right” people are distributed
• Business becomes distributed
• Access to global HR market
• No dependency on “hot” local market
consulting.ciklum.com
7. Distribution is a challenge
Some challenges of Distributed Teams:
• Lack of Transparency
• Lack of Trust
• Loss of Context (Tech & Business)
• Cultural differences
• Time differences
• Slow Communication
• Management isolation
consulting.ciklum.com
9. Tools, Tools & Tools…
Right tools make life of Distributed Teams easier
(if used efficiently):
• Source Control systems
• Project management & Issue tracking
• Knowledgebase tools & Wiki’s
• Communication tools (Skype, Chat, Email…)
• “Video windows” (when Dev Team distributed)
consulting.ciklum.com
10. Technical practices
Technical Practices that make a Difference:
• Continuous Integration
• Test Driven Development
• Automated Testing
• Collective Ownership
• Continuous Refactoring
consulting.ciklum.com
11. What else?
Some good non-technical practices:
• Co-located start of the project
• Frequent bi-directional “maintenance” visits
• Common Team building activities
• Every location needs a “leader”
consulting.ciklum.com
12. Summary
• Small & self-organized teams built around motivated
and passionate individuals
• Short iterations with frequent releases increase
visibility and enable early feedback
• Daily synch-up meeting to keep the Context and
identify problems on early stage
• Right tools & practices to collaborate more efficiently
consulting.ciklum.com