Game development stages: a full production cycle

Game development stages are the structured phases a studio moves through to turn a concept into a released, supported product. The widely used framework has six phases: pre-production, production, alpha QA, beta, launch, and post-launch live ops. Each phase has its own deliverables, team composition, and acceptance criteria.

What are the stages of game development?

Most studios organize a project around six recognizable stages, each ending in a reviewable artifact. Pre-production produces the Game Design Document (GDD), a proof of concept (POC), and a playable prototype. Production builds the vertical slice and the alpha build, where core systems are feature-complete. The QA-driven alpha and beta phases harden the build through functional, regression, compatibility, and performance testing. Launch covers the release candidate, soft launch in a limited region, and full release. Post-launch live ops keeps the title alive with patches, balance updates, seasonal content, and platform-certification follow-ups. The six-stage view is helpful because it lets producers map budget, team size, and risk to a known timeline. Studios that skip pre-production usually pay for it later in rework during production, and studios that compress beta tend to ship the kind of stability issues that erode reviews in the first week.

Six-stage framework with duration, deliverables, and lead roles:

Pre-production: GDD, POC, and prototype

Pre-production is the planning phase where a studio decides whether the game is worth building and how it will be built. The phase ends with three artifacts: a Game Design Document (GDD) that describes mechanics, systems, monetisation, and scope; a proof of concept (POC) that validates the riskiest gameplay loop in code; and a playable prototype that lets stakeholders feel the core fantasy. For a mid-budget mobile title this stage runs two to four months, for a multiplayer PC title four to six months. The team is small at this point, usually a game designer, a tech lead, an art director, and a producer. Decisions made here have outsized weight: a vague monetisation model or an undefined target frame rate at the end of pre-production almost always becomes a production bottleneck later. A clear GDD also speeds vendor selection if any production work will be outsourced, because external teams can scope from documented requirements rather than verbal briefs.

Typical pre-production deliverables:

Production: vertical slice to alpha

Production is the longest phase and the one that consumes the largest share of budget. The team grows to its full size, often three to five times the pre-production headcount, and content pipelines are pushed to capacity. The phase typically begins with a vertical slice, a polished representative segment of the game that proves the production pipeline can hit the target quality bar. From there, teams build out levels, characters, animations, and systems in iterative sprints. The phase closes when the build reaches alpha, the point at which every planned feature is in the game in some form, even if not yet polished. Production is also where engagement models matter most for outsourcing. A Co-development model lets an external team own a defined system (for example, multiplayer netcode or character animation), while a Team Extension model adds named specialists to the internal pipeline under the studio's own producers. Engine choice (Unity or Unreal Engine) is usually locked at the start of production, because changing later is expensive.

Alpha and beta QA

QA is a continuous activity, but two formal milestones sit between production and launch: alpha and beta. Alpha is feature-complete: every system planned for the release version is in the build, and QA moves from smoke testing to structured test plans. The team runs functional testing of gameplay systems, regression suites after every merge, compatibility testing across the device matrix, and performance testing against the frame-rate and memory budgets. Beta is content-complete: art and audio assets are final, localisation strings are locked, and certification testing for first-party platforms (PlayStation, Xbox, Nintendo, App Store, Google Play) begins. Beta is where build stability is measured against a crash-free session rate target, usually 99.5 percent or higher for a mobile soft launch. Studios that treat alpha and beta as overlapping phases rather than sequential ones ship with fewer last-minute regressions, because performance and stability issues surface while the team still has time to address them.

Test scopes typically covered before launch:

Launch: release candidate, soft launch, full release

Launch is the shortest stage but the highest risk. It begins with a release candidate (RC), a build that QA and production both believe could ship. From there, most modern projects run a soft launch in one or two regions to validate retention, monetisation, and server load with real players before the worldwide release. A soft launch typically runs four to twelve weeks. Data from this window drives the final tuning pass: economy balance, onboarding flow, ad placement, and server capacity. Once the soft launch hits its target metrics, the team locks the gold master and pushes the global release. Launch coordination also covers store assets (screenshots, trailers, store descriptions), platform certification sign-off, day-one patch planning, and customer-support readiness. A well-rehearsed launch has a documented rollback plan, an on-call rotation for the first 72 hours, and dashboards that show install rate, crash rate, ARPU, and retention in real time.

Post-launch live ops and content updates

Post-launch is the longest stage by elapsed time, often longer than pre-production and production combined. The live-ops team owns patches, balance changes, seasonal content, events, and platform-certification updates. For free-to-play mobile and PC titles, content cadence usually runs two to six weeks between meaningful updates, with smaller hotfixes between them. The team composition shifts: many production specialists rotate off, while live-ops engineers, community managers, data analysts, and a smaller content squad rotate in. Post-launch is also where outsourcing patterns differ from production. A live-ops engagement is usually long-running and lean, with a stable team of named specialists who learn the codebase deeply. Backend reliability, anti-cheat, A/B testing infrastructure, and analytics pipelines become the dominant engineering surface. A studio that documents the production codebase well during the previous stages spends much less effort onboarding live-ops engineers, which is a hidden but real production cost saving.

Engagement models mapped to project stages:

Roles, tools, and risks across game development stages

Each stage has a recognizable role mix and a recognizable risk profile. Pre-production risk is scope ambiguity, production risk is pipeline throughput, QA risk is regression debt, launch risk is platform certification and server capacity, and live-ops risk is content cadence slipping. Mapping roles and risks to stages early lets producers staff and budget against known failure modes rather than reacting to them.

Lead roles and tools by stage:

1. Pre-production roles: game designer, tech lead, art director, producer. Tools: Confluence, Miro, engine prototypes, paper design
2. Production roles: gameplay programmers, technical artists, animators, level designers. Tools: Unity or Unreal Engine, Perforce or Git LFS, Jira
3. QA roles: QA lead, automation engineer, performance engineer, compliance specialist. Tools: TestRail, Jenkins, device labs, profilers
4. Launch roles: release engineer, publishing producer, community lead. Tools: store back-offices, dashboards, on-call rotation tools
5. Live ops roles: live-ops engineers, data analyst, community manager. Tools: A/B testing platforms, analytics pipelines, CMS for content

About Game-Ace

Game-Ace has been delivering custom production work since 2005, with 120+ in-house specialists and 200+ delivered games across mobile, PC, web, and iGaming. The studio supports projects at any stage of the framework above, from GDD authoring in pre-production to live-ops engineering after release. For studios that want a single accountable vendor across the cycle, Game-Ace offers full-cycle game development. Selected work across genres and platforms is available in the Game-Ace portfolio, with further case studies under NDA. To discuss scope, milestones, or a specific stage of the production cycle, contact our team.