this post was submitted on 29 Apr 2025
134 points (97.9% liked)
Games
38883 readers
873 users here now
Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.
Rules
Authorized Regular Threads
Related communities
Video games
Generic
- Gaming: Our sister community, focused on POC and console gaming. Meme are allowed.
- Cozy games: Because not everything has to explode to make a good game
- Photo [email protected]
Help and suggestions
- [email protected] : You are searching for a game, but can't remember the name? Someone will find it for you here.
- Video Game [email protected] : Can't find a game to play in among the hundred you already own? Find another one to add to your library here.
- Patient [email protected]: Gaming isn't only about having the latest great games. Good old games are there too.
Platform specific
- Linux gaming : For everything related to gaming on Linux platform, be it on Steam Deck or Desktop Linux.
- Steam Deck : A Steam Deck specific community
Game specific
Language specific
Others
PM a mod to add your own
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
As a project manager (well sort of, but did IT projects for a while, have multiple friends in the gaming manager): Yes and no.
From my point of view: The problem isn't the fact that games are art. While games have their creative side they also require good "brick and mortar work" in the back - as many games as went horribly wrong due to a lack of space for creativity went wrong due to a lack of "less than glamorous" brick and mortar work and overcreativity. (Most drastic example would be the reddit dragon MMO story)
This is actually a reason why people who are very invested in the subject matter of the project they manage often are horrible project managers - and vice versa people who have no clue can't be good PMs either.
Project management has one core component: Knowing when to ask whom. A good PM knows that the dev(or dev team lead) will always know better how long "feature X" will take. Of course I can try to learn how to do things... but that wouldn't help much as the exact dev or team will still have their individual speeds. But a good PM also will know when to ask someone else who is nore knowledgeable for advice or to confirm things. (I literally had an Dev trying to tell me a small feature would take two weeks. Fair enough. But interestingly enough two other Devs were fairly sure it takes 30min including documentation. Which sounded way more reasonable. Turned out said Dev always tried to pull these stunts with new PMs and his lead being on vacation)
A good PM will also know when to give people space for creativity - and defend this room towards the budget.
Sadly - and this is a problem existing on all sides around PM- in the end it all boils down to a simple thing: Everyone thinks they know better. The PM thinks they know the job of being a Dev(or engineer,etc. etc.) better than the actual people doing the job. And vice versa the Devs think they could do without PMs (they can't for larger projects it's impossible, for mid size projects often really inefficient) or know their job better.
Such is life.