My advice: While I find TDD is not a good practise for all day problems, it has its good parts for educational purposes. Pair programming is one of them.<p>1. Start with planning a coding dojo (about 2-3 hours), invite the whole team<p>2. Start a small theory session (15 minutes) about TDD and Pair-Programming essentials when starting the dojo (someone of you has to research, build knowledge and prepare beforehand)<p>3. Select one pair - the others are watching (in your case 1 other person)<p>4. Start the TDD cycle with your challenge (e.g. fizzbuzz) - Write a failing test, switch driver, fix the test, refactor, write next failing test, switch driver, repeat<p>5. Urge yourself and your partner to communicate (talk about what your doing atm), focus on the method not the problem and remember to stay in the roles (driver writes code, navigator manages tasks / todos)<p>6. After 15 minutes Change pairs to devs, who haven't been practising yet<p>7. Repeat until your dojo time is over<p>This way you can educate yourself without focusing on your current work problems, but having fun focusing on the TDD and pair programming part. Knowledge transfer is also guaranteed, because the ones that don't pair-program will at least look at what the others are doing.<p>After you've built some knowledge (after around 2 or 3 dojos), try to do 1h pair programming sessions (no longer - without the need of TDD) in your all-day work. Set a clock timer to around 10 minutes, so you don't forget to switch driver and navigator.<p>I would not start with sessions > 1h, because pair programming can be pretty exhausting when you start.<p>Have fun :-)