scrum and distributed teams
Post on 04-Jul-2015
Embed Size (px)
DESCRIPTIONOften teams are on different locations in the enterprise. If you work with agile methode as Scrum or Kanban this is difficult to handle. This short presentation shows you some ideas and pitfalls about this topic.
2. Artifacts Sprints Meetings Planning Meeting Sprint Reviews Daily Scrum Retrospective 1, 2 or 4 week sprints Fixed length Fixed workload Product Backlog Sprint Backlog Potential shippable product increment 3. 12 principles The most efficient and effective method of conveying in development team is face-to-face conversation. 4. 5. Distributed Teams Costs KnowHow not available Shift Operation Governance 6. Work @home No culture clashes Shift operation available Seemingly cost reducing 7. Much more communication Loosing information Language clashes No gestures or mimics available 8. 9. 10. 11. 12. Realize a development process around the clock 13. Setup 3 or more autonomous teams in 3 different timezones 14. Setup hand-over phases between the teams 15. Setup fully automatic continuous integration and delivery 16. Team1 Work & hand-over Team2 Work & hand-over Team3 Work & hand-over 17. 1 7 1 1 7 1 1 7 1 18. Phone Video No face- to-face Language Timezone issue Network issues 19. Support & Maintanance worldwide SoftwareLocal parts Production Worldwide locations 20. itemis AG | Am Brambusch 15-24 | D-44536 Lnen | www.itemis.de Thorsten Kamann @thorque 0175-4310599 email@example.com http://www.thorsten-kamann.de