• Save
Everything you wanted  to know about PairProgramming but were afraid to ask
Upcoming SlideShare
Loading in...5
×
 

Everything you wanted to know about PairProgramming but were afraid to ask

on

  • 11,218 views

(Previously called PairProgramming is like sex) ...

(Previously called PairProgramming is like sex)
I created this presentation to explain to IT students what is PairProgramming. The second part of my talk they had to PairProgram themselves.
(Hence the title: nobody can explain sex in a book or presentation, you have to do it, to know what it does to you.)

Statistics

Views

Total Views
11,218
Views on SlideShare
6,158
Embed Views
5,060

Actions

Likes
16
Downloads
1
Comments
10

9 Embeds 5,060

http://www.hanoulle.be 4961
http://paircoaching.wordpress.com 58
http://www.slideshare.net 19
http://paper.li 8
http://translate.googleusercontent.com 7
http://www.lmodules.com 3
http://webcache.googleusercontent.com 2
http://www.netvibes.com 1
http://twitter.com 1
More...

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

15 of 10 Post a comment

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • On November 17 (2011) I am giving a workshop where this presentation is part of http://www.ilean.be/course/pp201111
    Are you sure you want to
    Your message goes here
    Processing…
  • @Yves: I see. I usually argue that TDD is and should be development. You could drive design from BDD which could be less fine grained than TDD (as in working at a higher level of abstraction).
    I also argue that the tests that one writes stems from some sort of requirement, constraint or expectation on the software. Design is one kind of constraint and therefore I don't see that tests can (or should) drive design. But this all comes down to what you put into the word 'design'.
    I'm not saying that you're wrong - these are the questions or arguments I usually put forward to get a discussion going in order to better understand what the other person actually means with TDDesign. :)
    Are you sure you want to
    Your message goes here
    Processing…
  • @Adolfo that is one of the reasons. There are more, like 'you can't learn it from a book.' what else?
    Are you sure you want to
    Your message goes here
    Processing…
  • @Frederik: originally TDD was called Test Driven Development. These days a lot of people (including me) say that TDD works because it is more a design technique then a development technique.
    That is why I call it Test Driven Design. Although you can do PP without TDD and viceversa, the two techniques support eachother. That is why usually when I talk about ne, I add a small part about the other, for if I have time to space.
    Are you sure you want to
    Your message goes here
    Processing…
  • Well, PairProgramming is typically associated with TDD (as in Development, not Design). My assumption might've been wrong.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Write this down during 1 minute then share this with your neighbour
  • If during the course, you have questions, please write them on a post it.
  • Two guys working on the same taskBoth have the same target
  • One person executes, the other watches and gives directions
  • Two site or two people working as one team
  • "yep, dat is de drill. In de eerste plaats een veiligheidsmaatregel. Als je verongelukt, of er is een probleem met je persluchttoestel is er direct iemand op de hoogte. Ook handiger om aan de slang te sleuren of te overleggen."
  • The junior developer slows down the senior?The speed of your team is not about the fastests developer, it is about the slowest developerIf you speed up the slowest developer, you speed up the teamUse the
  • The junior developer slows down the senior?The speed of your team is not about the fastests developer, it is about the slowest developerIf you speed up the slowest developer, you speed up the teamUse the
  • Pairing experiment at University of Utah
  • How many people can YOU afford to loose
  • Write this down during 1 minute then share this with your neighbour

Everything you wanted  to know about PairProgramming but were afraid to ask Everything you wanted to know about PairProgramming but were afraid to ask Presentation Transcript

  • www.PairCoaching.net Everything YOU wanted to know about PairProgramming but were afraid to ask... Yves Hanoulle PairCoaching.net
  • What is the succesfull outcome of this talk?
  • It’s a Topless talk...
  • Questions by Post-it 4
  • Aha Wall
  • Referee cards 6
  • You.About()  Who is a programmer?  Who is a manager?  Who has done PairProgramming?  Who likes pairing?
  • The goal is to enlarge your toolbox
  • PairProgramming what is it? What is this Russian thinking ?
  • Driver - Navigator
  • Experience
  • one team
  • Pair Programming
  • Isn’t it waste?
  • Why would two people do the job of one? I
  • Why would two people do the job of one? II
  • Why would two people do the job of one? III
  • Why would two people do the job of one? IV
  • Why would two people do the job of one? V
  • Why would two people do the job of one? VI
  • Why would two people do the job of one? VIII
  • Why would two people do the job of one? IX
  • Why would two people do the job of one? X
  • Why would two people do the job of one? XI
  • This is why two people do the job of one !!!
  • Won’t a junior developer slow down senior developer?
  • It’s about the speed of the team!
  • The power of the junior
  • The EGO of the senior
  • My cost will double I
  • My Costs will double II
  • My cost will double III “IBM reported spending about $250 million repairing and reinstalling fixes to 30,000 customer-reported problems. That is over $8,000 for each defect!” -“A Discipline for Software Engineering”, 1995, Humphrey, W.S.
  • Less distraction...
  • It’s Fun...
  • Let’s talk about the resistance
  • Small work area
  • Strong Code Ownership
  • Inconsistent workstation setup
  • People don’t care
  • Everyone settles into their own “Comfort Zone” over time
  • Hard and dangerous tasks
  • Boring tasks
  • New Team Member
  • New Framework
  • New Language
  • Need more experts
  • Have a higher Truck Number...
  • Knowledge Sharing Tacit knowledge Explicit Knowledge
  • Just Do IT
  • PingPong Programming
  • Keyboard and Mice Pairing
  • Pairing Station I
  • Pairing Station II  Promiscue pairing
  • Pairing Rotation
  • Distributed PairProgramming
  • Promiscue pairing
  • Side-By-Side programming
  • Screen Pairing
  • Pomodoro Technique
  • Ask for help
  • Rescue
  • Pairing Smells
  • Distracted Pair
  • No pair rotation
  • Manager decides the pair
  • Nobody talks about the elephant
  • Selective Pairing
  • Some people can’t do it
  • Some people can’t do it... III
  • Discussions are needed for GREAT results
  • Productivity Alone
  • Productivity Together
  • What is the succesfull outcome of this talk?
  • Pictures  Naresh Jain: http://www.slideshare.net/nashjain/pair-programming  Jurgen Appelo: http://www.noop.nl/2011/04/the-feedback-door.html  Vera Peeters personal collection  Dilbert : http://www.dilbert.com/  British Monarchy http://www.flickr.com/photos/britishmonarchy/  Jan Tielens: http://www.flickr.com/photos/JanTielens  Picture Bill Gates: http://www.labnol.org/internet/favorites/13-year-old-bill-gates- with-paul-allen/330/  One-Agency: http://www.one-agency.be/jobs  Pomodoro: http://www.pomodorotechnique.com/  Drupal Image: http://www.zabisco.com/  B Marick & C Haines: http://www.exampler.com/blog/2008/12/10/screen-pairing/  Yves Hanoulle & Els Ryssen http://www.flickr.com/photos/yveshanoulle/  Lots of picture already years on my drive. If you recognise one, please tell me and I add credentials.
  • Url’s  http://www.slideshare.net/nashjain/pair-programming  http://nat.truemesh.com/stairmaster.html#  http://www.mitchlacey.com/docs/XR4PromiscuousPairingandBeginnersMind.pdf  http://collaboration.csc.ncsu.edu/laurie/Papers/Kindergarten.PDF  http://www.britannica.com/bps/additionalcontent/18/34706583/Pair-Programming-as-a-Modern- Method-of-Teaching-Computer-Science  http://www.pomodorotechnique.com/  The Core Protocols http://alturl.com/b9fn  The Costs and Benefits of Pair Programming (Laurie Williams & Alistair Cockburn)  Strengthening the Case for Pair-Programming (- Laurie Williams, Robert R. Kessler, Ward Cunningham & Ron Jeffries)  On the Economic Feasibility of Pair Programming (Hakan Erdogmus & Laurie Williams )  http://www.netobjectives.com/ap/download/pairing.pdf  http://salfreudenberg.wordpress.com/2013/06/08/pair-programming-and-expertise/  http://salfreudenberg.wordpress.com/2013/06/15/pair-programming-uptake-and-peripheral- awareness/  http://altabel.wordpress.com/2013/05/24/pair-programming-pluses-and-minuses-bonuses-and- anti-patterns/
  • History  Version 4: Created for a mini conference for students  Version 8: adapted for internal PairProgramming training  Version 11: Uploaded a new version to be used for public training  Version 15: Added extra material  Version 20: renamed the presentation + removed content
  • I give Free Lifetime support on everything I do  Blog, slides, books, pictures : http://www.hanoulle.be  Social Media @YvesHanoulle  Linkedin: http://www.linkedin.com/in/YvesHanoulle  Mobile: +32 476 43 38 32  Skype: YvesHanoulle  Free life time:  My life not yours
  • Me.About() Creative Collaboration Agent in EMEA. Partner of Els Ryssen Father of Joppe 2002, Bent 2004, Geike 2007 @YvesHanoulle
  • PairCoaching.net the way to leading greatness Thank you !!