Pairing
Upcoming SlideShare
Loading in...5
×
 

Pairing

on

  • 198 views

Co-hosted a pairing workshop at Agile Practitioners Meetup at SF.

Co-hosted a pairing workshop at Agile Practitioners Meetup at SF.

http://www.meetup.com/Agile-Practitioners-Meetup/events/149251292/

Statistics

Views

Total Views
198
Views on SlideShare
197
Embed Views
1

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 1

http://www.linkedin.com 1

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Pairing Pairing Presentation Transcript

  • Pairing
  • Agenda ● ● ● ● Introduction to Pairing Workshop Activity (Game!) Retrospective Discussions Summary
  • What is Pairing? ● 2 Brains, 1 Task ● Real-time code review ● Collective ownership
  • Pairing Guidelines ● Take turns ○ Driver and Navigator roles ● Mindset ○ Be open to alternatives ○ Keep each other focused ○ short experiments are ok
  • LET’S PLAY
  • Build a Robot...ANY Robot ● Use the K’nex ● Pick a pair ● Decide who is the driver and navigator
  • 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
  • Build A Robot...ANY Robot
  • 시작! (go)
  • 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
  • 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
  • 行く! (go)
  • 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
  • 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
  • давай! (go)
  • 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
  • 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
  • Objections? Skeptical? ● Does pairing halve productivity?
  • Objections? Skeptical? ● Does pairing halve productivity? ● Should pairs be of similar skill levels?
  • Objections? Skeptical? ● Does pairing halve productivity? ● Should pairs be of similar skill levels? ● Are pairs forever?
  • Objections? Skeptical? ● ● ● ● Does pairing halve productivity? Should pairs be of similar skill levels? Are pairs forever? Pairing fatigue/impatience?
  • 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?
  • 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?”
  • 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?
  • 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
  • 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
  • Additional Resources Overcoming management resistance to pairing (http://www.pearsonhighered.com/samplechapter/0201745763. pdf)
  • Thanks! Zeljko Pavic, Vlad Zelmanov, Eric Mrak, Bonna Choi