1 / 92

Remote Pair Programming

Remote Pair Programming. Agile 2013 Johannes Brodwall Exilesoft Chief scientist @ jhannes. Guest starring : Niruka Ruhunage. Can a distributed team still Communicate closely?. This talk is for you if you…. Want to work with remote colleagues. Want to practice pair programming (more).

wilmer
Télécharger la présentation

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 Agile 2013 Johannes Brodwall Exilesoft Chief scientist @jhannes Gueststarring: Niruka Ruhunage

  2. Can a distributed team still Communicate closely?

  3. This talk is for you if you…

  4. Want to work with remote colleagues

  5. Want to practice pair programming (more)

  6. Want to see some TDD coding

  7. Want to see some TDD coding (And you’re not scared by coding)

  8. After this talk Find a remote mentor Pair with your remote team Run a distributed workshop

  9. Why How Demonstration Discussion:Distributed agile

  10. Why global teams

  11. There are not enough devshere

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

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

  14. But

  15. Communication cost increases with distance

  16. Luckily

  17. Communication cost increases with distance

  18. Everybody knows that: Communication cost increases with distance

  19. Which would you prefer:

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

  21. 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

  22. Distribution change communication

  23. Huge email discussions

  24. Large meetings

  25. Small group discussions

  26. Structured collaboration

  27. Practical remote programming

  28. Don’t send each keystroke acrosstheworld and back

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

  30. Voice sharing Screen sharing File sharing

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

  32. Pingpong

  33. Ingredient #1: Pair programming

  34. Ingredient #2: Test driven development

  35. Failing test Write code Failing test Write code Failing test

  36. Ingredient #3: Refactoring

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

  38. Puttogether

  39. Failing test Write code Failing test Write code Failing test

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

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

  42. Demonstration

  43. What to watch for?

  44. What to watch for? Collaboration Problems and approaches

  45. Sayhello to my team!

  46. Remember: Suboptimalnetwork

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

  48. Demonstration (Guest starring Niruka Ruhunage)

More Related