Pair Programming

Who am I? @_pedro_torres | pedrogustavotorres.com Pedro Gustavo Torres

A little bit of background

What is Pair Programming? code is produced by two people programming: on one task on one workstation Two keyboards (optional) Two mice (optional) Two monitors mirroring (ideally)

Driver

navigator

Change roles multiple times a day

Change roles multiple times a day

Change roles multiple times a day

Quiz time! In which scenarios are the developers properly pairing? A B C D

Setup #1

Setup #2

Setup #3

Setup #4

All the times in front of

except in

and in!

Task BTask B Task ATask A Rotation between pairs Monday Wednesday

Pair rotation lader Source: Rachel Davies, Agile Coaching

Collective code ownership

bus factor

beginners mind

Engagement / Commitment

valuable stand-ups

better integration of new team members

limit WIP

to skip code reviews?

Less bugs

more fun

less distractions

less interruptions

less slacking

and comfort zone wise

bigger comfort zone!

Two heads think better than one

Common habits

no music / social stuff

So is Pair Programming for everyone?

It should not be imposed

Remotely works?

Are estimations affected?

What about size or length of tasks?

Is it xpn$ive?

Is it only for mature teams?

Does it scale?

Companies that use it?

Scholars and hands-on fans?

Maybe slow

or all in!

Thank you Next time Ill pair present!