3 ms·
You guys use Jira? I think the person to blame is you. The friendly "public shaming" might also be counterproductive as it will discourage developers from doing
by briandear 14y ago
You guys use Jira? I think the person to blame is you. The friendly "public shaming" might also be counterproductive as it will discourage developers from doing anything to rock your very carefully managed boat. As far as production bug preventing, that's what a dedicated QA team is for. You said it yourself, "We anticipated the increase in production bugs when we moved away from having a dedicated QA team."
Putting the QA job on the developers is fair enough, I guess, however it would seem like you neglect using proper staging environments to ensure that broken code never sees production.
At my place, we have a staging environment for every team, then we have a company staging environment then stuff goes to production. The product manager and team devs test at the team level staging, then it moves to the company staging server where QA (or another developer) tests and then it goes to production.
We do Continuous Integration as well but we sure as hell don't have a "Person to Blame" -- we are a fucking team. The person to blame is the boss that lets shitty code make it onto production.
So I guess it would be easy to fill out the "Person to Blame" box.. just type your own name in every time.