Comment on BioWare veterans confirm they were laid off by EA, including senior Dragon Age and Mass Effect devs
scrubbles@poptalk.scrubbles.tech 1 week ago
So EA put way too high of a sales target on the game, obviously held it back from becoming what it could be, and now are blaming the studio with layoffs, ensuring the next game will flop.
I don’t care what their “numbers” and “projections” were. The game was on the top 10 list in Steam. Even if it wasn’t an A+ game I’d say it looked like it at least hit Assassin’s Creed numbers, I’d hardly call that a failure. Sounds more like a failure to accurately predict, maybe they should fire their business analysts instead of the people who you know, make the games.
SARGE@startrek.website 1 week ago
But the business analysts are the most profitable group, anywhere! If you don’t believe me just hire a business analyst to analyze things and they’ll prove it to you!
luciferofastora@lemmy.zip 6 days ago
As a Data Analyst / Business Analyst, let me assure you: Not all of us are stupid (some are, for sure), but there’s only so much you can do about stupid managers. If they decide that a certain measure is key, it can be really hard to explain why it isn’t that important or where a certain distortion comes from. To compound this, some managers genuinely don’t understand their business processes and are unwilling to have it explained to them. They’ll make assumptions about how things work, then base their demands on those.
For an entirely made up example, consider a department manager looking to monitor a software development team’s workload. That workload, to them, consists of bug tickets and feature implementations. Not counted here are feature requests because, apparently, fielding them and discussing their feasibility isn’t actual development work. That’s management work, which is the Product Manager’s job… Except the Product Manager can’t unilaterally decide whether something is feasible without consulting those actually familiar with the code, taking up the developer’s time. On the other hand, since it’s an internally developed tool for other units, they can’t just say No to every request or else they risk people calling their team’s funding into question.
Now, you have the choice between frustrating yourself and annoying the manager by trying to explain all that, or gritting your teeth and just giving them the stupid chart on bugs closed and feature implementations completed over time. Guess which one is healthier for your employment prospects?
And we haven’t even started talking about the variance in effort of bug fixes or about non-feature work for code stability or QA. Eventually, we’ll reach the point where the measure becomes a target and you have to start reframing bug fixes as features and splitting features up into smaller features just to make the figures look nicer.
What I’m getting at is this: Sometimes, the analysts aren’t to blame, but the managers making decisions.
That’s not to say there aren’t absolutely shitty business analysts out there that will gladly figure out ways to polish the figures and then cash the check for making the figures look better.
Crotaro@beehaw.org 5 days ago
Thank you for that perspective. It seems to be somewhat similar and thankless to when I get tasked with taking microbio samples from the machines to check for contamination and then get grumpy department leads because the analysis results show over and over again that their cleaning procedure is inefficient.
luciferofastora@lemmy.zip 4 days ago
What, can’t you just… idk, check better to see how clean it actually is? That can’t be right, you probably got your samples contaminated. Were those really from that machine? Maybe you got them mixed up. Well you’re really itching to find contaminants, aren’t you? Of course you’ll find something if you look hard enough…
I don’t know how your business works, so I’m trying to project the managers I know onto it - am I so far off that I look like a manager?