When you have a small XP team, you have a couple of choices with respect to coaching:
Having not been at it for as long as RonJeffries and KentBeck its hard to say what all the potential drawbacks of this are, but so far, so good. -- KenAuer
We had some experience with this on the VcapsProject. What we had was one person who knew XP fairly well, several experienced people who had tried various other name brand methodologies, and a couple of hack and slash programmers. At the beginning the person who knew XP would suggest we solve problems using pieces of XP and explain how XP works. Sometimes we would try those ideas out right away, sometimes we would wait. It didn't take very long before everyone comprehended how it would work and was contributing equally. We found that by re-discovering XP together, step by step, everyone felt a much stronger sense of responsibility and empowerment. The team became self coaching (group coaching) and was able to keep going even through the high-pressure times because we were all responsible for the process. None of it had been handed to us easily. We had to convince upper management and even some of our fellow developers to try new things. When trouble came we supported and encouraged each other to keep following our new methodology and see it through, no matter how tight things got. --DonWells
Don, I want to highlight something you said. by re-discovering XP together, step by step, everyone felt a much stronger sense of responsibility and empowerment. I am finding this a common theme for methodology adoption, have heard several teams speak it in about the same words. I'm trying to see how to say this formally and strongly and apply it widespread - the concept is turning out to be key. cheers - AlistairCockburn