In CS2110, we work in groups to complete programming assignments that take up more than they should. Because one person submits the file, the entire project for the most part is completed with one computer through a single display. However, there are points where the project “morphs” from being a single-display to a hybrid configuration.
Because there is only one submission per group, one person types out the code while the others contribute ideas. Usually, the two other people will be handling and reminder the typists of how the structure of the code and what steps should have been taken or what steps are missing. For this part, our “communication was mainly verbal, but also included body language [] and gestures” (Cost, et al). However, this sometimes becomes a problem the people implementing the code cannot work as fast as the ones giving out the steps/ideas. Often, this leads to the creation of 2 groups within the group, where one group is working on the computer and the others working on the side. Our group subconsciously created an in-group and an out-group, which coincide with Bos’s observation with states “that these groups did exchange a great deal of verbal information, checking on shape availability” (Bos et al, 433). I ended up being the in the contributor group and collaborated more with the other “contributor.”
While each of the subgroups created their own “private space”(a hybrid system), niche and created common ground due more interactions with each other, sometimes, there isn’t nearly as much interaction between the two subgroups. This problem leads to miscommunication, which leads to mistake in code. The only reason we have to get around this is the goal of our group, to get a good grade. The last problem we have his meeting times. Working offline is even worse because our task is very tightly coupled.
To improve our system of work, we need to establish common ground between all members of the group and make sure that all members have access to the same information (both code and notes on the code). We also need to have a common meeting time every week when we all can be there, and maybe use a dual monitor screen (on side for notes, the other for code).
Subscribe to:
Post Comments (Atom)
Posts
It is interesting that your groups form around sides of a computer screen. I find that often when I am working with a group, the person typing or taking notes is equally active in the discussion as the other members. By the same token, taking notes does not require the constant attention that coding does. However, I wonder what would happen if you set rules so that every group member collaborated, wrote down ideas, and finalized a plan. Then one or many group members could "break out" of the group and code.
ReplyDeleteOne thing I noticed when I took 211 was the common ground issue. It is tough to know what the other person worked on. Digesting a large amount of code quickly can be difficult, and as a result, the other person isn't up to speed. From then on, they could feel marginalized. Coding is definitely something that can be both helped and harmed by the teamwork aspect.
ReplyDelete