1 / 59

Remote Pair Programming

Remote Pair Programming. ScanDev 2013 Johannes Brodwall Exilesoft Chief scientist @ jhannes. Guest starring: Adipa Gunesekara. Can a distributed team still be Communicating closely?. After this talk Find a remote mentor Pair with your remote team. Why How Demonstration

ferdinand-little
Download Presentation

Remote Pair Programming

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Remote Pair Programming ScanDev 2013 Johannes Brodwall Exilesoft Chief scientist @jhannes Guest starring: Adipa Gunesekara

  2. Can a distributed team still be Communicating closely?

  3. After this talk Find a remote mentor Pair with your remote team

  4. Why How Demonstration Discussion Conclusion

  5. Global teams

  6. There are not enough devs here

  7. There are not enough devs here (for most values of “here”)

  8. (There are not enough devs here) But there are more “over there”

  9. Communication cost increases with distance

  10. But

  11. Communication cost increases with distance

  12. Everybody knows that: Communication cost increases with distance

  13. Which would you prefer:

  14. Which would you prefer: Team sits onsite, but…uses headphones all dayspeak to customer monthly

  15. Which would you prefer: Team sits onsite, but…uses headphones all dayspeak to customer monthly Team 1/3 around the worldPair programs with local devsSpeak with customer daily

  16. Practical remote programming

  17. Don’t send each keystroke acrosstheworld and back

  18. We want a solution that is not super-expensive

  19. Voice sharing Screen sharing File sharing

  20. Voice sharing (Skype) Screen sharing (GoToMeeting) File sharing (Dropbox)

  21. Pingpong

  22. Ingredient#1: Pair programming

  23. Ingredient#2: Test driven development

  24. Failing test Write code Failing test Write code Failing test

  25. Ingredient#3: Refactoring

  26. Failing test Write code Refactorcode and tests Failing test Write code Refactorcode and tests Failing test

  27. Puttogether

  28. Failing test Write code Failing test Write code Failing test

  29. Failing test Write code Refactorcode and tests Failing test Write code Refactorcode and tests Failing test

  30. Failing test Write code Refactorcode and tests Failing test Write code Refactorcode and tests Failing test

  31. Demonstration

  32. What to watch for?

  33. What to watch for? Collaboration Problems and approaches

  34. Sayhello to my team!

  35. Remember: Suboptimalnetwork

  36. Please: Talk aboutwhatyousee to the person next to you (whisper) Tweet to @jhannes

  37. Demonstration (Guest starring Adipa Gunasekara)

  38. Kata: Numbernames

  39. Kata: Numbernames 1 => one 2 => two 33 => thirtythree 365 => threehundred and five … 1,230,113 => one million, twohundred and thirtythousand, onehundred and thirteen

  40. Discussion

  41. Benefits (Guest starring Adipa Gunasekara)

  42. Faster Lower error rate More productive

  43. Usage

  44. Team startup Training Job interviews

  45. Team startup Me locally with customer 3 developers in Sri Lanka First month: Daily remote pairing on rotation High bandwidth for learning tech and domain

  46. Dev extension Not tried, but I think… One Scandinavian dev can work closely with three devs offshore If you can double your productivity, the math looks profitable…

  47. Training You just saw it…

  48. Interviews Reveals real skills Motivating: fun and educational => Good PR Pre-start training

More Related