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
1AI Makes You a DevTest Engineer But Testing Work Gets Heavier AI makes DevTest engineering accessible to everyone, but core testing work remains untouched—and AI-generated code actually adds hidden risks. A frontline tester explains why.
2The Underlying Logic of Software Testing: Core Skills & Black‑Box Strategies Understanding the underlying logic of software testing: black‑box input‑output model, 2W1H analysis, tester core skills, and invisible outputs. Essential for QA engineers.
3Value and Obstacles of Continuous Automation | Guide 2026 Learn the key value of continuous automation (testing, deployment, release) for agile teams, plus common obstacles and practical solutions to implement it successfully.
4How to Write a Test Plan | QA Best Practices from an OMS Expert Discover a step-by-step guide on how to write a test plan for complex systems (OMS). Learn 5 key phases, evolving focus points, and QA strategies to ensure quality & project rhythm.
5A Brief Discussion on Precise Testing: Concepts, Industry Practices & ICBC Development This article discusses the background, core objectives of precise testing, analyzes industry practices of iQiyi and ByteDance, and introduces ICBC's current status and future construction of precise testing, helping to understand the application and development of precise testing in fintech.