Slide 1

Slide 1 text

To Pair, or not to Pair Birgitta Böckeler | @birgitta410

Slide 2

Slide 2 text

1940s: The first programmers

Slide 3

Slide 3 text

“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

Slide 4

Slide 4 text

30-40 years later https://twitter.com/MrAlanCooper/status/1060553914209071106

Slide 5

Slide 5 text

Another 10-20 years later

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

1 IT’S A LONG GAME.

Slide 9

Slide 9 text

https://martinfowler.com/bliki/PairProgrammingMisconceptions.html

Slide 10

Slide 10 text

2 ONE DOES NOT SIMPLY PAIR PROGRAM.

Slide 11

Slide 11 text

IS IT WORTH THE HASSLE? CHALLENGES BENEFITS

Slide 12

Slide 12 text

BENEFITS

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

1 + 1 > 2

Slide 15

Slide 15 text

1 + 1 > 2 Knowledge sharing Combine 2 modes of thinking: Tactical and strategic Helps you get unstuck Onboarding

Slide 16

Slide 16 text

!

Slide 17

Slide 17 text

AVOID WASTE

Slide 18

Slide 18 text

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

Slide 19

Slide 19 text

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“

Slide 20

Slide 20 text

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“

Slide 21

Slide 21 text

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“

Slide 22

Slide 22 text

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“

Slide 23

Slide 23 text

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“

Slide 24

Slide 24 text

Seen on https://devops.com/dark-side-infrastructure-code/

Slide 25

Slide 25 text

FLOW

Slide 26

Slide 26 text

FLOW Focus

Slide 27

Slide 27 text

Kathy Sierra, „Your brain on multitasking“ https://headrush.typepad.com/creating_passionate_users/2005/03/your_brain_on_m.html

Slide 28

Slide 28 text

FLOW Focus Reduced team WIP

Slide 29

Slide 29 text

Kathy Sierra, „Your brain on multitasking“ https://headrush.typepad.com/creating_passionate_users/2005/03/your_brain_on_m.html

Slide 30

Slide 30 text

TRUE CONTINUOUS INTEGRATION

Slide 31

Slide 31 text

TRUE CONTINUOUS INTEGRATION Code review “on-the-go” Collective code ownership >>Trunk-based development

Slide 32

Slide 32 text

CHALLENGES BENEFITS 1+1>2 AVOID WASTE CONT. INTEGRATION FLOW

Slide 33

Slide 33 text

ENERGY

Slide 34

Slide 34 text

ENERGY Don’t pair 8 hours a day Take breaks Switch roles and modes

Slide 35

Slide 35 text

COLLABORATION

Slide 36

Slide 36 text

COLLABORATION Feedback Exchange “READMEs” Awareness of your differences

Slide 37

Slide 37 text

IT’S PERSONAL

Slide 38

Slide 38 text

“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/

Slide 39

Slide 39 text

“you can criticise each other and find each other’s errors”

Slide 40

Slide 40 text

IS IT WORTH THE HASSLE? CHALLENGES ENERGY INTENSE COLLAB. IT’S PERSONAL … BENEFITS 1+1>2 AVOID WASTE CONT. INTEGRATION FLOW

Slide 41

Slide 41 text

Concentration Giving & Receiving Feedback Task organisation Time management Empathy Communication

Slide 42

Slide 42 text

Pia Nilsson, “Knowing Me, Knowing You - Growing teams to continuously deliver” https://www.youtube.com/watch?v=S92vVAEofes

Slide 43

Slide 43 text

Pia Nilsson, “Knowing Me, Knowing You - Growing teams to continuously deliver” https://www.youtube.com/watch?v=S92vVAEofes Diversity

Slide 44

Slide 44 text

https://hbr.org/2016/09/diverse-teams-feel-less-comfortable-and-thats-why-they-perform-better “Homogeneous teams feel easier – but easy is bad for performance” Fluency Heuristic

Slide 45

Slide 45 text

Pia Nilsson, “Knowing Me, Knowing You - Growing teams to continuously deliver” https://www.youtube.com/watch?v=S92vVAEofes

Slide 46

Slide 46 text

IT’S FUN!

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

EMBRACING CHANGE += EMBRACING FRICTION

Slide 49

Slide 49 text

To Pair, or not to Pair Do something today that your future self will thank you for. Birgitta Böckeler | @birgitta410