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 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.

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.

---

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

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

Assignment 7.2 — Weekly Journal | Reign and Rebellion

---

Introduction

This week focused on refining ways to present and position the team’s game, alongside developing an improved version of the game pitch that would be engaging and persuasive. A significant amount of time was dedicated to organizing and structuring the presentation content. This process served as a valuable learning experience, providing deeper insight into the team’s production methodology and workflow. Presenting clear information about how the group operates helped communicate the project’s structure and intent more effectively.

---

Project Doing

During this week, I worked on enhancing the video pitch presentation by improving the overall demonstration of the game. Preparing the video and ensuring that all essential details were included helped communicate the game’s value clearly and cohesively, supporting its presentation and positioning.

---

Project Learning

Scrum addresses communication challenges in larger teams not by adding management layers, but by dividing project staff into smaller, focused groups. One of the most critical responsibilities of a lead is mentoring developers to improve how they work. For example, lead programmers often pair with associate programmers to help refine coding and design practices.

---

Book Reading

Scrum creates opportunities for leads to remain actively involved in game development and to lead by example rather than through task-tracking tools alone. Instead of spending excessive time managing spreadsheets, leaders engage directly with team members through one-on-one interactions. Another important leadership responsibility is providing career support for developers within their discipline. In organizations that employ matrix management structures, this often takes the form of annual performance and salary reviews, which can reinforce discipline-centric evaluation over team-centric collaboration. Scrum also drives change across disciplines by encouraging teams to reflect on and improve their day-to-day working practices, enhancing communication and iteration speed.

---

Book Learning

Game development requires a high level of collaboration across multiple disciplines. A single character, for example, involves animation, physics, textures, models, sound, and behavior systems that must work together seamlessly. No single discipline can accomplish these functions independently; close collaboration is essential to create complete features. While feature teams are common, functional teams—composed of developers within the same discipline—also offer distinct advantages. Studios often distribute development work across teams to reduce costs and balance staffing demands.

---

Conclusion

There is no single formula for building effective teams in game development. The team structures and practices discussed here result from adapting Scrum roles and workflows to improve collaboration and align shared vision. Exploring roles and team structures is an ongoing process. Retrospective practices are essential for improving how teams work together and interact with stakeholders. When teams are given ownership and authority over aspects of their daily work, they are more likely to take responsibility for outcomes. This transformation often takes years and may create friction with existing studio leadership cultures, but the long-term results justify the effort.

---

References

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

Previous entry in this series:

Presenting With Care — A Professional Video Pitch Grounded in Teamwork, Methodology, and Iterative Improvement

Next entry in this series:

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

---

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.

---

Presenting With Care — A Professional Video Pitch Grounded in Teamwork, Methodology, and Iterative Improvement

Originally submitted February 23, 2022 | MS Game Production and Documentation Course

Assignment 7.1 — Video Pitch | Reign and Rebellion

---

Video Pitch Overview

This post documents the submission of the video pitch for the Reign and Rebellion project. The objective of this deliverable was to provide a comprehensive overview of the project, the team’s contributions, and the production methodology employed during development. The pitch highlights the project’s design intent—its premise, objectives, and intended player experience—while also emphasizing the value added by team members and the adapted, Scrum-informed workflow used to manage production.

The video demonstrates how the team collaborated, organized tasks, and applied Scrum principles in practice, adapting them to the project’s needs rather than following a rigid framework. It communicates the game’s design direction, mechanics, and player interactions alongside the production processes that guided development, ensuring transparency and alignment among contributors.

The pitch was structured to balance clarity and depth, presenting essential aspects of the project, team dynamics, and methodology without unnecessary detail. This approach ensured the presentation remained accessible and informative for both peers and academic stakeholders.

---

Peer Feedback Integration

Feedback received from peers provided constructive and actionable insights. Alexander Laurie noted that the pitch effectively communicated the project’s rationale and the team’s contributions. He observed that the video slightly exceeded the recommended 2–5 minute duration, while also acknowledging the clarity and strength of the production methodology explanation

Jennifer Hull highlighted the effectiveness of the Scrum methodology discussion and the overall production overview. She suggested that reducing the length could help maintain audience engagement while preserving informational quality.

These observations informed considerations for future presentations, reinforcing the importance of conciseness, clarity, and audience awareness in professional and academic communication.

The video pitch submission can be accessed here: Video Pitch Submission – Reign and Rebellion (Google Drive)

This artifact reflects an applied understanding of game production communication, stakeholder-oriented presentation, and iterative refinement through peer feedback, aligning with academic documentation standards and professional game development practice.

---

References

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

Previous entry in this series:

Learning to Lead With Care — Coaching, Scrum, and the Craft of Building Games Together

Next entry in this series:

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

---

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.

---

Learning to Lead With Care — Coaching, Scrum, and the Craft of Building Games Together

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:

Presenting With Care — A Professional Video Pitch Grounded in Teamwork, Methodology, and Iterative Improvement

---

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.

---

Learning With Care — Documentation, Collaboration, and Reflective Game Production Practice

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

Assignment 5.1 — Weekly Journal | Reign and Rebellion

---

Introduction

This week, I worked on a web document and a video pitch for the game. One of my responsibilities as a producer on the project was to help document the website. The web document contains detailed information on the game’s art and design, while the video pitch provides a comprehensive overview of the game and the production methodology used by the team.

---

Project Doing

In addition to the web game document, I prepared a pitch video that describes the game in detail. The video demonstrates the product, outlines its benefits, and explains the production methodology used by the team. It discusses Scrum as the chosen framework and also highlights what does not align with Scrum in the team’s current production approach.

I also made progress on the web document by adding several new sections focused on game modes. These sections describe different game types and arenas available for players to explore. The documentation provides gameplay details, including distinct elements such as enemies, objectives, scoring systems, and overall player experience.

---

Project Learning

Working on the pitch video provided valuable insights into the shooter game market and the benefits this product offers to its audience. Researching team values and evaluating how the team functions helped me gain a clearer understanding of team dynamics. I also learned how a production methodology—specifically the Agile framework using Scrum—can be applied in practice. Most importantly, examining “Scrum-but” scenarios offered meaningful perspective on how closely the team’s operations align with Scrum principles.

---

Book Reading

Agile teams do not operate without planning; rather, they iterate toward goals with intentional direction. Planning is both crucial and risky for agile teams that lack clarity. One challenge in adopting Scrum is that the framework is not suitable for everyone. During the initial transition, some individuals may resist working in an agile environment and choose to leave. The most effective way to adopt Scrum is to do so with full awareness and realistic expectations. Establishing metrics and practices such as velocity tracking and daily Scrum meetings demonstrates clear value.

---

Book Learning

Working with publishers or stakeholders can be highly challenging. The common root of many of these challenges is a lack of trust and collaboration between developers and publishers. Trust takes time to build and is strengthened through iteration, transparency, and collaboration—core agile principles. Large design documents and rigid schedules can feel reassuring but often provide only temporary comfort. Two important tools for applying fixed ship date principles are the product backlog and a clearly defined “definition of done.”

---

Conclusion

Collaboration is an essential element of high-performing teams. A group of highly skilled developers who cannot collaborate cannot reliably achieve success. Teams that prioritize their consumers’ needs and actively address production challenges are more likely to create better products. Every studio’s experience with Scrum is unique. The journey from apprentice to journeyman to master varies—some teams progress steadily over years, while others struggle or stall along the way.

---

The above content reflects learning insights from both the Reign and Rebellion project and the assigned reading.

---

References

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

Previous entry in this series:

Building With Care, Clarity, and Gratitude — A Reflective Journey in Game Production

Next entry in this series:

Learning to Lead With Care — Coaching, Scrum, and the Craft of Building Games Together

---

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.

---

Building With Care, Clarity, and Gratitude — A Reflective Journey in Game Production

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

Assignment 4.1 — Weekly Journal | Reign and Rebellion

---

Introduction

This week, I worked on a web document for the project. As a producer, my responsibility is to document information on the website. The web document functions similarly to an art document and a design document. It consists of character art and design-related details such as gameplay descriptions, game modes, and other essential elements.

---

Project Doing

My role within the production team involved building art and design web documents. These documents serve as a central source of information needed to progress with the project and help streamline the team’s workflow. The documentation includes multiple aspects of art creation for the 3v3 shooter game, such as asset packs, concept art, design specifications, and detailed descriptions.

The design section covers gameplay descriptions, UI details, prototype requirements, artistic style, different game modes, and arenas. Preparing these documents is research-intensive and time-consuming, but essential for maintaining clarity and alignment across disciplines.

---

Project Learning

While working on the design page for the web document this week, I learned several important lessons, including the significance of team communication and understanding team dynamics. The web document provides clear, written guidance that team members can rely on when facing uncertainty or unresolved issues.

Beyond my assigned tasks, I realized how critical leadership is in ensuring that every team member understands where the project stands and how they can best contribute. When there are constant changes or gaps in communication, contributing effectively becomes difficult. Clear and consistent communication is the most effective way to reduce such challenges and move the project forward.

---

Book Reading

Technology creation and innovation can be risky. Competition in gameplay and visual quality remains important, but the technical aspects of video games have become increasingly significant to players. Extreme Programming (XP) introduces principles and practices such as test-driven development and pair programming, which aim to address these challenges

In the context of Reign and Rebellion, artists face numerous challenges within game development teams, including uncertain technology, unrealistic schedules, overproduced assets, and compromised quality. These issues are often compounded by communication barriers between disciplines, even though game development fundamentally relies on cross-disciplinary collaboration to create a fully interactive experience.

---

Book Learning

Designers must collaborate and communicate face-to-face within small, cross-disciplinary teams, and Scrum practices help facilitate this process. Designers are responsible for ensuring that the project vision is clearly conveyed and remains open to new ideas. Agile QA and production demand a deep passion for video games, strong organizational skills, and effective communication. Testers and producers face significant challenges, but these challenges also provide opportunities for growth and leadership.

---

Conclusion

The most important lesson I learned this week centers on communication—particularly addressing improper communication, lack of detail, and misalignment within a team. As a Producer on the Reign and Rebellion team, it is clear that I will encounter substantial challenges. Tackling these challenges will not only test my abilities but will also serve as a valuable learning experience as I continue to grow in this role.

---

The above content reflects learning insights from both the Reign and Rebellion project and the assigned reading.

---

References

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

Previous entry in this series:

Learning With Care and Gratitude — A Grounded Journey of Responsibility and Growth in Game Production

Next entry in this series:

Learning With Care — Documentation, Collaboration, and Reflective Game Production Practice

---

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.

---

Learning With Care and Gratitude — A Grounded Journey of Responsibility and Growth in Game Production

Originally written January 30, 2022 | MS Game Production and Documentation Course

Assignment 3.1 — Weekly Journal | Reign and Rebellion

---

My journey as a producer continued into Week 3 with the Reign and Rebellion  project. This week primarily involved working on the Reign and Rebellion website, beginning with the homepage’s Art section, which showcases in-game characters and their abilities. Exploring the website in greater depth helped me gain a clearer understanding of the game’s vision and the current stage of development. It also provided valuable insight into where the team stands in the overall production pipeline.

I dedicated significant time and effort to refining the homepage, art pages—including character profiles and abilities—and the finer details that contribute to a polished presentation. Creating a website that documents in-game characters, their supernatural capabilities, and features related to design and engineering requires extensive research and is a time-consuming process. However, this effort is essential for clearly communicating the game’s identity and mechanics.

Understanding the target audience and player demographics is a vital aspect of game production. Recognizing users’ needs and expectations allows the team to design experiences that resonate more effectively with players. Users often have specific ideas or requests about the type of gameplay they want to experience, and acknowledging these perspectives can be crucial in shaping features and content. By focusing on the level of detail and breaking complex systems into smaller, manageable components, it becomes easier to plan and execute development tasks efficiently.

Planning video game development is both challenging and essential. A structured approach helps save development time and cost while also reducing waste throughout the production process. As the project progresses, I look forward to learning more and continuing to work on the website to ensure it meets a high standard of quality and effectively supports the Reign and Rebellion project.

---

References

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

Previous entry in this series:

What It Truly Takes to Produce a Game — A Grateful Journey of Learning, Teamwork, and Growth

Next entry in this series:

Building With Care, Clarity, and Gratitude — A Reflective Journey in Game Production

---

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.

---

What It Truly Takes to Produce a Game — A Grateful Journey of Learning, Teamwork, and Growth

Originally written January 23, 2022 | MS Game Production and Documentation Course

Assignment 2.1 — Weekly Journal | Reign and Rebellion

---

My journey as a producer began with the Reign and Rebellion project, a third-person shooter game. Learning is vital in game development, and through in-depth exploration this week, I discovered several concepts essential to game software production. I work closely with project leads across different departments—Art, Design, and Programming—to help set up and maintain the game project’s website documentation. In doing so, I contribute to the project’s vision by supporting the team and helping reduce potential hurdles in the production process.

During this week, I learned about game flowcharts, which are visual representations of the internal structure and functionality of game software. These flowcharts cover multiple aspects of the game, including features ranging from the splash screen to multiplayer options, on-screen buttons, and player navigation. Flowcharts are powerful tools that designers use to explain gameplay mechanics, system logic, technology trees, and skill progression in a clear and accessible manner.

While exploring and navigating the project website, I also gained insight into several in-game characters sketched by one of the artists on the team. Character representation is a crucial component of any game project, as it defines a character’s visual identity and personality. Reign and Rebellion introduces new characters for players to experience, including both male and female characters, which helps diversify the gameplay experience and broaden player engagement.

Through assigned readings, I further explored the Scrum framework and its history, which provided a clearer understanding of how Scrum functions in game development. This process includes elements such as the product backlog, sprint backlog, daily scrum meetings, sprints, and the creation of potentially shippable game builds. Game development should remain a creative and enjoyable process, and this mindset should be reflected in the final product.

As the team and I work to complete tasks assigned by the project leads, it is evident that challenges related to scope and feature implementation will arise. Addressing these challenges is an important part of the learning process. Prioritizing work effectively is a vital component of fulfilling responsibilities and ensuring steady progress. From a stakeholder perspective, key considerations include value creation, return on investment (ROI), and risk management.

I continue to make progress toward completing my assigned tasks while learning what it means to be part of the Reign and Rebellion production team. I am gaining exposure to tools, techniques, and collaborative practices that will help me solve production-related problems in the coming weeks. There is no strict timebox or deadline for my current tasks, as the team is continuously producing new in-game content that may be showcased on the project website. As the art team develops visual assets, selectively displaying content on the website—while reserving some elements for in-game discovery—can be an effective strategy for attracting users and promoting the game without revealing everything upfront. This approach may play a crucial role in marketing and player engagement.

---

References

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

Next entry in this series:

Learning With Care and Gratitude — A Grounded Journey of Responsibility and Growth in Game Production

---

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.

---