This document discusses tips for facilitating distributed Scrum teams. It notes that distributed Scrum can be painful, especially for unprepared Scrum Masters, and that training often focuses on collocated teams. Some tips include using lightweight virtual Scrum boards, focusing on communication through video chat when possible, and humanizing the distributed experience by establishing trust and putting names to faces. The key messages are to start small with tools, prioritize communication effectively, and act as a champion to bind the distributed team together.

1. Distributed ScrumMasters & the art of digital facilitation @davidjbland #Agile2010

2. ScrumMaster & Agile Coach Introduced to Agile Software Development in 2002 Collocated & Distributed Teams Tech Startups & Enterprise Organizations financial – saas - ecommerce - counter terrorism

3. Distributed Scrum is painful* *especially for unpreparedScrumMasters

4. Vanilla flavored Distributed Scrum is a myth

5. Training often focuses on collocation

6. Effective ScrumMasters in collocatedteams can be… …ineffectivefor distributed teams

7. Tips that will help you find your way with Distributed Scrum

8. Virtual Scrum Boards (Free Google Drawing Template pictured above)

9. DistributedScrum is not an AgileLifecycle Management tool.

10. Complex tools can raise your barrier to adoption

11. Teams will channel their frustrations into the tool.

12. You’ll steer around the usability flaws

13. individuals and interactions… … over processes and tools http://agilemanifesto.org/

14. Find the right balanceof tools for your team vs.

15. Lightweight & low cost experience

16. Cross the chasmbefore worrying about scale

17. Try a lightweightvirtual scrum board tool for 2 to 3 iterations

18. You’ll place the focus backonto your team

19. DistributedCommunication

20. Distribution generatesmore documentation Planning & Preparation Iteration Info/Goals Daily Scrum Recaps Documenting Impediments Reviews & Retrospectives

21. “I haven’t even opened my email today” - Anonymous Developer

22. Online Text Chat (8:00am) ScrumMaster:Yt…. (8:01am) ScrumMaster:You there? (8:02am) ScrumMaster:hello? (8:03am) ScrumMaster:HI (8:04am) ScrumMaster:Ping me (8:05am) ScrumMaster:yt? (8:06am) ScrumMaster:what’s up (8:07am) ScrumMaster:hi there… (8:08am) ScrumMaster:YT?

23. Phone

24. Body languageis important

25. Video

26. Fight for the video conference room

27. Setup 10 to 15minutes early

28. Stand Up

29. 3 Questions(maximum overlap) What did you do yesterday? What will you do today? What is in your way?

30. 3Questions(minimum overlap) What did you do today? What will you do tomorrow? What is in your way?

31. Removing impedimentswhile the team is asleep

32. Feedback loops10 minutes vs. 10 hours

33. Humanize the distributed teamexperience

34. Being a mirror for distributed teams is difficult

35. Hone yourperception skills

36. Cultureaffects your distributedteam

37. Chicken & Piglabelsdo not translatewellacross cultures

38. Establishtrust with retrospectives

39. Team membersare notresources

40. “Metrics are people too” - Eric Ries

41. Put names with faces

42. Organize group outings

43. Be thechampion for your team

44. To Recap - Start with a lightweightvirtual scrum board - Use video chat whenever possible to communicate - Humanize the distributed development experience

45. Questions?

46. Youare the glue that holds distributed teams together

47. Don’t give up! (thank you) #Agile2010 @davidjbland