3 ms·

You sound like you are siloing your developers by having individuals in charge of stories and also being the gatekeeper to production. You should be baking TEA

You sound like you are siloing your developers by having individuals in charge of stories and also being the gatekeeper to production. You should be baking TEAM review and TEAM approval into your development process especially if you want to start doing continuous deployment, and it sounds like you have jumped off a cliff without a parachute if you have eliminated dedicated QA... If your team decides they want to involve some public shame in their processes that's one thing but it's extremely dangerous for any manager to introduce themselves and it should never relate to production. The team owns the code.

nickler 14y ago
Innovating practices are always about iteration and learning. The tragic point here is that the learning is being done in a public forum. Team accountability is a best practice because trickle down hierarchies tend to do just that...trickle down. Depending on the size of the teams, share victory, share defeat should always be your mantra. I don't know the size of your organization, but if you need to track these issues with automated metrics, you may have a larger communications problem in your workflow. People are always better managers than spreadsheets. Use your metrics to support your initiatives, but use your people to come up with them.