My preferred method for training right now is "promiscuous pairing" http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CB8QFjAA&url=http%3A%2F%

My preferred method for training right now is "promiscuous pairing" http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CB8QFjAA&url=http%3A%2F%2Fcsis.pace.edu%2F~grossman%2Fdcs%2FXR4-PromiscuousPairing.pdf&ei=5uVpUIPRLNO20AGBwIEw&usg=AFQjCNH3bCoqR03ePnhYF2ij9EbYvxvH_w&sig2=394LR-w21i90PaDqRDGPpA&cad=rja http://www.google.com/url?sa=t&rct=j&q=&esrc=s&#... As for hardware setup, the best I have used is: machines with cloned monitors, two mice, and two keyboards, both side by side so the developers can talk in low tones and not bother anyone else. I do this now at work, and it is a lot of fun, and it really averages to be that we get done more than twice what we would work normally alone.