Building on the key contextual differences between games and task-oriented software, we review common agile practices that aren’t fit-for-purpose, and reframe opportunities for new approaches.
Agile
Game teams that have “gone agile” with standardized methodologies run into problems almost immediately, creating confusion and wasting time and energy. The source of the problem is mistaking one context for another, and the solution is not “do the practices better”. In this post I deconstruct those key contexts as starting points for more effective game development.