Vladimir Dobrov - Distributed agile teams @ First Tuesday Bergen 4 Juni 2013
•
0 likes•672 views
Vladimir Dobrov - Distributed agile teams @ First Tuesday Bergen 4 Juni 2013
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (13)
Similar to Vladimir Dobrov - Distributed agile teams @ First Tuesday Bergen 4 Juni 2013
Similar to Vladimir Dobrov - Distributed agile teams @ First Tuesday Bergen 4 Juni 2013 (20)
More from First Tuesday Bergen
More from First Tuesday Bergen (20)
Recently uploaded
Recently uploaded (20)
Vladimir Dobrov - Distributed agile teams @ First Tuesday Bergen 4 Juni 2013
- 1. Distributed Agile Teams Nearshore Outsourcing that works! consulting.ciklum.com
- 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
- 5. CiklumClient Distribution types Nearshore co-located Development Team consulting.ciklum.com DELIVERY Team Agile PM / Scrum Master Product Owner
- 6. Distribution types Distributed Development Team consulting.ciklum.com CiklumClient DELIVERY Team Agile PM / Scrum Master Product Owner
- 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
- 8. Process: What about Agile? 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
- 14. Contacts Vladimir Dobrov Technical Consultant Consulting Office (CSC) M +375 29 666 88 06 E vld@ciklum.com W consulting.ciklum.com S vr.dobrov We would be glad to answer your questions! consulting.ciklum.com
Editor's Notes
- 2 developers sitting in different rooms is almost the same if they are on different planets.
- If you know how to work efficiently with distributed teams you have a huge advantage over your competitors.
- Agile is based on right core values