I wonder what people experiences are with group work projects at college, or even better how to deal with them without becoming burnt out myself.
To get straight my point of view: it sucks.
In the last 5 courses I've taken, 3 of them involved group work sized between 2-4 people. In all courses I've been frustrated with the outcome.
It's often a mix of:
- Students that are completely incapable. Last semester we had to develop a CPU in VHDL (sounds fun) with a guy (ex 'Creative Tech') that barely has done
any programming at all.
- Students that regret taking the course, but don't quit because they need the credits.
- Exchange students that don't regret taking the course, but actually don't need finishing it because they're unsure if their credits can be taken over to their other uni.
- Students that despite their bests efforts are incapable of keeping up, because of perhaps social life but also frankly unreasonable time management (like working for 3 days a week alongside a masters)
I think the first 3 is a matter of picking your right poison (or avoiding all of them); but that can be hard when each class is different and you have different people.
Is this really similar to work in real life, which is the often claimed aim/acquired competence with group work? My past experiences tell otherwise. If someone is unmotivated at a job, they get the boot. Moreover I never experienced such close interleaved project work anyways.. I hate it when someone else is watching over my shoulder half of the time.
What I find that is happening I often try to compensate others shortcomings to cover it up in the grade. I'm not in it to get a mere pass, but rather actually learn a subject well when I'm at it and pass with much room to spare. I have given up my turmoil about
them also getting the same grade.. they will probably face their shortcomings later in their careers and be on their own to fix them.
Nevertheless it stays especially frustrating. When others get stuck (or progress is absent despite deadlines) it often means I will jump on it to fix it. For said 3 projects I got the feeling that I've done more than half of the (grind) work, mind you in groups of 3+ people.
It's quite a pity because at an intellectual level I feel like there interesting subjects to tackle, but at this rate I rather only take the math-only courses & exams, and skip all the practical (group) work.
Any tricks in the book to manage this?

Note; talking about a master in EE/Embedded here.