To pair, or not to pair

To pair, or not to pair

A talk about pair programming, an agile development practice that still has only relatively patchy adoption across the industry. I talked about a few of the top benefits, then highlighted the challenges, and talked about why I believe those challenges are worth the hassle.

Presented at ThoughtWorks events in Munich and Hamburg, November 2018

645147e9899005bc24e5ff7d65a1d60c?s=128

Birgitta Boeckeler

November 27, 2018
Tweet

Transcript

  1. 3.

    “Betty Snyder and I, from the beginning, were a pair.

    And I believe that the best programs and designs are done by pairs, because you can criticise each other, and find each other’s errors, and use the best ideas.” Jean Bartik http://www.computerhistory.org/revolution/birth-of-the-computer/4/78/2258 1940s: The first programmers
  2. 6.
  3. 7.
  4. 12.
  5. 13.
  6. 14.
  7. 15.

    1 + 1 > 2 Knowledge sharing Combine 2 modes

    of thinking: Tactical and strategic Helps you get unstuck Onboarding
  8. 16.

    !

  9. 18.

    „THE 7 WASTES OF SOFTWARE DEVELOPMENT“ Mary & Tom Poppendieck:

    „Implementing Lean Software Development: From Concept to Cash“
  10. 19.

    Partially Done Work Extra Features Relearning Handoffs Delays Task Switching

    Defects „THE 7 WASTES OF SOFTWARE DEVELOPMENT“ * Mary & Tom Poppendieck: „Implementing Lean Software Development: From Concept to Cash“
  11. 20.

    Partially Done Work Extra Features Relearning Handoffs Delays Task Switching

    Defects „THE 7 WASTES OF SOFTWARE DEVELOPMENT“ * Mary & Tom Poppendieck: „Implementing Lean Software Development: From Concept to Cash“
  12. 21.

    Partially Done Work Extra Features Relearning Handoffs Delays Task Switching

    Defects „THE 7 WASTES OF SOFTWARE DEVELOPMENT“ Mary & Tom Poppendieck: „Implementing Lean Software Development: From Concept to Cash“
  13. 22.

    Partially Done Work Extra Features Relearning Handoffs Delays Task Switching

    Defects „THE 7 WASTES OF SOFTWARE DEVELOPMENT“ * Mary & Tom Poppendieck: „Implementing Lean Software Development: From Concept to Cash“
  14. 23.

    1 handoff 2 handoffs 3 handoffs 4 handoffs 5 handoffs

    Knowledge lost in handoffs Mary & Tom Poppendieck: „Implementing Lean Software Development: From Concept to Cash“
  15. 25.
  16. 33.
  17. 38.

    “To pair requires vulnerability. It means sharing all that you

    know and all that you don’t know. This is hard for us.” Tom Howlett, “The Shame of Pair Programming” https://diaryofascrummaster.wordpress.com/2013/09/30/the-shame-of-pair-programming/
  18. 40.

    IS IT WORTH THE HASSLE? CHALLENGES ENERGY INTENSE COLLAB. IT’S

    PERSONAL … BENEFITS 1+1>2 AVOID WASTE CONT. INTEGRATION FLOW
  19. 42.

    Pia Nilsson, “Knowing Me, Knowing You - Growing teams to

    continuously deliver” https://www.youtube.com/watch?v=S92vVAEofes
  20. 43.

    Pia Nilsson, “Knowing Me, Knowing You - Growing teams to

    continuously deliver” https://www.youtube.com/watch?v=S92vVAEofes Diversity
  21. 45.

    Pia Nilsson, “Knowing Me, Knowing You - Growing teams to

    continuously deliver” https://www.youtube.com/watch?v=S92vVAEofes
  22. 47.
  23. 49.

    To Pair, or not to Pair Do something today that

    your future self will thank you for. Birgitta Böckeler | @birgitta410