Example 3: Lack of Pair Programming

I was asked to help a client figure out why they weren’t doing XP practices such as pair programming and test-driven development. “We know that we should be doing it, but we aren’t,” the client said.


So is lack of test-driven development (TDD) and pair programming really a problem? As usual, the things we call problems often turn out to be just symptoms.


What is the consequence of not doing pair programming and TDD?


We think we’d have much better code quality if we did these things.


What is the consequence of bad code quality? Have you encountered any actual problems due to bad code quality? ...

Get Lean from the Trenches now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.