Considering Large Student Teams in Game Development Education: A Post-Mortem
Bibliographic record
Abstract
Having a large (>100) team of students work on a single game as part of their games education experience sounds like a terrible idea. But, is it really? I provide an examination of the reasons why students are encouraged to participate in collaborative game development projects, challenge some of those assumptions, and propose the megateam as an alternate model that might be worth considering. I also present a brief post-mortem of a large (~70 student) team class explicitly designed to provide an educational experience more authentic to working at a large game studio by forcing an organizational structure that foregrounds the content pipeline (and bottlenecks), requires additional communication and coordination, and challenges everyone to maintain a coherent vision for the game they were working on. All of these are common problems identified in game industry post-mortems. While the megateam experience was not without flaws, it demonstrates there is potential for re-imagining the student game project experience such that it highlights a production model (i.e. AAA game development) that is more authentic to what many students aspire to, and may end up participating in. In this way game educators can better prepare students meet their career expectations and help them succeed.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.006 | 0.022 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.016 | 0.005 |
| Scholarly communication | 0.010 | 0.006 |
| Open science | 0.002 | 0.009 |
| Research integrity | 0.002 | 0.008 |
| Insufficient payload (model declined to judge) | 0.013 | 0.004 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".