Tips for teamwork
It is probably best if you choose your team members from the same
practical that you are attending.
During your first meeting you should
Exchange email addresses
Decide on a time to meet (e.g., you could decide to spent 10-20 minutes
of each practical on team matters).
Assign a team leader for each week. The team leader is in charge
of arranging your meeting and coordinating your work during that week.
There are different ways in which you can distribute your work among team
You can divide the work into separate components. One day
before your meeting, each of you emails what they have done so far
to the others. At the meeting you then comment on each other's work.
Every student is involved in testing the components.
Or you could work on components in parallel. At each meeting
you exchange your code and select the version which you like best.
Some student other than the one who wrote it, would then modify, test,
and debug a component. To avoid using only a single student's code,
a different student's version should be selected for each component.
Or you actually meet and write the code as a team. (This is probably
the most time consuming method, but it could be used for smaller components
or your coursework.)
Whatever method you choose, you should ensure that every student is
involved in the coding process as much as possible. It is a good
idea to have a piece of code that is written by one student, tested, modified
and debugged by the other students, so that all students are familiar
Problems within a team
You should choose your team members carefully. If for some reason, you
discover that you do not get along with your team members or someone
in your team seems to have disappeared and does not answer his/her email,
please, notify the module leader as soon as possible.