Comment by whstl
6 days ago
Off topic, but:
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.
6 days ago
Off topic, but:
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.
> It's interesting how everyone thinks they're "managers" in "agile" teams.
In scrum in particular, teams are supposed to be "self-organizing and self-managing". Perhaps that's why :-)
Well, yes, but "self-managing team" implies the team manages itself, not that one person picks up the slack. As the sibling poster said, this is a sign of a dysfunctional team.
> QAs trying to make decisions on behalf of the team
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.
Yep.
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.
That sounds like a dysfunctional team to me, to be honest.
It is indeed.