Originally written July 14, 2025 | MS Game Production and Documentation Course
Postmortem Report — Reign and Rebellion
Project Context
Role: Producer
Studio: University of Advancing Technology (UAT) Game Studios – Opera Skunk Initiative
Timeline: Spring 2022 (January–March)
Platform: Unity (PC Multiplayer)
Genre: Competitive 3v3 Third-Person Shooter
Reign and Rebellion was developed as part of a studio-style academic environment, designed to simulate real-world production conditions. The project emphasized cross-discipline collaboration, structured documentation, and agile-informed workflows aligned with contemporary game production practices.
Project Overview
The game featured distinct playable characters and multiple multiplayer modes — including Domination, Capture the Flag, and Arena. Each mode required coordinated teamwork, situational decision-making, and strategic collaboration. My responsibilities focused on documentation support, production coordination, and communication alignment across disciplines.
A core learning objective of this experience was to observe how agile practices function inside a collaborative environment and to understand how production decisions influence both workflow and final outcomes.
What Worked Well
Clearer role definition helped the team gradually improve coordination. Sprint planning sessions, retrospectives, and shared documentation provided structure and visibility into ongoing work. Production artifacts — including the project website, documentation, and pitch materials — supported communication with stakeholders and reinforced milestone clarity.
These practices strengthened accountability, encouraged iteration, and created opportunities for reflective improvement.
What Could Be Improved
Earlier clarification of leadership expectations would have reduced uncertainty and prevented duplicated efforts. Dedicated documentation ownership, improved version tracking, and more deliberate communication rhythms would have supported smoother production handoffs.
These observations reinforced how important it is for teams to establish shared agreements early and to revisit them as projects evolve.
Key Insights
Trust, communication, and shared ownership emerged as central themes. Agile methods work best when adapted thoughtfully to a team’s real context instead of being applied mechanically. Consistent reflection helped identify challenges without assigning blame and encouraged practical, process-focused improvement.
Takeaways
- Strong teams benefit from psychological safety, clarity of purpose, and predictable communication.
- Leadership functions best as stewardship—orienting people, clearing obstacles, and reinforcing shared vision.
- Iteration surfaces issues early, while documentation and retrospectives help ensure they are addressed constructively.
Conclusion
Reign and Rebellion strengthened my understanding of production pipelines, collaborative leadership, and agile-based studio practice. The experience encouraged disciplined organization while also reinforcing empathy, patience, and reflective thinking — qualities essential to sustainable creative work.
References
Keith, C. (2021). Agile Game Development (2nd ed.). Pearson Education, Inc.
Previous entry in this series:
Reflective Postmortem — Game Production Insights and Scrum Learnings From Reign and Rebellion
*This entry concludes the Reign and Rebellion documentation series, bringing together the core reflections, lessons, and production insights gathered throughout the project.
This post is part of the comprehensive documentation for the Reign and Rebellion project, capturing structured learning outcomes and reflective insights from both production practice and subsequent revisions.