Using “Share of Mind” to explore and align the individual and shared responsibilities within a group, by revisiting the opportunity spaces within their context.
Traditional game development phases carry mental models that are hard to escape or reconsider. Here I offer some observations on what harm it may be doing, and starting points for more learning-oriented, contextual framing.
A simple reminder and a lightweight exercise to help clear out some of that organizational overhead.
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.
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.
