Odd Teams

Any team I am a member of is bound to be a little odd....

OddTeams is a practice used to deal with the situation where you have an odd number of developers who are trying to pair program. The basic practice is as follows:

  1. Give each pair station an identifier, preferrably a number
  2. Pair up on the stations to the extent possible. I recommend letting a stronger developer take the helm as the loner to start.
  3. Set a timer for a reasonably short duration. We have found 20 minutes to be a comfortable clip.
  4. Hack away
  5. When the timer goes off, switch. Follow rules of:
    • drivers stay at their stations and become navigators
    • navigators move to the next station and become drivers
    • alternate between moving to the left and moving to the right (see below)

For three people, two stations it looks like (parens represent a pair at a station):

For five people, three stations, it looks like: It continues to scale in this manner. Notice that the outer pairs get increased focus from individuals -- i.e. one full hour of attention at a station, while the inner pairs get more pair focus.

Cons:

Pros: Feedback appreciated -- JefNewsom


What we do here is, just avoid odd number of devs. (Disclaimer: we're not extreme yet, still ad[ao]pting.)

So if the team ends up having odd devs, we split the pairs at the stand-up meeting as usual. The person who gets to be pairless at any given time:


See PairProgrammingTrainingWithBlitzClock PairPromiscuously


EditText of this page (last edited April 7, 2005) or FindPage with title or text search