Timeline for How to deal with inactive students in undergraduate projects?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 17, 2017 at 3:59 | comment | added | Daniel R. Collins | This is actually an interesting point that the original question is ambiguous about whether it concerns group projects or not (not terribly well written). | |
| Dec 16, 2017 at 22:12 | history | edited | Mad Jack | CC BY-SA 3.0 |
added 494 characters in body
|
| Dec 16, 2017 at 3:04 | comment | added | Mad Jack | @TasosPapastylianou Hmm, I didn't read the question as being about group projects, but rather a group of students that OP was having issues with. Nowhere in the following text does OP mention that this is a group project: "and I have noticed a trend among a group of students when dealing with undergraduate programming projects" | |
| Dec 15, 2017 at 21:11 | comment | added | Tasos Papastylianou | This superficially sounds useful, but goes against most of the principles of a group project in terms of role allocation. Only the least organised team which ended up with everybody duplicating everything will know everything about the project. The whole reason group projects are hard (and hard to mark) is that all the individuals in the team need to have different roles and contributions, and it's hard to allocate roles such that 'conceptually' the contributions were more or less equal. | |
| Dec 15, 2017 at 18:06 | history | answered | Mad Jack | CC BY-SA 3.0 |