Getting Started with a Remote Team
- 2. Getting Started with a Remote Team TRANSATLANTIC AGILE IAN GRUNERT • DEVELOPER • ATLASSIAN • @iangrunert
- 17. Challenges with Remote Teams U S + T H EM MENT A LIT Y C O MMU NIC A TIO N BOTTLENEC KS
- 18. Three strategies 1.Unify your Remote and Local Hiring 2.Face time 3.Local advocate
- 24. Unify your remote and local hiring
- 28. Travel Planning
- 35. 67 Versions
- 36. 17 Collaborators
- 41. Have a local advocate for the remote team
- 42. Recap 1.Unify your Remote and Local Hiring 2.Face time 3.Local advocate
- 43. Challenges with Remote Teams U S + T H EM MENT A LIT Y C O MMU NIC A TIO N BOTTLENEC KS
- 45. Three strategies 1.Clearly communicate team goals 2.Local Rooms and Virtual Standups in Hipchat 3.Oversharing using Atlassian Tools
- 46. Team Mission v Epics v Stories for a Sprint
- 56. Use everything at your disposal to push your message
- 58. Share thoughts via Confluence
- 60. Share wins via blog posts
- 66. Recap 1.Clearly communicate team goals 2.Local Rooms and Virtual Standups in Hipchat 3.Oversharing using Atlassian Tools
- 67. Challenges with Remote Teams U S + T H EM MENT A LIT Y C O MMU NIC A TIO N BOTTLENEC KS
- 70. Three strategies 1.Bottlenecks can be good at first 2.Avoid stepping on each others toes 3.Push for local responsibility and expertise
- 72. Pull Requests
- 73. ... but most bottlenecks are bad.
- 76. Merge PRs, fix feedback from across the pond after being merged.
- 78. Recap 1.Bottlenecks can be good at first 2.Avoid stepping on each others toes 3.Push for local responsibility and expertise
- 80. Rate this Talk Getting Started with a Remote Team Text code below to 22333 or visit http://bit.ly/1fRIAif MEH = 1B NO T BA D = 1C P R ET T Y GO O D = 1D A WES O ME = 1E To join this session, send text 136888 to