Curious to know why my comment received a downvote / downvotes.
It's interesting how everyone thinks they're "managers" in "agile" teams.
Scrum Masters, Product Owners. I've even had Designers and QAs trying to make decisions on behalf of the team.
In scrum in particular, teams are supposed to be "self-organizing and self-managing". Perhaps that's why :-)
Oof, hits close.
Suggestion from a QA to implement some feature that is hugely difficult to implement? Business agrees so developers now need to make it happen.
The crazy one for me was QA not going through business and just marking new feature ideas as "bugs", and then informing business that "there are still lots of bugs to be fixed".
Cross-functional teams can be very toxic when there is no decision maker, and someone suddenly decides they don't want to really collaborate.
At best they're clerical support and training. In practice they can become officious ticket minders.
Hope you will experience better Agile Coaches through your career.
> You’re not the player, you’re the coach. Sometimes that means strategy and big-picture thinking. Sometimes it means shielding your team from dumb shit. Sometimes it means buying someone coffee and saying, “You’re not crazy. This is hard.”
Guess what good agile coaches or scrum masters are expected to do :-)
Agile coaches are also not able to shield the team from dumb shit. They don’t have the power to make priority calls on what the team is doing.
Also - I "deal" with underperformers because my team needs to deal with them. It all comes back to "what benefits the team".
I see that there are a lot of different varieties of agile coaches out there.