Avoiding the poor release blame game: The secret to alignment between developers and testers
Despite all your planning, the release made it to market with some significant bugs, and your company has had to run damage control. Now you’re getting questions about what went wrong, and before you know it, the blame game is in full force, with your developers and testers pointing fingers at one another.
So what happened? Whose fault was it really? And what can you do better next time? The truth of the matter is, at a time when the stakes for software development are higher than ever (and only continuing to rise), the blame game simply isn’t going to cut it. And if you’re operating in a true DevOps environment, the finger-pointing should never even happen in the first place.