|
To setup an XP team you must work not only with very skilled but open-minded people: pair programming can be a problem if you don't feel comfortable with your desk-mates. Many XP evangelists suggest what seems a religious approach to test-driven programming, but tests are code, and someone have to maintain it! Moreover, testing is most useful in algorithmic-oriented pieces of code. What I find to be indispensable is evolutionary design by refactoring, always trying to apply the DRY principle (Don't Repeat Yourself). Then I write tests for the most critical sections, this way I feel confident while I'm changing. XP still requires a lot of craftsmanship and expertise, but it often works better than many other methodologies. |