As manager, I shut this conversation down via direct messages to each team member involved.
I remind them that they agreed during retro to live with the current set of decisions for exactly two weeks until next retro.
I don’t dictate much, but I do dictate that Slack isn’t an acceptable place for this kind of discussion, on my team.
The only related thing, that belongs in slack, on my team, is a link to the current accepted team standard - which will be open for review and changes again during next retro.
Alternately, if there’s no strandard for this yet then my team knows they’re encouraged to wing it until we discuss at next retro.
And yeah, I’ve had to open an issue to revisit a variable name after retro, lol.
My team are an opinionated bunch, and they’re often perfectionists.
Oof. This is a pet peeve of mine.
As manager, I shut this conversation down via direct messages to each team member involved.
I remind them that they agreed during retro to live with the current set of decisions for exactly two weeks until next retro.
I don’t dictate much, but I do dictate that Slack isn’t an acceptable place for this kind of discussion, on my team.
The only related thing, that belongs in slack, on my team, is a link to the current accepted team standard - which will be open for review and changes again during next retro.
Alternately, if there’s no strandard for this yet then my team knows they’re encouraged to wing it until we discuss at next retro.
And yeah, I’ve had to open an issue to revisit a variable name after retro, lol.
My team are an opinionated bunch, and they’re often perfectionists.