Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

6.
One of the quotes that I used to flash around
people was "if you're doing Extreme
Programming the same way as you were
doing it a year ago, you're no longer doing
Extreme Programming". Because if you don't
take charge and you don't alter things to fit
your circumstance, then you are missing the
key part of it.
- Martin Fowler
https://martinfowler.com/articles/agile-aus-2018.html

8.
“The thing I found most interesting is that this project should have
failed. A HUGE incredibly complicated body of enterprise software
with near-100% team turnover? I would have bet against it ever
working.
But all that pair programming and rotation and writing stories and
backfilling tests etc just eventually ground the problem down.
It was expensive as hell and it took years but it looks like a success story
now.
I don't know of any other big takeover project like this that worked.”
- Hacker News comments on Pivotal’s ~ 5B IPO
https://news.ycombinator.com/item?id=16664024

9.
“Most of the over 100 companies Pivotal works
with every year come to them because they
think they just need more development
support to ship faster or manage their growth.
But more often than not, Hieatt believes the
problem is actually related to the broader issue
of development culture…”
- Edward Hieatt

28.
• Plan
- What are we working on today? What do we plan to achieve?
- Syncronize breaks - pomodoro or otherwise, but opposite-sync is silly
• Respect
- Pairing is a democratic process, not a competition where another individual is made to feel inferior
- Type at a reasonable speed lah!
• Take Notes!
- When your pair is coding, take notes on things you think will need attention later. Do not interrupt or
flag issues immediately – breaking their flow. Once your pair is done with the typing, discuss
• Vocalize / Communicate
- What was just done, what is being done, and what is going to be done next.
- Pre-empt and analyze expected test results.
• Team Leads: Check in, evaluate, rotate
- Not always easy, but team leads need to work on how to do it
KMK’s pairing rules:

33.
how to fail!
• Forcing people to pair
They will sandbag the project
• Totally flexible hours
• Taking on too many changes
at the same time: Scrum,
TDD, DevOps...
• Not adquate seating /
infrastructure

39.
Pomodoro Technique
• Decide on the task to be done
• Set the pomodoro timer to n
minutes (traditionally 25)
• Work on the task until the
timer rings
• Take a short break (3–5
minutes)
• After four pomodori, take a
longer break (15–30 minutes)