Pair Programming :: Agile Portugal 2014
•Download as PPTX, PDF•
5 likes•2,155 views
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to Pair Programming :: Agile Portugal 2014
Similar to Pair Programming :: Agile Portugal 2014 (20)
More from Pedro Gustavo Torres
More from Pedro Gustavo Torres (20)
Recently uploaded
Recently uploaded (20)
Pair Programming :: Agile Portugal 2014
- 2. Who am I? @_pedro_torres | pedrogustavotorres.com Pedro Gustavo Torres
- 5. A little bit of background
- 6. What is Pair Programming? • code is produced by two people programming: – on one task – on one workstation • Two keyboards (optional) • Two mice (optional) • Two monitors mirroring (ideally)
- 7. Driver…
- 8. …navigator
- 9. Change roles multiple times a day
- 10. Change roles multiple times a day
- 11. Change roles multiple times a day
- 12. ¡Quiz time! In which scenarios are the developers properly pairing? A B C D
- 14. Setup #1
- 15. Setup #2
- 16. Setup #3
- 17. Setup #4
- 19. All the times in front of…
- 20. …except in…
- 21. …and in!
- 23. Task BTask B Task ATask A Rotation between pairs Monday Wednesday
- 24. Pair rotation lader Source: Rachel Davies, Agile Coaching
- 27. …bus factor…
- 28. …beginners mind
- 32. …better integration of new team members…
- 33. …limit WIP…
- 34. … to skip code reviews?
- 36. Less bugs…
- 37. …more fun…
- 40. …less slacking…
- 41. …and comfort zone wise…
- 43. Two heads think better than one
- 45. “Common” habits…
- 46. …no music / social “stuff”
- 47. So is Pair Programming for everyone?
- 48. It should not be imposed
- 50. Remotely works?
- 52. What about size or length of tasks?
- 53. Is it €xp£n$ive?
- 54. Is it only for mature teams?
- 55. Does it scale?
- 56. Companies that use it?
- 57. Scholars and hands-on fans?
- 59. Maybe slow…
- 60. …or all in!
- 61. Thank you Next time I’ll pair present!
Editor's Notes
- NCIS 2 IDIOTS 1 KEYBOARD video
- eXtreme Programming (XP) Software development methodology
- code is produced by two people programming: on one task on one workstation Two keyboards (optional) Two mice (optional) Two monitors mirroring (ideally)
- How should the driver and navigator seat? Which hardware should they have to pair programme effectively?
- All the times: In front of a working station Except in: meetings (finishing each other sentences) Bathroom (taking a leak)
- Engagement / Commitment Valuable Stand ups Better integration of new team members
- Should I stay or should I go? It really depends how obsessed you are with reviews…but I would say no. One of the members of the pair is already reviewing With proper rotation everybody gets a chance to review the code
- Less bugs More fun Less distractions Less interruptions from “outsiders” (changed from stopping one dev to stopping two) Less slacking on important stuff (testing, coding properly, adding comments, etc...)
- Because you are pairing: you have better ideas stay in the zone for longer More courage to take “risky”/”unconfortable” tasks Opportunity to learn and to teach
- [Image] Dude coding and listening to music [Image] Dude coding on workstation and having facebook on the laptop
- No music (at least headphones) No youtube No facebook No twitter No instagram No tumblr … Basically No social crap (your manager is going to love this part)
- * Nop! * You must: Be willing to give it a try Be social Be confident Embrace/deal with partners feedback Manage conflict Accept differences (not everything will be like you want) * It’s quite exausting It’s not rainbows and unicorns You will have a learning curve ahead
- BUT... It should be highly recommended! (Story at sky where the team stick to pp because of not wanting to do code review.)
- The non believers think so: Twice the salary / cost? Half the speed? So what about: Bugs? Technical debt? Bus factor? Team spirit? Morale? WIP limit? It wont be expensive on the mid/long term
- BSkyB 2degrees network NotOnTheHighStreet.com Virgin Media Orange O2 eBay Hashrocket Pivotal Labs Facebook Square Twitter Groupon SaludOnNet Feelunique.com CustoJusto.pt
- * Couple of days a week * Just one team * Just one pair (in a team) …