← All guides

How to Use a Gantt Chart for Video Game Development

Learn how to build a game production Gantt chart covering pre-production, Alpha, Beta, Gold milestones, platform cert, and post-launch patch planning.

How to Use a Gantt Chart for Video Game Development

Game development is a multi-disciplinary engineering and creative project that runs on parallel tracks for 12 to 48 months. Art, programming, audio, QA, and marketing each have their own cadence, their own dependencies, and their own blocking risks. A Gantt chart is the tool that holds all of those tracks in one view -- letting leads see how a delay in character rigging might push the Alpha milestone, or how a platform certification queue affects the ship date.

This guide covers building a game production Gantt from GDD approval through post-launch patch cadence, with attention to the milestone structure that defines professional game development.

Pre-Production Phase

Pre-production is where the Gantt chart prevents the most common game development failure: starting full production before the design is stable. The pre-production track runs approximately 2-4 months for a mid-size title.

Game Design Document (GDD) approval is the anchor task. Everything in production depends on a stable, approved GDD. Do not start assigning art tasks or beginning engine architecture until the GDD is signed off by the creative director and production leads.

Technical Design Document (TDD) follows. This is where engine selection happens -- Unity, Unreal, or Godot each have implications for team hiring, render pipeline choices, and platform compatibility. The TDD documents target platform specs (PC, console, mobile), graphics API choices, networking architecture if multiplayer, and any middleware commitments (physics engines, audio middleware like Wwise or FMOD). Engine and middleware decisions belong on the critical path because changing them mid-production is catastrophic.

Concept art and visual bible runs in parallel with the TDD. The visual bible establishes art style, color palettes, character design language, and environment tone. Art production cannot begin at full capacity until the visual bible is approved.

Prototype milestone closes pre-production. A working prototype demonstrates core gameplay loop, validates the TDD's technical decisions, and gives leadership confidence to greenlight full production. Plan 4-6 weeks for prototype development after TDD approval.

Production Milestones

Professional game development runs on four named milestones. These belong as anchor points on your Gantt chart with hard dates and entry criteria.

Alpha milestone means all features are implemented and playable, but assets may be placeholder or low-quality. At Alpha, every room can be entered, every weapon can be fired, every UI screen exists -- but textures might be gray boxes and audio might be temp music. Alpha is the software engineering finish line.

Beta milestone means feature-complete with final assets, ready for full QA. At Beta, every asset is in its final state. All animation, all audio, all UI/UX is final quality. The build can be played end-to-end. QA escalates from functional testing to full regression and performance testing at Beta.

Gold milestone (sometimes called Release Candidate) is the cert candidate. All bugs are at acceptable severity -- no crash bugs, no progression blockers. Platform certification submissions happen from Gold.

Gold Master is the cert-approved build, ready to manufacture (physical) or deploy (digital). This is the finish line.

Plan backward from the intended ship date, accounting for platform certification queues, to find your Gold milestone date -- then work backward through Beta and Alpha.

Parallel Tracks Gantt Excels at Modeling

The core value of a Gantt chart in game development is modeling parallel production tracks with explicit dependencies between them.

Art Track

Concept art → 3D modeling → rigging → animation → VFX → UI/UX. This sequence has strict dependencies: you cannot rig a character before the 3D model is complete, and you cannot animate before rigging. The art track also has massive scope -- a 40-hour game may require thousands of unique assets. Break this track into character art, environment art, prop art, UI/UX, and VFX sub-tracks. Each sub-track has its own lead and its own milestone schedule.

Programming Track

Core systems → gameplay mechanics → AI → networking → platform integration. Core systems (input, physics, rendering pipeline, save system) must be complete before gameplay mechanics can be built on top of them. Platform integration -- especially console certification requirements for achievement systems, save data handling, and certification technical requirements (CTRs) -- is often underestimated and should be planned explicitly in the final months before cert submission.

Audio Track

Sound design → music composition → voice recording → mix and implementation. Voice recording has significant lead time: casting, script finalization, studio scheduling, recording sessions, and editing. For narrative games, voice recording often needs to be scheduled 3-4 months before Beta because the resulting audio assets need implementation and QA time. Music composition can start earlier in production but final mixing happens post-Beta.

QA Track

Test plan development → functional testing → performance testing → platform certification testing. QA ramps up throughout production but accelerates dramatically at Beta. Platform certification testing (CTS for PlayStation, XR for Xbox, Lotcheck for Nintendo) requires dedicated QA staff who understand each platform's specific technical requirements. Build this ramp into the Gantt chart explicitly -- most studios understaff QA early and scramble at Gold.

Platform Certification Track

Platform certification is the most common cause of missed ship dates in console game development. Certification queues are real, they are not compressible by the developer, and they must be built into the schedule.

Sony's PlayStation cert process (the Submission, Evaluation, and Report cycle) typically takes 2-4 weeks per submission, and most games require 2-3 submission rounds before passing. Plan 6-8 weeks of calendar time from first cert submission to cert approval for a typical title.

Microsoft's Xbox certification (Xbox Certification Submission, or XCS) runs on a similar timeline. Nintendo's Lotcheck is known for strict technical requirements and frequently requires multiple submission rounds -- plan 8 weeks minimum.

For PC via Steam, Valve's review process is much shorter (2-5 days), but Steam deck verification and age rating submissions (ESRB, PEGI) add lead time.

For mobile, the Apple App Store averages 2-3 days for review, and Google Play is typically under 24 hours, but both can reject for policy violations that require code changes and resubmission.

The practical implication: if your ship date is December 1, your first cert submission for console must go out by early October at the latest. Your Gold milestone must be 2 weeks before that to allow QA validation of the submission build. Work backward from there to find Beta and Alpha.

PERT Analysis on Top of Gantt

Game development has uncertainty that construction does not. Feature scope creep, engine bugs, and creative direction changes are common. Layering PERT (Program Evaluation Review Technique) estimates on top of your Gantt chart accounts for this uncertainty.

For each major milestone, estimate three durations: optimistic (everything goes right), most likely, and pessimistic. The PERT formula (Optimistic + 4 × Most Likely + Pessimistic) ÷ 6 gives you an expected duration. Apply this to your critical path milestones -- Alpha, Beta, first cert submission -- and you will have a probability-adjusted schedule instead of a wishful one.

Critical path analysis matters in game development because delays compound. If Alpha slips 6 weeks, Beta slips at least 6 weeks, cert submission slips, and the ship date either slips or the team crunches. Identifying the critical path (usually the art track for narrative games, the programming track for physics-heavy games) tells you where schedule risk lives and where to focus resources.

Release Management

Between Gold Master and launch, the release management track includes:

  • Manufacturing for physical editions: 4-6 weeks for disc production and distribution logistics
  • Digital store submission: store build uploaded, store page live, pre-orders open
  • Review embargo: press builds distributed to outlets under NDA, embargo lift date aligned with marketing campaigns
  • Influencer and content creator preview: separate builds under separate embargo
  • Launch day support: server monitoring (for online titles), day-one patch coordination, customer support staffing

Day-one patches are now standard practice. Plan a parallel track for the day-one patch running alongside cert of the base game. The day-one patch can fix issues discovered during cert testing that do not block cert but do affect player experience.

Post-Launch Patch Cadence

Game development does not end at launch. Map the first 90 days of post-launch on the Gantt chart:

  • Week 1: hotfix window (critical bugs and crashes)
  • Week 2-4: first patch (community feedback, performance issues, balance)
  • Month 2: content update or seasonal event (if applicable)
  • Month 3: second major patch or DLC announcement

A Gantt chart for post-launch planning ensures the team knows what comes next before launch day, rather than scrambling reactively when player feedback arrives. Assign a post-launch producer who owns this track while the core team transitions to next project pre-production.

Building the Gantt Chart

Start with the ship date and work backward. Lock the platform cert submission date first (the most fixed external constraint), then derive Gold, Beta, and Alpha dates. Build art, programming, and audio tracks to meet those milestones, and identify where parallel tracks create shared resource contention.

gantt-chart.io lets you build this structure with multiple swimlane rows, link dependent tasks, and see the critical path automatically highlighted. Start with the four milestone anchors, add tracks for each discipline, and connect the dependencies between them.