Welcome to RandyLoops! SourceForge Logo

Main

Group Members

Documentation

Files

Wiki Page

Meeting Notes

How We Follow The XP Process

Pair Programming

We have divided our system into two major subsystems:
1. GUI- with three programmers
2. Back-end- with five programmers

The back-end is further subdivided into two components:
1. Loop class- with three programmers
2. Output class- with two programmers

The implementing of pair-programming was structured into four pairs:
1. The two members of the Output class formed a pair
2. Two of the three members of the Loop class formed a pair
3. Two of the three members of the GUI formed a pair
4. One member from the loop class and one from the GUI formed a pair as to help facilitate the interfacing of the two components

As we began the pair-programming process we distributed group members initiallly in the following way:

Loop Class
1. David Carlisle- pair 1
2. Keith Herring- pair 1
3. Michael Song- pair 2

Ouput Class
1. Matt Keelan- pair 3
2. Pat Richey- pair 3

GUI
1. Mai Ton- pair 2
2. Barbara Okupna- pair 4
3. Paul Tongyoo- pair 4

Also Phil Wenstrand has acted as our Project Manager and On-Site Customer, a position that he has held througout the duration of the project.

In order to increase communication and understanding between the indivduals working on each component of the project we rotated pairings and responsibilies from the initial setup. The idea in the rotation was to keep one original member on each task while pairing she/he up with an individual that had been working on another facet of the project. Below are the assignments during the second pairing:

Second Pairing:

Loop Class
1. David Carlisle- pair 1
2. Keith Herring- pair 1
3. Paul Tongyoo- pair 2

Ouput Class
1. Michael Song- pair 3
2. Pat Richey- pair 3

GUI
1. Matt Keelan- pair 2
2. Barbara Okupna- pair 4
3. Mai Ton- pair 4

It was found that the rotation was helpful in that it did aid in stronger feedback between project components. It was a hinderance for individuals to have to adjust from one subsystem to another, however keeping one experienced member on each task did help to make this transition easier and more efficient. Overall the pair programming setup has worked well and has contributed to strong project cohesion.

All of our code was developed in small releases. If you go check the CVS changelogs, you can see all the small releases of our code, as XP calls for.