Moving Fast with XP
summary
Claims that TDD, pairing and continuous deployment are slow get refuted with concrete practices: teams pair on all production code using one machine with two keyboards, rotate pairs to spread knowledge, estimate as a team assuming a pair, and use pull requests merged same day sized to a day of work. Pairing produces fewer post-release bugs, faster ramp-up on a codebase, resists distractions, and keeps delivery sustainable rather than a short burst of speed.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:39Extreme Programming
- 3:37Code Reviews
- 8:11Resistant to Personal Distraction
- 13:29Pair on all Production Code
- 14:13Estimating the Effort








