Agile Approaches for Gaming Software Development (Kim et al. 2026) | FT50 POMS

<p>English Podcast Starts at 00:00:00</p><p>Bengali Podcast Starts at 00:32:21</p><p>Hindi Podcast Starts at 00:52:40</p><p>Danish Podcast Starts at 01:13:12</p><p><br></p><p><strong>Reference</strong></p><p>Kim, J., Johar, M., &amp; Mookerjee, V. (2026). EXPRESS: Agile Approaches for Gaming Software Development. Production and Operations Management. <strong>https://doi.org/10.1177/10591478261495695</strong></p><p>‌</p><p>‌Youtube Channel</p><p>⁠https://www.youtube.com/@weekendresearcher⁠</p><p>Podcast Website</p><p>https://mayukhmukhopadhyay.com/reviseandresubmit</p><p>AOM SIM Curriculum Committee</p><p>https://sim.aom.org/curriculum/curriculum-committee</p><p>AOM SIM-Bytes Curriculum Lessons</p><p>https://sim.aom.org/simthrive/teaching/simbytes</p><p><br></p><p>🎙️ <strong>Welcome to </strong><em><strong>Revise and Resubmit</strong></em><strong>.</strong> Today, I want to take you somewhere that may seem, at first, like a very familiar place: the restless, constantly changing world of online games. 🎮</p><p>But as I read <strong>“Agile Approaches for Gaming Software Development”</strong>, by <strong>Joohyun Kim, Monica Johar, and Vijay Mookerjee</strong>, I began to see something rather different beneath the surface. Published online on <strong>28 September 2026</strong> by <strong>SAGE Publications</strong>, this paper appears in <em>Production and Operations Management</em>, a highly prestigious journal that is included in the <strong>Financial Times 50, or FT50, journal list</strong>. The journal regularly publishes research at the intersection of operations, technology, and management, which makes this paper&#39;s question particularly fitting.</p><p>🕹️ Online games are no longer finished products that simply leave the developer&#39;s hands. They live. They change. They receive new features, updates, fixes, patches, and sometimes seemingly endless streams of small adjustments. And somewhere behind all of that lies a deceptively difficult question: <strong>when should the next release happen?</strong></p><p>Kim, Johar, and Mookerjee approach that question through an optimal control framework, looking closely at the delicate relationship between <strong>new functionality, debugging effort, release cadence, and growing system complexity</strong>.</p><p>⏳ The paper considers two familiar approaches. One releases according to time, such as fixed sprints. The other releases according to functionality, waiting until a particular bundle of features is ready