IGDA Quality Of Life Survey Analyzes Game Developer Crunch

Thanks to the IGDA for its survey details discussing the problems videogame developers face trying to balance work crunch and family/relationships. A survey commissioned by the IGDA revealed "34.3% of developers expect to leave the industry within 5 years, and 51.2% within 10 years", and also noted: "Crunch time is omnipresent, during which respondents work 65 to 80 hours a week (35.2%). The average crunch work week exceeds 80 hours 13% of the time. Overtime is often uncompensated (46.8%)." The IGDA's Jason Della Rocca is quoted as suggesting: "While game development is a stimulating and rewarding career, the work conditions are often taxing, making it hard to sustain a balanced lifestyle and leading many senior developers to leave the industry before they've done their best work... it is not just the community that is affected - these issues also impact the quality of games produced." Are insane hours just part and parcel of working in games, or is there another way?

Comments

Personal experience

[almaon]

I worked at a well known, shovelware game dev studio. I won't say exactly where, to protect the innocent/guilty. But lets say it was a number one title around 97-99 timeframe.

The main cycle for this unsaid company was in shovel ware, low budget, 'value priced" (such a bastardization of the word 'value'), and equally low timeframe to build these games.

They'd produce about 8-10 of these crappy games a year, each game being alloted 2-3 months on average. So crunch-time was all the time, it wasn't uncommon to see their best and lead programmer working 80+ hours a week, sleeping under his cubicle desk.

Once in a rare while this is alright, but all the time got old. I left quickly and decided "This isn't for me" the pay is alright, but money is worthless if you don't have time to spend/enjoy it.

At the end of it all, it was just a nice way to get the bug out of my system. I always wanted to design games for a living, got my foot in the door and got it right back out. Fulfilled the dream, went on to do other things.

I enjoyed it more when it was just myself, hacking away at early games like Doom and Duke3D. No pressures, just fun like the games themselves.

Soon as yo umake your hobby your career, the pracitce often starts to taste sour and eventually bitter.

Re:Personal experience

[wibs]

I'm friends with a handful of people who worked on a particular game that fit into pretty much all of the evil categories of game development, It was the third installment of a trilogy which had just been bought by another company, so they were running it into the ground and hoping for money just because of the name. My friends spent a year of their life spending every waking moment (and a lot of sleeping ones) in the office, had the release date moved up 2 months in what was originally a 12 month plan (which is already pretty fast), and then the whole staff got fired a week before the publisher put it on the shelves. In other words, no bonuses based on sales, no dev staff to make (sorely need) patches or updates, and none of the big bonus milestones that would have been reached with the originally planned 2 months more of dev time.

Basically they threw away a year and a lot of pay, all for the benefit of having an unfinished and therefore not very impressive game on their resume. I wish I could say this was some sort of freakish breakdown in the game development industry, but from my experience and what I've seen this is par for the course.

Isn't this true for most software developments?

[antdude]

Non-game projects also make developers, QA people, etc. work long hours as well.

So whats new?

[ZorMonkey]

This has been the norm for at least a decade, probably more. Maybe this is the first time someone did a survey, but I've heard the horror stories for years.

The trouble is, programming games is "cool" and "fun". People dream about playing and writing games all day, and getting paid for it. So, the development companies have a huge pool of people they can recruit from. If you dont like your working conditions, they'll just hire someone else who will put up with it longer. Thats also why they can pay less on average for young programmers, they have plenty to choose from.

entertainment industry

[tolldog]

Sounds like the entertainment industry in general. When I was working on a small animated 3d feature film a few years back, I averaged over 80 hours a week for over a month. I peaked at over 100. My average week off peak was about 60. Crunch time kills. I know people that quickly quit the industry afterwards because it just isn't worth it.

The primary reason it happens is sliding deadlines, misunderstood goals and ill-prepared schedules. That and people being overly picky about parts of a project too early in the game.

I swore to myself that I was done with it. But I love the industry and got myself into a non-production role where I only work 50 hours a week. I am a much happier man now.

-Tim

Re:Too complex

[Sigma 7]

Games have become so complex: That is why developers need to work so hard, for so long, while spending so much money, to get games today finished. With so much complexity involved, many developers won't be able to keep up.

In almost every instance within the software industry (games or otherwise), an improperly planned project will end up either incomplete or behind schedule - especially if there are large groups working on the project.

While complexity does have a factor in delaying projects, it is minimal when compared to lack of planning.

What Brings the Dreaded Crunch

[MiceHead]

There are plenty of reasons why a studio might enter crunch-mode:

• Approaching holiday - Christmas brings about the hottest season in retail, and publishers want to capitalize on this by releasing new titles in time for this. The Christmas push is less pressing for smaller studios that distribute outside of retail.
• Media event - E3 is when all the gaming companies and all the gaming press come together and pretty much stand around in a competition to see who can avoid having a seizure (flash/audio). Or, such was my take on it. There's a huge PR incentive to have content prepared for this event; more eyeballs translates into more potential sales.
• Publisher-imposed milestone - Publishers can withhold payment or cancel projects outright if a team misses milestones; if you're nearing such a deadline, the extra hours may be the difference between a happy publisher and a cranky one.
• Competition - You might have a solid first-person shooter, but if it's released concurrent with Doom III or Half-Life 2, there's a good chance it'll be overlooked. If you own the UHF DVD, you'll hear Al Yankovic lament that his movie went up against Batman, Indiana Jones, Lethal Weapon II, among others. You may also have your favorite game that was underrated due to poor timing. (Fortunately, there's always the possibility of a sequel.)
• Budgetary constraints - Especially crucial if a development house is self-funding a title. If a generous publisher sees a promising project go over-budget, they might extend it. If an independent studio runs out of money for going over schedule, it must secure more financing.
• Loss of staff - This can be devastating at project-end. There's no time to train new staff; existing members must take up the slack.

Game development is a wonderful vocation, but as with anything, too much of a crunch (the death-march) results in burnout. There must be ways we can mitigate some of the above causes. Less reliance on outside investment is one, but maybe that's wishful thinking my part.

I found this story amusing, considering...

[Zoid]

I'm currently in my 14th hour at work. E3 is next week.

Working on a triple-AAA title requires that effort. The guys who made the LOTR movies put insane hours in as well. When you're making outstanding triple-AAA quality entertainment based media, be it movies, games, televisions shows, etc, you've got put the effort in to make it as good as it can be.

There are horror stories about publishers fucking developers with unreasonable deadlines. Fortunately, I work for a publisher that doesn't do that--the extended effort is for quality, not just for making the deadline. I count myself lucky, and I hope guys who did get fucked can find themselves working for a developer who has a good relationship with a publisher.

For me, I'm still here because I want to make the best game I can.