Yeah I figured but wasn't sure. Also I don't have experience with supporting so many systems at once, PS4, Xbox One, and PC, so I'm not familiar with how often a bug is limited to one system vs multiple systems. Though they're on the same Frostbine engine so I'd think most bugs would be present on all systems. It was way too easy in Andromeda to hit a crash until like version 1.04 or so, they had to have known that was there and someone stupid didn't ever play the game or believe his teams.
My previous project spent five years in development and then management just HAD to release it. The developers said it wasn't ready, the test team said it wasn't ready, our immediate leadership said it wasn't ready and was overruled because higher leadership had to have a "win" in 2011. "win" being make the target date of sometime in 2011, and it was released in December. It was disappointing cause you knew the users were disappointed with it and it got a lot of flak, when we just needed like six more months to put some polish on it. Five years development, give me six months or even just three months more isn't asking too much. Especially with a dev team that's proven that they can get things permanently fixed fast (vs a team that breaks software as they fix it) and a test team that's proven that they can find both the obvious bugs and the hard-to-get-to bugs.
With Andromeda it's a little weird cause I read somewhere that EA was willing to let the release date slip, and Bioware said no and released anyway. That seems unlikely to me given the two companies' reputations. If true, it makes me question what was going on. I hope whoever made the call to release before it was ready lost their job, they lost a ton of sales due to those bugs getting in the wild, and Bioware patched that game to be working well within a few months.
no subject
Date: 2019-05-31 04:22 am (UTC)Yeah I figured but wasn't sure. Also I don't have experience with supporting so many systems at once, PS4, Xbox One, and PC, so I'm not familiar with how often a bug is limited to one system vs multiple systems. Though they're on the same Frostbine engine so I'd think most bugs would be present on all systems. It was way too easy in Andromeda to hit a crash until like version 1.04 or so, they had to have known that was there and someone stupid didn't ever play the game or believe his teams.
My previous project spent five years in development and then management just HAD to release it. The developers said it wasn't ready, the test team said it wasn't ready, our immediate leadership said it wasn't ready and was overruled because higher leadership had to have a "win" in 2011. "win" being make the target date of sometime in 2011, and it was released in December. It was disappointing cause you knew the users were disappointed with it and it got a lot of flak, when we just needed like six more months to put some polish on it. Five years development, give me six months or even just three months more isn't asking too much. Especially with a dev team that's proven that they can get things permanently fixed fast (vs a team that breaks software as they fix it) and a test team that's proven that they can find both the obvious bugs and the hard-to-get-to bugs.
With Andromeda it's a little weird cause I read somewhere that EA was willing to let the release date slip, and Bioware said no and released anyway. That seems unlikely to me given the two companies' reputations. If true, it makes me question what was going on. I hope whoever made the call to release before it was ready lost their job, they lost a ton of sales due to those bugs getting in the wild, and Bioware patched that game to be working well within a few months.