Embed Size (px)
Citation preview
promiscuous
ankur sambhar | [email protected]
pairingmore the merrier!
Disclaimer: The views presented in this presentation are in the speaker’s individual capacity and J.P. Morgan Services India Private Limited does not endorse the same in any way.
Agile India 2015
who we are?
you practicepair programming?
why we moved topromiscuous pairing?
Promiscuous Pairing and Beginner’s Mind: Embrace Inexperience
-Arlo Belshee
http://user.it.uu.se/~carle/softcraft/notes/PromiscuousPairing.pdf
what ispromiscuous
pairing?
switching pairs very
frequently
pair split
Task A
Task B
Task C
Pair Switch
pair split
Task A Task B
Pair Switch
optimize learning andspread of knowledge
preventing state of flow
what is “beginner’s mind”?
state of few limits
transitory state thatdepends on instability
to maintain it as astable state?
change thingsaround frequently
what worked for us?
fine granular tasks
each < 3 hrs
tasks pulled bywhom?
most pair?
least pair?
random pair?
mix pair?
mix pairmost + least qualified
pair splitting period
every 30 mins?
every 120 mins?
every 60 mins?
sixty mins
pair rotation
twelve mins?
five mins?
thirty mins?
twelve mins
code check-in
every 12 mins
challenges we faced
team compositionjunior – master developers
who is least qualified?
not switching pair atlogical point
ramp-up period after pair switch
compromising expertise
no-one owns task
odd number ofteam members
finding optimumpair switching frequency
30 mins?
60 mins?
120 mins?
how frequentlyrotate roles?
10 mins?
25 mins?
60 mins?
what have we achievedwith it?
quick knowledge sharingacross team
on each task
better quality deliverables
no local optimization
improved throughput of team
shorter ramp-up time fornew hires
better design of deliverables
improved skill set of team members
team maturing to betechnology agnostic
less spillovers
boosted morale of each individual
promiscuous!
keep pairing…
it pays to be
as they say
questions& answers?
backup
