Project Management by Industry guide · IT, software and digital
Game Development Project Management: Phases, Roles and Tools
Game development project management is the planning and coordination of a video game from concept and pre-production through production, testing, platform certification and launch, and often years of live operations afterwards. It blends software project management with creative production: a game must be technically stable, but it also has to be fun, which can only be judged by playing it.
Key takeaways
- Game development project management blends software delivery with creative production, and the fun must be found through playtesting.
- Milestones and publisher gates set the outer plan; Scrum and Kanban run the work inside it.
- A vertical slice proves vision and production cost before full production.
- Plan realistically and keep a cut list to avoid crunch.
What makes game development project management different
- Fun is discovered, not specified. Core mechanics must be prototyped and playtested, and some ideas will be thrown away.
- Many disciplines. Design, programming, art, animation, audio, writing, QA and production all depend on each other.
- Content pipelines. Large volumes of assets (characters, levels, animations, sounds) flow through repeatable production steps.
- Publisher and platform milestones. Funding is often released against agreed milestones, and console platforms require games to pass certification before release.
- Fixed launch windows. Marketing campaigns, events and seasonal sales make release dates hard to move.
- Live service. Many games are updated after launch with new content, events and fixes, turning the project into an ongoing operation.
Phases of game development
| Phase | What happens | Key outputs |
|---|---|---|
| Concept | Pitch the idea, target audience, platforms and business model | Pitch, concept art, high-level budget |
| Pre-production | Prototype core mechanics, set the art style, build tools and pipelines, plan production | Playable prototype, vertical slice, game design document, production plan |
| Production | Build the content and features at scale | Feature-complete and content-complete builds |
| Alpha | All key features playable; focus shifts to completing content and fixing major issues | Alpha build |
| Beta | Content complete; focus on bug fixing, polish, performance and balancing | Beta build, playtest data |
| Certification and launch | Final candidate builds, platform submission and approval, launch preparation | Gold master / release build, launch plan |
| Post-launch and live ops | Patches, updates, events and new content | Update roadmap, live metrics |
A vertical slice is a short, polished section of the game at final quality. It proves the vision, the pipeline and the cost per unit of content before full production begins, and it is often a key publisher milestone.
Key roles
| Role | Main responsibilities |
|---|---|
| Executive producer | Overall responsibility for the project, budget and relationships |
| Producer | Plans and runs production day to day: schedules, priorities, risks, communication |
| Game director / creative director | Owns the creative vision and the player experience |
| Discipline leads (design, art, engineering, audio, QA) | Plan and review work in their area and set quality standards |
| Designers, programmers, artists, animators, sound designers | Create the game's features and content |
| QA testers | Find, reproduce and verify bugs; check compliance requirements |
| Publisher producer | Represents the publisher, reviews milestones and coordinates marketing and platform relations |
| Live ops and community team | Run updates, events and player communication after launch |
In game studios the project manager is usually called a producer, though larger studios may also have project managers working under producers.
Methodologies that fit
| Approach | Use in game development |
|---|---|
| Scrum | Feature teams in production working in sprints, with playable builds reviewed at each sprint review |
| Kanban | Art and content pipelines, bug fixing in beta and live ops tasks; see Kanban boards |
| Milestone-based (stage-gate) plan | Publisher milestones and funding gates set the outer structure |
| Rapid prototyping | Short, throwaway experiments in concept and pre-production to find the fun |
| Hybrid | Most studios: milestone plan outside, Scrum and Kanban inside |
For how Agile ideas carry over from general software work, see Agile software development and Agile for creative teams.
Essential documents and templates
| Document | Purpose | Template |
|---|---|---|
| Game design document | Living description of mechanics, systems and content | Business requirements document template adapted as a GDD |
| Production backlog | All features and content, ordered by priority | Product backlog template |
| Milestone schedule | Publisher milestones, phases and key dates | Gantt chart template, project schedule template |
| Sprint plans | Sprint goals and selected work | Sprint planning template |
| Content pipeline board | Assets moving through each production step | Kanban board template |
| Budget | Team costs, outsourcing, licences and tools | Budget template |
| Risk register | Technical, creative, staffing and schedule risks | Risk register template |
| Post-mortem | Lessons from the project | Lessons learned template |
KPIs for game development
| KPI | What it measures | Typical use |
|---|---|---|
| Milestone acceptance | Milestones accepted by the publisher on first submission | Delivery reliability and funding |
| Feature and content completion | Planned features and assets completed | Progress toward alpha and beta |
| Open bugs by severity | Count and trend of critical, major and minor bugs | Readiness for beta, certification and launch |
| Bug find and fix rate | Bugs opened against bugs closed per week | Whether the team is converging on release |
| Performance targets | Frame rate, load times, memory use on each platform | Technical quality |
| Crash rate | Crashes per session or per hour played | Stability before and after launch |
| Player retention (live games) | Share of players returning after 1, 7 and 30 days | Live ops and content planning |
Common challenges
- Crunch. Long periods of excessive overtime harm people and quality. Protect against it with realistic scope, early vertical slices, clear cut lists and buffers before milestones.
- Feature creep. Keep a prioritised backlog and a visible 'cut list' so the team agrees what goes if time runs short; see scope creep.
- Pipeline bottlenecks. Measure throughput per pipeline step and balance capacity across disciplines; see theory of constraints.
- Late discovery that the game is not fun. Playtest early and often, from prototype onwards.
- Certification failures. Learn platform requirements early and run compliance checks well before submission.
Software for game development project management
Studios rely on game engines, version control systems that handle large binary assets, bug trackers and build pipelines. Production teams need backlogs, sprint boards, milestone timelines and dashboards that show progress across disciplines.
Many engineering-led studios use Jira for tasks and bugs. Wrike, the strongest all-in-one option in our tool rankings, suits studios and publishers that need milestone timelines, content pipeline boards, asset proofing and approvals alongside marketing and localisation work in one place.
Free templates for this topic
Frequently asked questions
What is game development project management?
Game development project management is planning and coordinating a game from concept and pre-production through production, testing, certification and launch to live operations.
What are the phases of game development project management?
Concept, pre-production, production, alpha, beta, certification and launch, and post-launch live operations.
Who does game development project management in a studio?
Usually producers, supported by discipline leads; larger studios may also employ project managers who work with the producers.
Is Scrum used in game development project management?
Yes. Many studios run feature teams in Scrum sprints during production and use Kanban for content pipelines, bug fixing and live ops.
What is a vertical slice in game development project management?
A short, polished section of the game at final quality that proves the vision, pipeline and production cost before full production.
What KPIs are used in game development project management?
Milestone acceptance, feature and content completion, bugs by severity, bug find and fix rate, performance targets, crash rate and player retention for live games.
How can game development project management reduce crunch?
By setting realistic scope, proving production costs with a vertical slice, keeping a cut list, protecting buffers and tracking bug trends early.
What documents are used in game development project management?
A game design document, production backlog, milestone schedule, sprint plans, content pipeline boards, budget, risk register and post-mortem.
What software is used for game development project management?
Game engines, version control for large assets, bug trackers such as Jira and a planning platform such as Wrike for milestones, pipelines and approvals.
What is the difference between alpha and beta in game development project management?
At alpha, key features are playable; at beta, the game is content complete and the focus moves to bug fixing, polish and performance.
What is platform certification in game development project management?
Console platform holders test submitted builds against their technical requirements; the game must pass before it can be released on that platform.