3. What is Pairing?
● 2 Brains, 1 Task
● Real-time code review
● Collective ownership
4. Pairing Guidelines
● Take turns
○ Driver and Navigator roles
● Mindset
○ Be open to alternatives
○ Keep each other focused
○ short experiments are ok
6. Build a Robot...ANY Robot
● Use the K’nex
● Pick a pair
● Decide who is the driver and navigator
7. Driver
● Concentrate on assembly
● Follow Navigator's lead
● Think about
implementation
Navigator
●
●
●
●
Think what to build
Describe design
Help selecting parts
Think about the bigger
picture
10. Remember...
Driver
● Concentrate on assembly
● Follow Navigator's lead
● Think about
implementation
Navigator
●
●
●
●
Think what to build
Describe design
Help selecting parts
Think about the bigger
picture
11. Swap Pairs!
Drivers
Navigators
● Stay put
● Move to the right
● You are now navigating ● You are now
● Explain the concept
driving
● Listen to the
concept
13. Driver
● Concentrate on assembly
● Follow Navigator's lead
● Think about
implementation
Navigator
●
●
●
●
Think what to build
Describe design
Help selecting parts
Think about the bigger
picture
14. Swap Pairs!
Drivers
Navigators
● Move to the right
● Move to the left
● You are now navigating ● You are now
● Explain the concept
driving
● Listen to the
concept
16. Driver
● Concentrate on assembly
● Follow Navigator's lead
● Think about
implementation
Navigator
●
●
●
●
Think what to build
Describe design
Help selecting parts
Think about the bigger
picture
17. What did you think?
Well
●
●
●
●
●
●
●
●
●
●
Creativity introduced
learned new techniques
showed up knowing how to do things
Enjoyed watching others with robot
When confronted with all new, liked having
a pair to hash things out
Less fear of the unknown
Experimented more
Shared responsibility
Context switching makes you think
Learning from pair
Less Well
●
●
●
●
●
Too much guessing with new context
(sometimes)
Pair is not productive when both are newbies
Need some context to remain to keep
requirements clear
Documentation needed if context is not
preserved (stories, docs, requirements)
Pair may have separate, but applicable role
22. Objections? Skeptical?
●
●
●
●
●
Does pairing halve productivity?
Should pairs be of similar skill levels?
Are pairs forever?
Pairing fatigue/impatience?
How to transfer knowledge within the team?
23. Objections? Skeptical?
●
●
●
●
●
●
Does pairing halve productivity?
Should pairs be of similar skill levels?
Are pairs forever?
Pairing fatigue/impatience?
How to transfer knowledge within the team?
“I work better alone. Do I pair all the time?”
24. Objections? Skeptical?
●
●
●
●
●
●
●
Does pairing halve productivity?
Should pairs be of similar skill levels?
Are pairs forever?
Pairing fatigue/impatience?
How to transfer knowledge within the team?
“I work better alone. Do I pair all the time?”
Pairing Stations?
25. Pairing in your Organization
● Share this experience with peers or team
members
○ talks, short pairing sessions, discussions
● Just Ask to Pair: “Hey, I need help with X”
● Start small - it doesn’t need to be a
Movement
26.
27.
28. Pairing Studies
● Laurie Williams “Pair Programming Illuminated”
http://collaboration.csc.ncsu.edu/laurie/pair.html
●
http://collaboration.csc.ncsu.edu/laurie/Papers/ESE%20WilliamsPairProgramming_V2.pdf
●
Introduction to Pair Programming
http://www.youtube.com/watch?v=A6kdFdJp4jY
● Pairing in other disciplines
○ Pair Researching
http://groups.csail.mit.edu/uid/other-pubs/cscw14-pair-research.pdf