Originally written March 1, 2022 | MS Game Production and Documentation Course
Assignment 6.2 — Weekly Journal | Reign and Rebellion
Introduction
As a producer on the Reign and Rebellion project, I worked on the web documentation, specifically the Design section, game modes, and different game types. I also worked on the video pitch, which provides a detailed description of the game and the production methodology used by the team.
Project Doing
I improved my pitch video by adding more content to the presentation, including a product demo video. I edited the video using Adobe Premiere Pro, a tool well suited for editing gameplay footage and producing polished game demo videos.
Project Learning
I refined how game content is described within the web document, including systems such as scoring, enemy respawn mechanics, and hidden locations within the game. The document also explains how points and scores relate to kill counts, helping to clarify gameplay systems for the team.
Book Reading
Coaching is often one of the most critical factors in a team’s success, even though a coach may not be the best at any individual role. A coach keeps the team focused on the larger goal and reflects observations back to the team. One of the biggest challenges a coach faces is resisting the urge to take the easy path by solving problems for others, instead helping them grow as independent problem solvers. A coaching stance refers to the mental and emotional disposition coaches adopt when assisting others. It supports individuals or teams who will most benefit from guidance and growth. When helping someone with a problem, it is common to already have a solution in mind; however, forcing that solution often creates resistance and emotional investment in its adoption. Effective coaching involves discovering solutions collaboratively—from developers to studio executives—rather than imposing answers.
Book Learning
Self-organization is one of the most culturally challenging aspects of Scrum. It requires significant trust and team maturity, while still demanding strong leadership. Resistance often comes from developers who focus narrowly on their individual tasks and expect managers to resolve broader issues and uphold quality. Teams that select their own members demonstrate higher levels of accountability. In contrast, teams assembled solely by management may lack a sense of ownership, which can hinder commitment. By preserving Scrum principles while scaling, teams can maintain short communication lines and ensure developers retain purpose and autonomy. By analyzing player reactions, teams can shift focus toward features players prefer. In live game development, the measurable goal is not simply defeating enemies, but increasing the number of players enjoying the game—often tracked through metrics known as Key Performance Indicators (KPIs). Feature boards help teams visualize progress daily and encourage the conversations necessary for effective cross-discipline collaboration.
Conclusion
The practices and experiences of Agile game development are very real. While many studios have adopted Agile-based methods over the past decade, many still struggle to fully embrace the underlying values and principles. As new platforms and business models continue to emerge, new practices, tools, and approaches will evolve, enabling creative teams to build better games more efficiently. This adaptability is what makes Agile particularly well suited to game development. The goal is not to find a “perfect” methodology, but to remain open to change.
References
Keith, C. (2021). Agile Game Development (2nd ed.). Ebook: Pearson Education, Inc.
Previous entry in this series:
Learning With Care — Documentation, Collaboration, and Reflective Game Production Practice
Next entry in this series:
This post is part of my weekly journal series documenting my experience in the MS Game Production and Documentation course. Follow along as I learn what it really takes to produce a game.