Four Cases of Pair Programming
summary
The talk examines four real paired-programming (or close-collaboration) cases: a single code owner with ten junior developers, a “tomorrow team” that keeps postponing work, whether to refactor or rewrite from scratch, and a year-long refactor period that produced no results. It describes the problems encountered (team dynamics, failed Agile practices, panic), the hands-on remediation steps used to recover and stabilize development, and how to continue product development under those conditions.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:03External expertise
- 12:52Internet banking case
- 22:00Task redistribution
- 29:23Team changes
- 36:39Leadership choice
- 42:52Q&A
related talks
23mWarm-Up Talk: Perceptions of Pair Programming
32mMaximizing the Fun Pair Programming Benefits
43mPair Programming Pragmatically
28mPair Programming as a Mechanism for Growth
48mHow to Really Work as a Team - From Sleepy to Strong Pair Programming
41mPair Programming
44mWhat We Learned in 8829 Hours of Pair Programming
22mA Pair Programming Workshop