Why do video games get delayed so often?
Because games are among the hardest software projects to schedule, and the industry has slowly concluded that delaying is usually cheaper than shipping broken.
Why estimation is so unreliable here:
Games must be fun, and fun cannot be specified in advance. Most software has a definition of done — the invoice calculates correctly or it does not. A game mechanic either feels good or does not, and you cannot know until it is built and played. Systems get built, tested, discarded and rebuilt, and none of that iteration is visible in a Gantt chart.
Everything is interdependent. Change a core movement system late and animation, level design, combat balance and audio all need revisiting. Dependencies fan out in a way they rarely do in other software.
Content scales badly. A large open world requires enormous volumes of art, audio, writing and testing, and each addition multiplies QA surface area.
Platform breadth. Shipping across several consoles, PC hardware permutations and sometimes older generations multiplies optimisation and certification work.
Announcements come far too early. Dates are frequently attached to marketing beats, funding rounds or investor expectations rather than to engineering estimates — sometimes years ahead, before the game is fully designed.
Why delays became more acceptable: several high-profile launches in poor technical condition caused refunds, store removals and lasting reputational damage. Against that, a delay costs additional development months but protects the release. Publishers increasingly find the arithmetic favours waiting.
What a delay usually means for players is more finishing and polishing work. It does not necessarily indicate a troubled project, and a game delayed twice may still be excellent.
The human cost matters too. The alternative to delay is often crunch — sustained mandatory overtime — which the industry has faced significant criticism over.