If you’ve ever had to convince a manager of the value of agile programming techniques, such as test-driven development and pair programming, you know what an uphill battle that can be. But Mike Bria at InfoQ has just posted an article titled “How TDD and Pairing Improve Production,” which takes those anti-agile attitudes to task. In response to such common criticism of pair programming as “twice as many people writing half as much code,” Bria turns to Mike Hill who identifies the key to boosting productivity as a matter of improving internal quality, citing the following three proof points:
1. “Because internal quality and external quality are not the same things.
2. “Because the biggest single determinant in today’s production is the quality of yesterday’s production.
3. “Because typing is not now and never has been the bottleneck in writing code.”
So what steps can development teams take to ensure that their internal code maintains a high level of quality? Again, Hill provides the answer with three more things to consider:
1. “Write a microtest that fails before you change any code.
2. “Adopt a “no-pair no-keep” agreement.
3. “Establish a shared understanding of internal quality.”
You can take a look at the entire article here.