3 ms·
> But the programming team continually worked towards shipping in only two months for the next fourteen months! Every time I hear these stories from game devel
by ryandrake 4y ago
> But the programming team continually worked towards shipping in only two months for the next fourteen months!
Every time I hear these stories from game developers, I just shake my head and think “where the hell is the project manager?” It’s as if the whole game industry just doesn’t believe in rigorous, disciplined project management, and instead always relies on crunch time, 48 hour days and an endless supply of naive youth to burn out. Nobody benefits when you keep saying “we’re two months from shipping” for 14 months.
- xmprt 4y agoStarcraft was released in 1998. The game development industry was still pretty new and nowhere near the size it is today. Also, modern project management strategies weren't really used much back then and even if they were, they probably wouldn't be found in a gamedev studio where headcount was really tight.
- wizofaus 4y agoIs there actually solid data modern project management strategies work better than the ones from 20 odd years ago? Best run project I think I ever worked on was from the late 90s.
- mixmastamyk 4y agoPM hasn't changed much besides trending towards smaller batches, the difference is more business folks are aware there are strategies at all.
- wizofaus 4y agoThat "smaller batches" change has been pretty extreme though. My current company is on the bandwagon of being able to release new features every day, even if we have to jump through hoops and severely compromise quality to make it happen. I appreciate being able to avoid the disadvantages of 6-12 month long release cycles, but surely there's some sweet spot between daily and yearly (which almost certainly varies depending on the product and company developing it).
- mixmastamyk 4y agoAfter thirty years, trends tend to add up!
- melling 4y agoDo you mean “release early, release often”? https://en.m.wikipedia.org/wiki/Release_early,_release_often https://en.m.wikipedia.org/wiki/Release_early,_release_often
- wizofaus 4y agoRelease early/often is fine as a philosophy but there need to be better guidelines around how early/often actually makes sense, rather than assuming just because company X releases product Y multiple times a day it must be something to aim for.
- deepsun 4y agoOn the other hand, early software development resembled more established hardware development at the time, with much higher quality requirements. So I would expect otherwise. Maybe 1998 was the tipping point?
- 29athrowaway 4y agoModern project management is mostly predicated on fallacious dogmas and pseudoscience.
- wizofaus 4y agoTrust me that's not exclusive to game shops. Even an open source project (but that is run by a for-profit organisation) I've been involved in for the last year and a half has been similar, even though anyone could surely see 6 months ago it wasn't shipping any time soon. They're still staying 2 months away (I reckon 4 minimum now).
- 29athrowaway 4y agoLet's be honest: most project managers cause more problems than they solve. They would do stuff like downplaying all the problems and ship a broken game, or pulling developers into redundant meetings to waste their time. A software engineer that is proficient at memory management, multithreading, pathfinding, networking, graphics, linear algebra, computer science, data structures and algorithms, and all the other stuff involved in programming a game, doesn't want to listen to a person that not only doesn't understand any of that, but feels entitled to have an opinion on how tasks involving that should be triaged and executed, and sometimes are insufferable people obsessed with hierarchy and domination to compensate for not understanding things. Want your project to be fast? Get out of the way. Let engineers collaborate and figure it out. And most importantly, stop trying to see software projects through the perspective of oversimplification. Good project managers exist, but most are not. Hear it from Steve Jobs if you need to: https://www.youtube.com/watch?v=fj0hpsJvrko https://www.youtube.com/watch?v=fj0hpsJvrko
- deleted 4y ago[deleted]
- rocqua 4y agoThat is not what project managers do. Project managers set priorities, communicate requirements to developers, and communicate expected timlines, problems, needed changes, and other developer-surfaced issues back up the chain. If engineers (like me) are left alone to work on it, either one of them becomes de-facto project manager, or you probably end up with a well-engineered product and wholly unsatisfied customers.
- 29athrowaway 4y agoIf one engineer becomes a de-facto project manager is because the team lets them because they realized it's in their best collective interest. And that's not a bad thing.
- rocqua 4y agoThat's a great thing, presuming that engineer actually enjoys the task. I know many people who pick up the task out of necessity, but dislike it and burn-out if forced to do too much of it.
- _the_inflator 4y agoIt is a general phenomenon, nothin the game industry has exclusive rights to. Stubbornness, cognitive dissonance are my explanations. I witnessed quite a few projects, whose deadlines got postponed for more than 6 month. Now comes the exciting part. These managers had a track record of postponing or more neutral: experiencing delay. Instead of fewer crunch time during the next projects, they stick to their previous behavior instead of trying to learn. There you go, learned self-inflicting pain.
- kzrdude 4y agoI think it goes high up - all the way up to the company's relationship with its investors (venture capital or investing customers both). Investors and customers stick around because the company promises that it's just around the corner. Then that's unrealistic and the delays start racking up. (This is at least what I have seen, when deadlines come from all the way from top management and everyone below tries to squeeze their plan into those deadlines.)
- deleted 4y ago[deleted]
- fragmede 4y ago> Nobody benefits Somebody benefits alright, just not the developers who are on the death march.
- kzrdude 4y agoStarCraft was developed 1995-1998. That's something to keep in mind. This is not today