Disclaimer: This portfolio showcases how I would apply my PMP-certified Project Management experience to game production. While Project AEON is a conceptual case study, the coordination, Jira workflows, and delivery practices shown here are based on approaches I’ve used in software project environments.
<aside> 💡
Note: Technical diagrams and Jira snapshots are provided in high resolution. For a detailed review, click any image and select the Expand icon (top-right) to view in full size.
</aside>
Executive Profile - Sunghun Kang, PMP PMP-certified project professional with experience coordinating software delivery and cross-functional teams. Currently transitioning into game production, with a focus on coordination, workflow organisation, dependency tracking, and team communication.
<aside> 📁
Project Foundation: The Master Blueprint (GDD)
This portfolio demonstrates production workflows and dependency management based on:
Sunghun Kang PortFolio (GDD).pdf
For a comprehensive understanding of the game's creative vision, technical constraints, and business specs, please refer to the sample GDD above.
</aside>
Managing Complexity in Open-World Development
Open-world projects naturally involve many moving parts across engineering, art, design, and QA. Without clear coordination and priorities, teams can run into delays, rework, or shifting scope. This concept focuses on building stable technical foundations first before scaling content production.
1-A Example: Jira backlog showing task sequencing, dependencies, and sprint planning structure.
Case Study: Technical Dependency Management (AI Drone System)
I selected the Tactical Drone System as a case study to show how a high-level GDD could be broken down into trackable tasks and production workflows. In more complex systems, unclear dependencies can slow teams down and create unnecessary blockers, so the focus here was on structuring work in a way that allows Art, Tech-Art, and Engineering to move in parallel where possible.
2-A Example: Centralized GDD via Confluence-Jira integration to maintain a Single Source of Truth.
Establishing a Single Source of Truth
To avoid scattered documentation and reduce confusion, Jira references were linked directly into the Confluence GDD. This keeps implementation notes, requirements, and references in one place, making it easier for teams to work from the latest information instead of outdated documentation.
2-B Example: Cross-functional task decomposition with clear Acceptance Criteria to enable parallel development.
Breaking Down Features for Cross-Functional Teams
Complex gameplay features require coordinated implementation across Engineering, Design, Art, Tech-Art, and QA workflows. The feature scope was decomposed into teams covering Engineering, Art, Design, and QA requirements.
Rather than waiting for one discipline to fully finish before another starts, the work was broken down to allow multiple teams to move in parallel. Clear acceptance criteria also helped reduce confusion around expected outcomes and made implementation easier to track.
In game development, blocked dependencies can slow teams down and create avoidable delays. To reduce this risk, the focus was placed on removing blockers early and sequencing work more intentionally.
Instead of starting all tasks at once, I prioritized the "Player Pawn" and "Proxy VFX" in our very first sprint. In this sequencing model, AI programmers would have a working Player Pawn to test against from the start, making early testing and iteration easier for the team.
3-A Example: Critical path visualization mapping technical dependencies across art and engineering timelines.
3-B Example: Dependency tracking structure used to reduce blockers between teams.