The use of programming partners is a concept that I have been using for several semesters in order to help students help themselves become more proficient in the programming process. Teams are an integral part of the IS process. In order to model the team concept in a programming environment every student in the class will be paired with another student.
After a certain point in the semester, I will select a programming partner for each student. You will be paired with this partner for two programs. For every program you will designate one partner as the primary programmer, and the other as the secondary programmer. While you should divide the work and alternate on the primary programmer and secondary programmer, each partner should contribute to the solution and coding of EVERY program. While both partners are equally responsible for every program, the secondary programmer is personally responsible for thoroughly documenting the program. The primary and secondary programmers should alternate with each program. This will hopefully insure that both partners will learn equally from each program and take equal responsibility. The partner approach is designed to reduce your burden, but it is still a team effort and you are expected to contribute your fair share.
A programming team will turn in a single program for both
partners. Clearly indicate the primary and secondary programmer.
If a partner slacks off on a program DO NOT list them as a primary programmer (even if it
is their turn!) and if they don't comment the code they shouldn't even be listed as a
secondary programmer.