Game Studio Production Pipeline

Team Allocation (weight)

Programming 5

Art 5

QA 5

Prog: 7 devs Art: 7 QA: 7

Production Settings

Feature complexity 2.0

Studio Status

Features Shipped

Work in Progress

Game Quality

100%

Team Morale

100%

Bugs caught: 0 Bugs escaped: 0

How it works

Each feature is a task that flows Design → Programming → Art → QA → Ship. Every station is a small server: it can work on a limited number of tasks at once, and tasks that arrive faster than the station can finish them pile up in a visible backlog behind it — the classic queueing bottleneck of software production.

capacity(station)   = max(1, round(heads / 4))
rate(station)       = heads × 0.14 × crunchMult × moraleFactor
moraleFactor         = 0.5 + 0.5 × (morale / 100)
Little's Law:  WIP (tasks in system) = arrival rate × average time in system

Your 20-person team splits across Programming, Art and QA by the weight sliders (heads_i = 20 × w_i / Σw); a fixed 4-person Design crew keeps concepts flowing in. Feature complexity scales how much work each stage needs — bigger scope, slower pipeline, but the same headcount.

p(QA catches a bug) = 1 − clamp(0.55 − heads_QA × 0.05, 0.05, 0.55)

A caught bug is sent back to Programming for a short rework pass, then ships clean. An uncaught bug ships anyway and costs Game Quality — so an under-staffed QA station trades speed for defects. Crunch mode raises every station's rate 30% but drains Team Morale, and low morale throttles every station's rate right back down — the same burnout feedback loop real studios fight during crunch.

Design Programming Art QA Rework Shipped

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.