You're view of XP has to be flexible though. For instance we could never do pairs programming because there are only 3 of us... hard to justify in that case.. but you can still follow the other principles of XP (such as work environment, interaction, and delivery schedule).
The first thing to write in a method body is something to make your test FAIL! ;)
Chris - I agree. That's why ASSERTs and Exception throwers are the first thing:)
Ray: I agree. Pair programming is better suited to somewhat bigger teams. But I'm a supporter of even partial implementations, so PP would not have to be THE thing to keep, although it's a great technique for bug proofing and speed coding.