Customer Cases
Pricing

The Challenges and Illusions of Developing AAA Games —— Part 3

In this article, we will explore four common deadline-setting methods, discussing their advantages and disadvantages, and providing insight into how these approaches can shape the dynamics within a game development team.

The previous article, "The Challenges and Illusions of Developing AAA Games - Part 2," mentioned the goodwill of leadership. Now, as the leader steps up to the plate, the pressing question arises: when will your game be released?

Various Methods for Setting Deadlines in Game Development

1. Reserve a Safety Margin

One effective management technique is to reserve a safety margin for deadlines. By setting a deadline with a buffer period, the team can account for any unforeseen issues or extra polishing needed. However, this approach may lose its effectiveness if the team catches on to the producer's strategy and starts to anticipate the extra time.

2. Squeeze Potential

Squeezing potential involves setting a tight deadline to push the development team. This method is commonly used in the gaming industry, as it takes advantage of the fact that overtime often doesn't require additional pay. However, excessive overtime can have negative effects on the team, such as reduced personal growth and increased acting skills to cope with the workload.

3. Casual Delay: "When It's Done"

Some more relaxed companies may adopt a casual approach to deadlines, stating that the game will be released "when it's done." This can lead to projects dragging on for years, and in some cases, never actually being completed. The technology and concepts may become outdated, and the game may serve as a negative example for the industry.

4. Small Steps, Quick Iterations

Taking small steps and iterating quickly is another way of saying 996 or 997, an even stronger version of squeezing potential. This approach involves releasing the game with limited content and continuously improving it based on market feedback. While this can lead to more targeted improvements and better games, it also requires an intense workload for the development team.

Balancing Deadlines and Team Morale

Game producers need to balance the need for deadlines with the impact on team morale. Occasional overtime to meet version milestones is acceptable, but long-term overtime can have detrimental effects on the team's personal growth and honesty. Regularly summarizing the success and failure of each version allows everyone time to recover and reflect on how to improve next time.

In conclusion, setting deadlines in game development can be a delicate balance between pushing the team to achieve their goals and maintaining a healthy work environment. Different methods may work better for different teams and projects, but producers need to consider the long-term effects on both the game and the team members.

To be continued......

Latest Posts
1Hybrid Remote Device Management: UDT Automated Testing Implementation at Tencent Learn how Tencent’s UDT platform scales hybrid remote device management. This case study details a 73% increase in device utilization and WebRTC-based automated testing workflows for global teams.
2How AI Is Reshaping Software Testing Processes and Professional Ecosystems in 2026 Discover how AI is reshaping software testing processes and careers in 2026. Learn key trends, emerging roles, and essential skills to thrive in the AI-driven QA landscape.
3WeTest at GDC 2026: AI Automated Testing Ushers in a New Era of Game Quality WeTest at GDC 2026 showcases a revolutionary AI Automated Testing Solution that transforms game quality assurance. Learn how WeTest's AI Test Agent Platform enables scalable quality production through computing power, delivering controllable, reproducible, and intelligent testing capabilities.
4Precision Testing in Practice: A Fund Team's Journey from Experience-Based to Data-Driven Quality Assurance Learn how Shenwanhongyuan Securities implemented precision testing to reduce regression testing by 67%. This technical guide covers JaCoCo implementation, method-level code mapping, and intelligent test case recommendation for financial services applications.
5How to Do Performance Test Monitoring: Key Metrics & Tuning Tips Learn how to do performance test monitoring effectively. Discover key metrics (RT, TPS, IOPS), identify CPU/memory/database bottlenecks, and follow step-by-step tuning tips for stable, efficient systems.