Game Development Death March

One reason I don't want to work as a game developer. [Link]

Horror stories are constantly surfacing about the lengths game developers sometimes have to go in order to ship a game on time. The worst involve up to 85-hour work weeks—12 hours a day, seven days a week—which is more than double the century-old 40 hour per week standard. Extended periods of crunch can last up to a year, with sustained 60-hour weeks. This practice has earned a markedly less innocuous name than "crunch time." It's called "the death march."

In some cases it's nearly dehumanizing: the closure of All Points Bulletin developer Real Time Worlds in September of last year left more than 185 employees out of a job. They were welcomed to the end of a particularly long crunch period by pink slips rather than profit sharing and bonuses.

In an industry that is steadfastly focused on fun, it seems counter-intuitive that video gamers should be the ones who have to worry about the sagging quality of life of those who make the games. No kid should ever have to wonder if Santa Claus is cracking the whip too hard on his elves to make the Christmas Eve shipping deadline, but despite widespread outrage over revelations from ex-employees describing poor conditions, the status quo remains largely unchanged and unchallenged.

Bad Santa

On the surface it's simple. Studios push their employees harder to finish projects faster. Less time spent on development means less time employing a full team of artists, programmers, designers, testers etc.

This is one of the principle factors perpetuating the use of crunch by management. The vast majority of employees working in the development of video games are salaried employees and do not receive overtime for additional hours spent at the office. A recent poll of over 350 industry professionals taken by developer-focused website Develop, showed that 98 percent of those polled received no compensation for their overtime work.