Tuesday, February 10, 2026

Reflective Postmortem — Game Production Insights and Scrum Learnings From Reign and Rebellion

Originally written February 27, 2022 | MS Game Production and Documentation Course

Assignment 7.5 — Postmortem | Reign and Rebellion


What new ideas did you learn?

I learned about game flowcharts, which are visual representations of the structure and navigation of game software. They illustrate various aspects of a game, including features from the splash screen to multiplayer options, on-screen buttons, and player navigation paths. Flowcharts are powerful tools that designers use to explain gameplay mechanics, system logic, and progression structures such as technology trees and skill systems.

While exploring and navigating the project website, I also learned more about the in-game characters sketched by one of the artists on the team. Character representation is a crucial element of any game project, as it defines visual identity and player connection. The game includes both male and female characters to diversify the player experience. Additionally, learning about the Scrum process and its history through assigned readings provided a clearer understanding of how Scrum functions in practice, including concepts such as the product backlog, sprint backlog, daily scrums, sprints, and potentially shippable increments. Game development should remain a creative and enjoyable process, and this mindset should be reflected in the final product.


What did you find the most helpful or useful?

Working on the project website provided a strong understanding of the game’s current state and the team’s overall progress. I contributed time and effort to the homepage, art sections (including characters and abilities), and various design details to improve clarity and presentation. Preparing a website that documents in-game characters, supernatural abilities, design features, and engineering considerations is both research-intensive and time-consuming.

Understanding the target audience and player demographics is vital to identifying user needs and expectations. Players often have specific preferences regarding gameplay depth and design details, and recognizing these expectations makes it easier to break complex systems into manageable components. Planning game development is challenging but essential, as it helps reduce wasted effort, manage costs, and improve production efficiency.


What did you find the most puzzling or confusing?

The web document provides clear written guidance that helps the team navigate unclear situations or issues. Beyond the assigned tasks, I realized the importance of leadership in ensuring that all team members understand the project’s direction and their role within it. Having a clear overall vision allows individuals to contribute more effectively.

Due to frequent changes and occasional communication gaps, contributing to the project could sometimes feel difficult. The most effective way to address these challenges is through consistent communication and collaborative problem-solving.


What surprised you the most about this class?

A team of highly skilled developers cannot guarantee success if collaboration is lacking. Teams that value their players’ needs and work together to overcome production challenges tend to create stronger products. Each studio that adopts Scrum has a unique experience shaped by its culture, structure, and constraints.


How will you use what you have learned in this class?

One of the most important lessons from this course was the importance of communication and addressing issues such as unclear expectations and missing details. As a producer, I expect to face significant challenges, and learning how to navigate and resolve them will be critical to my growth.


How did this class make you a better innovator, creator, or producer?

This course provided valuable experience through hands-on participation in the Reign and Rebellion project. It helped identify common root problems in production, particularly the lack of trust and collaboration between developers and publishers. Trust takes time to build and is strengthened through iteration, transparency, and alignment—core agile principles.

Large design documents and rigid schedules can provide temporary comfort but often fail under changing conditions. Tools such as the product backlog and the definition of done help teams apply fixed ship-date principles more effectively.


What went right?

Situation 1 — Documentation
I worked on a detailed web document covering the art and design aspects of the game. This document included information on art assets, character abilities, UI elements, and design specifications such as game modes, game types, scoring systems, and gameplay descriptions.

Situation 2 — Video Pitch
I also worked on the game’s pitch video, which presented the production methodology, team processes, core values, and a gameplay demo. Creating the video was time-consuming but highly engaging and informative.

Situation 3 — Team Communication
Regular stand-ups and team discussions demonstrated emotional intelligence within the group. These interactions showed that effective teamwork was possible and highlighted the importance of emotional intelligence in predicting both individual and team performance.


What went wrong?

Situation 1 — Communication Gaps
In the early weeks, a lack of communication and incomplete information led to uncertainty. Effective communication depends not only on frequency but also on participation. Research shows that balanced conversational turn-taking is a key trait of high-performing teams.

Situation 2 — Leadership Challenges
Strong leadership is essential at every stage of a project. At times, the team appeared to lack the leadership structure needed to maintain momentum while supporting a healthy work-life balance. Effective leadership requires setting norms, communicating vision, delegating tasks appropriately, resolving conflicts, removing blockers, and recognizing achievements.

Situation 3 — Unclear Goals
Well-defined goals that are measurable, challenging, clearly communicated, and mutually agreed upon are critical for success. Much of the communication occurred through Microsoft Teams, and at times it felt as though the team struggled to stay aligned and focused.


What is the most important takeaway you gained from this project?

Teamwork is essential regardless of role or discipline. While collaboration consistently delivers value, its success depends on assembling the right team and establishing strong communication and trust. When these foundations are in place, teamwork becomes both effective and rewarding.


References

Keith, C. (2021). Agile Game Development (2nd ed.). Pearson Education, Inc.

Previous entry in this series:

Learning With Care — Collaboration, Methodology, and Steady Growth in Game Production

Next entry in this series:

Grateful Reflection — Lessons in Collaboration, Leadership, and Better Production Practice


This post is part of a weekly documentation series created during the Reign and Rebellion project, capturing structured learning outcomes from both production practice and coursework.


Case Study Spotlight

Grateful Reflection — Lessons in Collaboration, Leadership, and Better Production Practice

Originally written July 14, 2025 | MS Game Production and Documentation Course Postmortem Report — Reign and Rebellion Project Conte...