home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!prism!gus
- From: gus@prism.gatech.EDU (gus Baird)
- Newsgroups: comp.edu
- Subject: Re: collaborative work
- Message-ID: <67712@hydra.gatech.EDU>
- Date: 5 Sep 92 12:55:15 GMT
- References: <20161@plains.NoDak.edu>
- Organization: College of Computing, Georgia Institute of Technology
- Lines: 27
-
- In article <20161@plains.NoDak.edu> kmagel@plains.NoDak.edu (ken magel) writes:
- >
- > What is your opinion with regards to the value or harm in having student
- >work together on programming projects?
-
- It depends on the objective of the exercise. If you're in a lower-division
- course where the objective is learning the basic skills, then group projects
- are counterproductive. If it's to learn "higher" skills then group projects
- can help or hinder, depending on how students are allowed to break up the job.
- If the objective is learning how to work in groups then group projects are
- exactly right.
-
- Analogy: if you send a team out to do labor, then the guy with the strong
- legs will do the leg-work. The ones with weak legs won't develop their
- legs by doing that job, because that would hinder completion.
-
- Letting students work together in groups on projects where they're to learn
- basic skills tends to result in each student getting more practice in what
- he's already good at and discourages students from filling in the gaps in
- their skills sets, because of the students natural tendency to view the
- objective as being to get the program working. We don't need the *program*,
- we need them to benefit from the exercise.
- --
- gus Baird, College of Computing
- Georgia Institute of Technology, Atlanta Georgia, 30332
- uucp: ...!{allegra,amd,hplabs,seismo,ut-ngp}!gatech!prism!gus
- ARPA: gus@cc.gatech.edu
-