Thai Dinh Chinh CV
All work
Project Lead · Product

Outline — high-concurrency multiplayer game engine (capstone, Top 4)

Leading a five-person Agile team to build and optimise a real-time, high-concurrency multiplayer game engine — as project lead, analyst and developer.

Outline — high-concurrency multiplayer game engine (capstone, Top 4)
Role
Project Lead · BA · Developer
Timeline
05/2025 – 10/2025
Team
5 members
Stack
Photon Fusion 2 · Unity · C#
Tools
Jira · Figma · Draw.io
Context

Capstone: Multiplayer Outline Survival Battle Game

“Outline” is a multiplayer survival battle game built as our software-engineering capstone at FPT University, using Photon Fusion 2 for online play. The technical heart of the project was a high-concurrency, real-time simulation engine. The project was ranked Top 4 among capstone projects.

Problem

Real-time concurrency with a small team and a fixed deadline

  • Real-time multiplayer requires precise definition of system behaviours, data flows and performance requirements — ambiguity here becomes desync and lag.
  • A five-person team had to balance engine optimisation with gameplay features inside one semester.
  • Stakeholders (supervisors, reviewers) needed regular demos and clear documentation.
My role

Lead, analyse, build

  • Led an Agile team: sprint planning, backlog refinement and stakeholder demos.
  • Led system-level requirement analysis and optimisation for the high-concurrency simulation engine.
  • Worked with developers to define system behaviours, data flows and performance requirements.
  • Contributed to implementation alongside the team.
Process

Engineering rigour, Agile rhythm

STEP 01

Requirements

System-level requirements: tick rate, state sync, authority model, performance budgets.

STEP 02

Design

Data-flow and behaviour definitions shared with developers before implementation.

STEP 03

Sprints

Short sprints with backlog refinement and demo at the end of each.

STEP 04

Optimise

Profiling and optimisation passes on the simulation engine.

STEP 05

Document

Capstone project document and demos for supervisors and reviewers.

Artifacts

Deliverables

Capstone project documentRequirements, architecture, data flows and test results.
System behaviour & data-flow definitionsShared contracts between gameplay and networking.
Sprint backlogRefined stories with performance acceptance criteria.
Playable buildMultiplayer survival battle on Photon Fusion 2.
Outcome

Delivered, demonstrated, ranked Top 4

Top 4
capstone project — FPT University
5
person Agile team led
Real-time
high-concurrency engine implemented and optimised
Demos
regular stakeholder demos through the project
Learnings

Takeaways

  • Performance requirements need numbers, not adjectives — “smooth” is not an acceptance criterion.
  • When you lead and build at the same time, protecting time for planning is the hardest and most valuable discipline.
  • Frequent demos keep a technical project honest about what is actually working.